Ability to have an epic be a single source of truth?

[Stephen Weaver]

In our projects, Epics are the single source of truth, and they are the tickets that are most consistently updated.  We then pull pieces of that epic into Stories and Tasks.  This can cause issues when the Epic is updated, but the underlying stories are not updated.

I'm wondering if it is possible to have Tickets associated to an epic programmatically pull information from the Epic.  So let's say you have an Epic with three stories under that Epic.  In my mind, you would somehow tag the information you wanted on each story from the Epic, and then that info would flow to the story.  And if the Epic were updated, then the associated story would update.  Is there any addon or functionality that attempts to solve this issue?

Thanks!

[KJ]

Automation for Jira can do most of what you are asking and the good news is that it will soon be an integrated part of Jira Cloud. 

You would define a Trigger (Epic is updated) and within the configuration you would determine what field values would be copied to the linked Stories. 

More info here: https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/