Introduction
Managing issue hierarchies effectively is crucial for successful Agile implementations, particularly within frameworks like SAFe. This article addresses a common challenge regarding Jira Issue Type hierarchies, specifically the desire to modify the level of an Epic. We’ll explore a practical solution for achieving this within the Jira Cloud environment.
Jira Issue Type Hierarchy and the Feature Level
Our team utilizes a standard hierarchy: (Initiative/Objective/Project) > Epic > Feature > Story > (Task/Sub-task). Currently, we’re seeking a way to introduce a higher level within the Scrum board backlog for Features. Within Jira Cloud, direct adjustments to the Epic level are unavailable, appearing greyed out. A temporary workaround involves creating a new Epic version labeled “SAFe Epic” and either moving Features to this level or establishing a secondary Feature issue type iteration.
A Recommended Solution
Fortunately, there’s a viable alternative. James Woyciesjes suggested renaming the default “EPIC” issue type and creating a new one at a different level. This approach avoids altering the inherent Jira semantics. For example, renaming “EPIC” to “XYZ” would not change how the system recognizes it as an Epic within boards. However, the renamed issue type would no longer be treated as an Epic.
Conclusion
By renaming the native “EPIC” issue type and introducing a new one at a higher level, teams can effectively manage their Jira Issue Type hierarchy and accommodate the need for a level 1 within the Feature hierarchy, improving backlog organization and Scrum board functionality.
Source: https://community.atlassian.com/forums/Jira-questions/Adjust-Jira-Issue-Type-Hierarchy-so-that-you-can-change-the/qaq-p/2894166
Leave a Reply