Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
Sign up Log in

Jira Automation Update Child Issue of a Child

Shmuel_ Dave July 11, 2024

Dear Atlassian Automation Community,

I have defined my Jira issues hierarchy to Initiative>Epic>Task
I have defined a Related Product field on each of the issue types and would like to set an automation that will cascade the Related Product field value set in the Initiative level to all it's Children (i.e. branch for children and then branch once again for their children)

 

Jira issues hierarchy.jpg

Can anyone assist in suggesting an automation approach to achieve this goal šŸ™šŸ¼ 

2 answers

1 accepted

1 vote
Answer accepted
Duc Thang TRAN
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 11, 2024

Hello @Shmuel_ Dave 

I can suggest to use another way :

  • trigger when field value changed ( related product) 
  • Then add brand with JQL  like this : 
    • issue in portfolioChildIssuesOf("{{triggerissue}}")
    • edit issue : with copy value of the field  from trigger issue

 

Hope this can work on your instance  

Shmuel_ Dave July 11, 2024

NICE !!!!!!!!
Thank you šŸ™šŸ¼

Update Child Issue of a Child.jpg

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 11, 2024

Hi @Shmuel_ Dave -- Welcome to the Atlassian Community!

You may need additional automation rules if you want to handle other possible scenarios / edge cases.  For example:

  • What should happen if someone manually changes the Related Product field in a Task or Epic?
  • What should happen if the parent Epic of a Task changes?
  • What should happen if the parent Initiative of an Epic changes?
  • What should happen if the parent Epic of a Task is deleted, leaving the child Tasks in place with no connection to the prior Initiative, grandparent?
  • etc.

Kind regards,
Bill

Like ā€¢ # people like this
Shmuel_ Dave July 14, 2024

Yep...
That's correct šŸ‘šŸ¼
Here is what i have added so far -

Untitled.png

Added one for when issues are created under an existing issue -
Untitled.png

2 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
July 11, 2024

Hi Dave - Welcome to the Atlassian Community!

I usually do that with two different rules. So create a rule based on a Field Value Changed rule. Leave it for all types of changes. 

Then add a Condition for Issue type = Initiative

Then add a Branch for Children

Then add an action for Edit Issue and select the same field. 

In the blank below the field name put: {{triggerIssue.Related Product}}

This will update the Epic field with the value from the Initiative. 

Then copy that rule and give it a new name. 

Change the new copied one to change the Condition from Initiative to Epic. Be sure to check the box on the Rule Details to allow it to fire the trigger when another rule fires. 

Then you are ready to test it out. The first will fire and update the value in the Epics, which will cause the second rule to fire, which will update all of the Epics' children. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events