Page Comparison

...

Code Block
datesBeyond("Time_Frame", "Date_Field_Name_1", "Date_Field_Name_2")

Items	ExplanationDescription
datesBeyond	Return all the issues whose time difference between "Date_Field_Name_1" and "Date_Field_Name_2" is greater than or equal to "Time_Frame"
JQL Context	issue in/not in
Time_Frame	Time frame can be w, d, h, m and separated by spaces. w: week d: day h: hour m: minute Example: "1w 2d 3h 4m"
Date_Field_Name_1&2	Supports "due": issue due date and any other Date Picker custom fields
JQL Example	*issue in* dateTimeWithindatesBeyond("3d 8h1w", "createdEstimated Start", "updatedEstimated End")

datesWithin

Code Block
datesWithin("Time_Frame", "Date_Field_Name_1", "Date_Field_Name_2")

Items	ExplanationDescription
datesWithin	Return all the issues whose time difference between "Date_Field_Name_1" and "Date_Field_Name_2" is less than or equal to "Time_Frame"
JQL Context	issue in/not in
Time_Frame	Time frame can be w, d, h, m and separated by spaces. w: week d: day h: hour m: minute Example: "1w 2d 3h 4m"
Date_Field_Name_1&2	Supports "due": issue due date and any other Date Picker custom fields
JQL Example	*issue in* dateTimeWithindatesBeyond("3d 8h1d", "createdEstimated Start", "updatedEstimated End")

dateTimeBeyond

Code Block
dateTimeBeyond("Time_Frame", "DateTime_Field_Name_1", "DateTime_Field_Name_2")

Items	ExplanationDescription
dateTimeBeyond	Return all the issues whose time difference between "DateTime_Field_Name_1" and "DateTime_Field_Name_2" is greater than or equal to "Time_Frame"
JQL Context	issue in/not in
Time_Frame	Time frame can be w, d, h, m and separated by spaces. w: week d: day h: hour m: minute Example: "1w 2d 3h 4m"
DateTime_Field_Name_1&2	Supports "created": issue created datetime "updated": issue updated datetime "resolved": issue resolved datetime and any other DateTime Picker custom fields
JQL Example	*issue in* dateTimeWithindateTimeBeyond("3d 8h1w", "created", "updated")

dateTimeWithin

Code Block
dateTimeWithin("Time_Frame", "DateTime_Field_Name_1", "DateTime_Field_Name_2")

Items	ExplanationDescription
dateTimeWithin	Return all the issues whose time difference between "DateTime_Field_Name_1" and "DateTime_Field_Name_2" is less than or equal to "Time_Frame"
JQL Context	issue in/not in
Time_Frame	Time frame can be w, d, h, m and separated by spaces. w: week d: day h: hour m: minute Example: "1w 2d 3h 4m"
DateTime_Field_Name_1&2	Supports "created": issue created datetime "updated": issue updated datetime "resolved": issue resolved datetime and any other DateTime Picker custom fields
JQL Example	*issue in dateTimeWithin("3d 8h", "created", "updated")*

epicTree

Code Block
epicTree("Epic_Issue_Key_1", "Epic_Issue_Key_2", ..., "Epic_Issue_Key_N")

Items	ExplanationDescription
epicTree	Return all epics with those given epic issue keys, all issues linked to those epics and all sub-tasks of those issues linked to the epics at least 1 epic issue key and up to unlimited epic issue keys in JQL statement
JQL Context	issue in/not in
Arg: Epic_Issue_Key_N	Support all Jira Epic issue keys
JQL Example	*issue in epicTree("Data Storage", "System Config", "Security")*

FieldValueMatches

Code Block
FieldValueMatches("Field_Name", "Regex_Pattern")

Items	ExplanationDescription
JQL: FieldValueMatches	Return all the issues whose specific field value matches the "Regex_Pattern"
JQL Context	issue in, issue not in
Field_Name	Support any text-based fields. i.e. "Summary", "Description", ' text field (single line)', etc.
Regex_Pattern	Support any regular expression patterns
JQL Example	*issue in FieldValueMatches("summary", "[hm]at")* will return all the issues whose summary contains hat or mat

issueLinkType

Code Block
preStatusWasissueLinkType("statusIssue_Link_A") preStatusContainsAll("status_A, status_B, status_C,..., status_X") preStatusContainsEitherType")

Items	Description
issueLinkType	Return all the issues that have a certain type of issue link
JQL Context	issue in/not in
Issue_Link_Type	Support all issue link types. i.e. "blocks", "is blocked by", "duplicates", "relates to" etc.
JQL Example	'*issue in issueLinkType("clones")*' will return all the issues whose issue link type is "clones"

membersOfRole

Code Block
membersOfRole("Project_Role")

Items	Description
membersOfRole	Return all the issues where a specified user is in a specific project role.
JQL Context	creator in/not in assignee in/not in reporter in/not in voter in/not in watcher in/not in
Project_Role	Support all Jira project roles
JQL Example	*assignee in membersOfRole("Administrators")*

preStatusContainsAll

Code Block
preStatusContainsAll("status_A, status_B, status_C,..., status_X")

preStatusWas

preStatusContainsAll

...

Return all the issues whose most recently previous status is status_A

