As we know, we can't create a hierarchy between an Epic and the standard issue types or between a standard issues type and a sub-task.
I am wondering what the workaround is to use a Safe Hierarchy such as: Initiative > Epic > Feature > Story > Task
How are people getting around this limitation?
While this isn't possible at the moment, we're currently working on functionality which would enable the practicing of SAFe in Jira. You can read a bit more about it in our announcement blog: https://community.atlassian.com/t5/Jira-articles/Upcoming-Rename-epics-in-your-company-managed-projects/ba-p/1874726
Essentially, once this is rolled out, you'll be able to rename your "Epic" to "Feature", then create a new "Epic" issue type on the hierarchy level above (and "Initiative" above that) to implement a SAFe hierarchy.
While this functionality isn't available yet, we're expecting to roll it out in Q4 2023 - you can keep an eye on progress at the blog post I linked above, as well as on our public roadmap: https://www.atlassian.com/wac/roadmap/cloud/flexible-naming-of-epics??&search=epic&p=c0c344ce-98
I can't speak much to the workarounds that people are using at the moment unfortunately, so I'll leave our other community members to jump in there!
Let me know if there's anything I can help clarify.
Cheers,
Daniel
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.