Understood. However why can’t you have one owner and then people that are secondary/supporters. You don’t always want to break down a task into too many sub tasks.
User Stories need multiple roles like Product Owner, Business Analyst, UI, Tech etc. to work on it at the same time.
Am I the only one that thinks that multiple task per role / resource are overkill and add additional complexity for users as well?
You could see the "Assignee" of an issue as the person being responsible for it. What you can do, is creating a multi user custom field with the persons working on the issue. Still, one person is responsible (assignee). If you have many workers on an issue, who defines that the issue is done/finished?
Hii @Kerry Wilson
As @Gikku_Mathew_John said its right, but you can make custom field as multi user picker and then assign it to the screen of your project and when you want to assign a task to 2 or more users, you mention all users in that. And for sending notification you can add the custom field that you have made.
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