Upgrade and Import Project with Greenhopper 5.7.4 to 5.8.4 index problem?

[Thomas Trostel]

I'm having a problem importing a project into our new system. I have upgraded JIRA (4.4.4) and Greenhopper(5.8.7) on the source system and re-indexed to produce a new backup ... however when I try to import the project I get the following error:

The backup project 'XXX' requires custom field named 'Global Rank' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of JIRA the plugin is at version '5.8.4', but in the backup it is at version '5.7.4'.

What steps can I take to rectify this situation?

[chrismott]

I had this problem, exporting from JIRA OnDemand (5.0.4) and importing into standalone JIRA (5.0.4) with GH 5.9.7. The validation error that I got was:

• The backup project 'Data Service' requires custom field named 'Global Rank' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of JIRA the plugin is at version '5.9.7', but in the backup it is at version '5.9.5'.

• The backup project 'Data Service' requires custom field named 'Rank' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of JIRA the plugin is at version '5.9.7', but in the backup it is at version '5.9.5'.

• The backup project 'Data Service' 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 '5.9.7', but in the backup it is at version '5.9.5'.

Taking suggestion above to edit the XML, this is the solution I used:

1) Exported JIRA from OnDemand, using a beta exported (enabled with a ticked to support)

2) Unzipped the backup file

3) Replaced all instances of "5.9.5" with "5.9.7" in the entities.xml (NOTE: i manually inspected all instanaces "5.9.5" to ensure they were just Greenhopper related) :

used a perl script:

#!/bin/sh
# Globally replace one string with another in a set of files
/usr/bin/perl -p -i -e "s/$1/$2/g" $3

called like this:

replace.sh "5\.9\.5" "5.9.7" entities.xml

4) Zipped the contents of the export back up into a zip file

5) Followed the restoring a project instructions

That edit eliminated the error in the import validation, and the import proceeded successfully. Looks like the integrity of my data is good so far.

[sclowes]

Hi Thomas,

This is a restriction to do with the way that project imports happen (specifically, they do not run upgrade tasks so GreenHopper cannot automatically migrate the necessary data from the 5.7.4 version to the 5.8.4 version.

The required procedure is documented at http://confluence.atlassian.com/display/JIRA/Restoring+a+Project+from+Backup

Basically, you need to import the entire backup in to a system with the same JIRA and GreenHopper versions as in your target system. You can then re-export the data and import just the project in to the target system.

Thanks,

Shaun

[Michael Andreacchio]

Hi Thomas,

Thanks for your question there. It seems that your instance at the moment with GH 5.8.4 is looking for a global rank field inside of your .xml backup. It won't be finding it because this fiels did not exist from when your backup was made back with GreenHopper 5.7.4.

We would recommend getting your JIRA 4.4.4 installed with the older version of GreenHopper 5.7.4 and then trying to import the .xml data from there, and then upgrading GreenHopper from that point.

If you experience any difficulties with this please log an issue with us on support.atlassian.com

Cheers,

Michael

[Thomas Schlegel]

Hi Thomas,

have a look here: https://jira.atlassian.com/browse/JRA-26085

Unfortunately this major Bug is unresolved. Perhaps you can manually modify the xml ?

Cheers

Thomas