nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Copy project to another Jira instance

Michael Danielsson

I have a project in production and want to copy it to another JIRA instance where I can play around with it or where I can use it as a demo project on courses.

I have seen that it is possible to copy the workflow as xml and import it, but you need to have all statuses an possibly all screens that are used in the workflow.

*Is there some way to copy all settings from the project or copy the whole project to a new JIRA instance?*

It is not neccessary to have the data copied.

Regards,

Michael

Accepted answers

All comments

Luis Mayora1

If this is for a demo why dont you overlay the data from production to your training site. I think this should be a good practice since all data gets migrated and not just pieces of configuration. It shouldnt take you that much time.

1. Shutdown JIRA Training Site

2. Copy Attachments from Prod to Training Site

3. Export All Data from Data (Export Folder as Zip)

4. Copy .zip to the Training Site (Import Folder)

5. Start JIRA Training Site

6. Importa Data.

Michael Danielsson

I have more than one project with the same settings and the projects are confidential for others than members in the project. Therfor when I shall demo something or hold a course with some hands on I want to have the possibility to use the project setup but create some dummy issues.

Is it possible to remove all issues from a project?

Jo-Anne MacLeod

Given what you have said above, I would just manually create a new project using the same settings as the original project. Its going to be easier to do that way.

If you are able to bring the xml backuop over from your production system. After you have it running in your new instance, just run a query to get all the issues in the project, and do a 'bulk delete' (upper right of your screen is tools -> bulk change -> delete)

bring over the xml backup, and then just make a new project using the same settings as the old project. The new one will not have any issues in it, but all the screens workflows issue types etc will be the same. Delete the old project if you are really concerned.

Michael Danielsson

I have made an XML backup of the production JIRA and tried to import just one project.

The problem is that I have to have the statuses, custom fields, workflows, etc in the demo environment and what I wanted to find a solution for was to not have to do the setup in that environment too.

I suppose it would be possible to restore the whole backup but it is big and I am only interested in one project.

Isn't there a way to just clone one project, including all settings, from one JIRA instance to another?

Or is there a way to clone the necesary settings to the new JIRA instance?

Jo-Anne MacLeod

not easily. Not without everything else already in place.

Barry Britnell

Michael,

I am working on a plugin right now that does exactly what you are asking. However, what Jo-Anne has stated is correct, it's not easy. We have about a 60% solution in place, but that is all. I am hoping that with the new stable API in v5.0, this might become easier. But, we're still pressing forward trying to develop a solution.

José Marañón [Awnaba Software S.L.]

There is a plugin called Project Configurator, that copies all elements in a project configuration (workflows, schemes, custom fields, screens, statuses,...) to an XML file and it is able to restore it later to another JIRA instance, regardless those configuration elements already exist in the new instance. It does not transfer data (issues or attachments), just the configuration.

(Disclaimer: I am a developer of this plugin)

TJ Baker

A feature request has been created for this, please vote for it: https://jira.atlassian.com/browse/AOD-6722