The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Update field for all hierarchy of child issues

Mykhailo Oleksiuk
July 22, 2023

Hi,

I've created an automation that helps me to update the 'Component' field on child issues if it's changed on the parent one. But it works only in 2 levels of hierarchy.

Parent

|---Child

 

 

Is it possible to automate forScreenshot 2023-07-22 at 17.27.56.png N levels of hierarchy?

Epic -> Story -> Task

So, if I changed the 'Component' field in Epic level it will be updated automatically for Story and then for Task.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

3 votes
Answer accepted
Jehan Bhathena
Community Champion
July 23, 2023

Hi @Mykhailo Oleksiuk ,

Perhaps you can create 2 automation rule?

First will run when the Component gets updated in the EPIC, and update the STORIES. The next automation can be executed to update SUB-TASKS when the above STORY gets the component field updated. You will need to check the below option in the second automation rule though.

image.png

Mykhailo Oleksiuk
July 23, 2023

Hi @Jehan Bhathena 

Thanks a lot. It works as expected 👍

 

Posting final result that could be helpful for others:

 

1. The first rule updates 'Component' field for epic, story, task, bug

Screenshot 2023-07-23 at 21.27.09.png

 

2. The second rule updates 'Component' field for sub-task only and has enabled in 'Rule details' settings suggested checkbox 

Screenshot 2023-07-23 at 21.30.56.png

Screenshot 2023-07-23 at 21.27.28.png

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events