Project cloning / duplication using the API

Hi,

as far as I know, it is not possible to duplicate a project using the API.
Such an option would really be helpful.

Let me explain:

For specific customers we do have so called „day-to-day business“ projects.
If a new request is made by the customer, the project manager creates a job in our agency management / ERP software, from where a middleware syncs the job into an existing awork project in a task / subtask logic.
Those day-to-day business projects should be closed and archived e.g. at the end of a year.
However, not all tasks have been completed at this point. Furthermore a new project needs to be created, which would mean maintenance to make all automations work.

Therefore we had the idea to create the new project status Archived (as completed) and we do create a parallel running „archive project“. Tasks are then automatically moved there (according to a defined specific schedule - monthly / quarterly /…).

This „archive project“ should be created automatically (through our middleware) the moment the first task should be archived.

For this process a functionality to create the archive project on basis of the existing day-to-day business project using the same settings and custom fields would be helpful.

In the moment writing this, I am thinking about letting do this in our middleware, as cloning a project would also mean having all existing tasks in both projects…

Using a project template is also not an optimal solution, as the assignment of custom fields is very individual for us.

Perhaps someone has an idea…

Regards
Lars

Hi @LarsG

Thanks for explaining your setup. If I understand correctly, you want to keep the existing day-to-day project as the destination for new jobs from your ERP. Your middleware would create a separate archive project when the first task is ready to move, then move further tasks there on your schedule. The archive project should have the same settings and custom field assignments, but start without tasks. Correct?

The public API cannot currently create a project directly from another project’s setup. Your middleware can create a new project, assign the relevant custom fields, and move tasks through the API, but it would need to assemble the setup itself.

One detail I want to check: would the new “Archived” status apply to the archive project, while the day-to-day project stays open for new ERP jobs?

Hello @Sebastian ,

yes, absoultly correct concerning the setup and the „Archived“ status on the archive project.
So, the day-to-day project does not ever end, but is „cleaned up“ at the end of the year by moving all (finished) tasks to the archive project, which has the status „Archived“.

I will let the middleware do the project creation / assembly.