Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira Migration from Cloud to Jira Server 7.2.0

Rangaraj January 21, 2019

Hi Team,

 

I am trying to migrate projects from Jira Cloud to Jira In-house. I am running into issues with Greenhopper and Development Integration Plugin.

The backup project 'project1' 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 '7.2.8-DAILY20160816152029', but in the backup it is at version '1000.20.0'.

The backup project 'project1' requires custom field named 'development' with full key 'com.atlassian.jira.plugins.jira-development-integration-plugin:devsummarycf'. In the current instance of JIRA the plugin is at version '4.0.5', but in the backup it is at version '5.0.0-D20160815T040704'.

 

Please provide download link for compatible server version of Greenhopper(1000.20.0) and Development Integration Plugin(5.0.0-D20160815T040704) 

3 answers

2 votes
Charly [DEISER]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 21, 2019

Hi @Rangaraj

I believe that the problem is your server version (7.2.0), if you are migrating from cloud you need to have the latest stable products version.

 

Try installing a trial with the latest version and importing the backup again.

Hope this helps!

Rangaraj January 21, 2019

Hi @Charly [DEISER],

 

I have tried 7.13.0 version and i got below error and I find the build number is 72002 is compatible with 7.2.0. Even 7.6.6 version also has same issue.

This data appears to be from an older version of Jira. Please upgrade the data and try again. The current version of Jira is at build number '713000', but the supplied backup file was for build number '72002'.

Is there a way to upgrade Jira Cloud build number(72002) to latest ?

 

Thanks,

Rangaraj

0 votes
Tarun Sapra
Community Champion
January 21, 2019

Hello @Rangaraj

The cloud version is always the latest version, thus in order to restore your cloud backup on the server then you need to make sure that the server version is the latest as well.

Complete docs here

https://confluence.atlassian.com/adminjiraserver/migrating-from-jira-cloud-to-server-applications-938846963.html

Rangaraj January 22, 2019

Hi ,

 

I have tried backup from cloud , it is showing build number correctly. but when I do backup for server, it comes with wrong build number(72002).

 

Do anyone face this kind of export issue before?

 

Thanks,

Rangaraj

0 votes
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 21, 2019

Hello,

What do you mean by Jira Cloud? Do you mean that your Jira Cloud instance exists in yourdomain.altassian.net? Or you installed an on-prem Jira to AWS or something similair?

Rangaraj January 21, 2019

Yes, Jira Cloud instance exists in yourdomain.altassian.net

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 21, 2019

It is strange. You should take a Jira Backup for Server in your Jira Cloud and install it to the latest Jira Server version available (7.13.0 right now). And it should work.

Rangaraj January 21, 2019

Hi @Alexey Matveev

 

My cloud jira instance is showing version as 1001.0.0-SNAPSHOT with build(100098). But when I do Jira Backup for server and try to import projects in Jira Server 7.13.0, it shows "the supplied backup file was for build number '72002'".

 

This is so confusing.

 

Is there any other option to identify the exact build number of backup file or to upgrade backup file to latest build version.

 

Thanks,

Rangaraj

Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 21, 2019

I never had a problem like you have....

Tarun Sapra
Contributor
January 21, 2019

Hello @Rangaraj

The error you are facing is because at the time of backup you have to mention that the backup is for server, as I think by default it takes the backup for cloud only.

Rangaraj January 21, 2019

@Alexey Matveev

One more information about the issue.

Cloud Jira Instances : 

Version : 1001.0.0-SNAPSHOT
Build # : 100098

Jira Server :

Version : v7.13.0 #713000

 

Original backup(Backup for Server) from Cloud Jira Instance failed during import with below error.

There was a problem parsing the backup XML file at E:\Atlassian\Application Data\JIRA\import\jira-export.zip: No 'key' field for Issue 35656.

So  I have ran python script given in below link to make the backup file compatible with Jira Server

https://community.atlassian.com/t5/Jira-questions/Import-Error-No-key-field-for-Issue/qaq-p/582385

After running the python script against the backup file, I tried to upload the backup file and got build mismatch error given below.

This data appears to be from an older version of Jira. Please upgrade the data and try again. The current version of Jira is at build number '713000', but the supplied backup file was for build number '72002'.

Please let me know if any solution available for this issue.

Thanks,

Rangaraj

  

Rangaraj January 21, 2019

Hi @Tarun Sapra,

 

I have selected Back up for Server and download the file.

 

Jira_export_info.png 

Thanks,

Rangaraj

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events