On this page
Use case
Often it is necessary to keep parent issues and sub-tasks in sync. To do so, the following automation rule comes with a handy configuration that automatically updates specific sub-tasks' field values with their corresponding parent issue's value.
In our use case we want to automatically update the priority field.
Field changed event
Create a new rule and name it appropriately.
Providing a description will help you to identify what the rule does but this step is optional.
Add a Trigger → Field Changed Event
Field*
Choose Priority
Changed to*
Choose Any value
Issue selector
Add Selector → Issue selector → Sub-tasks
No further configuration needed.
Update field configration
Next to Issue selector click on Add → Action → Update Field
Field*
Choose Priority
Update to*
Choose Value returned by parsed expression
Parser Expression*
%{trigger.issue.priority}
# Since we want to get the value from that issue that is triggering the rule, we add the "trigger" prefix.
→ 
Screencast
This is how the configuration above should look on your screen
Related examples
| 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 | |
| Update assignee and reporter to facilitate user deletion | To facilitate deleting a user account, all issues will be reassigned and the reporter changed to avoid potential problems when deleting the user. | INTERMEDIATE |
If you still have questions, feel free to refer to our support team.
