How can I automatically set an Epic’s due date based on the farthest due date of its User Stories in

[Bachir AMMACHE]

I have an Epic with multiple User Stories, each with different due dates. The due dates for the User Stories are inherited from their associated Sprint's end dates (via automation as well)

What I would like to do is have the Epic’s due date automatically inherit the due date of its farthest User Story, meaning the latest due date of all the associated User Stories.

Does anyone know how to automate this process in Jira, so that when the due dates of the User Stories are set (via Sprint end dates), the Epic automatically updates its due date to reflect the farthest User Story due date?

[Bill Sheboy]

Hi @Bachir AMMACHE -- Welcome to the Atlassian Community!

First thing, this scenario is a commonly asked question.  I encourage you to search the community posts to find similar ones that already have suggested answers.

Doing that, you would learn this scenario cannot be solved with a single automation rule.  Instead consider how accurately you want the Due Date value in the Epic to be as that will determine how many rules are needed and their triggers.  For example, these events could lead to updating the date field:

• When a new child issue is added to the Epic, gather all the children (e.g., using the Lookup Issues action) to find the new, latest date (e.g. using the max function: {{lookupIssues.duedate.max}} )
• When the Due Date is changed in the child issue of an Epic...
• When a child issue is removed from an Epic...
• When a child issue is moved from one parent Epic to another...(update both)
• When a person manually changes the Due Date in an Epic, set it back to the automatically determined value
• etc.

Kind regards,
Bill

[Harrison Ponce]

Hi @Bachir AMMACHE ! This is a great question!

One way you can solve this is with automation comparing the due dates. Would something like the following work for you? Of course you can add other IF statements like to check if it is in an active sprint, for example.

[Bachir AMMACHE]

Thank you so much for your reply , but it didn't work :(

That is what it is giving me (MPT-1766 is my epic)

[Harrison Ponce]

Can you send a screenshot of your automation rule and verify what the current values are for your story and parent Epic?

[Bachir AMMACHE]

I’ve attached a screenshot of my automation rule, which follows all the steps you provided. Additionally, I’ve included screenshots of my User Story details, showing that the Due date is inherited from Sprints, as well as a screenshot of my Epic view, where no changes are occurring for the Due date. I’ve also provided a view of my Plan Board for further context.

P.S if needed : the link between issues is done via a "Parent" field as you can see in the details .