How to configure work item type hierarchy to support the SAFe framework?

[Jay McKelvey]

I have a desire to configure my Jira instance to follow the SAFe framework hierarchy (see below).  I've seen multiple articles about how to configure hierarchy, but the problem seems to be that in Jira Epic is always level 1 and User Stories always level 0.  There is no way to put a work type in the hierarchy between the two.  Is anyone using Atlassian and the SAFe framework who has figured out a solution to this?

Epic (Portfolio)

└── Capability (Large Solution, optional)      

└── Feature (Program)          

└── User Story (Team)                

└── Task / Sub-task (Execution)

[Walter Buggenhout · Accepted solution]

Hi @Jay McKelvey,

Rename both your Epic work type and the corresponding hierarchy level to Feature. Then add Capability and a new work type that you call Epic and map those last two to the hierarchy levels above epic in the work type hierarchy.

Just be aware that this will apply to your entire Jira instance and that it will rename the epic panel in your boards to feature panel everywhere as well.

Hope this helps! 

[Jay McKelvey]

Thanks @Walter Buggenhout   This makes sense.  I'm a little concerned about overly customizing the configuration that might cause me a problem in the future due to a currently unknown complexity.  I'd be curious if you or anyone else out here has real experience implementing the SAFe hierarchy in Atlassian and any lesson's learned from an implementation?   I would think it would be pretty common as both SAFe and Atlassian are leaders in Agile Software development.  

[Daniel Franz - JXL]

Hi @Jay McKelvey 

I'd second Walter's approach here.

There are certain semantics associated with work item level #1 (by default called "Epic"), e.g. in how such work items are displayed in the Jira Software backlog view, etc. So while it is possible (and not uncommon) to rename level #1, just be mindful that it may become confusing to others if you create another hierarchy level - e.g. a level #2 - and call this other hierarchy level "Epic".

Just as food for thought, another way to implement the exact hierarchy you are looking for is via work item linking. Work item links give you full flexibility in how you can model your hierarchy, and unlike Jira hierarchy configuration, don't globally impact your whole site.

The downside is that work item links aren't natively recognised as parent/child relationships, so you won't get a lot of hierarchy-related features out of the box. This being said, if you are open to solutions from the Atlassian Marketplace, there's a number of apps available that you can use to configure customised work item hierarchies.

E.g., this is how your hierarchy could look in the app that my team and I are working on, JXL for Jira:

In this example, Features and Stories are connected to each other via "is parent of" / "is child of" work item links, and the work is visualised in a custom structure.

Any questions just let me know.

Cheers,
Daniel

[Jay McKelvey]

Thanks so much @Daniel Franz - JXL   this is supe helpful.