How to add a Capability level between Epic and Initiative?

Darlene Ciarcia November 9, 2017

We had created the Initiative layer and have been using it without issue. However, now we would like to add a layer between Initiative and Epic called Capability. 

It is pretty simple to add the Capability layer in Portfolio, but it breaks the existing hierarchy.  We started with:

Initiative

Epic

Story

 

Now we have added:

Initiative

Capability

Epic

Story

 

The problem is that we want both Epics and Capabilities to be able to link to parent Initiatives and that doesn't seem to work. So, with a Capability layer inserted between Epic and Initiative, we are forced to only link Epics to Capabilities but we cannot link Epics directly to Initiatives.

If we don't add the Capability layer and instead add Capability to the Initiative Layer then Epics can link to both Initiatives and Capabilities BUT Capabilities cannot have an Initiative as a parent. 

Is there a way around this problem? 

2 answers

1 accepted

1 vote
Answer accepted
Thomas
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 9, 2017

Hi @Darlene Ciarcia,

 

The Portfolio hierarchy is not made for this use case and skipping a level is currently not supported. I would suggest replacing your Initiative level with either Themes (https://confluence.atlassian.com/jiraportfolioserver/themes-report-816527579.html), Jira labels or components that would work regardless of the issue hierarchy.

If you want to maintain Initiative as a hierarchy you would currently have to duplicate it as a capability which would work with Portfolio but not well for Jira filtering.

 

Let me know if that would work for you!

 

Cheers,

The Portfolio for Jira Team

0 votes
Theresa McFarlane October 28, 2021

This is not supported in 2021. You need to see Jira Align which is made for SAFe.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events