Trying to move JIRA data in-house

[johnathansmith]

Right now my firm is using JIRA on the Atlassian site and we are looking to move (export) all the data into the in-house version of JIRA that we have..  

I want to the altassain JIRA and I did my backup file and I was going to import it into the JIRA we have in-house but I seen that we are running version  6.4.2 in-house and the online version is 6.5-OD-03-002.

I would like to know if the import would work.. also I was thinking of upgrading the in-house version but I dont see any 6.5 version online to download?

[crf]

In general, you have to use the latest public release and upgrade all plugins to the version that is currently used in JIRA Cloud.

Full instructions are here:  https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server

[johnathansmith]

Epic Colour LOCKED Epic Color field for JIRA Agile use only. Color of Epic but on the in-house version of JIRA Agile 6.7.2 installed we dont have "Epic Colour" we have: Epic Color LOCKED Epic Color field for JIRA Agile use only. Color of Epic so the fields dont match... what can we do?

[Matheus Fernandes]

Hi, Johnathan.

You should:

1. Restore the OD (Cloud) backup to a local/test JIRA 6.4.4 instance of JIRA;
2. Upgrade the current in-house instance to the latest available (6.4.4);
3. Create a backup of the test instance (with Cloud data);
4. Import it into the in-house 6.4.4 instance.

I hope this helps!

[johnathansmith]

If I try to do this Maetheue I am getting a "invalid license key" for the new test JIRA?

[Matheus Fernandes]

Go to my.atlassian.com and create a new evaluation license of JIRA. Then, when importing the Cloud data to the in-house test instance, apply the key when selecting the backup file. :)

[johnathansmith]

So this is where I am at.. I created i new test JIRA server with 6.4.2 and then I did a backup of the Cloud and then restore it to my Test JIRA (6.4.2) and it looks like everything is getting import. but the issue is now that I am trying to do a backup from my JIRA 6.4.2 server so I can import the project into my production JIRA 6.4.2 but it does not give me the BACKUP OPTION anymore???

[johnathansmith]

So this is where I am at.. I created i new test JIRA server with 6.4.2 and then I did a backup of the Cloud and then restore it to my Test JIRA (6.4.2) and it looks like everything is getting import.

but the issue is now that I am trying to do a backup from my JIRA 6.4.2 server so I can import the project into my production JIRA 6.4.2 but it does not give me the BACKUP OPTION anymore???

[Matheus Fernandes]

As per https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server, try to log in using the System Administrator account (sysadmin/sysadmin)

[johnathansmith]

But now I try to "import the project" to the production jira server and I am getting the following: The backup project ' Rest Gateway' requires custom field named 'Epic Colour' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'. The backup project ' Rest Gateway' requires custom field named 'Epic Link' with full key 'com.pyxis.greenhopper.jira:gh-epic-link'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'. The backup project ' Rest Gateway' requires custom field named 'Epic Name' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'. The backup project ' Rest Gateway' requires custom field named 'Epic Status' with full key 'com.pyxis.greenhopper.jira:gh-epic-status'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'. The backup project ' Rest Gateway' requires custom field named 'Rank (Obsolete)' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'. The backup project ' Rest Gateway' requires custom field named 'Rank' with full key 'com.pyxis.greenhopper.jira:gh-lexo-rank'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'. The backup project ' Rest Gateway' requires custom field named 'Release Version History' with full key 'com.pyxis.greenhopper.jira:greenhopper-releasedmultiversionhistory'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'. The backup project ' Rest Gateway' requires custom field named 'Sprint' with full key 'com.pyxis.greenhopper.jira:gh-sprint'. In the current instance of JIRA the plugin is at version '6.3.13.1', but in the backup it is at version '6.6.69'.

[crf]

As it says here: https://confluence.atlassian.com/display/JIRA/Migrating+from+JIRA+Cloud+to+JIRA+Server#MigratingfromJIRACloudtoJIRAServer-6.CheckwhichpluginsareinstalledonyourJIRACloudsite You need to identify and install the same version of JIRA Agile, as well as any other plugins. You cannot import JIRA Agile 6.6.69 version data if you are only running JIRA Agile 6.3.13.1.

[johnathansmith]

sorry I did not know that was AGILE.. Can you please tell me how to upgrade it

[Matheus Fernandes]

Just navigate to Administration » Add-ons » Manage Add-ons and upgrade it to the same version in both instances.

[johnathansmith]

Can you please tell me how can I upgrade to 6.6.69 without the market place my firm has the blocked

[Matheus Fernandes]

Download it from https://marketplace.atlassian.com/download/plugins/com.pyxis.greenhopper.jira/version/1870 And on the Manage Add-ons page, upload it. Just make sure to upload it to both instances

[johnathansmith]

if I upgrade the plug do we have any outage, restart or anything else...

[johnathansmith]

also if I upgrade to the new version of Agile will my lic still work?

[Matheus Fernandes]

No, there is no outage when updating add-ons (the add-on itself will be unavailable in while it is updated). If it is an evaluation license or if the license is not expired, it will still work. :)

[johnathansmith]

Every time I try to upload the jira-greenhopper-plugin-6-7-2.jar on the production servers I get uploading screen and if never comes back.. what should I look at or try

[crf]

If it is failing to resolve the plugin, then there should be error messages visible in JIRA's log files (atlassian-jira.log). Depending on your hardware and what other plugins you have installed that integrated with JIRA Agile, replacing the plugin on a live system can sometimes take several minutes even if it is going to succeed.

[johnathansmith]

we only have the Agile plug-in and I let it run for over 2 hours... Can you please tell me the location of the atassian-jira.log file... thanks and anything else I can look at

[crf]

<JIRA-HOME>/log/atlassian-jira.log

[crf]

Honestly, with the level of back and forth here and the likelihood that you will need a support engineer to help you make sense of the log, you should probably open a support request for this.

[johnathansmith]

it looks like we are about 95% done... if I try to import the project to the new server I get the following: Errors The data mappings have produced errors, you can not import this project until all errors have been resolved. See below for details. Custom Field Configuration The custom field 'Epic Colour' of type 'Color of Epic' is required for the import but does not exist in the current JIRA instance.... but I dont see any type "Color of Epic" please help

[Matheus Fernandes]

Try installing JIRA Agile in the instance in which you are importing the data and then importing it again

[Johnathan Smith]

I have JIRA Agile 6.7.2 installed

[Johnathan Smith]

I have JIRA Agile 6.7.2 installed

[johnathansmith]

Epic Colour LOCKED Epic Color field for JIRA Agile use only. Color of Epic but on the in-house version of JIRA Agile 6.7.2 installed we dont have "Epic Colour" we have: Epic Color LOCKED Epic Color field for JIRA Agile use only. Color of Epic so the fields dont match... what can we do?

[David Di Blasio]

Hi Johnathan,
Are you attempting to merge the OD instance with data that already exists on the local JIRA server, or are you wanting to just replace all the data on the local server with the OD data?

[Jobin Kuruvilla [Adaptavist]]

You can import it into the latest download version available. I haven't tried it when the next major version was out in Cloud but might just work.