Cloning a Project
Asked by Craig Jennings:

I have populates a Project into a full project delivery plan.   
I'm wondering If I can then use this as a master template and clone it multiple time 'without' them all linking together. I do NOT want them to update each other.


Answers:
author: W_Diehl _Litew8 GmbH_
body: Hello [@Craig Jennings](/t5/user/viewprofilepage/user-id/5528875)

we've built our app '**[Project Templates for Jira](https://marketplace.atlassian.com/apps/1230303/project-templates-for-jira?hosting=cloud&tab=overview)**' pretty much to serve your use case.

You can clone a project including issues, components version and more, decide what parts to keep and create custom project settings for future usage.

It has no limitation during free trial so go ahead and test it's capabilities. Please let us know if you have questions or additional feature requests.


author: Luka Hummel - codefortynine
body: Hi [@Craig Jennings](/t5/user/viewprofilepage/user-id/5528875) and welcome to the community!

If you are willing to try a third-party app, our [Deep Clone for Jira](https://marketplace.atlassian.com/apps/1218652?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2736022) can help you to clone your projects.

Deep Clone can clone your template projects including all their schemes and issues with its [Project Clone feature](https://documentation.codefortynine.com/deep-clone-for-jira/project-clone?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2736022). Templating is a quite common use case for the app, and we have even a small guide for that in our documentation [here](https://documentation.codefortynine.com/deep-clone-for-jira/article-a-story-about-working-with-template-issues?utm_source=atlassian&utm_medium=referral&utm_campaign=deepj-new-reach-com-2736022).


author: Clara Belin-Brosseau
body: Hello [@Craig Jennings](/t5/user/viewprofilepage/user-id/5528875)

If you're seeking for an easy way to **clone all your issues from your master template** , you can try our app [Elements Copy \& Sync](https://marketplace.atlassian.com/apps/1211111/elements-copy-sync-clone-jira-issues?tab=overview&hosting=cloud?&utm_source=community&utm_medium=answer&utm_campaign=question_2736022&utm_keyword=CS&utm_vendorID=4952)that allows you to clone issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.

You have the option to unlink them. You can check our guide [here](https://doc.elements-apps.com/copy-and-sync-jira-cloud/copy-all-issues-from-one-project-to-another?&utm_source=community&utm_medium=answer&utm_campaign=question_2736022&utm_keyword=CS&utm_vendorID=4952).

You can try the app for **free during 30 days** (and it stays free under 10 users).

Kind regards,

Clara


author: Ezgi Bay?nd?r
body: Hey [@Craig Jennings](/t5/user/viewprofilepage/user-id/5528875) ,

Welcome to the community

Cloning project with issues is not a default option in Jira. However, you can create your new project with "share settings with an existing project" option.

![image (36).png](https://community.atlassian.com/t5/image/serverpage/image-id/331684iD142E96B7A5252A9/image-size/large?v=v2&px=999 "image (36).png")

Reminder; since components and versions are project-based settings you need to add them manually.

If you have issues in the past you can take an export of your existing issues and import them to your new project with CSV import. After that you can create an automation rule for cloning your new issues.

![image (37).png](https://community.atlassian.com/t5/image/serverpage/image-id/331685i1CBD7374853EDE67/image-size/large?v=v2&px=999 "image (37).png")


author: Trudy Claspill
body: Hello [@Craig Jennings](/t5/user/viewprofilepage/user-id/5528875)

Welcome to the Atlassian community.

Jira does not include a native project cloning feature that includes cloning the issues in the project. It is possible to construct a solution with other native functionality, like Automation Rules. Or you can invest in a third party app that provides the functionality.

Cloning issues die not result in updates of one issue causing updates to another.


Tags: cloud

jira-cloud