Is it possible to have hierarchy levels on the level?

[Ashley Roberts]

I have a user who wants to be able to have the hierarchy to be able to fan out under feature? As shown in this screenshot:

[Danut M _StonikByte_]

Hi @Ashley Roberts,

Try the Work Breakdown Structure (WBS) gadget offered by our Great Gadgets app.

This gadget can display the issues from a filter / JQL in a tree structure, in form of Initiatives > Epics > Stories > Sub-Tasks along with their status. 

 

All you have to do is to configure this gadget to use a filter / JQL that returns the issues to be grouped and it will display the hierarchy for you.

Hope this helps. 

Danut

[Aron Gombas _Midori_]

@Ashley Roberts I don't think that this is supported.

There could be creative workarounds like introducing an issue type that covers both "sub-types" and using an additional custom field which specifies the exact type.

For example, the issue type could be "Epic or Improvement" and have a selection custom field "Precise type" with two options "Epic" and "Improvement. Or a boolean "Epic?". Or use labels. Or something. :-)

[Simon Carroll]

I believe that is possible to replicate through Jira issue hierarchy for Advanced Roadmaps

[Hannes Obweger - JXL for Jira]

Hi @Ashley Roberts

unless I'm missing something this should totally be possible in Advanced Roadmaps; you should be able to simply map both the Epic and the Improvement issue type to the Epic hierarchy level. This is how this looks on my Cloud site, but it should look the same in Server/DC:

Note how there are multiple issue types mapped to the Epic level.

Is there any reason why this wouldn't work for you?

Best,

Hannes

[Ashley Roberts]

Hi Hannes,

Sorry I am new to Advanced Roadmaps, and I am too still learning about how to use them. My understanding is that if I do your suggested change would that effect anyone else using Roadmaps?

The following is how we have got it currently setup:

So, I would just need to add Improvement to the Epic under Jira Issue Types and that will work as you have shown in your screenshot?

[Hannes Obweger - JXL for Jira]

Hi @Ashley Roberts

you are correct that any changes to this hierarchy configuration will impact your entire site, and any plans that exist in Advanced Roadmaps. You definitely want to discuss this with whoever is in charge of your Jira site!

Apart from these possible side affects, I believe that you should be able to map the Improvement issue type to the Epic level (so that both the Epic and the Improvement issue types are listed on the Epic level), and model your other levels/issue types above the Epic level. (I don't have a Server/DC-version of Advanced Roadmaps available to be 100% certain.)

But again, please definitely be cautious of making any changes here, as it will impact your entire site.

[Hannes Obweger - JXL for Jira]

Also @Ashley Roberts

just as food for thought: If you want to have greater freedom in modelling your hierarchies without impacting all other users, there are options available on Atlassian Marketplace. E.g., my team and I work on an app in which you can model as many hierarchies as you want, JXL for Jira. Happy to elaborate if this is something that might be of interest to you!