You can automate that, if you like. Here is an example of an automation rule to update the due date of an epic if one of it's child issues due date is later than the current epic's due date:
When an issue's due date is updated, it looks up the issue's parent Epic and compares both due date. If the issue's due date is later than it's epic's due date, it will adjust the epic's due date accordingly.
You can obviously extend that same principle for the start dates.
This setup will obviously work for future updates. So for a clean start, you should make sure that epics with existing issues in them are aligned first. As from them, you have a system that is being kept up to date automatically.
Hope this helps!
Hello @GuillaumeJolly ,
Maybe smart values will help you in finding the solution.
Please check these 2 links.
Gents, Thanks a lot. I had a mistake in my variable and found the debug page very useful.
All working now. I love Zero Code!
Because I am a total newbie in Jira Automation, I also found this link very useful:
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events