The basic text parsing mode allows you to write free text and insert field codes. The text does not have to be enclosed in "" like in the Advanced text mode.
All field codes will be replaced at runtime with the corresponding field value of the issue currently being processed.
Besides supporting field code replacement, the usage of parser functions like in the Advanced text mode is also available when placed between two curly braces starting with a percent sign, e.g. %{{subtasks()}}.
Example expressions
| Parser expression | Description |
|---|---|
This is the issue summary: %{issue.summary}
| This example might return: This is the issue summary: JWT 3.0 wording update |
Next status update needed by: %{issue.dueDate}
| This example might return: Next status update needed by: 30.07.2020 |
This issue has been re-assigned to %{issue.assignee}.
| This example might return: This issue has been re-assigned to a.grant. |
The number of sub-tasks is: %{{count(subtasks())}}
| This example returns the number of sub-tasks of the current issue, e.g. The number of sub-tasks is: 2 |
Tomorrow is %{{dateToString({system.currentDateTime} + 1 * {DAY}, LOCAL, SERVER_LANG)}}.
| This example returns tomorrow's date, e.g. Tomorrow is 24/May/20. |
While it's %{system.currentDateTime} now, it'll be %{{dateTimeToString({system.currentDateTime} + 1 * {DAY}, LOCAL, SERVER_LANG)}} in 24 hours.
| This examples illustrates the parallel usage of field codes (the current date and time) and parser functions (tomorrow's date and time), e.g. While it's 29/Nov/20 8:33 AM now, it'll be 30/Nov/20 8:33 AM in 24 hours. |
%{{capitalizeWordsFully(trim(%{issue.summary}))}}
| This returns a well-formatted summary by removing leading and trailing blanks as well as capitalizing each word (only the word's first letter is upper case and the remaining letters are lower case). |
If you still have questions, feel free to refer to our support team.
