Can epic start and end date linked to its child issues' start date and end date in Roadmap?

[Verena Law]

Like portfolio, the epic's date is correlated to its child issues' dates. 

For example, if I set an epic with 2 child issues:

Issue A which starts and is done in sprint 1 (11/28/2018 - 12/3/2018)

Issue B which starts in sprint 1 and is done in sprint 2 (12/4/2018 - 12/10/2018)

In the Roadmap, can the epic start date be automatically updated as 11/28/2018 and end date as 12/10/2018, instead of changing manually? 

[Jack Brickey]

As Bryan eluded, natively this is not the way it works. I raised this to Jason Wong (cloud PM) in the recent AMA he created. I provided a bit of feedback on how it should work. I have not opened a suggestion and unsure if anyone has as yet. If so inclined you may wish to research this on JAC

[brbojorque]

In theory you can use ScriptRunner to achieve this behaviour by utilizing the listener feature. 

I may be wrong but I think there is some sort of built in automation under the hood of epic but I haven't really looked into it.

Every time an issue is created, the due date has been updated and issue has been linked to the epic it will trigger the psuedo-code in order.

• Find the issue
• Find the epic of the issue
• Find the issues linked to the epic
• Collect the due dates from all the issues inside the epic
• Calculate the earliest due date and the latest due date
• The result will determine the start date and the due date of the epic
• Update the start date and the due date of an epic
• Win!

That being said, there might be an add-on to implement this but its just a rough idea.