Hierarchies and Customization of Issue Types in Jira: Is It Possible with an Add-on?

[Eduardo]

I'm wondering to implement a customized structure somthing similar to SAFe 6.0, where I want to create specific hierarchical levels such as change the Epics to "Features" or "Capabilities," even if they are "Enlaber-type".

But also, define normal and enabler-type Stories, in addition to establishing different types of subtasks (focused on frontend, backend, etc.), we would need a high level of customization that Jira does not natively allow.

However, is it possible to achieve this through some add-ons from the Atlassian Marketplace, which allow me to customize hierarchies, issue types, iconography, and the names of each type of element?

EXAMPLE:

• Epic
  • Enlaber Capability (Feature)
    • Enlaber Story
      • FrontEnd (subtask)
      • BackEnd (subtask)
      • UX (subtask)
      • UI (subtask)
      • Functional / BA (subtask)
      • etc.
  • Capability (Feature)
    • Story
      
      • FrontEnd (subtask)
      • BackEnd (subtask)
      • UX (subtask)
      • UI (subtask)
      • Functional / BA (subtask)
      • etc.

 I clarify that, although I do not fully agree, it is the client's requirement.

[Wilson Sheng · Accepted solution]

Hi @Eduardo , this is Wilson from Hierarchy for Jira. 

I understand your need to implement custom structure similar to SAFe 6.0. 

Hierarchy for Jira is an add-on that can help you achieve the issue structure you mentioned above. 

You can easily create your own issue types like "Feature" or "Capability" and add your prefer icons on them. Then, you can easily custom-build issue hierarchies by linking issues and define different types of Stories and Subtasks to match your specific SAFe implementation. 

Hope this helps :)

[Leonhard Molitor · Accepted solution]

Hey @Eduardo

Your configuration already looks really great. We also offer options for mapping SAFe 6.0 as well as possible for Jira Cloud.

For example, you can use our Jira add-on Agile Hive to configure your own SAFe hierarchy based on Jira projects in an additional view and link them together in teams, ARTs, large solutions and portfolios:

You can also see the hierarchy of issue types that you mentioned; these are displayed on the issue itself in a separate area and have their own links:

You can either test the Agile Hive add-on free of charge for 30 days via the Atlassian Marketplace or, if required, we will be happy to provide you with a slightly longer instance for testing. Just let us know!

Best
Leo

[Eduardo]

Hi Leo,

Thank you so much for taking the time to review my configuration and for suggesting Agile Hive as a solution for implementing SAFe 6.0 in Jira. The ability to map hierarchies and link teams, ARTs, and portfolios sounds very promising, and I’ll definitely give the tool a try.

I’ll take advantage of the 30-day trial to explore whether it meets my client’s specific needs. If we find that more time is necessary, I’ll reach out to arrange an extended instance, as you kindly mentioned.

I really appreciate your support and assistance. I’m looking forward to seeing how Agile Hive can help us build an optimal structure in Jira!

BR,
Eduardo

[Marc - Devoteam · Accepted solution]

HI @Eduardo 

You can re-name the Epic issue type, but you can't create an issue type like an Epic.

It is also not possible to add an issue type in the hierarchy of plans within Jira.

You can create new issues types on Story Level and Sub-task level.

[Hannes Obweger - JXL for Jira]

Hi @Eduardo,

I think you'd like 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 range 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. As issue links can be established between any pair of issues, you have full flexibility over the hierarchies you want to model.

This is how it looks in action:

This is an Objective - Program - Initiative - Epic - Base-task - Sub-task hierarchy - but you can model whatever hierarchy works for you.

Issue hierarchies can also be combined with JXL's other advanced features, such as issue grouping by any issue field(s), sum-ups, or conditional formatting.

Any questions just let me know,

Best,

Hannes

[Rahul_RVS]

Hi @Eduardo 

You can create different issues types in Jira and then link them through issue links. However you would need an app to view them in a hierarchy. If you would like to try out an add-on for this use case, pls take a look at 

Issue Hierarchy 

The app shows your issue hierarchy in a tree view created through Issue Links. The Issues in the tree can be in multiple projects and the app will pull out each one of them and show you a structured hierarchy. You can also filter specific linked issues as per your requirement. As you can see in the screen grab below, we have created an issue type Initiative at the top level.

The app has multiple other features which are very useful in project tracking and management. 

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

[Teresa_DevSamurai]

Hi @Eduardo

While Jira doesn’t support this level of customization out-of-the-box, there are add-ons in the Atlassian Marketplace, like TeamBoard ProScheduler that can help.

This tool lets you create custom hierarchies, so you might want to give it a try.