Jira expression validator | Decadis App Help Center

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.

⚒️ Configuration

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.

Remember that the usage of field codes is different when being used in Jira expressions. Curly brackets surrounding the field code are not supported. Not for every field code known from the JWT Expressions an equivalent is available.

Error message

Enter the message to show to the end-user when the validation fails. In case you don't enter a message, the default error Message for JWT for Jira Cloud "Validation failed for validator 'Jira expression validator (JWT)'" is displayed in case of a failing validation.

Test expression

We highly recommended to test your expression before publishing the workflow. Click on and select an issue for the context of the evaluation of the given Jira expression. After clicking the "Run" button the result of the evaluation is shown in a message box below.

Learn more about how to test an expression!

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 expressions.

Special case: Using specific fields in the Create transition

In the Create transition, the Jira expression in a Jira expression validator/condition to check if a value is empty has to be created as shown below for the following fields:

Text field (multi-line)
Request fields
Organization fields
Assets fields

For example:

 ((typeof issue?.customfield_nnnnn == "Map") ? new RichText(issue?.customfield_nnnnn).plainText : issue?.customfield_nnnnn) != null

 issue?.customfield_nnnnn != null

For all other other transitions, this comparison looks like follows:

((typeof issue?.customfield_nnnnn == "Map") ? new RichText(issue?.customfield_nnnnn).plainText : issue?.customfield_nnnnn) != ""

issue?.customfield_nnnnn != ""

📚 Use cases and examples

Use case	Workflow function	Use case description
Block a transition based on issue links	Jira expression condition Jira expression validator	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.
Block a transition based on sprint information	Jira expression condition Jira expression validator	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.
Block a transition based on the day of the week	Jira expression condition Jira expression validator	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.
Block a transition if a predefined field value has not been changed	Jira expression condition Jira expression validator Update fields	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.
Block a transition if some issues under an epic are not in a certain status	Jira expression condition Jira expression validator	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.
Check current issue status	Jira expression condition Jira expression validator	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.
Check for unresolved sub-tasks	Jira expression condition Jira expression validator	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.
Check if an attachment was added recently	Jira expression condition Jira expression validator	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.
Check parent issue type	Jira expression condition Jira expression validator	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.
Check the number of times that a field has changed	Jira expression condition Jira expression validator	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.
Check whether an attachment was added during the transition.	Jira expression condition Jira expression validator	Make sure that the current user has uploaded a attachment during the transition. 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.
Evaluate the Parent field	Jira expression condition Jira expression validator	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.
Evaluate worklogs in sub-tasks	Jira expression condition Jira expression validator	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.
Validate an issue only if a comment is written during the transition	Jira expression validator	Evaluate the comments and block 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.
Validate worklogs	Jira expression condition Jira expression validator	Evaluate if a user has logged more than a certain amount of time in the latest worklog.