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

Ranking within the hierarchy levels

My Requirements Hierarchy (from highest to lowest) is (1) Initiative, (2) Epic, (3) Story.

In Portfolio, how does the ranking change based on the level of the hierarchy you are in? That is, if my highest level in the hierarchy is initiative and the initiatives are ranked in priority order, then if I view the next level down - i.e., epics, should I not see the epics in priority order based on the order of its parent initiative?

I want to ensure the epics I work on is based on the priority of the parent initiative.

 

1 answer

0 votes
Roi Fine Atlassian Team Mar 26, 2018

Hi @Edmund Louie,

If a issue has children (e.g. initiative with some epics) then the rank of the parent becomes the rank of its highest-ranked child. The reason for that is that we want to make the parent rank represent what will be done first, if the top story of an epic is ranked last this epic will be scheduled last so it should appear last in the ranking.

Re-ranking a parent issue will re-rank both the parent itself and all of its children.

I.e: Ranking an initiative at the top will cause all of it's epics to get ranked at the top among other epics as well.

Let me know how I can assist further,

Cheers,

What if that doesn't seem to be happening?

i.e. I order my portfolio plan by initiatives and save the changes.

I go to the kanban backlog to see them in that order and the tasks/stories are in the right order but that initiatives are in random places.

It sounds like the initiative should be showing above all its children in the kanban backlog which is what I want, but it's not what I'm seeing.

Any thoughts?

Could it be related to not all the initiatives that exist in the board/issue source are in the portfolio plan? In which case, how do we overcome this?

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