Epic Rollup Dates from Child Issues

[Alex Suterlowe]

I am trying to follow the instructions detailed in the following post solved by @Trudy Claspill . My goal is to get an Epic to copy the earliest Start Date and last Due Date of its child issues. Following the instructions in this post I can get the Start Date working but when I copy branch for Due Date it doesn't work. Any ideas what I could be missing?

https://community.atlassian.com/t5/Jira-Software-discussions/Set-Epic-Start-and-Due-Date-to-earliest-latest-Child-Dates/m-p/2353100#M20046?utm_source=dm&utm_medium=unpaid-social&utm_campaign=P:online*O:community*I:social_share*

[Bill Sheboy]

Hi @Alex Suterlowe -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

You can also do this with a single Lookup Issues on the child issues, and then use the min and max functions on the dates.  For example:

{{lookupIssues.Start date.min}}

{{lookupIssues.duedate.max}}

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#list.max

Kind regards,
Bill

[Alex Suterlowe]

@Bill Sheboy Thank you for the advice. Image of the rule attached. 

[Bill Sheboy]

Based on the rule you are showing, the JQL is checking "Parent Link" when I believe you want to use "parent" instead. 

I believe the "Parent Link" field is used with advanced roadmaps when the hierarchy has been modified: https://confluence.atlassian.com/jiraportfoliocloud/searching-for-portfolio-for-jira-custom-fields-in-jql-941619014.html

Next, your first JQL is returning with ORDER BY "Start Date" ASC.  In that case, the value to use from the lookup is the first one: {{lookupIssues.first.Start date}}

Your second JQL is returning with ORDER BY "Due Date" ASC.  In that case, the value to use is the last one: {{lookupIssues.last.duedate}}

How do these compare to what your edit actions are doing?

Finally, you can simplify this with the one lookup issues action I noted, using min and max functions.  The key would be removing the checks on the dates from the JQL.

• trigger: field change for Start Date or Due Date
• condition: issue is not epic or subtask
• branch: to parent
  • action: lookup issues to gather the child issues
  • action: edit to update both fields in one step