Copy Projects with ticket data.

[Neeta Dubey]

Hi All,

We are on atlassian cloud , could anyone let me know if there is a way to copy project with tickets into a new project?

[Wolfgang -Litew8 GmbH- · Accepted solution]

Hi @Neeta Dubey

there are multiple approaches to this.

Natively you could create a new project with shared settings and manually clone the issues into the new project. Doing that would not clone project components, versions, board and project role assignment. So you have some manual tasks to do afterwards.

Instead there are third party apps that aim to make it smoother for you to clone projects or like our app, Project Templates for Jira to create custom project templates from projects that allow to clone the project, it's issues, components, version and more.

[Clara Belin-Brosseau_Elements]

Hello @Neeta Dubey

If you're willing to use a third-party application, I can suggest trying our Elements Copy & Sync app that allows you to copy issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.

You’ll be able to copy your entire project without losing any data.

Don't hesitate to try our app, it's free during 30 days and stays free under 10 users.

Let me know if you have any questions.

Kind regards,

Clara

[Luka Hummel - codefortynine]

Hi @Neeta Dubey

I'm Luka from codefortynine 👋

If you are willing to use a third-party app our Deep Clone for Jira offers a robust solution for your needs. It is designed to work seamlessly with Atlassian Cloud and can help you clone an entire project, including all its tickets (issues).

Here’s how Deep Clone can assist you in copying a project to a new one with Project Clone:

1. Clone Entire Projects: Deep Clone allows you to duplicate an entire project, including all its issues (tickets), configurations, and even attachments if necessary.

2. Preserve Issue Links and Hierarchy: If your project includes issues that are linked together or have a hierarchical structure (like Epics and Stories), Deep Clone ensures that these relationships are maintained in the new project.

3. Bulk Cloning: Deep Clone is efficient in handling numerous issues, making it ideal for cloning entire projects without the need to replicate tickets individually.

[Neeta Dubey]

Hi Luka,

Yes Deep clone did help however two steps are involved.

 first clone the project and then clone the tickets. When I was on server version of jira there was a check box while creating copies of project that if we want to copy issues as well.

Move option doesn't help as it moves all ticket from my source project.

[Luka Hummel - codefortynine]

Hi @Neeta Dubey

Glad our app could help you! We currently want to give the user the ability to stop after cloning the project without cloning any issues. This is a common use case for people that need to set up empty projects according to an already defined configuration.

Thank you for your feedback! I do understand that having an option to let the clone run from start to finish without user interaction would be an improvement. I have forwarded you feedback to the product manager, but I can't promise you that we will work on this in the near future 😊

[Trudy Claspill]

Hello @Neeta Dubey 

If you want to copy the issues to another project while leaving the original issues in the original project, you might want to consider a third party app such as:

Deep Clone for Jira

That is just one possible app. There are others that could also be used. I have no first hand experience with the app, I am not affiliated with the vendor, and I am not compensated for mentioning it.

[Ezgi Bayındır]

Hello @Neeta Dubey ,

Unfortunately you can't copy entire project but you can create a new project by using share settings with an existing project option. Then you can clone the issus to the new project by using automation, bulk edit, or the export-import.

Best,

Ezgi

[Sebastian Krzewiński]

Hi @Neeta Dubey 

Project is on the same instance? If yes, create new project and move tickets.

Regards,

Seba