What are my options for bulk moving JIRA issues between On Demand instances?

We have a closed JIRA instance, and want to mostly open it. We're starting a new open (default public) instance, and want to move issues from the old to the new. I know there isn't a simple bulk export, edit, bulk import flow I can use. What are my options?

1 answer

1 vote
Pedro Souza Atlassian Team Jun 16, 2014

Hello,

Actually there is no way to merge two OnDrmand instances directly, you will need to merge the data in a Standalone instance, then perform a full import to your OnDemand instance.

This article may provide you more detailed information:

https://confluence.atlassian.com/display/ONDEMANDKB/How+to+Merge+Two+JIRA+OnDemand+Instances

Cheers.

Pedro Souza Atlassian Team Jun 16, 2014

Hey Ned,

Yes, this is much easier! you will need to take a backup from your old instance, and restore this backup in your new instance, we have some documents that can help you with this procedure:

https://confluence.atlassian.com/display/ONDEMANDKB/Restoring+a+JIRA+OnDemand+Backup+into+a+JIRA+OnDemand+instance

https://confluence.atlassian.com/display/ONDEMANDKB/Changing+the+OnDemand+instance+URL+address

Feel free to contact us at support.atlassian.comin case you face any issue during the import.

Cheers.

Thanks, I may not have been clear. The new instance doesn't have any issues in it. We just want to move issues from the old to the (now empty) new. Does that change the answer?

Thanks, I have read about this option, but it sounds like it's an all-or-nothing proposition. Is there any way to control which subset of issues end up in the new system?

Pedro Souza Atlassian Team Jun 16, 2014

Yes you're correct, it will import everything, or nothing.

I think you can import all the data, and simply delete what is not relevant to your new OnDemand instance.

I know this is a kind of extra work, but for now we don't have an option to choose what will be imported to an OnDemand instance during a restore or Project Import.

We're now looking at using the per-issue export to XML as a way to build a CSV file that we can import. Is this crazy? Is there a reason this won't work? Is there a better option? Can you point me to docs for the CSV import format?

Pedro Souza Atlassian Team Jun 16, 2014

Got it, here's another sugestion if so:

Run a filter searching for those issues that you want to import to the new instance, then Export the filter result to an Excel file (with all fields), open the Excel file and conver to a CSV file, perform the proper adjust on the CSV, and perform the import as per of our documentation:

https://confluence.atlassian.com/display/AOD/Importing+Data+from+CSV

https://confluence.atlassian.com/display/AOD/Exporting+Search+Results+to+Microsoft+Excel

See if it helps. :D

Best Regards.

The excel(all fields) export does not include the comments, you only get get issue titles& description.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

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...

2,417 views 15 19
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you