We're exploring changing the name of the Epic issue type to Feature, so our features will function as epics and we can create a new Epic issue type (that functions as a story) above Feature in the hierarchy. The issue type hierarchy will look like this:
- Initiative
- Epic
- Feature (as "Epic" class issues)
- Story
- Subtask
I read a response in a blog here that this change will cascade to filters and automation in Jira, but not to third-party apps. With that understanding I have a few questions:
I am assuming that is the case for ScriptRunner, could someone please confirm? Is there a way to identify the scripts that use the Epic issue type in the library that will need to be adjusted to use the newly named Feature type instead of Epic?
If anyone has ideas on how to lesson the impact to the third party apps they would be greatly appreciated.
Thanks!
-Scott
