"add to another project" possible bug

[Bernardeta_Designs_P]

Briefly describe (1-2 sentences) the Bug you’re experiencing: “add to another project” will duplicate what is typed in description on both the original task and duplicated task.

Steps to reproduce: Select several tasks, click the 3 dots , click “add to another project”. Now under this, one can see that these tasks are under different projects but when you type on description on “Acme” project it will also add it to the “test” project (see screenshot).

Browser version: Chrome

Upload screenshots below:

[Phil_Seeman]

Hi @Bernardeta_Designs_P and welcome to the forum!

Actually this is not a bug: the “Add to another project” function does not duplicate the task, but rather adds the same task to multiple projects. This is known in Asana lingo as “multi-homing” a task (i.e. it has multiple homes). Because it’s the exact same task, any changes you make to it in one project will be reflected in the other.

If you’re wanting to actually duplicate a task, you can do that by selecting the task, clicking the same 3 dots menu, and selecting “Duplicate task”. Note that you can only do this for one task at a time, though - if you select multiple tasks, the “Duplicate task” option is not available on that menu.

[Bernardeta_Designs_P]

Thank you Phil. That really doesn’t make sense though. Why would a person want to add to another project the same section with the same content? For example I created sections that I would like to use as templates for other projects where I have questions that need answers…so each project is going to have different answers. Duplicating a task would be too time consuming.

[Phil_Seeman]

FYI here is the documentation on multi-homing:

Task fields and tags

There are actually a lot of good use cases for multi-homing tasks; you can search the forum here for “multi-hom” and find discussions about this topic. Here are a few:

Meaningful Summary of Projects?

Hi and welcome, @Monique_Lay, One approach would be to adopt a standard of including one “reference” task in every project that you want to keep track of. For all such reference tasks, make the task title be a short phrase describing the project. “Multi-home” (add the task to another project as well as the one project it’s already in) the task to a project called “Projects Summary” (you will need to first create this project so you can multi-home into it; I like List projects though you could …

Working with Clients

Unfortunately visibility is set at the Project-level (vs. Task-Level), so I don’t think it’s possible accomplish exactly what you’re looking for. That said, could you create 2 separate projects (1 for internal work, 1 for client work) and multi-home Employee tasks from their Internal Project to the Client Project? That way, whatever is multi-homed to the Client Project is visible to the client, but you don’t need to give them access to the Employee Project with presumably a lot more tasks.

Allow a task to belong to multiple projects?

It would be great for companies in a KanBan framework to allow a task to belong to multiple projects, since one task might as well belong to the Development Project and to a Client Project. It would increase flexibility.

Event Planning -- One Project or Multiple?

If you have access to Portfolios, you can see the new timeline per project but this is only on project level. The other option to see all tasks on a timeline is to create a project called “Overview” or “All tasks” and then multi-home all the tasks in this project that will act as a overview on the calendar and timeline view. This could be a bit overwhelming, i would maybe do this with certain milestones only.

[Bastien_Siebman]

Multi-homing for the win once you really wrap your head around it, you’re gonna love it!