This validator depends on issue type, status, resolution, and number of sub-tasks.
Configuration
Only sub-tasks with the selected issue types are allowed. Leave empty to allow all issue types.
Only sub-tasks with the selected statuses are allowed. Leave empty to allow all statuses.
Example of possible statuses:
- Open
- To Do
- In progress
- Done
- Approved
Only sub-tasks with the selected resolutions are allowed. Leave empty to allow all resolutions.
Example of possible resolutions:
- Unresolved (resolution is empty)
- Done
- Duplicate
Only sub-tasks matching the field value condition provided will be allowed. Leave empty for no filtering.
Test your expression by clicking the run button on the top right of the expression box.
The minimum number of sub-tasks required to satisfy selected filtering conditions (issue type, status, resolution, and field values).
The maximum number of sub-tasks allowed to satisfy selected filtering conditions (issue type, status, resolution, and field values).
Choose from one of the following options (multi-choice is possible):
| Option | Description |
|---|---|
Sub-tasks in unselected issue types will be ignored, i.e., they will be allowed regardless of their status, resolution, field values, and number. Nevertheless, if none of the issue types are selected, checking this option will make the condition behave as if you had selected every issue type. | |
Sub-tasks in unselected statuses will be ignored, i.e., they will be allowed regardless of their resolution, field values, and number. Nevertheless, if none of the statuses are selected, checking this option will make the condition behave as if you had selected every status. | |
Sub-tasks in unselected resolutions will be ignored, i.e., they will be allowed regardless of their field values and number. Nevertheless, if none of the resolutions are selected, checking this option will make the condition behave as if you had selected every resolution. | |
Sub-tasks not satisfying filter by field values will be ignored, i.e., they will be allowed regardless of their number. |
Choose from one of the following options (multi-choice is possible):
| Option | Description |
|---|---|
If the transition is triggered by a JWT post function, the validation will be skipped. | |
If the transition is triggered by a bulk operation, the validation will be skipped. | |
If the create transition is triggered by a clone operation, the validation will be skipped. | |
f the create transition is triggered by a mail handler, the validation will be skipped. |
Add an optional error message to show when validation fails.
Location
Define where the error message should be displayed.
Message
For the message content to be displayed when an error occurs, enter plain text and optionally use Field codes, e.g. %{issue.summary}, to insert field values.
Test your expression by clicking the play button on the top right of the expression box.
Click on the Add translation button and choose the desired language to be translated to.
Translations will be displayed based on the user's language setting.
Use cases and examples
| Title |
|---|
| No content found. |
If you still have questions, feel free to refer to our support team.
