This validator can block a transition based on the state and the number of an issue's sub-tasks.
The validator only makes sense when used in a workflow used by standard issue types.
You can specify multiple filter criteria that will be "and concatenated". Per default, all sub-tasks must match the combination of all criteria.
Configuration
If you select specific issue types, all sub-tasks must be of any of the selected issue types. If subtasks with other issue types are found, the condition will fail.
The additional filters can be used to further restrict the state of the selected issue types.
If you leave this filter blank, e.g. if the issue type is irrelevant, you must check the additional option Allow unselected issue types. → Ignore issue type filter / issues in unselected issue types
If you select specific issue types and also check the additional option Allow unselected issue types, the additional criteria (status, resolution, field value) will only be applied to the selected issue types.
If you select specific statuses, all sub-tasks must be in any of the selected statuses. If subtasks with other statuses are found, the condition will fail.
The additional filters can be used to further restrict the state of the issues in the selected statuses.
If you leave this filter blank, e.g. if the status is irrelevant, you must check the additional option Allow unselected statuses. → Ignore status filter / issues in unselected statuses
If you select specific statuses and also check the additional option Allow unselected statuses, the additional criteria (issue type, resolution, field value) will only be applied to the issues in the selected statuses.
If you select specific resolutions, all sub-tasks must have any of the selected resolutions. If subtasks with other resolutions are found, the condition will fail.
The additional filters can be used to further restrict the state of the issues with the selected resolutions.
If you leave this filter blank, e.g. if the resolution is irrelevant, you must check the additional option Allow unselected statuses. → Ignore resolution filter / issues with unselected resolutions
If you select specific resolutions and also check the additional option Allow unselected resolutions, the additional criteria (issue type, resolution, field value) will only be applied to the issues with the selected resolutions.
Optionally limit the sub-tasks to be counted by their field values. To achieve this you must enter an expression in Logical mode. The expression must return true
or false
.
Examples:
Expression | Description |
---|---|
%{seed.issue.assignee} != null | All sub-tasks must be assigned to a user. If unassigned sub-tasks are found, the condition will fail. Values in sub-tasks have to be referenced by their seed field codes. |
%{issue.dueDate} <= %{seed.issue.dueDate} | All sub-tasks must have a due date of equal to or later than the current issue's due date.. Values in sub-tasks have to be referenced by their seed field codes. |
If you specify an expression and also check the additional option Allow unsatisfied condition on field values, the additional criteria (issue type, resolution, field value) will only be applied to the issues that match the expression.
Specify the minimum number of the sub-tasks that need to satisfy the specified filter criteria. The default value is 0 to ensure the condition passes if the current issue does not have any sub-tasks.
If you set this number to 1, the condition will fail if the issue does not have any sub-tasks or if the existing sub-tasks don't match the specified filter criteria.
Specify the maximum number of the counted sub-tasks that need to satisfy the specified filter criteria. The default 1000.
If you set this number to 1, the condition will fail as soon as more than one sub-task satisfies the specified filter criteria.
Optionally select one or multiple filters or issues not matching the defined filter criteria that should be ignored.
Option | Description |
---|---|
Ignore issue type filter / issues in unselected issue types | Check this option in the two cases:
|
Ignore status filter / issues in unselected statuses | Check this option in the two cases:
|
Ignore resolution filter / issues with unselected resolutions | Check this option in the two cases:
|
Check this option in the two cases:
|
Option | Description |
---|---|
If the transition is triggered by a JWT post function, e.g. through Transition issue, 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. |
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.
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.
Use cases and examples
Title |
---|
No content found. |
If you still have questions, feel free to refer to our support team.