Panel | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server. If you are using JSU on Jira Cloud, you can find the documentation here. |
Coming soon. Check out this page again to get some ideas what amazing things JQL in JSU will allow you to do.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.
Bellow you find several examples which demonstrate how flexible and powerful JQL can be used with JSU.
See also JQL Reference which gives you all the details how to use JQL with JSU.
JQL Conditions
Code Block | ||
---|---|---|
| ||
Sprint in openSprints() AND key = {issue.key} |
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.
Code Block | ||
---|---|---|
| ||
parent = {issue.parent} AND status in (Resolved, Closed) AND 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 .
Code Block | ||
---|---|---|
| ||
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: