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
Works for JIRA 7 and above.
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."
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.
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.
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.
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.
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 firstname.lastname@example.org.
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.
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 email@example.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.
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 firstname.lastname@example.org 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.
Just to update this thread.
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.
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.
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.
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