The JQL parsing mode, just like the Issue list mode, lets you define a target selection of issues. It is being used in Post functions and Automation actions, that allow you to create or updated multiple issues. Therefore it is being used in:
The output has to be a valid issue list as defined in the Data types section. The input must be a valid JQL query where you can also use field codes.
Additionally JWT expression parser functions can be used.
Example expressions
| Parser expression | Description |
|---|---|
type = Bug and project = %{issue.project.key}
| This example returns a list of all Bugs in the same project as the current issue. |
issuetype = "%{issue.issueType}" AND project = "%{issue.project.name}"
| This example returns a list of all issues in the same project and with the same issue type as the current issue. |
If field values are expected to have white spaces or JQL reserved words or characters, you should enclosed the field code in quotes (double or simple). Example: summary ~ "%{system.currentUser.displayName}" will return issues with the current user's full name in the summary. As the full name can contain spaces, the field code was enclosed in double quotes.
Anyways, there is an exception to this general rule: when the field contains a comma-separated list of values, and you want to use it with the JQL operator IN. In those cases the field code should not be enclosed in double quotes, since you want the content of the field to be processed as a list of values, not as a single text value.
Example:
You have temporarily stored the issue keys of all linked issues in a Temporary text field. The field now contains a comma-separated list of the following issue keys: "CRM-1, HR-2, HR-3".
| JQL query | JQL query after field code is replaced with values | Description |
|---|---|---|
key in ("%{issue.temporaryText1}")
| key in ("CRM-1, HR-2, HR-3")
| This query will not return any results as it is syntactically incorrect.  |
key in (%{issue.temporaryText1})
| key in (CRM-1, HR-2, HR-3) | This query will return all issues stored in the temporary field.  |
Disabling JQL Syntax Pre-Checking
When we enter our JQL query, a syntax pre-checking is carried out in order to verify that it's correctly written. But when we insert field codes in our JQL query, the definitive form of the query that will be executed is unknown, since it depends on the actual values of the fields in runtime. In these cases the syntax pre-checking is done with speculative values given to the fields, and it might happen that fake syntax errors are reported.
In order to inhibit the JQL syntax pre-checking you should enter
//at the beginning of the line ...Read field from issues returned by JQL query or issue list
Make sure to read all about working with Lists as they come with many extremely useful JWT expression parser functions.
List functions can also be used in the Advanced text mode. The difference is, that the output will be a flat text instead of an issue list.
The main advantage over the advanced text mode is, that you can use the returned elements of the issue list as Seeds.
Error rendering macro 'excerpt-include'
No link could be created for 'List management operators'.
