| Panel | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
This is the documentation of JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation. |
...
JSU includes a JQL Condition
...
and JQL Precondition
...
. We've also integrated JQL in many
...
of our workflow post functions, allowing Jira administrators to set wider parameters that
...
can be fully customized.
...
Below, you
...
will find
...
a few examples
...
of how flexible and powerful JQL can be when used with JSU.
Refer to the JQL Reference for details on how to use JQL with JSU.
JQL Conditions
| Code Block | ||
|---|---|---|
| ||
Sprint in openSprints() AND key = {issue.key} |
...
| Code Block | ||
|---|---|---|
| ||
parent = {issue.parent} AND key != {issue.key} AND status in (Resolved, Closed) |
With
With parent
...
= {issue.parent}
...
we we find all siblings of the current sub-task. However we want to exclude the current sub-tasks, so we addadd key != {issue.key}.
JQL Precondition
With Workflow Preconditionsworkflow preconditions for post functions, you can limit in which cases a JSU post function will be is performed. See also the documentation Workflow Preconditions .
| Code Block | ||
|---|---|---|
| ||
parent = {issue.key} AND issuetype = "Testing Sub-Task" |
With the first part
With parent
...
=
...
{issue.key}
...
we retrieve all sub-tasks of the current issue in transition. We then further refine this so to a particular sub-task type with 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 JSU post functions of JSU, you can specify a JQL query to retrieve the issues , which that 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 The issue is hidden in a project , which normal users cannot see (only Jira admins can view this), that is viewable only to Jira admins 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 the open state, change it to in progress In Progress status.
