Parent issue transition from subtask completion
Asked by Alyssa Hill:

Hi all!

I'm trying to create an automation that when each subtask is completed, the parent issue is transition to the next status.

For example, first the issue is created with the components necessary to trigger the rule, then forms are added, and last a subtask is added.

From there a parent branch is added that says when the subtask equals status done, transition the parent issue status to 'configure' however it's not working. What am I missing?

I'd like to apply additional subtasks and transitions to this same rule (once I get the first transition to work) to ensure certain tasks are marked as done throughout the workflow statuses:

![Screen Shot 2024-06-28 at 3.35.07 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/332535i254016AA22F07E97/image-size/large?v=v2&px=999 "Screen Shot 2024-06-28 at 3.35.07 PM.png")![Screen Shot 2024-06-28 at 3.35.17 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/332534iDD8A205B15AF4E4A/image-size/large?v=v2&px=999 "Screen Shot 2024-06-28 at 3.35.17 PM.png").

Thank you!

Alyssa


Answers:
author: Mikael Sandberg
body: You would have to create multiple automations in order for this to work. The way your rule is currently configured it is expecting that the issue that triggered the automation is in the the closed status and it has a parent.

Your first rule should be in issue create and that will add the forms and the subtasks. The second rule would trigger on when an issue moves to the Done status, and you can add controls to make sure it is a subtask and if so then use your branch above to move the parent issue to the next status.

comments: author: Alyssa Hill
body: Hi [@Mikael Sandberg](/t5/user/viewprofilepage/user-id/853579) I decided to try this out with a more simple workflow to begin, but am still lost-

Here's what ive tried so far:

1)

![Screen Shot 2024-07-01 at 4.18.06 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/332891iF959016DA4F79F96/image-size/large?v=v2&px=999 "Screen Shot 2024-07-01 at 4.18.06 PM.png")

This did now allow the parent issue to be updated as intended.

2) I've also tried this, but same result, parent status does not update: ![Screen Shot 2024-07-01 at 4.41.40 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/332893i6D74DDA77E9BBE51/image-size/large?v=v2&px=999 "Screen Shot 2024-07-01 at 4.41.40 PM.png")

Are you saying I would need 3 different automation rules in this case?

1) for the creation of task, and subtasks

2nd for, 'some' condition for subtasks

and a 3rd, for the final subtask condition that states all must be marked as done


author: Mikael Sandberg
body: You would need at least two automations. The first one would be on issue create which adds the subtasks that you want. The second would be on issue transition that moves the parent issue to the next status and would look similar to this automation template:

![Screenshot 2024-07-01 at 4.04.40?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/332900i82F757916D2560C1/image-size/large?v=v2&px=999 "Screenshot 2024-07-01 at 4.04.40?PM.png")


author: Alyssa Hill
body: [@Mikael Sandberg](/t5/user/viewprofilepage/user-id/853579) For the 2nd automation rule, what is initial the trigger? I can't seem to get it to work. It looks like you are having it based off the issue being transitioned to 'done' ?

For my use case it can't be when an issue is transitioned because I want to rule to transition the issue so a real person is never manually transitioning the parent issue.


author: Mikael Sandberg
body: [@Alyssa Hill](/t5/user/viewprofilepage/user-id/5200126) The second rule would trigger on transition as pictured above and because you are using the parent branch it would only run if the issue that is transitioning is a subtask and then you use the parent branch to transition it to the next status.


Tags: cloud

jira-service-management

jira-service-management-cloud