Taiga-front: tasks: Assigning multiple members.

Created on 9 Oct 2014  Â·  41Comments  Â·  Source: taigaio/taiga-front

So we have a task that requires multiple members to work on. I don't see support for this. Maybe consider an enhancement. :)

(So far, the tool is working great.)

candidate enhancement

Most helpful comment

I'd like to express another viewpoint on this. Epics, Stories, and Tasks need to have an owner -- a single assignee that is responsible for its completion and/or delivery. Adding more than one person makes this ambiguous. Sure, it might be the case that multiple people work on a task -- but then again, multiple people work on everything! Do we really want or need to track this? Let the task assignee figure out who needs to be involved by -- wait for it -- talking other other humans on the team. This way the team members don't have unnecessary overhead to track all this, teams are empowered, and the company still has one-throat-to-choke for each work result.

If you pass a task between different groups, then that is abusing the task feature. Make additional tasks then.

I say leave it as it is and spend time elsewhere.

All 41 comments

Thanks for your feedback!

We think about it some time ago. Assign task tasks/us/issues to members sounds good, but have some problem, adds complexity and if you have a big team with a big task you need a lot of "clicks" to add everybody to the task. We think about the concept of teams and assign tasks/us/issues to teams or to individuals. This can be a proposal: Add teams functionality, and can assign task to multiple teams or individuals.

On the other hand, you have the concept of "watchers", that are users that are related to the issue and want to be notified, this is a good workaround because, the task is only assigned to one user, this user is the responsible of the task, and the other may be co-workers.

Then, other solution with the current implementation is, assign the task to the responsable, the colaborartors may be added as watchers, and if the user isn't assigned yet, but you have a team to do this, you can "tag" the task/us/issue with one tag for the team.

I prefer the second solution because is simpler, and assign 1 and only 1 responsable.

Anyway we keep this open as an enhancement for an open debate.

What do you think?

So currently we are writing down all our tasks on a whiteboard, and put initials into the Ready, In Progress, and Closed columns next to them. If a task requires more then one individual, then we usually put 'T' for team. So this use case aligns with your first proposal.

From a UX perspective I understand that the quantity of clicks increases but in our team tasks can be collaborative, especially when pair programming or setting up an environment.

As for the current implementation, adding further watchers is just as many clicks. From the taskboard I cannot simply open the lightbox to add watchers.

Click on the title of the task to edit (task/${id}/edit) the task wasn't something I had done. The pencil had my focus so you may want to consider adding watchers to the modal window. There is probably an even better way to display assigned and watched members in a lightbox though.

Regards

+1 for this feature

+1
You can solve this by allowing @mentions in the task description. This would not only clarify responsibilities, but also allow faster and in-context task assignments.
related: https://github.com/taigaio/taiga-front/issues/70

+1 this would be helpful for us too

+500, need this! :)

+1

+1

On Wed, Apr 8, 2015 at 5:07 AM, Levi Strope [email protected]
wrote:

  • [image: :100:]

—
Reply to this email directly or view it on GitHub
https://github.com/taigaio/taiga-front/issues/90#issuecomment-90733052.

+1

+1

+1

+1

+1, Important feature to add.

We need this feature. I don't buy the argument that this feature increases complexity. In fact, I think the lack of this feature decreases collaboration and productivity.

+2

+1

So are we going to get the feature or not? Does GitHub listen to its users?

Hello @jorgelr617

We listen all the feedback from our users and this is a high priority enhancement for us but we huge quantities of work in Taiga and somethings must be done before, of course pull requests are welcome ;)

+1

Watchers are not a great workaround. We have a board for our mobile app and have devs who work on only Android or only iOS and therefore cannot be responsible for a full multiplatform feature.

+1

+1

It would be awesome!

In our case, the task is shared among UX, Design, Front, Back people. We mix'n'match for each task so static teams are not a good solution.
It would be nice if taskboard featured a (collapsible) list of users and one could just drag'n'drop users to tasks & stories. Well, such a collapsible list would also be welcome in the dashboard.

Sorry everyone!

The workarounds proposed here are OK but this feature must be added (considering the amount of people wanting it so badly!). Let us users decide whether the number of clicks is something we can deal with or not...to me is not a big deal. +1 for this feature to be added ASAP thanks

Any updates on this?

+1 useful for pair programming!

+1000 Must have feature

+1 no brainer

+1000
In our case, assigned to multiple user is the most needed feature.

*_Other related ideas : *_
Team ( multiple users, different from role, but can't replace multiple user assignement. ) would be appreciated, as the ability to assign directly a team ( or users ) from the backlog ( a lightbox like the point picker ).

Next big thing, the ability to view team taskboard ( looks, works like a milestone, parrallel sprint with no due date. Ux : the taskboard button : view team taskboard, just above the sprint sidebar in backlog ).

+1, This would be an amazing feature. I'm currently just using the add watches function, which works perfectly.

+1

+1 pair programming, you know

+++++1

Sent from my iPhone

On 08 Jun 2017, at 10:48, Marco Travaglini notifications@github.com wrote:

+1 pair programming, you know

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

+1

+1

+2

+1
Excellent feature if possible :)

+1

I'd like to express another viewpoint on this. Epics, Stories, and Tasks need to have an owner -- a single assignee that is responsible for its completion and/or delivery. Adding more than one person makes this ambiguous. Sure, it might be the case that multiple people work on a task -- but then again, multiple people work on everything! Do we really want or need to track this? Let the task assignee figure out who needs to be involved by -- wait for it -- talking other other humans on the team. This way the team members don't have unnecessary overhead to track all this, teams are empowered, and the company still has one-throat-to-choke for each work result.

If you pass a task between different groups, then that is abusing the task feature. Make additional tasks then.

I say leave it as it is and spend time elsewhere.

Would agree with @hdave and suggest to close this issue especial that there is a feature called Watcher where you can mention additional people. If you have more people responsible for a task probably you want to split the task to smaller.

We have been doing some housekeeping work prior to Taiga6 upcoming release and we are reviewing old issues that we didn't correctly address back then.
Taiga6 brings a significant UX/UI rework, and after the launch, we’ll come back to this issue to check it again. This time we will make sure to review it properly.

Thank you very much on behalf of the Taiga Team!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

george-viaud picture george-viaud  Â·  9Comments

carmelocatalfamo picture carmelocatalfamo  Â·  8Comments

iki picture iki  Â·  7Comments

apollolm picture apollolm  Â·  9Comments

SplendornetTech picture SplendornetTech  Â·  19Comments