Keep the status of parents and sub-tasks in sync

Use case

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.

Should I use an automation rule or a workflow post function?

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.

Boolean condition

Add a Condition → Boolean Condition

Expression*

Use the following Parser Expression:

%{trigger.issue.status} = "Rejected"

Boolean expressions are logical constructions that return true or false.
In this use case, the expression will only return true if the status of the issue triggering the rule is REJECTED.

Issue selector

Next to the Boolean Condition click on Add → Selector → Issue Selector

Target Issue(s)*

Choose Sub-tasks

Transition issue action

Next to the Issue Selector click on Add → Action → Transition issue

Mode*

Choose Execute transition

Choose your workflow

Choose Close issue

Enable the rule by clicking on the Enable button →

Screencast

This is how the configuration above should look on your screen

Related use cases

Use case	Automated action	Use case description	Complexity
Bulk edit the issue resolution	Transition issue	Set a specific resolution on all completed issues that miss a resolution value.	BEGINNER
Keep the status of parents and sub-tasks in sync	Transition issue	When an issue is being rejected, all sub-tasks will be transitioned to the REJECTED status as well - automatically.	BEGINNER
Resolve issues when all options of a checklist are checked	Transition issue	When all options of a custom checkbox field are ticked, the issue is resolved and transitioned to DONE	INTERMEDIATE
Schedule issues for re-submission	Transition Issue	Periodically transition all issues to OPEN when the re-submission date reminder has been reached.	BEGINNER
Schedule the escalation of overdue issues	Transition Issue	Periodically escalate all issues where the due date has been reached.	BEGINNER
Transition affected issues when releasing a version (automatically)	Transition issue	Automatically transition all unresolved issues with a Fix Version that is being transitioned to DONE.	BEGINNER
Transition affected issues when releasing a version (manually)	Transition issue	Manually transition all issues related to a specific version to DONE.	BEGINNER
Transition issues when assigned to a developer	Transition issue	When the assignee is changed to a user in the "Developers" project role, the issue is transitioned to IN DEVELOPMENT.	BEGINNER

If you still have questions, feel free to refer to our support team.

Content

Space Tools

On this page