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:Ā 

Edit a parent and its parent's parent

Logan Harvey
March 6, 2025

I made an automation that edits the due date of a parent task if its child task's due date is edited to be after the parent task. This way, if a sub task due date is set after the parent task, it automatically makes them the same due date.

I've found that the subtask updates the parent tasks just fine, but not it's "grandparent" Epic parent. Not sure if there is a way to have this loop back and check if the parent task that is updated also has a parent task above its parent that needs updating.

I've tried moving the If Issue fields condition around and seeing if it makes a difference, but I haven't been successful.

Any tips or insights on if this is possible would be appreciated!

 

image.png

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

7 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 Champions.
March 6, 2025

Hi @Logan Harvey -- Welcome to the Atlassian Community!

One way to do that is allowing the rule to trigger itself to run again, using this option in the rule details at the top: "Check to allow other rule actions to trigger this rule..."

With that, if the Due Date changes in a subtask the rule triggers and updates the parent Task.  That change will trigger the rule again to update the parent Epic of the Task.

This setting is disabled by default to prevent rule errors and accidental looping, so only use it when you intentionally want this type of recursive behavior.

 

Also please note that as written, your rule may be missing some cases.  Consider how / if you want to handle them:

  • What happens if someone manually changes the date in an Epic after it has been automatically updated?
  • What happens if a Task changes to a different parent?
  • What happens when a Task (or Subtask) is added as new with an already set Due Date?
  • What happens when a Task (or Subtask) is deleted?
  • etc.

 

Kind regards,
Bill

Logan Harvey
March 6, 2025

Thanks Bill, never noticed that checkbox before, that did the trick for a few other things I was working on too. Good ideas on the other situations this could be missing from, thanks again!

Like • Bill Sheboy likes this
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events