Furthermore, it is possible to then delete the new project from the task, and then the task enters the (usually impossible to achieve) limbo state of not having an assignee or a project, so it will likely escape any periodic review process unless it is searched for explicitly.
NOTE: The task history says I “unassigned” this task from “you” (i.e. me). But in fact all I did was move the task from My Tasks to an existing project. Asana unassigned me and then covered its tracks by making the audit trail show that I had done it.
Yes, I see this as well and it is easy to reproduce - @Rebecca_McGrath, just choose a task in your My Tasks, drag it onto another project in the nav panel, then go look at it in that project - you should see that it’s no longer assigned.
I doubt Asana considers this a bug; their rationale is that you’re moving it from My Tasks (I. e., your intent is to unassign yourself) to the other project. I’m not agreeing–I don’t like this kind of “helping” behavior on Asana’s part–just explaining.
There’s another example of the same unassigning behavior: Make a task assigned to you a subtask of another task and Asana removes your assignment; I don’t like that behavior either! But I suspect they’ll want to move this request out of the bugs category.
Hi folks I believe this is intended behaviour as @lpb mentioned. As you are moving a task out of your My Tasks, you are essentially removing it from your responsible tasks list and so, unassigning from yourself.
I’d suggest creating a #productfeedback post instead to request that this behaviour be updated/removed.
So @L112, given this, if one wants to put a task into another project but keep it assigned to oneself, the way to do that is to add the other project to the task (known as “multi-homing it” in Asana terminology).