Hello. Anyone knows how do i change the hierarchy of work types ?Currently i have Epic, Tasks and Subtasks. I would like to insert User Stories in between Epic and Tasks in terms of hierarchy but cant seem to be able to do that,
Hi @Kenny Chan and welcome to the community
The default Work item Hierarchy in Jira is:
Epic - Level 1
Story/Task - Level 0
Subtask Level -1
So, Story and Task are both on level 0 and can contain subtasks.
Since you are on Premium you can add levels above Level 1 (Epic) but you can't add additional levels between Level 1 and Level 0.
Best regards,/Staffan
Hello @Kenny Chan , you need to be a Jira admin first. Then go to Work items -> Work item type hierarchy. You can find the full article here: https://support.atlassian.com/jira-cloud-administration/docs/configure-the-issue-type-hierarchy/
Thank you for the welcome Staffan.Currently in my Work Type settings:Story Hierarchy Level 3Task Hierarchy Level 2Epic Hierarchy Level 1Bug Hierarchy Level 0Subtask Hierarchy Level -1I cant edit the Hierarchy Level part although i am an Admin and in the Premium package. Any ideas why the Hierarchy Levels are a bit odd?
Hi @Kenny Chan
Under Settings (cogwheel) -> Work Items -> Work Item hierarchy you need to set Epic to Level 1 'All other standard work types' to Level 0 and Subtask to 'All subtask work types'
That means that:
This is the default setting in Jira so you don't really need to change anything since all other standard types defaults to level 0
I hope this helps,/Staffan
Hi @Staffan Redelius Currently this is what is in my settings.What i am trying to do is make the Story above Task in terms of hierarchy.
This is my current Work Type Hierarchy. Any thoughts if it is possible?
Hello @Kenny Chan ,
It is technically possible to achieve the hierarchy you desire, but the functionality may be a bit different than you expect.
In Jira there is specialized functionality associated with the system-provide item type named "Epic" out of the box. No other issue type at Level 0 will get the custom functionality of being included in the Epics panel of an agile board, or having a default swimlane/grouping available for it.
You can, technically, move the Story work item type from Level 0 to Level 1 (in the Premium plan), which would then enable Story items to be parents of Tasks. With this one change, having Epics and Story at the same level, Epics could not be parents to Stories. However, the Story work items would not then get a special panel or grouping like Epics have. With this one change any parent/child relationships between existing Epics and Stories would be removed, because item types on the same level cannot have a parent/child relationship.
You can, technically, move the Epic work item from Level 1 to Level 2, which would then enable Epics to be parents of Stories. With this change any parent/child relationships between existing Epics and items that remain at Level 0 will be removed, as Jira does not support skipping levels for a parent/child relationship.
I'm actually not sure what happens with the special Epic functionality in the event of this change.
Note that these changes affect all Company Managed projects in your system.
If you want your "Story" item type to have the current special functionality of the native Epic, then you could rename the native Epic work item type. You could then create another standard work item type, name it Epic, and move it to Level 2 to enable it to be a parent to your renamed Epic/Story item type.
@Kenny Chan as the others already answered, this type of hierarchy in Jira is not possible. Even if you have a Jira Premium or Enterprise plan with access to a custom hierarchy, it's still not possible to insert new hierarchy levels below Epic.However, I can suggest a workaround. You can use checklists to add one more hierarchy level below the subtask.
As a result, your hierarchy will look like this:
Epic (1) -> User Story (0) -> Subtask (used instead of Task) (-1) -> Checklist items (used instead of Subtasks) (-2)
Here's an example of what it looks like:
You can add such checklists with the help of our solution, Smart Checklist for Jira.It allows you to use checklists as a substitute for tasks or subtasks. For example, you can:- tag responsible people
- add deadlines
- set custom workflow statuses for each checklist item
- add links, images, and details to the expandable sections below each checklist item
- save checklists as reusable templates and auto-add them to standard tasksI hope this helps!
It looks like you're new here. Sign in or register to get started.
