...
| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, you can find the documentation here. | ||||||||||
| Excerpt | ||||||||||
| Section | Column | | width | 67%
Description
The ‘JQL'
...
condition compares the number of issues returned from the JQL query against predefined conditions
...
such as:
Must find at least one issue
Must not find any issue
Compare with a particular number
...
| width | 33% |
|---|
...
| bgColor | #f5f5f5 |
|---|---|
| titleColor | #222222 |
| borderWidth | 0 |
| titleBGColor | #f5f5f5 |
...
Configuration
...
Write your required JQL expression and choose one option
...
for the number of issues found.
...
For information on how to configure a check for a workflow transition in JIRA, see the JIRA documentation.
Examples
See the JQL Use Cases for several examples.
How to write JQL Query
...
Supported Field Types
...
For example, Number of issues must > 2.
...
For more information on how conditions work in Jira, see Atlassian’s Advanced Workflow Configuration documentation.
Examples
Is the Issue in the current sprint?
| Code Block |
|---|
Sprint in openSprints() AND key = {issue.key} |
In the IT department only the approver can perform the transition
| Code Block |
|---|
approver = currentUser() OR component != "IT department" |
Or in other words: The condition is valid if the current user is the user in the Approver field OR anything not belonging to the IT department.
All other siblings must have status
| Code Block |
|---|
parent = {issue.parent} AND key != {issue.key} AND status in (Resolved, Closed) |
With parent = {issue.parent} we find all siblings of the current subtask. However, we want to exclude the current subtasks, so we add key != {issue.key}.