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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

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

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

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

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Advanced Roadmaps

Introducing Advanced Roadmap’s new dependency report

To see this feature in action check out our recent dependencies demo here: https://www.youtube.com/watch?v=eQu5VsUqyZA Keeping on top of your dependencies is a key part of ensuring project success....

150 views 2 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you