Skip to end of banner
Go to start of banner

JQL Use Cases

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

JSU for Jira Server

This is the documentation of JSU for Jira Server. If you are using JSU on Jira Cloud, you can find the documentation here.


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

Is Issue in current sprint?
Sprint in openSprints() AND key = {issue.key}


In the IT department only the approver can perform the transition
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 sibilings must have status
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 .


Check if Testing Sub-Task already exists
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:

  • No labels