You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
We're a game development team, and our skills are largely exclusive, like "Design", "Engineering", "Art". Each team member has only one of those skils. Most of my stories require at least one of those skills, but to get Portfolio to assign multiple people to a story, I need to set the "Maximum assignees per story" to 3. Now, if I have a story that requires 2d Art and 3d Engineering, Portfolio will correctly assign an artist and an engineer to that story in the same sprint. That's great! But what it also will do is try to assign multiple people of the same skill; in the example above, it might try to assign one artists and two engineers, and I only want one engineer to be assigned to it. Is there a way to limit the number of assignees in the same skill to a story, but still have multiple assignees to it?
I don't see an option so I feel like this is more of a workflow thing. Is there a better setup I should consider?