Use case
This use case ensures, that an issue must have at least three sub-tasks of type "Test Case" which must all be resolved.
You can either hide the transition using the Condition on sub-tasks or block the transition using the Validation of sub-tasks.
⚒️ Configuration
Add the condition or the validator to the desired transition or create a new transition.
Filter by issue type
Choose the desired issue type , e.g. "Test Case"
Filter by resolution
Choose the desired resolution(s) , e.g. "Done"
Minimum number of sub-tasks
Choose 3
Additional options
Allow unselected issue types
Check this option.
Checking this option ensures that other issue types are not being considered / analyzed since you only want to analyze Test Cases.
Allow unselected statuses
Check this option to skip the status filter.
The following parameters are only available, if you are configuring this use case as a validator.
📷 Screenshots
📚 Related use cases
| Use case | JWT feature | Workflow function | Parser functions | Label |
|---|---|---|---|---|
| All sub-tasks in the Closed status must have a specific resolution |
|
|
|
|
| All sub-tasks must be Done or Closed |
|
|
||
| All sub-tasks must be resolved |
|
STAFF PICK |
||
| All sub-tasks with a resolution of Done must be in a specific status |
|
|
||
| An issue must have at least 3 resolved Test Cases |
|
|
||
| Specific sub-tasks must be resolved |
|
|
