Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
This validator depends on issue type, status, resolution, and number of sub-tasks.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
UI Expand | |||||
---|---|---|---|---|---|
| |||||
Only 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 are allowed. Leave empty to allow all issue types.
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Only If you select specific statuses, all sub-tasks with must be in any of the selected statuses are allowed. Leave empty to allow all statuses. Example of possible 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.
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
Only If you select specific resolutions, all sub-tasks with must have any of the selected resolutions. If subtasks with other resolutions are allowed. Leave empty to allow all resolutions. Example of possible resolutions:
found, the condition will fail. The additional filters can be used to further restrict the state of the issues with the selected resolutions.
|
UI Expand | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||
Only Optionally limit the sub-tasks matching the field value condition provided will be allowed. Leave empty for no filteringto be counted by their field values. To achieve this you must enter an expression in Logical mode. The expression must return
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
The Specify the minimum number of subthe sub-tasks required to satisfy selected filtering conditions (issue type, status, resolution, and field values)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.
|
UI Expand | |||||
---|---|---|---|---|---|
| |||||
The Specify the maximum number of the counted sub-tasks allowed to satisfy selected filtering conditions (issue type, status, resolution, and field values)that need to satisfy the specified filter criteria. The default 1000.
|
UI Expand | |||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||
Choose from one of the following options (multi-choice is possible):Optionally select one or multiple filters or issues not matching the defined filter criteria that should be ignored.
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.
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
UI Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
| ||||||||||
UI Expand | ||||||||||
| ||||||||||
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. | ||||||||||
UI Expand | ||||||||||
| ||||||||||
Add an optional error message to show when validation fails. LocationDefine where the error message should be displayed. MessageFor 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.
UI Text Box | | |||||||||
|
Use cases and examples
Page properties report | ||
---|---|---|
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
Page properties | ||||
---|---|---|---|---|
| ||||
|