Copy tasks
The Copy tasks feature lets you reproduce one or several tasks — optionally with their allocations, comments and linked documents — either into the current project (duplication) or to another project in the workspace. It's the ideal tool to reuse a standard breakdown, duplicate a work package, or move part of a plan into a new project.
It is available from the 📋 Copy tasks icon in the Planning toolbar.
Open the copy dialog
Click the 📋 icon in the planning toolbar. A dialog opens with:
- a task tree of the current project, with a checkbox per task;
- a destination project selector;
- three content options.
If a task is selected in the Gantt when you click, it is automatically checked in the dialog. You can of course adjust the selection.
Choose the tasks
Check the tasks to copy in the tree. Checking a parent task automatically includes all its sub-tasks: the hierarchy is preserved as-is in the copy.
You can select as many tasks as needed (multi-selection), including entire branches of the WBS.
Choose the destination
The Destination project selector offers:
- the current project (default) — the copy creates duplicates of the tasks within the same project;
- another project in the workspace on which you are allowed to create tasks — the tasks are then transferred into that project.
Dependencies (predecessors) between copied tasks are rewired to the new tasks. A dependency pointing to a task not included in the copy is dropped to avoid any orphan link.
Content options
Three checkboxes (checked by default) determine what is carried over:
| Option | Effect |
|---|---|
| Copy comments | Carries over each task's comments. |
| Copy attachments | Carries over the linked documents. For a cross-project copy, the document is duplicated into the target project keeping its link. |
| Copy allocations | Carries over the assigned resources and their planned workload. |
Uncheck an option to skip the corresponding part.
What is copied (and what isn't)
- ✅ Task structure: name, dates, durations, parent/sub-task hierarchy, internal dependencies.
- ✅ Allocations (if the option is checked): each resource's planned workload (the assignment).
- ✅ Comments and linked documents (if the options are checked).
- ❌ Actuals / ETC are never copied. Only the planned assignment is carried over — the copy starts from a clean slate, with no progress or logged time.
When a copied allocation involves a resource that is not yet a member of the destination project, that resource is added automatically with the Resource role. See Project members.
Good to know
- Permissions: to copy to another project, you must be allowed to create tasks on that destination project.
- Copy to another project: the current view does not change. Open the destination project to see the copied tasks.
- Notifications: copying allocations may trigger assignment notifications to the resources involved, just like a manual assignment.
- In-place duplication: keeping the current project as the destination duplicates the tasks within the project — handy to reuse an existing breakdown.
You can also trigger the copy in natural language through the assistant, for example: "copy these tasks into project X". The assistant can even create a project and copy the tasks into it right away.