Multi-select and copy tasks to another project (using modifier key)


#1

It seems like everyone has the same problem, they want to mass select tasks that already have information set on them, and copy them to a new project. Since you can drag these tasks from one project to another (performing a MOVE function), if Asana can just add a modifier key (option, command, ?) that would allow us to COPY instead of move. Microsoft Outlook has a similar feature, you can drag an meeting from one day/time to another day/time. But if you hold down a modifier key (I think option), it will create a copy instead of just moving it.

I have tried every way conceivable for copying multiple tasks into projects. Templates only work if the project can be fully templated. But our projects have 5 different teams all working on the same project, and all require different workflows. It’s easy to setup, but I just can’t come up with a way to mass copy/paste tasks while retaining custom field and subtask information.

The best method so far I have found is:

  1. Create a template of “parent tasks”… for me I call these the deliverables
  2. Each parent task has it’s own workflow of subtasks, and those subtasks may have subtasks as well.
  3. Copy the parent task
  4. Change the project associated with the parent task to the new project.
  5. Go to the new project and change the name of the parent task to reflect what you want.
  6. Promote the subtasks to the task list
    6a. option 1 is to use the search to identify all the subtasks in that new project (assuming you have enough metadata in the custom fields to isolate these tasks), and then add these subtasks using the “add to project” function.
    6b. option 2 is to just grab all the subtasks and drag them to the task list. But this means they cannot easily return to the subtask area (you have to move them one-by-one if you want to put them back at any point)

That’s just too many steps to do something that should just be a copy/paste using a modifier key (dragging and dropping) or using a “copy all tasks” and allowing us to select the current or different project for the pasting of the tasks.

Sorry for the long rambling post… but this current system seems super inefficient.


#2

@Millor_Machado you might have a solution for this isn’t it?


#3

@Bastien_Siebman thanks for involving me!

@Francesco_Alessi, I’m working on a tasks library that you can create that add standard tasks to new or existing projects. The first version doesn’t have custom fields nor dates, just the names and descriptions of the tasks and subtasks.

Would this solution help you?


#4

Well, having subtask info carried over would be 1/2 the battle, so that would help. But I really would like all the info, including custom fields, to carry over.

As long as I can pull a list of tasks into a project and have all those tasks in some kind of group so I can select them all at once, I can then add the custom fields fairly easily. I only have one custom field that would require me to select chunks of tasks to set its information (which is phase/stage).

So maybe your solution would get me 1/2 way there.

Thanks for reply!


#5

That’s great! I’m sending you a private message so we can go further in this demo about the library.