01-14-2013 01:09 PM
When a task requires multiple team members to complete, multiple tasks must be created in order to accurately reflect capacity. It would be much more efficient to create one task and assign multiple people in some instances such as tasks that require collaboration.
01-15-2013 03:16 AM
A Task is the "smallest" working item, and it is designed to have one assignee.
Have you considered breaking the task to smaller units so it could have only one assignee?
01-15-2013 09:49 AM
If you are referring to "breaking the task" as just creating multiple tasks so that it can be assigned to each person responsible, then yes that is how we currently handle tasks that have multiple team members responsible for completing it. We need the ability to create, in some circumstances, a task that has multiple team members responsible for completing it in order to accurately track effort and capacity.
11-29-2013 05:44 AM
Our team would second the request to have tasks assigned to more than one team member.
We use pair programming techniques and rather than having two of the same task with the same hours assigned to two separate team members or having one task with twice the time assigned to one member but reflecting two members work it would be great to just have one task assigned to two team members.
The task could be as small as writing a unit test but it required the time of two team members (working as a pair) to complete it.
12-03-2013 09:50 AM
02-27-2014 09:59 AM
I have the same problem in my team. There are activities that multiple people work and it is not efficient to have multiple duplicated task only to be able to assign to multiple people.