I want to update the end date of the epic with the longest date of the daughter stories of that epic
If you were on a premium plan, the built-in advanced roadmaps could take care of that for you automatically.
As it seems you are not, automation can help you achieve this as well. In next gen, you can add an automation rule to your project by clicking the lightning icon towards the top right corner of your project board.
Create a rule somewhat along these lines:
It triggers when you add/change the due date of an issue. The create variable action stores the due date of your issue for later comparison with the due date of your epic:
And the part starting with For Epic (parent) does the comparison of both dates and updates the Epic if the new due date is more recent than the Epic's old due date.
To learn more about automation, definitely have a look at the automation template library
Thanks a lot for your instructions Walter, I basic user yet in Jira. We almost made it
I make exactly how do you discribe above, but if my epic has duedate 04/30 and my history1 has 05/05 and my next change has in history2 05/01 the epic change to 05/01 incorrectly..
I need, in this case, that epic duedate will be duedate 05/05
And now, with automatization above, a epic data was 05/01 (my las change)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is a fair observation, which is due to the fact that your data are initially wrong: if your Epic's due date had been 5/05 from the start, the update of your other story's due date would not have an impact on the Epic at all. But since you did not have this rule in place before, your historic data are not correct - obviously.
I do hope you don't have some 1.000+ open Epics currently. I would recommend to go through your open Epics and update the due date of those historic open epics to the due date of the latest story manually.
You can pull a list of all issues in an epic with the following JQL, by the way:
"Epic link" = <EPIC-123> ORDER BY Due DESC
EPIC-123 would be the issue key of any open Epic you want to check. And ORDER BY Due DESC would make sure the issue with the latest due date appears at the top of your list.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks again, your comments helped me learn more about automation
i'm trying to migrate to the premium version where i can use gantt with more quality
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Walter Buggenhout , we are currently on a free trial of Premium plan and I do not see this functionality on Advanced Roadmaps. I have due dates set on my stories - but the roadmap still doesn't show the epic dates accordingly. Am I missing anything here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Walter Buggenhout , I have implemented your automation, but for me the epic due date is not updated. Instead appears the notification as on the image:
I did not change your algorithm. Do I need to do anything else?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Jaqueline Frondola,
Welcome to Atlassian Community!
The Epic date range is currently only manual. It will change if you drag its left and right to adjust or if you change the start and due date. The Epic won't adjust automatically if a child issue, for example, has the due date after the Epic's due date.
There are feature requests suggesting improvements for that:
The best option is to use an Automation rule as Walter mentioned while the features above are not implemented.
Please, click on vote and also watch the features to receive updates
Kind regards,
Angélica
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
thanks a lot Angélica, I am studying the links you commented, thank you very much
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have followed the automation but epic is getting the update based on the trigger child issue whereas the idea to have the epic dates range aligned with the dates range of its child issues.
can you please help ?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.