Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

how do I clone a project?

What is the best way to create project templates on JIRA Sofware? Something we can use to create all projects (clone/copy)?


6 answers

5 votes
Julien Peyrade _ Elements
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Mar 21, 2023 • edited Mar 22, 2023


As far as I can tell, there are two aspects in using a "template project": you may want to copy the project configuration, you may want to copy its content (Epics/Stories/Subtasks), or both.

The configuration part can be achieved natively within Jira, even though I believe you need to have Standard Jira instance, not Free.

For the second part, you will need an add-on. I would advice using our app,  Elements Copy & Sync which can help you do exactly what you need and even go a little further : the app lets you keep your projects synchronized. This is useful when your "source of truth" needs to be updated. You will be able to simply update the stories in the template project, and the changes can be automatically applied to all the projects that were created from it.

To initialize the new projects themselves, I think the easiest way is to set up an Automation rule such as this one :

Basically what happens here is that every time a new project is created, the Epics (including all their issues and subtasks) from a template project TPL are automatically copied to the new project. This rule can be customized to your needs thanks to the variety offered by Automation and its full integration with Copy & Sync.

The app is free for 30 days, (and stays free if your instance is under 10 users), so feel free to give it a try, and don't hesitate to tell reach our Support if you have any question.

Kind regards,


4 votes
Tibor Hegyi _META-INF_
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Feb 09, 2016

An alternative to plugins is the feature in JIRA. When you create a project, the project type selector dialog has a link at the bottom: "Create with shared configuration". 

If you choose that, you can select a source project to base your new project on. You can this way set up template projects, or simply select on of your real projects.

It creates a project with the setting configuration but not the tasks

Like # people like this

Hi all ... Anyone found any route to do this? I will look at the Deep Clone add on but would like to try control this internal and possibly do this without an add on - either via the Interface or API? Anyone? Thanks in advance for new updates.

Marlene Kegel - codefortynine
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
Dec 03, 2020

It might be interesting that we released an update for Deep Clone for Jira that enables you to clone entire Jira classic projects (plus components, versions, settings, issues, ...).


This should be free

Like Jen Jordan likes this

Hi All,

I have cloned a project in jira from another project. But when i change any field in my new project it gets changed in my old as well. How to I solve this? Thanks in advance. 

When you clone a project, the schemes get cloned as well. Unless you create a new scheme, any time you update a scheme it will affect both projects. 

These schemes are:

  • permission scheme
  • notification scheme
  • issue security scheme
  • workflow scheme
  • issue type scheme
  • issue type screen scheme
  • field configuration scheme
Like # people like this
1 vote
Deniz Oğuz
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 09, 2016

Should be standard functionality.

Like # people like this

Yeah, I agree, it should be free and simple, like a button above the "Send to Trash" on the project, like "Clone Project">

I've entered all the free links, none of them are free for cloud and the ones tagged as free no longer function.

This is very sad, is there any kind of ticket raised for Atlassian for this matter?

Starting in the Projects screen, select Create project.

Click Advanced.  Select Share settings with an existing project and specify the Key of the project you want to clone.

Older version had an option to copy all tasks and connections too, Is this really gone now!?

Like # people like this

Curious about this as well

It doesn't copy the tasks and connections just the settings

It doesn't copy the board either.

Is the Advanced setting gone? I don't even see it now? When I create a project it sends me to the project templates screen which doesn't seem to allow this...

Suggest an answer

Log in or Sign up to answer