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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I clone a project?

We have a template project and would like to create new projects using the same configuration. Where is the button to do that?

15 answers

1 accepted

10 votes
Answer accepted
Timothy Community Leader May 07, 2016

This question should be getting a new answer. You can indeed create a new project with an existing project as a template.

  • When you create a new project from a template, that project is created with its own fresh set of schemes. These schemes are:
    • a permission scheme
    • a notification scheme
    • an issue security scheme
    • a workflow scheme
    • an issue type scheme
    • an issue type screen scheme
    • a field configuration scheme

https://confluence.atlassian.com/adminjiracloud/defining-a-project-776636280.html

Works for JIRA 7 and above.

 

 

@Timothy Chin can you tell me exactly how to create a new project with an existing project as a template. that will really help me so far

Like # people like this

From the documentation:

"When you are creating a new project, select Create with shared configuration to select an existing project and to use that project's schemes. Note that when you're sharing schemes, any change to the scheme will affect all the projects using that scheme."

jira proj.png

Like # people like this

Well, this does not copy anything. However, quite handy.

Like # people like this

Specifically - it doesn't copy the components from the previous project :(

Like # people like this

I get a 500 error message when trying to clone a project

Definitely need the ability to copy an entire project

Like # people like this

hi, does anybody know whether any of the cloning project add-ons you can get on-line enable cloning of other add-on data? I'm working with ATM as a Test Management Add-on to JIRA and want to be able to clone a project including Test Management set up so that I can have a full project template complete with TM aspects for use by new projects.

Ridiculous? Not hardly. Dismissing this feature out of hand is shortsighted.

Like # people like this

It's completely insane this is feature is not available as default. Cloning a project for repeated engagements is not an outrageous idea.

Hi @Aidan Millar-Powell,

We've just released an update of our Jira cloud app Deep Clone for Jira that enables you to clone entire projects, including issues, configurations, components and versions. 

You can access the new feature over the bulk clone dialog. Just select "Clone project..." as target project. 

deep-clone-jira_project-clone_screen1.png

Please note: Currently this feature is only available for classic projects due to technical reasons.

Let us know if you have feedback or questions about this update.

Atlassian, no solution for this in 6 years (besides paid 3rd party apps) ... seriously?

Isso é tão básico... ter que configurar um projeto todo do zero toda vez que criar um é muito iniciante... no asana.com isso é default

Like mohammed_ounouna likes this

Pode botar mais um ano aí...

This is really inconvenient. Clone of a project should be really easy to add as a feature. 

Yes needs to as a feature. 

Like # people like this

So do we have any concrete way of cloning the project, When I say "Cloning", Literally copying everything. (Just a clone of my project)!?

It's crazy that you can't have project templates that INCLUDE issues/tasks, and be able to create a new project that includes everything. So frustrating. 

JIRA Core is pitched as a Marketing Project Management solution and we have so many projects that have the same implementation. To create a clone of all the issues from the template project takes about an hour, when it should be a simple click. 

Like abe.naoki likes this

Hi David, hi Pieter-Jan,

if you have to clone the template issues on a regular basis it's maybe more cost effective for you to work with Deep Clone for Jira.

With our cloud app it's possible to bulk clone more than 1000 issues at once. You can also move the issues to another project while cloning.

If you have questions or feedback don't hesitate to get in touch with us at support@codefortynine.com.

Update Nov 25, 2020: 

We've just released an upate for Deep Clone for Jira that enables you to clone projects, including issues, components and versions.

You access the new feature over the bulk clone dialog. Just select "Clone project..." as target project when configuring your bulk clone.

Please note: Due to technical reasons, this feature is only available for classic projects.

We're curious to get your feedback about this update.

3 votes
Deleted user Mar 13, 2019

Hi, 

Has anybody found a solution to having a project template which includes a set of default tickets that can be used when creating a new project? 

It seems like something that should be relatively straight forward, so I'm thinking I'm missing something, but judging by previous comments here, it doesn't seem like this is functionality that exists. 

Can I bulk clone a list of default tickets within JIRA does anybody know, using the Bulk Edit function?

With  our cloud app Deep Clone for Jira you can bulk clone up to 5000 issues at once.

Don't hesitate to get in touch with us at support@codefortynine.com if you have questions or feedback.

Update Nov 25, 2020:

