Page History
UI Text Box | ||||
---|---|---|---|---|
| ||||
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
UI Expand | |||||
---|---|---|---|---|---|
| |||||
If you select specific issue types, all sub-tasks must be of any of the selected 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 | |||||
---|---|---|---|---|---|
| |||||
If you select specific statuses, all sub-tasks must be in any of the selected 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 | |||||
---|---|---|---|---|---|
| |||||
If you select specific resolutions, all sub-tasks must have any of the selected resolutions. If sub-tasks with other resolutions are found, the validator will fail. The additional filters can be used to further restrict the issues to be analyzed.
|
UI Expand | |||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||
Optionally limit the sub-tasks to 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 | |||||
---|---|---|---|---|---|
| |||||
Specify the minimum number of the sub-tasks 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 | |||||
---|---|---|---|---|---|
| |||||
Specify the maximum number of the counted sub-tasks that need to satisfy the specified filter criteria. The default is 1000.
|
UI Expand | |||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||||||||
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 Text Box | ||
---|---|---|
| ||
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 | ||||
---|---|---|---|---|
| ||||
|