Can an issue type be NOT included in the issue type hierarchy

[Gregory Hill]

We have a fairly standard issue type hierarchy: Feature -> Epic -> Story -> Subtask, but have a need for an issue type that lives outside the hierarchy but can be linked to a Feature or Epic.  Currently, it defaults to being a child of the Epic (set to hierarchy level 0) I'm guessing because Jira considers it to be one of "All other standard issue types". 

Is there a way to take it out of the hierarchy completely or do I need to put it higher in the hierarchy at it's own level?

Thanks,

Greg

[Trudy Claspill · Accepted solution]

Hello @Gregory Hill 

Welcome to the Atlassian community.

When you say you want to "link" the issue type to a Feature or Epic, you can do that using the generic issue linking functionality, regardless of the level at which the issue type exists. This does not confer the parent/child hierarchy to that relationship.

You cannot have an issue type that can be a "Child" of issue types that exist at other multiple levels. Child issues can be under issue types only at the level directly above the child.

All issue types must exist at some level in the hierarchy. Epics and subtasks have a fixed level. All other issue types by default are "standard" level 0 issues unless you move them to another level.

If you put that other issue type at a higher level, then the issue types at the level directly below it will be able to become its Children.

If that doesn't address your question, please let me know.

[Dave Mathijs · Accepted solution]

Hi @Gregory Hill welcome to the Atlassian Community!

If you don't use that issue type in the issue source of your plan, it won't show up in your scope or timeline. If it is part of your issue source, you can added in the exclusion rules as an issue type to exclude.

If you need it in your plan though, then it will always appear under the Epic it's linked to. If it's not linked to an Epic, it will show up below as an issue without a parent.

I wouldn't put it higher in the hierarchy at its own level though since it's not part of it.