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's expressions we strongly recommend reading the information we condensed on this single page. Especially when it comes to the difference between Jira expressions and JWT expression.
Configuration
Click on 
and 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 is displayed below.
Use cases and examples
| Use case | Complexity | Type | Function |
|---|---|---|---|
| Block a transition based on issue links | ADVANCED | ||
| Block a transition based on sprint information | BEGINNER | ||
| Block a transition based on the day of the week | BEGINNER | ||
| Block a transition if a predefined field value has not been changed | BEGINNER | ||
| Block a transition if some issues under an epic are not in a certain status | INTERMEDIATE | ||
| Check current issue status | BEGINNER | ||
| Check for unresolved sub-tasks | INTERMEDIATE | ||
| Check if an attachment was added recently | BEGINNER | ||
| Check parent issue type | INTERMEDIATE | ||
| Check the number of times that a field has changed | INTERMEDIATE | ||
| Evaluate the Parent Link field | INTERMEDIATE | ||
| Evaluate worklogs in sub-tasks | BEGINNER | ||
| Validate an issue only if a comment is written during the transition | BEGINNER | ||
| Validate worklogs |
If you still have questions, feel free to refer to our support team.
