The Issue selector needs an issue (context) as a starting point.
Therefore it can only be used with the following issue-related event trigger types:
Issue selector configuration
Below you will find a detailed description of each parameter needed to configure the condition.
Target issue(s)*
Select the issues that should be collected by the selector. Based on the selection, additional filters can be set for limiting the result.
Run as
Use Cases
Use case | Automated action | Use case description | Complexity |
---|---|---|---|
Sum up value in parent issue on field change in sub-tasks | Calculate field values from all sub-tasks and writes the sum into a corresponding field in the parent issue. | INTERMEDIATE | |
Keep the priority of parents and sub-tasks in sync | When the priority of a parent issue is updated, all sub-tasks will be updated accordingly. | BEGINNER | |
Keep the status of parents and sub-tasks in sync | When an issue is being rejected, all sub-tasks will be transitioned to the REJECTED status as well - automatically. | BEGINNER |
If you still have questions, feel free to refer to our support team.