Each task from the source project is recreated in the destination project with as many details copied as allowed by the Asana API.
A non-exhaustive list of supported fields:
As not all users of the source project may be members of the destination workspace, references to missing users are filtered out during copying.
You will be shown a warning before copying if this is going to happen, so that you may add any users you would still like to be part of the copied project.
Sub-tasks copied along with their parent tasks. There is no limit to the nesting depth, all sub-tasks in the hierarchy will be included.
All features supported for top-level tasks are also supported for sub-tasks.
Tasks may be present at the top level of a single project, or several different projects, and may also be assigned as a sub-task of a single parent task.
Ditto considers these relationships when copying projects and ensures that only one copy of the task is created, so long as all projects are copied together as a single transfer.
Later transfers of the same task will create a duplicate copy.
Asana has introduced the concept of a special task type, of which there are currently three: a 'Milestone', a 'Separator', and an 'Approval'.
These task types are shown differently in the UI, but behave much like normal tasks from the point of view of the API.
Ditto ensures that the type of each task is copied correctly.
Log in to comment