Currently, if someone needs to create a Project with layouts matching a pre-existing project, the Duplicate Project endpoint requires for the tasks to be copied. This isn’t always wanted, especially since duplicated tasks don’t retain any of the original comments/activity.
Can an additional parameter be provided to the endpoint so that tasks do not get copied? Currently my workaround is to delete all of the duplicated tasks after calling the Project Duplicate endpoint.
Hello @Justin_Opraseuth and welcome to the forum!
What you’re describing sounds like a strong fit for Project templates. Instead of duplicating a live project (which brings tasks along), it’s possible to set up a template with just the structure you want (sections, custom fields, rules, views), then instantiate a new project from that template.
There are dedicated API endpoints to work with these templates.
Hi Mikhail,
Thank you for the suggestion. I see there are valid points for both this workflow via Project Templates, and via Project duplication.
I see one drawback to project templates is that if you do have a long-running Asana Project, and plan to “snapshot” tasks on a schedule; changes to that project (new column, different layout, etc…) need to first be saved to the Project Template.
The decision currently, is that you either have a Project template that’s “throwaway” and gets deleted after use, or you have a duplicated project with tasks that need to be deleted after instantiation.
Thanks again for your reply.
-Justin