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.
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 | In order to deal as a validator, the Jira expression expect the return of a boolean true or false. When developing the expression used for validation it may help to evaluate intermediate results which doesn't return a boolean value. If you just enter a field code without any comparison operator you will simply get the value as a response! In this use case 'Task' will be returned as the current issue type. When storing this expression as it is, the validator evaluates to false, since with Jira expressions any non-boolean value will be considered as false. | |
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 | Function | Use case description | Complexity |
---|---|---|---|
Block a transition based on issue links | Evaluate issue links and hide transitions based on the outcome. This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator. | ADVANCED | |
Block a transition based on sprint information | Make sure that an issue is not in an active sprint. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
Block a transition based on the day of the week | Block transitions on weekends or any other day of the week. This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
Block a transition if a predefined field value has not been changed | Evaluate a Date Picker field and block the transition if it has not been updated. This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
Block a transition if some issues under an epic are not in a certain status | Check whether an epic has all issues under it in a certain status. This is particularly important if you want to block an epic as long as work is still being done on related sub-tasks. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | INTERMEDIATE | |
Check current issue status | Check whether the current issue is in a particular status. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
Check for unresolved sub-tasks | Check whether the current issue has any unresolved sub-tasks. This is particularly important if you want to block a parent issue as long as work is still being done on related sub-tasks. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | INTERMEDIATE | |
Check if an attachment was added recently | Make sure that the current user has uploaded a attachment during a definite period of time. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
Check parent issue type | Check whether the parent of the current issue is of a certain issue type. This is particularly important if you want to reuse a workflow for multiple sub-task issue types but only want a transition to be available if the sub-task belongs to a certain user story or a bug. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | INTERMEDIATE | |
Check the number of times that a field has changed | Check the number of times that a field has changed. This use case is valid for both conditions and validators. The only difference is that you can specify an additional error message when using a validator. | INTERMEDIATE | |
Evaluate the Parent Link field | Evaluate different values of the issue in the Parent Link field of the transitioned issue. This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator. | INTERMEDIATE | |
Evaluate worklogs in sub-tasks | Evaluate if work has been logged in a sub-task to prevent transitioning the parent issue when no work has been logged. This use case is valid for both conditions and validators . The only difference is that you can specify an additional error message when using a validator. | BEGINNER | |
Validate an issue only if a comment is written during the transition | Evaluate the comments and hide transitions based on the outcome. This use case is only valid for validators as it involves making changes during a transition. An additional error message can be added. | BEGINNER | |
Validate worklogs | Evaluate if a user has logged more than a certain amount of time in the latest worklog.
|