Items	Explanation	preStatusWas	Description
preStatusContainsAll	Return all the issues whose historical statuses (excluding current status) include status_A and status_B and status_C and ... and status_X	preStatusContainsEither	Return all the issues whose most recently previous status is status_A or status_B or status_C or ... or status_X
JQL Context	issue in/not in
status_X	Support all Jira workflow statuses
JQL Example	Four example issues with their workflow transition history: TK-1: Open TK-2: Open → In Progress TK-3: Open → In Progress → Under Review TK-4: Open → In Progress → Under Review → Rejected → In Progress 'issue in preStatusWas("Rejected")' will return TK-4 '*issue in preStatusContainsAll("Open, In Progress")' will return TK-3 and TK-4'issue in preStatusContainsEither("Open, In Progress")*' will return TK-2 and TK-3

Note
Automating high volume queries may result in performance degradation of your Jira instance. It is recommend that the StatusWas JQL statements are used ad-hoc, and not for automation or high-volume workflow actions.

...

preStatusContainsEither

Code Block
issueLinkTypepreStatusContainsEither("Issue_Link_Typestatus_A, status_B, status_C,..., status_X")

Items	ExplanationDescription
issueLinkTypepreStatusContainsEither	Return all the issues that have a certain type of issue linkwhose most recently previous status is status_A or status_B or status_C or ... or status_X
JQL Context	issue in/not in
Issuestatus_Link_TypeX	Support all issue link types. i.e. "blocks", "is blocked by", "duplicates", "relates to" etc.
JQL Example	'issue in issueLinkType("clones")' will return all the issues whose issue link type is "clones"

membersOfRole

Code Block
membersOfRole("Project_Role")

Items	Explanation
membersOfRole	Return all the issues where a specified user is in a specific project role.
JQL Context	creator in/not in assignee in/not in reporter in/not in voter in/not in watcher in/not in
Project_Role	Support all Jira project roles
JQL Example	assignee in membersOfRole("Administrators")

timeWithin

timeBeyond

timeWithin("Time_Frame", "Status_A", "Status_B", "Status_C")

Jira workflow statuses

Code Block

JQL Example

Four example issues with their workflow transition history:

TK-1: Open
TK-2: Open → In Progress
TK-3: Open → In Progress → Under Review
TK-4: Open → In Progress → Under Review → Rejected → In Progress

'issue in preStatusContainsEither("Open, In Progress")' will return TK-2 and TK-3

Note
Automating high volume queries may result in performance degradation of your Jira instance. It is recommend that the StatusWas JQL statements are used ad-hoc, and not for automation or high-volume workflow actions.

preStatusWas

Code Block
preStatusWas("status_A")

Items	Description
preStatusWas	Return all the issues whose most recently previous status is status_A
JQL Context	issue in/not in
status_X	Support all Jira workflow statuses
JQL Example	Four example issues with their workflow transition history: TK-1: Open TK-2: Open → In Progress TK-3: Open → In Progress → Under Review TK-4: Open → In Progress → Under Review → Rejected → In Progress 'issue in preStatusWas("Rejected")' will return TK-4

Note
Automating high volume queries may result in performance degradation of your Jira instance. It is recommend that the StatusWas JQL statements are used ad-hoc, and not for automation or high-volume workflow actions.

timeBeyond

Code Block
timeBeyond("Time_Frame", "Status_A", "Status_B", "Status_C")

Items	ExplanationDescription
timeWithintimeBeyond	Return all the issues whose sum of time spent in certain statuses is less greater than or equal to "Time_Frame" At least 1 status and up to 3 statuses in the JQL statement If Status_A isn't an issue's historical status, the time spent for that issue in Status_A will be 0 It won't return the issue if all the given statuses aren't that issue's historical statuses
JQL Context	issue in/not in
Time_Frame	Time frame can be w, d, h, m, s and separated by spaces. w: week d: day h: hour m: minute s: second Example: "1w 2d 3h 4m 5s"
status_A&B&C	Support all Jira workflow statuses
JQL Example	*issue in timeBeyond("1d 2h 30s", "Open")*

timeWithin

Code Block
timeWithin("Time_Frame", "Status_A", "Status_B", "Status_C")

Items	Description
timeWithin	Return all the issues whose sum of time spent in certain statuses is greater less than or equal to "Time_Frame" At least 1 status and up to 3 statuses in the JQL statement If Status_A isn't an issue's historical status, the time spent for that issue in Status_A will be 0 It won't return the issue if all the given statuses aren't that issue's historical statuses
JQL Context	issue in/not in
Time_Frame	Time frame can be w, d, h, m, s and separated by spaces. w: week d: day h: hour m: minute s: second Example: "1w 2d 3h 4m 5s"
status_A&B&C	Support all Jira workflow statuses
JQL Example	*issue in timeWithin("1h", "In Progress*")issue in timeBeyond("1d 2h 30s", "Open")

Versions Compared

Old Version 6

New Version Current

Key

datesWithin

dateTimeBeyond

dateTimeWithin

epicTree

FieldValueMatches

issueLinkType

membersOfRole

preStatusContainsAll

preStatusWas

preStatusContainsAll

preStatusContainsEither

membersOfRole

timeWithin

timeBeyond

preStatusWas

timeBeyond

timeWithin