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.
I wanted to give you insight about the most asked question from customers and how we solved this problem.
First of all, I want to emphasize that this is not a good idea. To assign an issue to multiple users is always a bad idea and you should always avoid it if you can. This is because, it's against the nature of Jira itself and it creates a problem with accountability. If an issue has multiple assignees, than you can't probably know who is responsible and also who did the most work, so it messes up the performance statistics.
But, if a customer wants something, they want something. Sometimes as a consultant, all you can do is explain why this is a bad idea and convince them otherwise but still commit to the idea. We got this question from multiple customers so we decided to at least create a solution and this is what we did:
Customers who mostly use this system uses a performance evaluation based on how many issues a user solves. Again, this is not an ideal solution but this is how we solved it.
Hope this helps someone out there struggling with this issue.
110 accepted answers