There are a few solutions for allowing multiple assignees to issues.
There is also a great article available here on a similar topic with some additional examples:
Assignee could be split into 2 fields as a core Jira feature: Lead assignee and current assignee. That way the person responsible is always Lead assignee but the current assignee could be e.g. 5 people at different stages of the ticket.
To make this more than just a custom field, each of the 2 fields should have Jira native support in reporting and backlog summaries so that workload can also be balanced.
Any reasons this is not a good suggestion?
We understand that Atlassian has provided a bunch of "workarounds" for this missing ability. And that's just what they are, "workarounds" until multiple assignees are supported. Unless some other tool has a patent on the concept that prevents Atlassian from implementing it.
Also, there's a difference between responsibility and accountability. I'd argue that RACI clarifies this and puts forth that Accountability is singular, while Responsibility can be held plurally. And especially in our Agile worlds of collaboration and pairing or swarming.
Must we really continue to have to leverage those "workarounds" or clone sub-tasks to map to multiple team members? Is this one a feature list to vote up somewhere? Or just constantly closed for comments (not this one yet...)?
How do you let them both log time on it?
To really be honest I have never had this issue of not knowing who was responsable for what. Even if 2 people had the same task assigned to them.There is usally a lead that assumes the respnsability and has better knowledge of the task even if it branches off to several other people.
Therefore I would like this feature added in Jira Agile! :)
Yes but how do I track the the time that those 2 or 3 people spent on the same task? I duplicate the task right?
No, let them both log time on it. Doesn't matter if it only has one assignee.
(And I agree with Joe - it's actually critical that an issue has a single responsible person. Think of the basics: "It went bang, who do I shout at?". With more than one assignee, people start ducking. And you get "I thought X was working on it". You have to be clear that it's a single person)
so obnoxious in your answers Nic .. No, wether you like it or not, there are use cases where we need multiple assignees on a task (case in point, so many people are asking for it), not everyone is a developer, we use it for marketing with checklists and multiple people need to be able to see it on their board.
i dont thing it is posiible to assigne one task to multiple user but work around you can do this
check the this document
some more help you can get from here
some onle already issue raised with atlassian here
Absolutely right, the assignee is a single user field and you simply can NOT assign an issue to more than one person.
This is by design and the request to "fix" it is rightly closed. The other two links Rambanam gives you are pretty much the best ways to indicate you've got more than one person with current responsibility for an issue.
We can create "Secondary Assignee" custom field and add another user to that.
Also, configure workflow post conditions to send notifications for the user in "Secondary Assignee" field.
Even though it is not the perfect answer you might be looking for, but if you have ScriptRunner or Automation for JIRA plugin, there are a lot of features you can do with this.
Truthfully if you are a "pair programmer" type of shop, you need to be able to assign both people to the issue and they should both have it on their board, record their comments and their time. Esp when dealing with branches (from bitbucket integration). It is a real hassle to have to set up a "team" of every pair programming team you have to assign to an issue. How have others worked this? Any plugins?
Agree Elena Ashley, And nearly every other tool allows you to have multiple assignees and multiple owners...the reason...agile teams...scrum teams have a montra - no one is done all are done...and stories as a construct are complete Design build test cycles with multiple contributors; therefore, multiple team members could be assigned to a Feature, or a Story or even a task due the Agile XP practices where two or more people pair up on the task...All of these are good reasons to add this feature... other tools allow this and have for years...
Introducing Jira Cloud for Excel Here at the product integrations team at Atlassian, we are thrilled to announce the new Jira Cloud for Excel add-in! This add-in lets you export Jira data directly ...
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