The Jira expression parsing mode, unlike the General mode and the Logical mode, is based on a domain-specific language designed and provided by Atlassian, not JWT. It can be used to evaluate custom Jira expressions. Jira expressions follow JavaScript syntax and can be thought as a JavaScript dialect. See the introduction section from the official documentation here. JWT for Jira Cloud only uses the features provided by Atlassian which cannot be modified by JWT for Jira Cloud! |
Jira expressions can be used whenever the Jira expression mode is available. Currently this parsing mode is the only available parsing mode in the:
Additionally the Jira expression mode is available when configuring the conditional execution parameter in workflow Post functions.
In order to illustrate with a simple example, the following Jira expression would ensure that an issue is currently assigned to a Jira user.
issue.assignee != null |
While they might look quite same, it is important to know that Jira expressions and the JWT expressions have nothing in common in the background.
The equivalent to our former example, using JWT expression field codes would read:
%{issue.assignee} != null |
Apparently, one of the main differences to Jira expressions is the way the field codes are referenced.
Rule of thumb! If you spot |
Right now, Jira expressions are the only officially supported way to formulate custom conditions or validators in Jira Cloud.
Being the "brain" of Jira Workflow Toolbox for Server and Data Center, its JWT expression editor and the underlying expression parser, have evolved from a small set of handy functions to a comprehensive list and a fundamental part of this app over the years.
Therefore it was only obvious to make this core functionality available for Jira Cloud as well.
Familiarize yourself with the Jira expression mode. Once you have a general overview make sure to check out the various use cases we have prepared for you.
To deep-dive into Jira expressions we suggest reading up on the additional information we have prepared for you:
Jira expressions follow certain constraints with regard to the evaluation of those expressions (see the official documentation).
While the limits should be high enough not to interfere with any intended usage, it's important to realize that they do exist:
Expressions can execute a maximum of 10 so-called "expensive" operations, i.e. those that load additional data, such as entity properties, comments, or custom fields, e.g.
Given an expression to check whether every sub-task has at least one comment containing an issue key, will fail if this issue has more than 10 sub-tasks.
issue.subtasks.every(sub => sub.comments.some(com => com.body.plainText.match('([A-Z][A-Z0-9]+)-\d+') != null)) |
The best way would be to start with the official documentation: