Rolling Up Status Transitions Across Multi-Level Issue Hierarchy
Asked by Sameeksha Shetty:

Hi,

I'm working with a Jira issue hierarchy that has three or more levels. Here's a simplified version of the hierarchy:

* **Epic**
* **Story**
* **Sub-task**

What I'd like to achieve is this:

* When a **Sub-task** is transitioned to "Done," the parent **Story** should automatically transition to "Done."
* Furthermore, when all **Stories** within an **Epic** are marked as "Done," the **Epic** itself should also transition to "Done."

I'm currently using Jira Cloud and I've set up automation rules, but I'm facing challenges with ensuring that the status transitions correctly roll up to the parent and grandparent levels. Specifically, I want to ensure that the parent issue (Story) and grandparent issue (Epic) are automatically updated when the child issues are completed.

Has anyone successfully implemented this kind of status roll-up across multiple levels? If so, could you share how you configured your automation rules or workflows to achieve this?or Can it be achieved by any other method?

Thanks in advance for your help!


Answers:
author: Arun Unnikrishnan
body: [@Sameeksha Shetty](/t5/user/viewprofilepage/user-id/5574075) You may have to use two automations to achieve this.

One for Transitioning Story based on Sub-Task and the other for transitioning Epic based on the Story.

You may use the trigger - When issue transitioned

Check if the transitioned issue is Sub-task using an Issue Type condition

![Screenshot 2024-08-26 155302.png](https://community.atlassian.com/t5/image/serverpage/image-id/343792iBC5872E8418553F3/image-dimensions/371x156?v=v2 "Screenshot 2024-08-26 155302.png")

Add a branching for Parent and check if Sub-Task status match Done/Complete using a Related Issue condition.

And finally finally transition the Parent (story) to Done if above condition is true.

![Screenshot 2024-08-26 154849.png](https://community.atlassian.com/t5/image/serverpage/image-id/343793i81EECDB470E3E94C/image-dimensions/371x274?v=v2 "Screenshot 2024-08-26 154849.png")

Similarly, you can do for Story-Epic status change.

Hope this helps.

comments: author: Sameeksha Shetty
body: Thank You [@Arun Unnikrishnan](/t5/user/viewprofilepage/user-id/5203881)

Is there any other way to achieve this?

I've tried setting up this rule before but it doesn't seem to work for Epic-level issues It only updates the parent Story and shows a success message.


author: Arun Unnikrishnan
body: [@Sameeksha Shetty](/t5/user/viewprofilepage/user-id/5574075) This can be achieved.

Can you share the screenshots of your automations?


author: Sameeksha Shetty
body: yes!

![sc1.png](https://community.atlassian.com/t5/image/serverpage/image-id/343846iE3EC3D3513B9A5D9/image-size/large?v=v2&px=999 "sc1.png")![sc2.png](https://community.atlassian.com/t5/image/serverpage/image-id/343847iA483BEB83573B2F9/image-size/large?v=v2&px=999 "sc2.png")![sc3.png](https://community.atlassian.com/t5/image/serverpage/image-id/343848i17FC379FC69CA49F/image-size/large?v=v2&px=999 "sc3.png")


author: Arun Unnikrishnan
body: [@Sameeksha Shetty](/t5/user/viewprofilepage/user-id/5574075) I think you should spilt the automations into two. one for story transition and other one for EPic transition. it will work.


Tags: cloud

jira-cloud