Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

×
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

Does moving items on Portfolio for JIRA change the Rank value like a Scrum board does?

I was having trouble finding this, so I thought I would ask; does moving items on Portfolio for JIRA change the Rank value in the same way the Scrum board does?

1 answer

0 votes
Jason Golden
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 12, 2017

Yes, and conversely, changes on the team's board will also change the rank of tickets displayed on the Portfolio plan. However note this only applies to Epics and Standard issues (Story, Task, Bug) - for virtual hierarchy above Epic, the Rank rules inherit from the Epic and Standard issue types. Ranking something in the virtual hierarchy above Epic does not always properly update the rank of Epic and Story below it globally.

I wish there was a way to have rank fixed for a certain level in the hierarchy, but this would be very difficult to solve for.

Much, much more in this thread here: https://community.atlassian.com/t5/Jira-questions/Epic-ranking-in-Portfolio-2-0/qaq-p/198306

And this ticket, which was resolved due to non-answer, but in fact the issue persists. https://jira.atlassian.com/browse/JPOSERVER-1387

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events