Defining a Jira issue type that can be a child of Feature and Epic

Question

I've defined a Issue type hierarchy as follows:

Feature -> Epic -> The rest -> subtask

Among "the rest", there is the "Bug" type.

I would like to define the "Bug" type as being able to have either an Epic or a Feature parent.

So a hierarchy like this:

Feature -> Bug , Epic -> The rest + Bug -> subtask

The only way I found was to duplicate the "Bug" type into "Bug (feature)" and "Bug (epic)" which isn't really convenient.

Feature -> "Bug (feature)",Epic -> The rest (including "Bug (epic)") -> subtask

Is this possible to have an Issue Type placed under different parents in the hierarchy ?

Hannes Obweger - JXL for Jira · Answer

... and to expand on my last point: If you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) issue hierarchies. These issue hierarchies can be based on Jira's built-in parent/child relationships (like task/sub-task, or epic/story), and/or based on issue links of configurable issue link types.

This is how this looks in action:

I'm using a slightly different hierarchy here, but yours would be easy to model, too. Sub-tasks and "sub-bugs", in this example, are connected to each other via issue links.

Hope this helps,

Best,

Hannes

Hannes Obweger - JXL for Jira · Answer

Hi @LV

as suggested, this isn't really possible in Jira's built-in issue hierarchy model.

The only way that I can think of is to use issue links. Issue links can be established between any pair of issues, regardless of the issue hierarchy - meaning that you have full control over which relationships you want to establish.

The downside is that Jira doesn't recognise issue links as parent/child relationships, meaning that you won't get a lot of hierarchy-related features, if any. This being said, if you're open to solutions from the Atlassian Marketplace, there are apps that can help with this. I'll add more information below.

Hope this helps,

Best,

Hannes

Trudy P Claspill · Answer

I don't know of a more efficient way, particularly since you have only two types of interest.