Update the subtask based on parent task status only if Deployed/Closed

[G Preeti]

I want to create an automation where, when a parent task is transitioned to DEPLOYED, all of its subtasks are automatically transitioned to DEPLOYED. This is working as expected. However, when the parent task is transitioned to CLOSED, the subtasks are still being updated to DEPLOYED instead of CLOSED. The expected behavior is that the subtasks should always transition to the same status as the parent task. Could you help me configure the automation so that when the parent task is moved to DEPLOYED, the subtasks move to DEPLOYED, and when the parent task is moved to CLOSED, the subtasks move to CLOSED?

[Arkadiusz Wroblewski]

Hello @G Preeti 

Are you Familiar with this page Branch automation flows to perform actions on related work items | Cloud automation Cloud | Atlassian Support and have tried to build that yourself ?

Concept how to Setup that is pretty easy, you need just Simple JQL Condition and branch after it, then add transition and for status copy from Trigger work item.

Best,

Arek🤠

[Dev]

Hi @G Preeti 

You can achieve this with a single Automation rule without creating separate rules for each status.

Configure the rule as follows:

Trigger: Work item transitioned.
Condition: Issue type = Parent issue (for example, Task, Story, or Bug).
Branch: Related work items → Sub-tasks.
Action: Transition work item.
For Destination status, select Copy from trigger work item instead of selecting a fixed status such as DEPLOYED.

This ensures that the subtasks always transition to the same status as the parent. For example:

Parent → DEPLOYED → Subtasks → DEPLOYED
Parent → CLOSED → Subtasks → CLOSED

If your subtasks fail to transition, verify that the subtask workflow has a valid transition to the target status. Automation can only transition an issue if the destination status is reachable in its workflow.

[Gor Greyan]

Hi @G Preeti

It sounds like your automation is always transitioning the subtasks to DEPLOYED, regardless of the parent's new status.

Instead of only checking that the parent has changed, also check the destination status.

Trigger: Work item transitioned

Advanced compare - If {{issue.status.name}} equals DEPLOYED

Branch to subtasks

Transition each subtask to DEPLOYED

Else if {{issue.status.name}} equals CLOSED

Branch to subtasks

Transition each subtask to CLOSED

This way, the subtasks will follow the parent's current status rather than always transitioning to DEPLOYED.

If you're already using a condition like this, could you share a screenshot of your automation rule? That will help identify why the CLOSED transition is still resulting in DEPLOYED.