Assign multiple assignees on one task

+1 Vote and counting… 2021, 4 years already? Should we sign happy birthday to this request? :slight_smile:


I’ve added another vote for this one. My organization commonly works on tasks in teams. It would be incredibly useful to be able to assign multiple people to a task and to be able to designate one as lead.


+1. This is P0 or in other word essential need for project management to have more than one assignee. If this feature isn’t available, i am leaving away from a great product management software.

I agree with the need for multiple assignees to one task. Especially from the perspective of creating Rules. At the bare minimum, add a feature that allows you to notify multiple people about a drop-down field change. This would then allow key stakeholders (re: said status) to begin their work or know where the task is at in the progress. Seems like a REALLY easy and simple addition to this software. We just started using asana, and I can already tell there are many headaches ahead just trying workaround the “governors” in place.

I agree, there are cases and types of tasks where multiple task assignees would work much better.

I am not sure if it easy to implement for Asana team, though.

This definitely needs to be an option. Almost every team I’ve ever worked on requires people to work together to complete tasks. Not being able to do this is a horrible decision that clearly doesn’t take the end-user into consideration.

If we can’t have multiple assignees, a person custom field would be great that way you can highlight the different roles and who needs to be informed.

I tried a hack it by manually adding team member names to a custom field dropdown but the limit is 50 and there are 70+ people on the team. Plus it would be good just to look up people’s names that are already there, rather than manually adding them. Monday, Airtable, Notion do this already


I admit this would be really convenient as well, however here is what I’ve done as a work around:

There are many times where you have a task that requires multiple different people to complete a part of that task or maybe it’s just you, but you want/need to do parts of the task on different days. To get around that, I’ve been making the initial task and leaving it unassigned and undated. Under that task, I create subtasks layout out each part of the job. Then I can assign those subtasks to individual people or on person with different dates.

In my example, I have one task under a project section, “writing articles reminding people to sign up” , but this task needs to be done on multiple websites and I wanted to break up the work between myself and a co-worker while stretching them out over about a month.

I created the task, then created subtasks for each website to write an article on, then assigned the individual subtasks to myself or my coworker with the desired due dates.

One of the only negatives I’ve found about this is that subtasks do not hold the color coding on a calendar view like a task does when assigned to a specific project. As an Asana Together Ambassador, I have yet to find a way around that one besides just making your subtasks regular tasks, but that doesn’t really look right structure wise.


In follow up to myself, I realized you can create tags on the subtasks and set the tag color to the color of the project and it’ll make your subtasks show up as the same as the project color. It does mean a bit more work when added each subtask, but if you really care about how it looks on your calendar seems like a google solution.

I think the use case that makes the MOST sense for this is on Milestones. Tasks I understand only being assigned to one person, because a specific amount of work is being completed—but many folks, managers, the person completing the work, c-suite people overseeing it need broad visibility into the dates of milestones. Even if only Milestones were allowed to have multiple assignees, that would be a huge improvement for our workflow.

1 Like

We are currently assessing Asana, and this is one feature that will be a dealbreaker.


Mar '17 → Mar '21 …four years have passed since @Michael_M posted rather simple idea. Multiple assignees. Four years.

@Marie any answers? Considering recent announcement The Asana Community Forum has been awarded best "Support and Customer Success Community” for 2021! 🏆?

Btw. wondering if @Michael_M is still a user…

Hi @Michal_Skrna

While I regularly share our community feedback on this specific with our team, Asana has made the decision to not move forward with this request at the moment. I’ve explained our reasoning for making this decision many times on this thread, but you can refer to this article for more info on this topic.

@Bastien_Siebman has also shared some handy workaround in 🔥 Hottest feature requests and their workarounds which you may find useful.

I don’t foresee this feature being implemented in the near future, but I’m committed to continue sharing your feedback with our team and will keep you posted here if our decision on this topic was to change.

@Marie thanks for your prompt answers. I completely understand “one responsible = job done” concept. From the ariticle you linked through I like this part -

“Still not convinced? Here’s a way to break up the work, but still just have one assignee: use one assignee on the parent task so the person ultimately responsible for making sure deadlines are met. Then, create subtasks, assigned to different members of the team. Divide up pieces of work across the team, but make sure someone is on the line to get the overall job done.”

The only problem is, that subtasks don´t appear neither in Timeline nor Workload so we can´t plan properly. Imagine a basic situation - a meeting or presentation where two colleagues should attend and we can plan time just for one. Multiplying all related taks is not the option, Asana list will be unorganizable, we´re architects we need simple features our work is complex enough ; )

Thank you anyway for definitely closing this topic.


It is considered bad advice by many, as subtasks really don’t behave the way you expect them to :slight_smile:

In that case you should assign duplicates I guess.

It depends. Just yesterday I just used two subtask assignments for two people to read a document, putting the document link in the parent task so there’s no unnecessary duplication. I use subtasks for this regularly with great success. This works very well for meetings, multiple approvals and signoffs, etc. I recognize @Michal_Skrna has an issue in not being able to track meeting attendance in Timeline or Workload without additional effort, but many (most, I’d imagine) don’t care about that, and certainly it doesn’t come into play for approvals and signoffs.

@Bastien_Siebman, I know you’re very against subtasks (and we disagree on this), but to not include the above in 🔥 Hottest feature requests and their workarounds as an alternative workaround (W1.3) for multiple assignment is really not helpful, in my opinion. Would you consider adding it?



I plan on recording a podcast episode with @Julien_RENAUD who never uses subtasks and that amazes me. I am not completely against it, but I believe not having a clear rule is bad and I struggle to make up my mind around subtasks :confused:

Yes sure I’ll add it!

1 Like

Dear Bastien,

Thank you very much for your effort to help us manage our workflow within Asana. My point was that we need Asana make the most of the organising automated for us. We´re architects, we don´t want to spend too much time organising the work, we like to design and create ; )

Duplicating everything is an option, we´ll try to get used to it. I follow your list of workarounds, any future tips are very welcome.

Best regards

Michal Skrna

Just in case you did not know that, there is a “Assign copies” feature. You create a task, click on the assignee, and then on Assign copies. That will automatically assign a copy, there no extra manual work and everyone get their own task.

Take care!

@Michal_Skrna and @Bastien_Siebman,

I feel the best workaround is to combine Assign Copies and Subtasks such that the assignments are in subtasks for that purpose only and the task content/details need not be repeated at all. I offered that workaround here in this very thread two years ago!:

(@Bastien_Siebman, perhaps this belongs in W1.3 of