Versions Compared

Old Version 6

changes.mady.by.user Morgan Folsom (Deactivated)

Saved on

compared with

New Version 7

changes.mady.by.user Morgan Folsom (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Items

Explanation

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

Explanation

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

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")

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
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:
  1. TK-1: Open
  2. TK-2: Open → In Progress
  3. TK-3: Open → In Progress → Under Review
  4. 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
Explanation
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_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
membersOfRole("Project_Role
X
 Code Block
Support all Jira workflow statuses
JQL Example
Four example issues with their workflow transition history:
  1. TK-1: Open
  2. TK-2: Open → In Progress
  3. TK-3: Open → In Progress → Under Review
  4. 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. 
preStatusWas
 Code Block
preStatusWas("status_A")
Items
Explanation
membersOfRolepreStatusWas
Return all the issues where a specified user is in a specific project role.whose most recently previous status is status_A
JQL Context
creator 
issue in/not in
  • assignee in/not in
  • reporter in/not in
  • voter in/not in
  • watcher in/not in
    • Project_Rolestatus_X
    Support all Jira project rolesworkflow statuses
    JQL Exampleassignee in membersOfRole("Administrators")
    Four example issues with their workflow transition history:
    1. TK-1: Open
    2. TK-2: Open → In Progress
    3. TK-3: Open → In Progress → Under Review
    4. 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. 
    timeWithin
    timeBeyond
     Code Block
    timeWithin("Time_Frame", "Status_A", "Status_B", "Status_C")
timeBeyond("Time_Frame", "Status_A", "Status_B", "Status_C")
    ...