I’ve set up user stories and assigned relevant team members to each in Taiga. Under these stories, I’ve created tasks. Most, I’ve assigned to individuals, but some are meant for collaboration; e.g. a meeting where the team creates a document together.
Since Taiga only allows assigning a task to one person, I’m unsure how to best manage these shared tasks. My initial thought was to copy the task for each team member, and this would have the advantage they they individually could mark them as “in progress” as they start preparing before the meeting. However, I have two concerns:
Managing multiple identical tasks could become confusing, as they would be harder to differentiate.
Each member would need to move their individual copy to “done” after one completion criterium is met, which seems redundant and I think this could lead to inconsistencies.
What would be the theoretically “correct” way to handle multiple team members working on the same task in Taiga?
When I assign a task (not a user story) to someone else while it’s assigned to one person, it just replaces who it is assigned to. If I go to the task’s page and click “Add assigned” and choose another team member, it just replaces the person on the task.
True, sorry, didn’t process that this was specifically about tasks (many people say task when referring to user stories, for some reason).
What we do is have a representative there. The task is still one, go to the meeting and create documentation. Someone gets the responsibility of representing what was spoken about in the task, plus anyone can comment in the task.
In a previous work, we used our task management system keep track of individuals to track what everyone was doing at any time and the finanses were linked up on this structure.
I can make it work, if I can get rid of these habits and think of Kanban more as a way to track tasks’ path from pipeline to done, rather than a way to track employees burning company hours.
