Keep the status of parents and sub-tasks in sync (post function use case)

Use case

Keeping parent issues and sub-tasks in sync is a lot of manual work. Therefore, the following use case 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 a workflow post function or an automation rule?

When to use this workflow post function and when to use an automation rule?

This use case is very useful, if there is only one specific workflow where this post function is needed. Configuring an automation rule might then be a bit too much. But if there are several worklfows where this behavior is needed, the Transition issue action would make more sense. In this case you might want to check out our corresponding automation use case.

Configuration

Add the Transition issue post function to the desired transition or create a new transition.

In our case we created a transition called Reject that goes to status Rejected.

Target issue

Choose Sub-tasks

Mode

Choose Transition to status and select Rejected from the drop down menu.

Make sure that the status can be reached by the sub-tasks from their current status. Otherwise they won't be transitioned.

Screenshots

Related use cases

Use case	Workflow function	Label
Fast-track transition issues assigned to the project lead	Transition issue	STAFF PICK
Keep the status of an issue and its linked issues in sync	Transition issue
Keep the status of parents and sub-tasks in sync (post function use case)	Transition issue
Reopen parent issue, if a sub-task is reopened	Transition issue
Start Progress on parent, if sub-tasks are started	Transition issue	STAFF PICK

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

Content

Space Tools

On this page