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 for 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.
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.
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
2. The second rule updates 'Component' field for sub-task only and has enabled in 'Rule details' settings suggested checkbox
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.