Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Adding multiple boards ignores Portfolio rank order

So I have one board/filter that only shows Epics and I use that to rank and prioritize the epics. If I add that Epic into Portfolio, the ranking and ordering show up perfectly.

 

The problem here is that the underlying Stories (with the assignees) do not appear in Portfolio, so I altered the issue source and added in a filter that include Stories as well. The Stories board has ranking turned off, so it's not conflicting. When I add in the Stories board, Portfolio suddenly ignores the ranking and it's all out of order. 

 

What am I doing wrong??

1 answer

0 votes

Hi Margaret,

I believe the answer you're looking for can be found in the thread titled Epic Ranking in Portfolio 2.0:

 

The rank from Portfolio should generally be represented on the JIRA board, however there are some differences in epic rank behaviour between Portfolio and JIRA which can cause epics to be inconsistent. This is because the rank of epics in JIRA are independent to the rank of stories whereas in Portfolio the rank of stories and epics directly impact each other.
The main contributors to inconsistent rank behaviour between JIRA & Portfolio are:
  • In Portfolio the highest ranking child issue of an epic determines that epic’s rank relative to other epics.
  • In Portfolio re-ranking the epic also bulk re-ranks all the child stories.
We recognise that this isn't optimal behaviour but it’s a necessary trade-off for the intended use of Portfolio and the integration with JIRA
Please take a look at the full thread and see if the proposed workarounds by Rhys Christian work for you.
 
Cheers,
 
Branden

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

122 views 8 10
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