On this page
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 and JWT for Jira Cloud parser expressions .
The configuration
To configure this validator you only need to specify two input parameters - the Jira expression and an error message to show when the validator fails.
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 .
|
| Error message * | Enter the message to show to the end user when the validation fails. |
| Test expression | 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 {}).Get started
Get started by trying out the example configurations provided out of the box.
The following example configurations are currently available:
Additional use cases can be found here!
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 four different responses:
| Response | Output | Explanation |
|---|---|---|
 Response: The value returned by the expression | Jira expressions usually expect the return of a boolean true or false.
In this use case 'Task' will be returned as the current issue type. | |
| Response: true | This response indicates that the expression itself is valid and the parent of the test issue (KANBAN-4) is an Epic. | |
| Response: false | This response indicates that the expression itself is valid but parent of the test issue (KANBAN-4) is not a Story | |
Response: error | There is a syntax error in the specified expression. In this case a missing "=". The correct syntax would be issue.parent != null && (issue.parent.issueType.name == 'Story') |
Use cases and examples using this validator
| Use case | Complexity | 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 |
