Thanks for consolidating this list of workarounds @Bastien_Siebman.
W4.4 and W8.2 added with a solution from our friend over at Flowsana @Phil_Seeman
Thanks for this!! Lots of great workarounds to consider. Regarding F2 and F3, I usually take the subtasks and “Add to Project” so they stay subtasks - consolidated within the main task - but can now be seen in the mainframe of the project and calendar. Or is this what you mean by “multi-home”. This is a new term for me if you could elaborate on its meaning.
Hi @Olive, it just means associating a task with multiple projects (so that it has “multiple homes”) - see:
@Bastien_Siebman - can you explain F1 more? I asked Asana about it and they told me not to do it. So would not explain.
I agree with them it is bad practice to have multiple assignees. It is the best one to have no accountability with no one responsible. If you really need to do it then I shared some workarounds. Why do you think you need it?
We are a small office of 15 people so I am not concerned with the if you have more than 1 person assigned it won’t get done. In the situation I want to have multiple assignees is where the director is the overall accountability owner of a strategic task but the actual work to be done or part of the work to be done will be handled by one of their direct reports. I want to assign the task to both parties so they know they need to work on it together but I want to be able to just see it on the the Director’s list so when I review the director’s tasks, I know to get an update on that item. Yes, I know that I can make copies of it and have 2 copies but that does clutter things up. When we first got Asana we broke things down into smaller tasks using subtasks. We realized subtasks didn’t work well for all the reasons everyone knows about. We also found that getting to granular made Asana too busy for us and people didn’t like wasting time checking off the small stuff. We try to keep our tasks more big picture and link to procedures that break down the smaller necessary steps to accomplish the bigger goal. I don’t see any work around to the guest things. Did you mean you will share the workaround? If you shared it please link to where it is shared. Thanks!
@Shirlyn_Adkins might I suggest that in lieu of multiple assignees you could perhaps use a group email account to assign the “grab bag” tasks that different individuals might take on. Once someone commits to performing the work, they could re-assign the task to themselves. If they are to work on these tasks together, can I ask what their individual roles are? Depending on this answer it might suggest tasks are either broken down more or duplicated to ensure everyone understands what they are responsible for.
As for the ability to see what remains to be completed on the Director’s list, I would suggest the work being done is either:
- A subtask to the final task assigned to the Director, perhaps even have this parent task be of the approval type. [it seems you have tried to use subtasks in this way so it might not be the preferred approach for you]
- A dependency which is “blocking” the task that is assigned to the Director.
Thanks for the discussion, you should probably have it on the actual thread about that topic