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,707
Community Members
 
Community Events
176
Community Groups

How story rank is affected when re-ranking an epic

We have a list of >150 epics (most of them containing stories) that we are weekly (re-)ranking in Portfolio v2.x.

The main issue we're facing is that - when changing the epic ranks - the story ranks don't get updated the way we want them to be.

What I found out is:

  • Rank epic A down under epic B means JIRA/Portfolio re-ranks all stories of epic A under the highest ranked story of epic B.
    Note: this is not the behaviour we expect, because we would like ALL stories of epic A to be ranked under the lowest ranked story of epic B.

    Likewise for ranking up: 
  • Rank epic A up above epic B means JIRA/Portfolio re-ranks the highest story/ies of epic A above the highest ranked story of epic B, but not all.

The problem with this is that the scheduling gets distorted.

Consider this example:

  • We have 2 epics: epic A with stories A1 and A2, and epic B with stories B1 and B2.
  • Assume that epic A was ranked above B originally, so the stories would be ranked A1 > A2 > B1 > B2
  • If I now rank epic A below B, then the ranking will be B1 > A1 > A2 > B2.
  • As a consequence, when calculating the scheduling, epic B will only be completed after epic A, because of the lower ranked story B2.

We have this issue with hundreds of stories, so looking for an elegant way to solve this. Manually dragging all stories to the correct rank upon changing an epic's rank is not an option for us.

 

Grateful for your feedback or thoughts on this!

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events