As mentioned in my post above, we've released an update recently that enables you to clone projects, including a set of tickets.

Let us know, if you have feedback about this update.

Like Darren Ryan likes this
2 votes

Hi Luciano,

Alternatively, if your instance is not compatible with the plugin mentioned by Timothy, you could use the JIRA CLI plugin as mentioned in this KB - Clone/Copy and Entire JIRA Project

Or, if you're just not that keen on plugins, you could do it the old-fashioned way : Exporting a backup, and then performing project imports.

We use Jira OnDemand, will the JIRA CLI plugin also work here and how would the CLI command look like?

Yes and here is the documentation link: JIRA Command Line Interface.

More specifically, you will need the cloneProject action with the parameters that match your requirements. It provides granularity in what aspects of the project to copy, so you need to specify.

But don't I have to buy that plugin license to be allowed to use the JIRA CLI which is not available for OnDemand?

Yes, I recommend a trial license to verify this is a good solution for you.

  1. Go to CLI Plugin for JIRA
  2. Try it free
  3. It is a download plugin, but you do not need to install it. It is just for licensing.
  4. Install the client - see Installation and Use

I cannot understand why my credentials don't work even if I am an admin

I can't believe there's no solution for this. Most development and project management apps have this feature.

Hi, there's a paid App: ScriptRunner can do the clone.

FYI: How-to: Copy a Project Script - ScriptRunner for Jira Server

The built-in ScriptRunner script to copy a project worked like a champ.

 

Thank you.

issue dates back to 2013. Still, it seems to me like a solution is pending. If only the bulk changes to issues allowed the option "clone to another project" it would save a lot of time in a relatively simple way

this doesn't work for cloud and it's a paid add on.

If you want to bulk clone issues on Jira cloud you can try our cloud app Deep Clone for Jira.

Don't hesitate to get in touch with our support at support@codefortynine.com if you have questions or feedback.

Update Nov 25, 2020

As mentioned in my post above, we've released an update of Deep Clone for Jira that enables you to clone classic projects, including issues, components and versions.

Hi Luciano,

You can use the Copy project buildin script.

https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-CopyProject

Regards

Onkar Ahire

Hello All,

 

Any news for this? Should be really easy to do, just duplicate a project.

 

Thanks

Still can't clone a project but the workaround is to clone issues. Since you can perform mass actions to them in the issues navigator and can find all necessary issues in a given project with needed criteria.

Just to update this thread.  

  1. Create Project.
  2. Choose a Template. Scroll to the bottom of the list and Choose "Create with Shared Configuration".
  3. Choose a project from the list that you want to "clone"

Just remember that changes to the original will affect the clone.  you can, however, customise your new project separately (I assume that if you then change the original it only changes the non-customised parts).

What does this copy exactly? All the schemes associated with a project? (Issue Type, Workflow, Screens, Fields, Permissions, Notifications?) Does this ALSO bring over the Components? I need a global field with the same data inside every single project at our organization and would like to use Components in this manner but hella forum posts suggest this is not possible to use as a global field. This seems to be a VERY common request.

We don't have a "Jira Admin" position at our company and we don't want to lose ANY engineering velocity setting up a new project with the appropriate fields/data. We want to empower engineers to make new projects with ease. Please help.

Give the above suggestion a try and then check the results to confirm if it carries across your desired settings.

Ooo Ooo I know the answer: it doesn't.

The specific item that Kateri was asking about is Components, and these are not copied in projects created with shared configuration.

In fact, that is why it is called "Create with shared configuration" and not "Clone", and also why this isn't the solution for this question.

Typically, people who are looking to clone projects want to do so because there are items like components and even tickets that should be cloned - the default set of tickets that all projects should have.

Like # people like this

I did this the other day and was able to copy a project, the entire set up, permissions, workflows, permissions, everything.  It was awesome.  This is available when you click to create a new project, there is an option to "share settings with an existing project", when selected, it creates your new project with all the settings from that project you choose.

This is not a clone, as other have observed.

This is what it says it is:  a new project with shared settings.

A clone would have a copy of all tickets, so the master serves as a starting point for new projects with all the same default tickets etc.

Like # people like this

@Martin Gregory Yes, you are right, I am looking for a full clone of a project from classic to Next-Gen, Not just the settings.

@Erika Sa Can you please help us with this?

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you