Update epic due date when child due date changes (Automation)

[Lucy Cookney]

Hi

Can anyone tell me where I'm going wrong with this automation rule? It isn't even attempting to run. Could it be because I am updating the child due dates via a different automation?

Edit: It works fine when you manually add the due date to the child so it is because I'm updating it via automation - any way to get around this?

[Gor Greyan · Accepted solution]

Hi @Lucy Cookney

Yes, if you are using another automation for updating the due date, you should put the following checkbox in order to allow another automation to run this one.

[Lucy Cookney]

Oh amazing! I completely missed that option. Thank you :)

[Gor Greyan]

Dear @Lucy Cookney

You are very welcome.

[Bill Sheboy]

Hi @Lucy Cookney 

In addition to your solved question...please consider when you want the field updated and how accurately you want it reflected in the parent work item.

Your scenario covers this case:

GIVEN a work item has a parent
WHEN the Due Date changes
THEN update the parent to maximum Due Date for all of its child work items

And, there are several others to consider, possibly requiring additional rules:

1. When a work item's Due Date changes, update the parent... (Your current case)
2. When a work item is created with a parent, update the parent
3. When a work item is deleted, update the previous parent
4. When a work item as added to a parent, update the parent
5. When a work item is removed from a parent, update the previous parent
6. When a work item changes parents, update both the new and previous parents
7. When a work item changes types such that it no longer has a parent, update the previous parent
8. When a parent's Due Date is manually changed, reset it back to the calculated value
9. When Atlassian has an outage impacting automation rules, there is no documentation on which rules will later run based upon events to "catch up".  As a workaround, one could create a scheduled trigger rule to update all of the relevant parents, leaving the rule disabled until needed.
10. When the above cases have rules which exceed the monthly service limits, rules will stop running completely.  A workaround may be to only update the Due Date in parents once per day, using a scheduled trigger rule such as in #9 above.  Please discuss with your Jira Product Admin to learn more.
11. etc.

Some of the above cases can be combined in to fewer rules, using conditional logic.  For example: #1 and #8 can be combined; as can #4, #5, and #6.

Kind regards,
Bill