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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs