Task due dates update Epic due date

Lee Tarter

Hello, I run this code and get and error in my compare two values. It does not like me second value being 0 I believe and help would be great!

 

Bill Sheboy

Hi @Lee Tarter -- Welcome to the Atlassian Community!

Without seeing the details of your Edit Issue Fields action, it is unclear what you are trying to do.  Is this what you are trying to do:

GIVEN an Epic issue which has one or more child issues
WHEN the Due Date changes in a child issue
OR WHEN the Start Date changes in a child issue
THEN update the parent Epic's Due Date to be the latest Due Date from its child issues
AND update the parent Epic's Start Date to be the earliest Start Date from its child issues

And, you do not state what you want to do in the cases of:

• all of the child issues have an empty Due Date field and the Epic's Due Date is not empty
• same as above for the Start Date

Let's assume those cannot happen...

 

For this scenario, none of conditions or extra expressions on the lookup JQL are needed.  Instead use the max and min functions on the date fields:

• trigger: Due Date or Start Date change
• condition: issue type does not equal Epic
• condition: parent is not empty
• branch: to parent
  • action: lookup issues with JQL of
    • parent = {{issue.key}}
  • action: edit issue
    • set the Due Date to {{lookupIssues.duedate.max}}
    • set the Start Date to {{lookupIssues.Start date.min}}

Note this could also run if you use Sub-tasks, so perhaps change that first condition to look for exactly the issue types which can be children of your Epics.

Also, I agree with Trudy to use two separate rules (rather than combining as I show).

 

Two more ideas...as written, your rule handles changing the date fields of existing children in the Epic, but not the other cases.  If you want to handle those also, additional rules with different triggers will be needed (using mostly the same logic):

1. When the Start Date or Due Data change in a child issue, update the Epic (This case is covered above.)
2. When a new child issue is created for an existing Epic parent...
3. When an issue's parent is set to become a child for an existing Epic...
4. When the parent of an issue is cleared, update the Epic for the remaining child issues  (This is a special case of #3 above.)
5. When an issue's parent is changed, update both parent Epics  (This is a special case covering both #3 and #4 above.)
6. When an issue is deleted from Jira, update the Epic for the remaining child issues (This is a special case of #4 above, and...hopefully, your Jira Site Admin has disabled issue-delete so this one cannot happen.)
7. When someone manually changes the Epic's Due Date or Start Date, and thus the values are no longer calculated from the child issues

 

Finally, if you need to handle empty / non-empty values for the child issues, a conditional expression could be used when the Epic's existing date values should be retained.

 

Kind regards,
Bill