Page History
Page properties | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
Tech review |
| |||||||
Style guide |
|
Status | ||
---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
Status | ||||
---|---|---|---|---|
|
UI Text Box | ||||
---|---|---|---|---|
| ||||
A parsing mode determines how the JWT for Jira Cloud expression parser interprets an expression. The available parsing modes depend on the context in which you use the expression. This means for example, that only the Logical mode is available if you configure a conditionalexecution in a workflow post function. |
Available parsing modes
Page properties report | ||||||
---|---|---|---|---|---|---|
|
The available modes depend on the context!
Please be aware that besides the JWT for Jira Cloud expression parser you can choose to use Jira expressions as a parsing mode in every context.
title | Parsing modes overview |
---|
Field codes
Parser Functions
Text with the following restriction: the following combination of characters has to be escaped by "\" when not being used as a field code field codes: %{ → \%\{
Status | ||||
---|---|---|---|---|
|
The general parsing mode allows you to write functions to read and manipulate data from any issue in Jira. Field codes are supported as well as clear text.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
This is the issue summary: %{issue.summary} |
Comments
UI Text Box | ||
---|---|---|
| ||
Comments can be added to all parsing modes. They serve as internal documentation for the expression and are ignored when evaluating the expression. |
Parsing mode | Syntax | Examples | ||||
---|---|---|---|---|---|---|
General | Only available when using expressions enclosed by %{}. Starts with # and ends either at the end of the line or if the expression is closed by } |
| ||||
Logical | It starts with # and ends at the end of the line |
| ||||
Jira expression | It starts with // and ends with the end of the line |
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
%{"This is the issue summary: " + %{issue.summary} + " and the assignee mail is: " + userEmail(%{issue.assignee.email}) |
Please be aware that the general mode always return a text. In case this is used as an input for a number (especially date) parameter or as an issue list, JWT for Jira Cloud cares internally for a correct conversion.
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
%{{trigger.issue.resolutionDate} - {trigger.issue.createdDate}} |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
%{subtasks()} |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
%{count(subtasks())} |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
This is the issue summary: "%{issue.summary}" and that of the parent "%{parent.summary}". Issue %{parent.key} has %{count(subtasks(%{parent.key}))} sub-tasks. |
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
%{"This is the issue summary: \"" + %{issue.summary} + "\" and that of the parent \"" + %{parent.summary} +"\". Issue " + %{parent.key} + " has "+count(subtasks(%{parent.key})) +" sub-tasks."} |
UI Text Box | ||
---|---|---|
| ||
The following combination of characters has to be escaped by "\" when not being used as a field code or function delimiter: %{ → \%\{ |
Field codes
Parser Functions
Status | ||||
---|---|---|---|---|
|
The logical parsing mode shall return true or false. Field codes, functions and quoted texts are supported as well as comparison operators and logical connection. For details, please have a look at Logical expressions
Code Block | ||||||
---|---|---|---|---|---|---|
| ||||||
%{issue.assignee} = %{issue.reporter} |
An example which uses functions and logical connectors
language | bash |
---|---|
title | Check if the issue is an Epic and has at least one subtasks |
linenumbers | true |