-
Bug
-
Resolution: Cannot Reproduce
-
Low (View bug fix roadmap)
-
None
-
6.2.1, 6.6.0
-
None
-
6.02
-
There has been a couple reports of failed project imports due to incompatible Greenhopper versions between source and destination instances. In the UI it appears that all everything matches up, however taking a closer look in the database, or XML backup, the inconsistencies start to unravel.
From the XML backup we noticed the following.
application properties section:
com.pyxis.greenhopper.jira:build : 33
User plugins section:
Atlassian GreenHopper : com.pyxis.greenhopper.jira
Version : 6.2.1
The above looks like the version is 6.2.1. Digging deeper though we find in the same XML backup the version is different:
<PluginVersion id="10100" name="GreenHopper" key="com.pyxis.greenhopper.jira" version="5.7.4" created="2012-06-22 15:35:34.0"/> <PluginVersion id="10100" name="GreenHopper" key="com.pyxis.greenhopper.jira" version="5.8.7" created="2012-06-22 15:35:34.0"/> <PluginVersion id="12001" name="Atlassian GreenHopper" key="com.pyxis.greenhopper.jira" version="6.1.6" created="2013-04-10 09:13:56.11"/>
Running the following query on the database where the XML was generated from shows the latest version of 6.1.6 as well:
select * from propertystring where id=(select id from propertyentry where property_key='GreenHopper Version');
Resolution
- Restarting JIRA appears to update the inconsistent version stored in the database, which should ensure any XML backup generated after that contains consistent version numbers.
KB article: Incompatible Greenhopper version during project import in JIRA
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-8973] Incorrect version stored in database table propertystring
Not sure what is going on here, but there are two major problems in the data as provided in the bug report:
<PluginVersion id="10100" name="GreenHopper" key="com.pyxis.greenhopper.jira" version="5.7.4" created="2012-06-22 15:35:34.0"/> <PluginVersion id="10100" name="GreenHopper" key="com.pyxis.greenhopper.jira" version="5.8.7" created="2012-06-22 15:35:34.0"/> <PluginVersion id="12001" name="Atlassian GreenHopper" key="com.pyxis.greenhopper.jira" version="6.1.6" created="2013-04-10 09:13:56.11"/>
Firstly, the "key" value (called "pluginkey" in the DB) should be unique, but all entries have the same key AFAICT.
Perhaps this problem is stopping JIRA from being able to do further updates on the PluginVersion???
Even more bizarre is the ID values ... the first two entries have the same ID even though this is the primary key of the DB table - how can this even happen?
I am surprised if you can even import this XML file with a "full import" let alone a project import.
Same issue in Jira 7.0.0 when I load a backup to import a project:
Das Sicherungsprojekt '<project>' erfordert ein benutzerdefiniertes Feld namens 'Epos-Farbe' mit vollem Schlüssel 'com.pyxis.greenhopper.jira:gh-epic-color'. Der Plugin in der aktuellen JIRA-Instanz ist bei Version '7.0.4-D20150923T101309', in der Sicherung ist es aber bei '7.0.6'.
...
Restarting the Jira Instance didn´t resolve the problem :-/
Update 1: Update my Jira Instances to 7.0.4 resolves the problem 
David Shaw
added a comment - Struck this issue with JIRA Agile 6.7.7 (on my local server) being incompatible with JIRA Agile 6.7.11 (OnDemand). Rebooting JIRA (local) did not resolve it. So I am unable to export projects from my OD instance to a local instance 
The plugin is currently name "JIRA Agile". The local version is "6.7.7-D20150701T035938".
David Shaw
added a comment - Struck this issue with JIRA Agile 6.7.7 (on my local server) being incompatible with JIRA Agile 6.7.11 (OnDemand). Rebooting JIRA (local) did not resolve it. So I am unable to export projects from my OD instance to a local instance
The plugin is currently name "JIRA Agile". The local version is "6.7.7-D20150701T035938". Even we are facing this issue, and bouncing JIRA didn't resolve the problem. We upgraded from 6.4.3 to 6.6.0. So the affected version is 6.6.0.
hemanth acharya
added a comment - - edited Even we are facing this issue, and bouncing JIRA didn't resolve the problem. We upgraded from 6.4.3 to 6.6.0. So the affected version is 6.6.0. 
Daniel Prahl
added a comment - I'm experiencing the same issue after upgrading to Jira Agile 6.3.2.1.
Daniel Prahl
added a comment - I'm experiencing the same issue after upgrading to Jira Agile 6.3.2.1.
Verified project import is working as expected in JIRA Agile 7.0.2 and 7.0.6.
Checked the import process uses plugin key (e.g. com.pyxis.greenhopper.jira) and not plugin name (e.g. "GreenHopper", "Atlassian GreenHopper", "JIRA Agile", etc) to check versions.
Verified that JIRA Agile's plugin version in UPM matches the version in the database backup.
Looks like sanity checks for duplicate keys were added around May 2013 - databases which predate these could have inconsistent data in their backups (cause the import to fail). In that case the backup xml files would need to be manually edited to remove the duplicates before attempting the import.
Also note that the plugin version for source and destination instances must exactly match for the plugin import to work.