How can I assign single task to multipule assignees? I am struggling to find how I can do this.
This crops up so often, the workarounds are well documented. Even has it's own page (oddly, the first hit on <a famous search engine>) See https://confluence.atlassian.com/display/JIRA/How+do+I+assign+issues+to+multiple+users
I think this has been answered to death. Multiple assignees don't work in the real world because there's no clear responsibility. It can be very useful to have secondary assignees as well, but in reality you always want a single owner.
In the real world, multiple assignees does not work. Can you honestly tell me that you have never once had any situation where A and B are assigned something and one of them doesn't deal with it because the other one should have? Or have two assignees accidentally duplicate effort?You say "task owner" and "helper". That's really clear and useful. The task owner is the assignee. They own it, they need to deal with it, it's great that they have helpers, but you really have no use for many users here. The owner owns it. That's a very strong argument for not having multiple assignees. It's a very strong argument for having other fields that can help say "these people are involved/helping" too.Agile's "shared responsibility" is about the team working together to get stuff done. Part of that is being utterly clear about who is doing what, so that nothing gets dropped and no one wastes time duplicating the effort.
My counter to that would be this:
On a physical board you would have two avatars and you'd pop them both against a backlog item. This is great as it helps non dev members of the team know who's working on what if they needs to speak to them about something (could be a PO with an update etc - we prefer to have this conversations in person rather than through comments in JIRA as it's more personal and builds a stronger relationship between team members).
It's also helpful to see how a day unfolds without asking people - at the standup someone may have said they were going to work on a specific backlog item and they start it, but then a colleague needs a hand with something so they go and pair with them, at which point they'd put their avatar on that backlog item and remove it from the other - now we can see what's going on without asking/interrupting.
A lot of teams complain about keeping JIRA up to date as well as a physical board so we tend to lean towards the JIRA board, but it's limiting in ways that are deeply frustrating like this - which leads to oft used phrase "I hate Jira"
In my experience all these things have been significantly easier if you use the entire Atlassian suite (from JIRA through to Bamboo and everything in between like Stash and Clover) as you can see who's been committing to what branches very easily and therefore don't have to do some of this other work.
And, yet again, what happens when both of them think the other one is dealing with it? It's fine to have multiple interested people, and your display would be a good move. But multiple assignees always introduces the problem and your solution does not fix that.
I can't see how that situation would ever arise between a pair? Pairing is the only situation I'd ever imagine you need to have to assign multiple users to one backlog item.
I do completely support your argument that if it isn't pairing then multiple assignees are indicative of having backlog items that are too large and need to broken down.
Sorry, yes, pairing is the exception, as you're working closely together. But you still don't need multiple assignees for it in real life, because you're so close. I like the idea of having a field for "other half" and displaying both avatars on the board.
Ah yes, we're refining this now! So I solutionised something and threw out everything I preach!
So here we go, the problem I'm trying to solve:
At the moment there is no way in JIRA to see if a ticket is being paired on or worked on by an individual team member. Pair's are not constant so being able to see the avatars of the team members working on a ticket would mean I could tell just by looking in JIRA rather than asking team members and appearing to micro manage.
We don't use the logging work feature on JIRA as it smacks of micromanaging by tracking the amount of time people are logging against a ticket.
We also desperately need this feature! This is a very limited way of thinking that the tasks assigned to several people can be overlooked. Maybe in some average situations. Then why all other parts of JIRA are so flexible, and this tiny little detail - not? Double standards, huh?
>Maybe in some average situations.
If by "average" you mean "all real world cases", yes. I've yet to find anywhere where "i thought someone else was looking at it" has not happened.
It's not a double standard, it's real-world deliberate design.
@Tatjana Domnina: I agree wholeheartedly. What @Nic Brough [Adaptavist] is saying, is that because he's seen a real-world problem with a feature, everyone should be denied it. It's like saying because eating too much red meat causes cancer, nobody should be able to eat red meat.
Yes, I am, except you're de-emphasising the scale of the problem.
I'm not saying "because I've seen a real-world problem", I'm saying "Everyone has seen this problem". A better analogy would be more like "we know eating too many foxgloves kills everyone who does it, so let's not sell it as food in all our supermarkets".
Here is my use case for multiple assignees. I want to add a task that is a design review for the developers. Also, code reviews, documentation reviews, spike findings reviews, etc. This is how we keep the whole team up to date on knowledge of business rules, design, implementation and so on. In the future, I'd like to include QA. In our case that would be 9 folks. (I agree that our team is too big, but I have no control of that.) I want one task assigned to all 9 people, that allows all 9 people to individually log time to that task, that shows up in our daily standup as a task for each person, and that can be moved along in the workflow as a single task. It is important to management that we keep time logging accurate for each person. Now, I can to that with 9 separate tasks but, as you can imagine, that is very tedious and seems, to me, to be something for which Jira could provide some relief. If there is some other way to handle this in Jira with a single task that allows logging of time for mulitple users that I've missed then...I've missed it. I do think that it is valid to have team reviews that are a single task but cannot, in fact, be done by one individual. I wouldn't have a problem with an assignment of a "responsible" individual for the task but I really need capabilities mentioned above.
Again, if there is already a baked in way to deal with this then I aplogize for my ignorance.
JIRA doesn't support it. They can self assign to log time and then reassign it to the 'responsible' person.
There's nothing to stop people logging work and updating issues without being the assignee.
And, as discussed before, there are plenty of ways of drawing many people into an issue.
But you need a single point of ownership in real life, and JIRA only supports a single assignee.
It looks like you're new here. Sign in or register to get started.