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. |
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 expression mode as a parsing mode in every context.
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 | ||||||
---|---|---|---|---|---|---|
|
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} |
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."} |
type | tip |
---|