How to allow Feature Tasks to be part of Hierarchy?

Question

Hello friends,

We are using JIRA premium cloud and In my organization we already have a hierarch set up as below:

Now, we have introduced "Feature Tasks" as an issue type which are also used as a separate task by testing team.

When testing team identifies a bug during SIT they want to link that bug as a child to Feature tasks. However as per above Hierarchy they can only assign the bug to Story/Feature. How do I enable them to be able to add bugs as child issue of Feature Tasks.

When I try to add Feature Task at same level as Feature - I get the alert that 400+ issues would be impacted and I can not proceed.

Please help me with way forward.

Ugnius Aušra · Accepted Answer

Hello @Anshuman Ankur

Welcome to Atlassian community!

Well there's two options to this situation.

From my side i would recommend you to create another level between Feature and Story.

Then you could link Story/Tasks/Bugs to Feature Task.

There's also option, to make Feature Task to Feature Hierarchy level, but i wouldn't recommend, since it's gonna impact a lot of tasks. (It's not gonna broke then, but link is gonna be re-evaluated)

Trudy P Claspill · Accepted Answer

Hello

Welcome to the Atlassian community.

For the hierarchy a parent/child relationship can exist only between issues at adjacent levels. The relationship can't skip over levels.

What level does the Bug issue type currently sit at?

What level does the Feature Task issue type currently sit at?

The Bug issue type can be a child only of the issue types at the level directly above its current level. If Feature Task is not in the level directly above the Bug issue type, then one of the other issue type has to be moved to the appropriate level to support creating a parent/child link between them.

How are you being blocked from proceeding with your change?

If you move an issue type from one level to another that will break any parent/child relationships between issues of that type and other issues. The warning is telling you that there are that many issues of that type that could have parent/child relationships that will break.

So, for instance, if you have an issue type at the "Story" level and you move it up to the "1 Feature" level, that issue type can no longer have children from the Sub-tasks level, and it can no longer have a parent at the "1 Feature" level. If any of the issues of the moving issue type have such a relationship, it will be removed.

And since this is a global setting it will affect all projects using the moving issue type.