-
Type:
Bug
-
Resolution: Cannot Reproduce
-
Priority:
Low
-
None
-
Affects Version/s: 6.2.1, 6.6.0
-
Component/s: 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