I would like to change the hierarcy of the issue types appearing in the kanban board.

[Dimple]

Hi, I am using the JIRA as an admin with the kanban board. 

I am not sure which version i am using right now but below is the scenario.

Current: We can create the stories, tasks and bugs under the epic. And we can create only sub-tasks under the story.

Epic-> Story/Bug/Tasks

Story-> Sub-tasks

Expected: I want to create only stories under epics, And tasks/bugs should be created under story and then sub-tasks can be created under story.

Epic-> Stories

Stories-> Tasks/Bugs

Tasks-> Sub-tasks

Can you suggest me if i can make the changes to edit the hierarchy level of issue types that're having currently to the expected one?

[Amay Purohit_RVS]

Hi @Dimple  , 

Welcome to the coomunity !!

You can use Issue Links to create a custom Hierarchy which will not impact your current project structure. If you would be interested in an add-on for this need, you can try out our plugin.

Issue Hierarchy 

The app shows your issue hierarchy in a tree view. The app can help you easily Sum up values (time tracking/story point/custom numeric fields) to see overall progress for your Issues at each parent level. Also it provides excel like editing for all the values right on the report and see real time progress updates. 

Do give it a try.

(Disclaimer: I work on RVS, the vendor for this app)

[Danut M _StonikByte_]

Hi @Dimple,

What you could to is to configure your project(s) to allow only Epics, Stories and Sub-task (so disable Bug and eventually Task issue types for your project).

And then, add a new sub-task issue type named "Bug". It might not be possible to use this name, because a parent issue type "Bug" already exists in the system. If so, named it "Sub-Bug" or "_Bug_".

This way you project will use the structure you want: Epic > Story, Task > Sub-task, Sub-Bug

Hope this helps.

Danut.

[Trudy Claspill]

Hello @Dimple 

Welcome to the Atlassian community.

It is not possible to change the hierarchy levels in that manner with native functionality.

The native hierarchy of Jira is

Epic
|-- standard level issue types (i.e. Task, Story, Bug)
    |-- sub-task level issue types

It is not possible to insert a level between "standard" and "sub-task".

You could use generic issue linking functionality to artificially indicate, through links, that you consider Tasks and Bugs to be "children" of Stories, but Jira will not recognize that as a parent child relationship.