-
Suggestion
-
Resolution: Unresolved
-
None
-
139
-
15
-
In light of recent updates, Admins can add hierarchies below an Epic in JIRA, which led them to anticipate that the new Epic level would inherit the same functions and features as the old Epic level.
To illustrate, we have the following issue hierarchy:
- 3 Initiative
- 2 Epic (New)
- 1 Story (Renamed Epic issue)
- -1 Task
- 0 Subtask
Currently, features such as the panel in the backlog are tied to the original Epic issue type. The epic name change is not reflected in the backlog when creating an Epic , in reports- cycle time Jira, Sprit insights
This suggestion is to have these features tied to the level named Epic instead of the issue type Epic that exists at level 1.
- is caused by
-
JSWCLOUD-25522 Custom epic issue type is not recognized by the epic panel in the backlog
- Closed
- is resolved by
-
JSWCLOUD-26916 Treat custom epic issue types like a base level (e.g. task, story) issue types in the backlog
- Closed