nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Adjust epic due dates to initiative

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!

Accepted answers

All comments

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

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

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.

Thank you! now it is working

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud