Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Automation to update the field of the child tickets and their child tickets

Good morning y'all, 

I need to create an automation (with automation rule) that, update a field automatically: 

From the "parent" ticket I modify a field. From there, the child ticket has this same field modified, as well as its child.


Here is the context: 

  • Issue #1 (parent of) -> field 'priority' is updated manually 
    • Issue #2 (which is child of #1 and parent of #3) -> field 'priority' must be updated automatically 
      • Issue #3 (child of #2) -> field 'priority' must be updated automatically

Thanks a lot for your help :)



2 answers

1 accepted

0 votes
Answer accepted
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.
Aug 25, 2021

Hi @Bastien Delourmel 

For a cascading updates like this (parent to child to...) it may help to have multiple rules for each level.  This will be easier to implement, debug, and maintain.

For example for a cascade downward:

  • One rule detects field changes in an epic, tests issue type to confirm it is an epic, and then update its children
  • Another rule (with the option "Allow Rule Trigger" selected in the Details), that detects the field change, tests issue type is story/task/bug, and then update sub-tasks

Best regards,

Hi @Bill Sheboy , 


Thanks a lot, it does work to create two rules! ^^

I was thinking to create a listener, but it will be easier with automation rule for potential maintenance. 




Like Bill Sheboy likes this
0 votes
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Aug 25, 2021

Hi @Bastien Delourmel

Take a look at this post

You will have to look at rule 2 and add an additional branch.  You will also have to change the brach to "linked issues" with the correponding relationships.

Hi, thanks for your answer. Unfortunalty I already try this solution, but in Automation Rule we  have "Parent of" and "Child of" (but not, the "Child of its child" ahah)


If from the Issue #1 I change the field priority, it will change the field "priority" to the issue #2 (but not for the issue #3, because #1 is not directly parent to the issues #3). 

But if I change the field priority of the issue #2, because the issue #2 is linked to #1 and #3, the update is made. 


Automation rule: (I tried to change "parent" of to "child of" and so on)


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events