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 with must be any of the selected issue types are allowed. Leave empty to allow all issue types. If sub-tasks with other issue types are found, the validator will fail. The additional filters can be used to further restrict the issues to be analyzed.
|
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 sub-tasks with other statuses are found, the validator will fail. The additional filters can be used to further restrict the issues to be analyzed.
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
Only If you select specific resolutions, all sub-tasks with must have any of the selected resolutions. If sub-tasks with other resolutions are allowed. Leave empty to allow all resolutions. Example of possible resolutions: found, the validator will fail. The additional filters can be used to further restrict the issues to be analyzed.
|
UI Expand | ||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||
Only Optionally limit the sub-tasks matching the field value condition provided will be allowed. Leave empty for no filteringto be counted or analyzed 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 validator 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 is 1000.
|
UI Expand | ||
---|---|---|
| ||
Choose from one of the following options (multi-choice is possible):
|
UI Expand | ||
---|---|---|
| ||
Choose from one of the following options (multi-choice is possible):
|
The following options can be used to refine the number of issues you want to analyze in this validator. Per default all filters are mandatory, filters are "and concatenated" and you cannot save your configuration unless you have specified values. Any sub-task being analyzed by the validator must match all criteria.
The additional options allow you to override the default behavior.
ExamplesThe table below lists a few example configurations and their JQL equivalent.
|
UI Expand | ||||||
---|---|---|---|---|---|---|
| ||||||
|
UI Expand | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
| ||||||||
UI Expand | ||||||||
| ||||||||
Add an optional error message to show when validation fails.
UI Expand | | |||||||
|
UI Text Box | ||||
---|---|---|---|---|
| ||||
Test your expression by clicking the play button on the top right of the expression box. |
UI Button | ||
---|---|---|
|
UI Text 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. |
If you want to use this functionality in a condition instead, have a look at the following condition: Condition on sub-tasks
Use cases and examples
Page properties report | ||||||
---|---|---|---|---|---|---|
|
Excerpt Include | ||||||
---|---|---|---|---|---|---|
|
Page properties | ||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||
|
Page properties | ||||
---|---|---|---|---|
| ||||
|
Page properties | ||||
---|---|---|---|---|
| ||||
|