Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,456,505
Community Members
 
Community Events
176
Community Groups

How to associate Epics with a new hierarchy level above Epics?

Deleted user Feb 06, 2019

Given that Portfolio can only do Epics at the Epic hierarchy level, and that I can only *create hierarchy/scaffolding above epic level, how would I associate Epics to the "new hierarchy" of something like MVPs>Features>Epics>Stories please?

And thank you.

*Reference:

https://confluence.atlassian.com/jiraportfoliocloud/how-to-create-a-new-hierarchy-level-in-portfolio-for-jira-941618926.html 

2 answers

Our current Portfolio Hierarchy as follows Initiative--> Feature--> Epic--> Stories can create Hierarchy as Initiative(Custom issue Type) -->Epic--> Feature(Custom issue Type)---> Story .In the current set I am able to create another level above Initiative rather we wanted to have another level after epic. Please advise

Hi. I solved this by considering the jira epic as a general grouping mechanism for e.g. stories, and then using my own issue type (here e.g. "portfolio epic") on top of it. 

Practically in the system admin interface "Add-on" tab, the Portfolio hierarchy looks like this:
1. (new) Portfolio Epic
2. (new) Capability
3. (new) Program Feature
4. Epic
5. Story
6. Sub-task
..but the picture says it better. Hope this helps. -Blaisehierarchy2.png

Deleted user Feb 07, 2019

Thank you Blaise, I appreciate the insight - did you create the new issue type in jira proper so it would propagate forward to portfolio, then assign the hierarchy within portfolio, or did you create the issue type portfolio-side  and inject it into the a new hierarchy as the procedure suggests, please?

If portfolio-side only does that mean maintenance of portfolio epics is done only on the portfolio side with no visibility within regular jira reporting?

Appreciate your insights and practical experience with portfolio.

Jeff

I created the new issue type "portfolio epic" in Jira , and then used it in the hierarchy within portfolio.

In my case, I also use a specific JIRA project for the Portfolio Layer, containing issues of type "portfolio epics". I then added the "structure" add-on to create a portfolio hierarchy across many JIRA projects (this is documented elsewere), but this is optional. If everything is one single JIRA project, then your new issue types and the proper "Portfolio" hierarchy works.

Enjoy - Blaise 

Like Caron Saul -Entier- likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events