We would like to copy multiple tasks from one project to another, including all their custom field values.
So far, we have tried copying and pasting the tasks using Ctrl+C and Ctrl+V. However, only the project title is carried over, while the custom fields remain empty in the destination project.
Both projects already contain the same custom fields, so we expected the existing values to be copied as well.
Is there a way to copy tasks between projects while preserving all custom field values? Or is there an alternative approach that would allow us to achieve this?
Thanks for explaining the issue! Instead of copying and pasting tasks between projects, I’d recommend using custom field standardization and Asana’s multi-homing feature. This lets you maintain the same task across multiple projects without creating duplicates.
Step 1: Add your custom fields to the field library
In your base project, when creating or configuring a custom field, enable “Add to [team name]’s field library”, as shown in the screenshot.
This makes the field available for reuse, helping standardize the field definition and its options across projects.
GID stands for Globally Unique Identifier. Think of it like a unique student ID in a school: two students might have the same name, but each student ID identifies one specific student. Similarly, when projects use the same shared custom field, they reference the same underlying field rather than separate fields that happen to have the same name.
Step 2: Add the same fields to the destination project
Open the destination project and add the custom fields from the field library rather than creating new ones with the same names. This ensures both projects use the shared field definitions.
Step 3: Multi-home the tasks instead of copying them
Now, you don’t need to copy and paste the tasks. Open each task and add it to the destination project using the option to add it to another project.
This is called multi-homing in Asana. The task remains the same task in both projects, so its custom field values and other task details are retained rather than recreated in a separate copy.
Thanks for your detailed explanation! I understand the benefits of multi-homing, but unfortunately, this doesn’t solve our use case, as we specifically need to create separate copies of the tasks, rather than have the same task in multiple projects.
Our use case is as follows:
We have a project containing all possible media placements for our marketing campaigns. For each individual campaign, we copy the relevant placements (tasks) into the corresponding campaign project.
We would like to duplicate multiple tasks at once, including all their custom field values. Once copied, we need to be able to adjust task details independently for each campaign, such as due dates and budget allocation.
With multi-homing, changes to the task would affect the same task across projects, which is exactly what we want to avoid.
Is there a way to bulk-duplicate tasks between projects while preserving their custom field values, provided that the same custom fields are already available in both projects?
Thanks for clarifying your use case! I understand why multi-homing won’t work here, since each campaign needs its own independent tasks, with separately managed due dates, budgets, and other details.
One alternative worth considering is Asana Project Templates.
If your campaigns follow a similar structure, you can create a project template containing the commonly used media placements, custom fields, and other standard project configurations.
For each new campaign, create a separate project from this template. This gives you an independent set of tasks that you can customize for that specific campaign, including adjusting due dates, budget allocations, and other task details without affecting other campaigns.
You can also update the template as your campaign process evolves, so future campaign projects start with the latest structure.
I hope this gives you a useful alternative to explore! If this approach helps solve your use case, please click the checkmark below this reply to mark it as a solution. Thank you!
Thanks for the suggestion! Unfortunately, using project templates doesn’t solve our use case either, as each campaign project already uses a different template.
Our source project is essentially a catalogue of all available media placements. For each campaign, we select only the placements we need and want to duplicate those tasks into the respective campaign project, including their existing custom field values.
What I find particularly confusing is that Asana allows us to duplicate entire sections into another project, but apparently not individual tasks in the same way, especially when it comes to retaining custom field values.
Ideally, we would like to select multiple tasks from our catalogue and duplicate them into an existing project, preserving all custom field values while creating independent tasks that we can adapt to the specific campaign.
Is there a reason why custom field values aren’t retained when copying and pasting tasks between projects, even when the same custom fields already exist in both projects? And is there any way to achieve this without having to recreate the tasks manually?
@ka_nishiyama, I think Duplicate task and the script action may only operate on a single task and the request is to copy multiple tasks.
One solution, which @Andrea_Oberholzer you may have ruled out prematurely, is Duplicate section. In your “model” project of all possible media placements, you could drag the unique set of tasks you want to assemble for copying to an empty section, then use Duplicate section which prompts for the destination project.
Another approach, thinking more broadly than “duplicating tasks” in order to attack the underlying need, would be to consider using task templates. (Your “model” project more or less sounds like your own workaround for task templates, in a way.) You can read about task templates in Help. But there’s a downside because they only work within a project. So that’s where this hack I came up with helps, and I believe this is another alternative for you:
Yet one more alternative: Automation. You could possibly turn your model project, or a new project, into a task “factory.” I didn’t attempt this, so this would need to be tested, but a tried-and-true approach to automating across projects (if you don’t have Bundles with Enterprise) is to put the automation into a factory project, temporarily muti-home a task from the destination project there, but first value a multi-select field with the selected media placements needed, and maybe another custom field with the project name, then have a rule run there to create the needed tasks in the destination project, and un-home the task, and maybe mark it complete after the work is done.
From the title, I thought this was about duplicating tasks.
When duplicating multiple tasks at once, it seems like it could be done using a combination of custom fields and scripts.
For example, checking a custom field might trigger a script execution.
Alternatively, you could multi-home the selected tasks to a temporary “conversion project,” and then duplicate them within the “conversion project.” There seem to be various possibilities.
Thanks a lot for all the suggestions and for taking the time to think through possible workarounds!
I’ve considered the different approaches, but unfortunately, none of them really fits our workflow:
Duplicate task: This works for individual tasks, but our requirement is to select and duplicate multiple tasks at once (bulk action).
Duplicate section: This is actually a good idea in principle. However, it would require us to move the selected tasks into a temporary section in our source project first. After duplicating them, we would need to move the original tasks back into the catalogue to keep it ready for the next campaign. Also, the destination project already has a designated section where the duplicated tasks should go, so creating an additional section isn’t ideal.
Task templates: Our campaign projects already use different templates, so introducing another template structure isn’t a suitable option. We have a catalogue of approximately 200–300 different media placements, of which we typically need only 5–30 per campaign. Creating and maintaining individual task templates for all these placements would be far too cumbersome and would not provide the flexibility we need.
Scripts / automations / task factory: These could potentially work, but since the destination project changes with every campaign, the setup would need to be adjusted or configured dynamically each time. This would add quite a bit of complexity and maintenance to what should ideally be a straightforward process.
Multi-homing: As mentioned before, we need independent copies of the tasks, as details such as due dates and budget allocations will differ between campaigns.
To clarify our workflow once more: We have one central project that serves as a catalogue of all available media placements. For each new campaign, we select the relevant placements and want to duplicate them into the existing campaign project, where they can then be managed independently.
Ideally, what we need is a bulk action that allows us to select multiple individual tasks and duplicate them directly into another existing project, preserving all custom field values.
Given that Asana already supports duplicating entire sections between projects, it seems like a natural extension to offer the same functionality for a selection of individual tasks.
Is this something that could be considered as a feature request? I believe this would be a useful functionality for many teams working with reusable task catalogues or libraries.