Adjust epic due dates to initiative

[tpedriel]

Hello, 
Is there a way to create an automation for initiatives that works as follows:

Pick the minimum start date of linked epics and the maximum end date of linked epics, and assign those to it's respective Start Date and Due date of the initiative.

This is how we are linking the "hierarchies":

--> Initiative

----> Epic

------->Story/Bugs/Tasks

This is where I left but I can't solve it:

I will appreciate any help!

[Bill Sheboy]

Hi @tpedriel 

From what you described, you could use a Lookup Issues action (instead of the branch) to gather the child epics: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues

And then use the min and max functions on the group to set your fields.  For example:

{{lookupIssues.Start date.min}}

Kind regards,
Bill

[tpedriel]

Hello Bill, thank you for your answer.

I'm having troubles with creating the automation rule.

This it the automation (I've only tested for the start date):

Here the initiative I'm testing:

But apparently there is an issue with the lookup:

Do you know Why I'm failing?

Thanks

[Bill Sheboy]

You appear to have 2 Lookup Issues actions, and you do not need the second one.

The first lookup will find all of the issues linked to your epic.  And then in the edit you just use the expression I suggested: 

{{lookupIssues.Start date.min}}

That will find the earliest Start Date within the looked up issues.

[tpedriel]

Thank you! now it is working :)

[Bill Sheboy]

Awesome; I am glad to learn it is working! 

Please consider marking this question as "answered"; that will help others with similar needs find solutions faster.  Thanks!

[Dani Miles]

@bill 

I am having an issue with this as I am getting an error with the lookup issue in linkedIssues({{issue.key}}, "Is Initiative of")

I am trying to look for all the Epics below my issue - which is an Initiative, and then change the Start and Due Dates as they are updated. 

Any advice?

[Bill Sheboy]

Hi @Dani Miles 

As this is an older thread, I recommend creating a new question, and perhaps adding a link to this one.  That will ensure the maximum number of people see it to offer suggestions. 

When you do that, please include images of your complete rule, the actions / branches using that JQL, and of the audit log details showing the rule execution.  Those will provide context for the question and symptoms.

Back to your question..

To connect your Initiative and the child Epics, are you using the Parent field or issue links?  The original question in this thread used links, but the built-in Parent field is used for hierarchy changes to add a level, such as for Jira Premium and Enterprise licenses.

Kind regards,
Bill

[Dani Miles]

Hi @Bill Sheboy 

I'm sorted. Was being stupid not thinking about Parent field. This JQL worked for me:- 

issuekey in portfolioChildIssuesOf({{issue.key}}) AND issuetype = Epic

Thanks!!

Dani