Date: Thu, 28 Mar 2024 13:13:16 +0000 (UTC) Message-ID: <2139600360.9.1711631596118@ea0904977630> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8_1387881644.1711631596118" ------=_Part_8_1387881644.1711631596118 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This is the documentation of JSU for Jira Cloud. If you are using JSU on= Jira Server or on Jira Data Center, see our Server/Data Center documentation.
The 'JQL Query' compares the number of issues returned from the JQL quer= y against predefined conditions like:
Find at least one issue
Must not find any issue
Compare with a particular number
Some of the simple things you would do with the JQL Precondition, you mi= ght also achieve with the Value Field = Precondition. Choose the approach that is the simplest for you and your= Jira admin colleagues.
Check out our tips be= low.
You must write the 'JQL Query' and choose one option about the number of= issues found. For example:
With this precondition, the post function will be only executed for =
bugs.
You won=E2=80=99t will need a separate workflow (and spec=
ial workflow scheme configuration), when you only want one post function to=
perform differently for a particular issue type.
For information on how to configure workflows in Jira, see the Jira documentation<= /a>.
See the JQL Use Cases for several exa= mples.
Atlassian's Jira Query Language (JQL) allows you to perform advanced search= ing in Jira's search dialog. JSU extends JQL with additional place= holders, which are replaced with the values of the current issue in transit= ion.
For example, if you configure the following JQL query in a configuration= screen of JSU:
parent =3D {issue.Parent} AND component !=3D {issue.Component/s} O=
R component is EMPTY
it will be converted by JSU before the search is executed similar to the= following:
parent =3D 'ABC-123' AND component !=3D 'Documentation' OR compone=
nt is EMPTY
This will search all sibling issues (same parent), which do not have= the same component as the current issue (in this example Documentation).= em>
Any text in curly brackets, which follows the pattern {issu= e.FIELD NAME} is replaced with the value of that field on the curr= ent issue (the issue in transition). See below for further details on which= names you can use for the different field types. Depending on your use cas= e, you might not use any {issue.FIELD NAME} placeholder at all.
Logical operators, functions, and operators are the same as the JQL in J= ira. It is important to use the correct JQL syntax. The easiest way to writ= e a JQL query for JSU is to prepare it first in Jira's standard search inte= rface (use 'advanced search') with some sample value, then copy it to JSU c= onfiguration and replace some of your sample values with {issue.FIELD = NAME} as required.
See JQL Use Cases for more examples.
Add the following to your JQL query:
... AND key =3D {issue.key}
Add the following to your JQL query:
... AND key =3D {issue.parent}
Add the following to your JQL query:
... AND parent =3D {issue.parent} AND key !=3D {issue.key}
<=
/p>
sub-tasks with the same parent: parent =3D {issue.parent}
excluding the current issue: key !=3D {issue.key}
See JQL Use Cases for more examples.
Think carefully about what values might be used as replacements for the&= nbsp;{issue.FIELD NAME} placeholders. Or, what happens if an issue has no v= alue in a specified field. There could be some variation in the data of you= r issues.
If you are not careful, the result of a JQL query might unexpectedly con= tain hundreds of issues. Or, the JQL query might fail because the syntax ha= s become invalid after the placeholders have been replaced.
You can set a limit for the maximum number of issues you expect from you= r JQL query. If the result of the JQL query returns more issues, JSU will n= ot process anything. JSU essentially stops the process before things get ou= t of control.
This way, you can prevent JSU from accidentally processing hundreds of i= ssues. By default, this limit is 50 issues, and the maximum limit is 1,000.=
Be aware of potential 'JQL injection'. JSU does not check any value that= it retrieves from the current issue. A malicious user might craft the valu= e of a field (for example the value of a text field) so that after the repl= acement it adds additional criteria to your JQL query.
We recommend that you do not use any text fields as placeholders, or any= other field for which a user can freely change the text. Only use fields t= hat can contain one/several clearly defined values.
Field names in your JQL should be the same as in the Advanced Search. We sugges= t using the issue navigator's auto-complete feature to get the correct fiel= d names. In Jira, go to Issues > Search for iss= ues, and switch to Advanced search.
System field names should be the same as those used in JQL. For example:=
reporter
assignee
issuetype
priority
Custom field names should be the same as those used in JQL. For example:=
Approver or cf[10010]
Hosting Server or cf[12910]
Date to Join or cf[11000]
If you have several custom fields with the same name, you can only use t= he cf[12345] notation to refer to one of them.
The replaceable value from the issue must be between curly brackets:
{issue.FIELD NAME}
Use the place holders from the following list:
{issue.Affects Version/s}
{issue.Assignee}
{issue.Affects Version/s}
{issue.Assignee}
{issue.Component/s}
{issue.Created}
{issue.Creator}
{issue.Customer Request Type}
{issue.Description}
{isseu.Due Date}
{issue.Environment}
{issue.Epic Color}
{issue.Epic Name}
{issue.Epic Status}
{issue.Epic Link}
{issue.Fix Version/s}
{issue.Issue Key}
{issue.Issue Type}
{issue.Labels}
{issue.Original story points}
{issue.Parent}
{issue.Priority}
{issue.Project}
{issue.Rank}
{issue.Reporter}
{issue.Request participants}
{issue.Resolution}
{issue.Resolved}
{issue.Security Level}
{issue.Sprint}
{issue.Status}
{issue.Summary}
{issue.Time to resolution}
{issue.Updated}
{issue.Voters}
{issue.Watchers}
{issue.Work Ratio}
Alternatively, you might use the technical field ID of a system field, o= r how JQL refers to it. For example, all three variants below refer to the = same field:
{issue.Affects Version/s}
Label in the English Jira user interface.
{issue.versions}
Technical field ID. See also the constant values reference from Atlassian.
{issue.affectedVersion}
JQL's method to refer to that field.
You can use either the name of a custom field or its ID. For example:
{issue.My Text Field}
{issue.customfield_12345}
However, the cf[12345] no= tation is not supported between curly brackets.
If you have several custom fields with the same name, you must= u> use the custom field ID.
JSU supports many different field types; system fields, as well as custo= m fields.
You should be aware, however, that not all field types or all combinatio= ns are supported. We have tried to cover the most important field types but= we are continuously adding more and improving how different field types ar= e supported. We recommend you test JSU with fields to see if it is com= patible with your system. Our evaluation license provides you with a 30-day= free trial.