Introduction
Time to be creative!
A huge number of potential use cases can be addressed by using Jira expressions which is currently a Cloud Only feature provided by Atlassian. Jira expressions can be a powerful tool but they come with limitations.
To master Jira expressions we strongly recommend reading the information we condensed on this single page. Especially when it comes to the difference between Jira expressions the JWT for Jira Cloud parser expressions.
The configuration
To configure this condition you only need to specify a single input parameter - the Jira expression.
Additionally you can test your expression by selecting a dedicated issue to test against.
| Parameter | Description |
|---|---|
| Jira expression * | Enter plain text and optionally use field codes, e.g. issue.summary, to insert field values. The result of the Jira expression shall return true or false.
|
| Evaluation test | Select an issue for the context of the evaluation of the given Jira expression. After clicking the "Evaluate" button the result of the evaluation is shown in a message box below. If the syntax of the Jira expression is wrong or the evaluation with the given context issue returns an error, an error box with the respective error is displayed in an error box below. |
Remember, that the usage of virtual fields is different when being used in Jira expressions (no need to add brackets {}).Test your expression
It is highly recommended to test your Jira expression before publishing the workflow.
To test an expression simply select an existing issue ad click on .
As a result you might encounter three different outputs:
| Output | Explanation |
|---|---|
Getting started
Get started by trying out the example configurations provided out of the box.
The following example configurations are currently available:
