Keeping parent issues and sub-tasks in sync, as described in this use case, is a lot of manual work. This automation rule will update the status of all sub-tasks based on the parent status: When the parent issue is rejected, all sub-tasks are also being rejected.
When to use this automation rule and when to use a workflow post function?
This use case is very useful, if there are several software projects with different workflows where all related issues have to be closed on releasing a new version. Configuring just one automation rule might then be the easier way to go. But if this scenario is only necessary for one workflow, the Transition Issues post function would make more sense. In this case you might want to check out our corresponding post function use case.
Issue transitioned 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 → Issue transitioned event
No further configuration needed. The automation rule is triggered every time an issue is being transitioned.
Add a Condition → Boolean Condition
Next to the Boolean Condition click on Add → Selector → Issue Selector
Transition issue action
Next to the Issue Selector click on Add → Action → Transition issue
Transition to status
Enable the rule by clicking on the Enable button →
This is how the configuration above should look on your screen