This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation.
To make work faster and more efficient for your teams with JSU, we built a JQL Condition, JQL Precondition and integrated JQL in many Workflow Post Functions, allowing advanced administrators to set wider parameters that may now be fully customized.
Below, you can find several examples which demonstrate how flexible and powerful JQL can be used with JSU.
Refer to the JQL Reference for details on how to use JQL with JSU.
JQL Conditions
Sprint in openSprints() AND key = {issue.key}
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.
parent = {issue.parent} AND key != {issue.key} AND status in (Resolved, Closed)
With
parent = {issue.parent}
we find all siblings of the current sub-task. However we want to exclude the current sub-tasks, so we add
key != {issue.key}
JQL Precondition
With Workflow Preconditions for post functions, you can limit in which cases a JSU post function will be performed. See also the documentation Workflow Preconditions .
parent = {issue.key} AND issuetype = "Testing Sub-Task"
With the first part
parent = {issue.key}
we retrieve all sub-tasks of the current issue in transition.
We then further refine this so a particular sub-task type
AND issuetype = "Testing Sub-Task"
For example, you might create the "Testing Sub-Task" with the Create a Linked Issue post function, but only if it does not yet exist:
JQL in Post Functions
In several post functions of JSU, you can specify a JQL query to retrieve the issues, which will be modified by the post function. See also Related Issues.
Update Description of particular sibling Issues
Transition: Resolve in "Testing Sub-Task" Workflow
Copy Fields from Template Issue
Let's say we have an issue XY-23, which we are using as a 'template'. It is hidden in a project, which normal users cannot see (only Jira admins can view this), and has pre-configured values on several fields.
Change Status of Critical Issues in Epic
If there are critical and blocker issues in an epic that are still in open state, change it to in progress status.