You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
Now we have added:
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?
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!
The Portfolio for Jira Team