Automation to update Parent Epic from Child work items

[Rich Allen]

Hi all,

I know there are an array of different solutions to this question but I can't get a working version, wondering if there are Smart Value deprecations taking place.

Scenario

When an Epic child work item has a Start or Due Date entered or updated, the automation updates the parent Epic with the earliest Start date and/or latest Due date from amongst the child work items, which may exists across multiple Sprints.

WHEN Due Date field update

IF Parent Exists 

--> Branch - FOR Parent IF Parent is Epic

THEN Edit Work Item - Set Due Date using Smart Value

Current Outcome

When I test my trigger it flows and identifies the Epic correctly, I have verified this by adding labels using the 'Additional Fields' section.

Current Problem

The Smart Values I'm using are not finding the Start Date and Due Date to do the update.

I have tried existing solutions below, but with no success

Due Date = {{issue.children.sprint.endDate.max.jiraDate}}

Due Date - {{issue.children.sprint.last.endDate.jiraDate}}

Due Date - {{lookupissues.dueDate.max.jiraDate}}

Due Date - {{lookupissues.sprint.max.endDate.jiraDate}}

Due Date - {{lookupissues.sprint.endDate.jiraDate}}

What concerns me is that neither of these sets of properties exist in the Smart Values Automation reference.

Automation smart values - issues | Cloud automation Cloud | Atlassian Support

Thanks in advance, look forward to putting this issue in the rear view :-)

Rich

[Bill Sheboy]

Hi @Rich Allen 

As you note, this is a commonly asked question and the solution approach depends upon what version of Jira you are using: Cloud, Server, or Data Center.

For Jira Cloud, use the Lookup Work Items / Issues action with JQL to gather the child items, and then use the min and max list functions to get the dates needed.

For Server or Data Center, the lookup does not support those fields yet.  A workaround is to use the REST API to gather the child items and then use the list functions on the web response.  That approach is described here:

https://community.atlassian.com/forums/Jira-articles/How-Can-I-Sum-Up-Multiple-Issues-into-a-Parent-Number-Field/ba-p/2882712#M16701

Kind regards,
Bill

[Alexander Hohmann]

Have you tried with "issue.duedate" instead?

[Alexander Hohmann]

I just found this set of examples in an older post:

https://community.atlassian.com/forums/App-Central-articles/Jira-Automation-rules-for-due-dates-5-examples/ba-p/2408969

[Rich Allen]

Thanks Alexander, a useful link for sure.
My scenario isn't solely setting dates, I have already implemented similar. 

I need to look through ALL child items of an Epic when one of them has a Due Date updated, and pull out the latest Due Date, whether that is the child item being updated or not and update the parent Epic Due Date