We have a request to modify the Work type hierarchy.
In summary the team is asking to add a hierarchy level for features between Epic and Story.
We want to know first is this possible, and second what would this change impact? (Boards, etc)
L4- Initiative
L3 - Solution
L2 - Epic
L1 - Feature
L0 – Story (All other Work Types)
Hello @Scott McDonald
First I want to mention that modifying the hierarchy in this manner is available only if you have a Premium or Enterprise subscription.
It is not possible to truly "insert" a level between the current L1-Epic and L0-standard items. But here is what you can do.
1. Rename the current work item type "Epic" to "Feature". At that point all the behaviour and functionality associated with the native epic type is applied to the "Feature" type.
2. Create a new standard work item type named "Epic". To avoid confusion you might want to give it a slightly different name, though, so that your users don't expect the original epic functionality to apply to this new work item type. You have to create a new work item type for this because it is not possible to move the native Epic type to a different level.
3. In the Work Item Hierarchy configuration screen add a new level above L1 and add your new "epic" item type to that new level.
Repeat steps 2 and 3 for Solution and Initiative, adding a level above L2 for Solution and then above L3 for Initiative.
Work Item names are global in Company Managed projects. Changing the name of the current Epic item to Feature will affect all Company Managed projects that use that issue type. It also changes the name of the "Epics" panel and the Group By and Filter options that previously said "Epic".
Changing the Work Item Hierarchy is a global impact for Company Managed projects. Adding new item types and new levels for L2, L3, and L4 will only impact projects that use those work item types. If the projects don't use those work item types then they will not be affected.
If those work item types already exist and are in use and you change the level at which they reside, that will affect any project already using them. It would also break parent/child relationships that involved those work items types.
Hi @Scott McDonald,
In short:
Just keep in mind that this update will be applied across your entire Jira instance.
Hope this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.