Jira export for CSV import on a system where I am not a Jira Admin

[Rob Horan]

I have a situation that is somewhat difficult.  I am a Jira Admin on a dev instance that contains a project I need to migrate to a production instance.  I am not a Jira admin on that instance, but I have been given the ability to person a CSV import of issues on that server.

What is the best way to export data in a format that can be used for import of this sort?

Also, if this is not realistic, please let me know what a good alternative could be.

[Michael Kuhl {Appfire}]

Hi @Rob Horan - You can use the Bob Swift Jira CLI to create a CSV export of any project where you can browse the issues. 

Here's a how-to article that should help you out: How to export Jira issues to CSV.

If you need any help along the way, you can create a support ticket here.

FYI - I'm the product manager for the Bob Swift CLI line of products.

[Kristian Walker _Adaptavist_]

Hi Rob,

I can confirm that as Benjamin mentioned that Project Configurator will be the best way to migrate projects configuration and data from a dev instance to your production instance as this will allow you to simulate the import and to verify what will happen before you run the actual migration.

However, I can confirm to use Project Configurator that you will need to be given full admin permissions on both instances as full admin permissions are required for running an import.

If you are interested in Project Configurator then I would advise reading through our docs located here along with our Migration Checklist which will give you some best practices for when performing a migration.

Finally I can confirm we have some example use cases which contain demo videos located here and here which outline how the plugin works, and these may be a useful reference guide. 

I hope this information helps.

Regards,

Kristian

[Benjamin]

@rob That is challenging situation. I use project configurator plugin. This needs to be on both systems. 

First, you need to know if the production system has the same version or level or plugins your dev system has. Any slight difference will possible cause issue for the import. 

Second, you should import that project on a test system similar to production, to test your import files. 

Third, make sure the production is frequently backup incase you run into issue importing. 

The good thing about the project configurator, it will run a simulation to make sure the importing goes smooth.

Hope this helps.