ScriptRunner - Scripted field calculated based on parent Epic

[Seth Grandeau]

We track a lot of our data only on the parent epic, including priority and several custom fields. We tried using scripted fields to "show" these values on the child stories. This gets the right value, but we run into the problem of the Jira index not updating, since the story itself did not change, just the scripted field on the story (and the parent epic). ScriptRunner documentation says that this can have unexpected effects and suggests writing a custom searcher. 

I was wondering if others have found ways to get past this limitation in ScriptRunner. 

Scriptrunner also has "Parent Navigators". Can these be used to safely copy data from the parent epic to the child story?

[Kyle Moseley]

I would create a scripted listener that looks for updates against Epic issuetypes then pushes those changes out to child (or epic-linked or whatever). So if you're using a scripted field for each normal field on the Epic, you'll just abandon the scripted fields.

https://scriptrunner.adaptavist.com/latest/jira/listeners.html#_custom_listeners

[Seth Grandeau]

Thanks, Kyle. We may have to go that direction. Our sys admin wanted to stay away from listeners, for peformance reasons, but there may not be any other option. I'm just surprised that there is no way to do this, from within the scripted field.