Examples of Issue List expressions
This page presents a collection of issue selection expressions valid for JIRA Workflows Toolbox expressions parser. All this expressions return an Issue List type.
Epic Link is also a kind of issue link. It's represented by the following 2 issue link types
has Epic and
is Epic of, which are used like this:
- Epic issue
is Epic ofStory issue
- Story issue
has EpicEpic issue
|Issues linked to current issue through any issue link type, including Epic Link.||-|
|Issues linked to current one through is blocked by issue link type, i.e., current issue ||-|
|Issues linked to current issue through is blocked by, is duplicated by and blocks issue link types.||-|
|An issue list containing only the Epic of current issue.||The returned list will contain 0 or 1 element, depending on whether current issue has an epic issue.|
|Issues current issue is epic of.||-|
|Issues with the same epic as current issue.||Current issue is also included in the issue list returned.|
|Issues with the same epic as current issue, excluding current issue.||Current issue is not included in the issue list returned.|
|All the issues linked to current issue, except those linked through has Epic or is Epic of issue link types.||-|
|Issues that have been linked to current issue in transition screen.||-|
|Issues that have been linked to current issue in transition screen through blocks issue link type.||-|
|Issues which are directly or indirectly blocking current issue.||Indirect blocking occurs when an issue is blocking an issue that is directly blocking current issue. Example: ISSUE-0 |
|Issues linked to parent of current issue.||This expression only makes sense when current issue is a sub-task.|
|Issues blocked by parent of current issue.||This expression only makes sense when current issue is a sub-task.|
All subtasks have one and only one parent issue, and may have sibling subtasks, i.e., those issues sharing the same parent issue. Relation between Epic and Stories is not implemented through parent-child relation, but using issue links "is Epic of" and "has Epic", as explained above.
|Subtasks of current issue.||-|
|Subtasks of current sub-task's parent, including current sub-task.|
|Subtasks of all the issues linked to current issue using is blocked by issue link type.||-|
|Subtasks of current sub-task's parent, excluding current sub-task.||-|
Filtering Issues Lists
Once we have an issue list, we can filter it by issue type, status, status category, resolution, project, field values, cardinality (i,e., number of appearances in the list), or using a boolean predicate, which is the most powerful method of issue filtering.
|Issue types "Improvement" and "New Feature" linked to current issue.||-|
|Issue types "Improvement" and "New Feature" linked to current issue, which are in statuses "Open" or "In Progress".||In this example we are applying 2 filters, one after another, using function composition.|
|Subtasks with resolutions "Cannot Reproduce" or "Incomplete".||-|
|Issue that belong to projects with keys "CRM" or "HR".||-|
Linked issues in statuses different from "Closed" and "Resolved".
Since version 2.2.42 case ignoring operator
|Linked issues with the same status as current issue, which also contain the word "important" in their summary.|
We use function
Obtaining Issue Lists using JQL Queries
Issue lists with big numbers of issues are temporarily stored in server's memory. For this reason it's recommended not to build up big lists in your expressions, like retrieving all the issues in a project using function
getIssuesFromProjects("PKEY"). Instead, it's better to use function
issuesFromJQL("JQL_Query") using a JQL_Query that returns a small number of issues to work with.
Parameter JQL_Query is a string that represents a valid JQL Query. We typically build dynamic JQL queries inserting field values that we concatenate to string literals using
|Issues with types "Bug" and "Incident" in the same project of current issue.|
Issues with same issue type and project as current issue.
|Note that we have written issue type in simple quotation marks. The reason is that issue type name may contain spaces.|