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

Maximum assignees per story set to 1, but portfolio still suggests 2 ppl to work on the story

Hi Community, 

I'm on newest portfolio version 2.9.0, and with Jira software server 7.4.3.

I've set "Maximum assignees per story" to 1, and set a story manually to a certain sprint (instead of "calculate").

Very strangely, after calculation, Portfolio still suggests me to assign two ppl on that topic (pls see pic below).

Could you explain me why and how should I really restrict it to one assignee per story?

Thanks,

Onyx

 

 

_t.useScrumMethod_2017Nov - Portfolio for Jira - Jira 2017-11-30 17-38-54 zzScShot.png

1 answer

0 votes
somethingblue
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Dec 01, 2017

Hi Tommy,

I did some research and haven't currently found a solution to this. There have been discussions on this in the past and it looks like a Suggestion was posted in that post that you can find at JPOSERVER-1741

In addition, I found another Suggestion at JPOSERVER-1502.  Please vote on both of these issues and add your use case to the comments to add impact to help get this feature implemented.

Cheers,

Branden

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events