Overview
Conditions are used to control the transitions available to a user. If a condition fails, the user will not see the transition button on the Jira issue view, and so will not be able to execute the transition and all validators, and potential post functions will be ignored.
JWT for Jira Cloud currently offers a single, but yet very powerful condition to let you control who can execute a given transition - the Jira expression condition.
As the name states, the condition uses the built-in Cloud functionality of Jira expressions - a unique feature of Jira Cloud which is developed by Atlassian.
Get started in no time!
To help you getting started, JWT for Jira Cloud comes with a predefined set of example configurations that you can apply with a single click.
Available conditions
Jira expression condition
Use cases and examples using conditions
| Use case | Complexity | Condition | Validator |
|---|---|---|---|
| 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 |
