Consensus Completion of Tasks

Hi Sandra, thank you for posting this! There were some great ideas about this in one of our Community discussions about subtasks, and a solution that could potentially help is to create subtasks for individual assignments. Key information, reference materials, and notes can be stored in the parent task, which is easily accessible from any of the subtasks. Once all users mark their individual subtasks complete, a supervisor (or one of the users) can change the status of the parent task too. Would love to hear what you think about this!

Well this is basically what I already do but it becomes cumbersome because a) you have to create a lot more identical or empty (sub)tasks and b) it clutters the view making it harder to see what is happening. A lot of the things are literally the same exact task like reviewing a document. I just need everyone to review it and the task to be 'completed' once they all have. (this is an AND rather than an OR - should be a simple option - yes we are engineers here). Typically if I have a task that one person needs to be responsible for closing then I assign that task only to that person and they are responsible to getting whoever else they need to help them close it. 

Hi Sandra :) Another option in this case might be to use the checkbox feature in the description field. So you would have something like an "Approvers" section with a checkbox list which references each person who needs to approve the document before the task is completed. Once all the names have been checked, the task assignee could complete the task.

This would look something like this:

I know this isn't exactly the feature you're looking for, but maybe the checkboxes could help add some structure to the approval process?

P.S I hear a lot about AND/OR situations from engineering friends, so I really enjoyed your engineers comment. 

I also would like the ability to have multiple assignees on one task and be able to see the status of each assignee for that specific task instead of using subtasks.

Sometimes I need to assign the SAME multiple tasks in a folder to over 10 people and would like to see the status for each assignee of any of those tasks.

To further help my case here, at times I have 15 tasks, that I need to assign 10 people to each of those 15 tasks.

If I had to use subtasks to see the status of each assignee, then according to the math, 15 x 10, i would have to manually create 150 subtasks just to accomplish this!

Hi again Isaac! I'm actually really interested in hearing about the use case for assigning 10 people to the same task. As a best practice, we usually recommend having one action item per task, and in this case it might be beneficial to set up a Folder/Project structure for a larger amount of tasks. I understand that workflows in different teams can be very different, and I'll be happy to share some tips about setting up a process for your use case. It would be fantastic to learn about your current processes, and I'm looking forward to hearing more from you!

Hi Anastasia,

The case that Isaac is describing comes up for us very often as well. Is adding this feature in Wrike's development roadmap?

Thanks

let me bump this one! 

It happens often that from a meeting a task emerges that has to be done by everyone. Everybody has to do the same thing and then we'd need to be able to follow up with the people who haven't done it yet... 

Thus an easy way to assign the same task to several people would be appreciated.

@Sandra, this isn't on the current roadmap, but all of the conversations happening here help us start conversations with our Product Managers about different use cases and needs.

@Phil, thanks for bringing this up! On a related topic, I'm really interested in hearing how you currently manage meetings and meeting notes in Wrike, and whether there's anything that could make that process easier for your team.

One very simple solution would be for Wrike to automatically duplicate all tasks when you assign multiple assignees. That would go very much in line with your philosophy of always having one person responsible for each task, don't you think?

@Cornelia I guess it depends on how you use wrike. I use the Gannt Chart view the majority of the time when managing my projects. Looking at bunch of replications of an identical task with the only difference being who it is assigned too would get unwieldy very quickly. Since all assigned people must "complete" or consent to completion of the task for it to be marked complete it would be much easier IMHO to have one task with multiple assignees that is only called "complete" when all of the assignees have designated it as such.

Sure, that depends on what kind of task it is. But I would argue both cases exist and should be use-cases for a tool like Wrike.