How can I clone a project in JIRA?

[LuziaL]

Would it be possible to download an XML copy of all the issues in a particular project and upload them into another project within the same JIRA Instance?

[spuddy ಠ_ಠ · Accepted solution]

JIRA allows you to restore a single Project from an XML backup, see Restoring a Project from Backup.

Since you want to restore (clone) the Project into the same JIRA instance, you should rename the source Project before doing the restore.

For example, if you want to clone Project SRC to TGT

• Make an XML backup.
• Copy your attachments directory somewhere.
• Rename SRC to TGT.
• Recreate a blank SRC project with the same schemes/settings as TGT.
• Restore SRC from the XML backup, you will need to point to the restore process to the copy of your attachements directory.

I suggest doing a trial-run of this procedure in a test environment first. (You can easily create a test environment with your XML backup and the copy of the attachements directory you need for the first two steps.)

[Radu Dumitriu]

Additionally, if you are not afraid of XML, you can simply modify the XML (not JIRA recommended way, but I used it). However, you MUST definitevly TRY it first on a CLONE of your production environment. Sorry for the emphasis, but it's needed :)

[Bob Swift OSS (Bob Swift Atlassian Apps)]

You can use the JIRA Command Line Interface getIssueList to get all issues within a project. Then there are a couple of options to automate copying them into a new project. Either use createIssue, cloneIssue or runFromCsv to process. This solution is best if it is a regular thing you need to do with automation as opposed to a one time thing :). cloneIssue between projects requires JIRA Clone-Plus plugin

NEW: A new cloneProject CLI action is in progress - a snapshot will be available soon! See JCLI-153 - comments and suggestions welcome there.

jira-cli-2.2.0-SNAPSHOT-distribution.zip is a snapshot available that implements JCLI-153 . Tested on 4.2.4, 4.3.3, and 4.4-beta1. I would like people to try it out and provide feedback.

[Andrei [errno]]

Bob, your cli-tools are fantastic! thanks

[Jobin Kuruvilla _Adaptavist_]

Not sure about XML but you can try exporting the issues into Excel, convert the file to CSV and use the in-built CSV importer to import it back to the new project.

http://confluence.atlassian.com/display/JIRA/Importing+Data+From+CSV

This would require all the customfields to be available in the target project as well. And the workflow should be same or else it requires a migration.

[DavidV]

Hi Luiza, not specifically answering your question, but you might find this interesting:

Have a look at this plugin:

https://plugins.atlassian.com/plugin/details/15453

Specifically have a look at this documentation to see what it does:

http://www.customware.net/repository/display/AtlassianPlugins/CustomWare+JIRA+Utilities+Usage+Guide

You could set up a workflow transition to copy your issue to a new project, and then perform a Bulk Edit operation to transition all your issues (or just the ones returned from your search).

[TJ Baker]

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

[David Skreiner]

• Status:CLOSED (View Workflow)
• Resolution:Won't Fix

... as usual when there's a paid addon as a "workaround", apparently