This validator is used for blocking a transition depending on the result of a JQL query.
⚒️ Configuration
JQL
Enter a JQL query using the JQL mode of the expression editor. The current issue will be matched against the result set of the query.
It is very common to use field codes inside the JQL query.
Validation
Define how the issue should be compared against the result set of the JQL query. You have the following options:
|
Option |
Description |
|---|---|
|
Current issue belongs to the output of the query |
The condition is passed, if the current issue is part of the result set of the JQL query. |
|
Current issue doesn't belong to the output of the query |
The condition is passed, if the current issue is not part of the result set of the JQL query. |
|
Number of issues returned by the JQL query satisfies a logical expression |
Define a logical expression in Logical mode which must return The number of issues returned by the query is stored in the Temporary number field 1. This is why this value is automatically added to your logical expression. |
Example for a logical expression
|
JQL query |
Expression |
Description |
|---|---|---|
|
|
The validator will pass, if there are less than 5 unresolved Bugs in the current issue's project. |
Validation options
The validation can be skipped under certain circumstances Select one or multiple scenarios in which you want to skip the validation to ensure the correct execution of certain operations.
|
Option |
Description |
|---|---|
|
Skip validation for JWT post functions |
If the transition is triggered by a JWT post function, e.g. through Transition issue, the validation will be skipped. |
|
Skip validation for bulk operations |
If the transition is triggered by a bulk operation, the validation will be skipped. |
|
Skip validation for clone operations |
If the create transition is triggered by a clone operation, the validation will be skipped. |
|
Skip validation for mail handlers |
If the create transition is triggered by a mail handler, the validation will be skipped. |
Error message
You can optionally define a custom error message in case the validator fails, which will be shown to the user trying to execute the transition.
You have the following options:
Location
Define where the error message should be displayed. By default, the message will be shown at the top of the transition screen, or in case there is no transition screen, as a popup.
Alternatively, you can locate the message below any other field. This option only makes sense, if there is a transition screen defined for the specific transition.
Due to limitations in Jira Service Management, the location parameter will be ignored on Jira Service Management related screens. The location parameter only works for the Create Issue transition screen if JSD version 4.10 or higher is being used.
Message
Define the content of the error message in Basic text mode or Advanced text mode.
Learn more about the possibilities of the JWT expression editor.
In comparison to e.g. our calculated custom fields it is not possible to display HTML here. Displaying links to specific issues, for example, is not possible inside the error message.
Translations
After clicking on the Add translation button you can optionally translate the error message to other languages.
The language in which the error message will be displayed depends on the language setting of the individual users.
Run as
Select which user will be used to execute the JQL query.
All permission and security level restrictions are being respected.
Only issues that the specified user can access will be returned by the JQL query.
If you want to use this functionality in a condition instead, have a look at the following condition: Condition based on JQL query
📚 Use cases and examples
| Use case | JWT feature | Workflow function | Parser functions | Label |
|---|---|---|---|---|
| Assignee may only have a restricted number of assigned issues |
|
|
|
|
| Prevent issue creation with the same field value |
|
|
STAFF PICK |
|
| Prevent creation of issues with a duplicate summary |
|
|
