Importing Project from JIRA OnDemand to Standalone
This week I had to import some projects from JIRA OnDemand (atlassian.net) into our company’s Standalone JIRA instance.
OnDemand JIRA Version: 6.0-OD-01
Standalone JIRA Version: v5.2.1#813
Frist, I took a full backup on the source JIRA using JIRA Backup Manager, and copied to the Standalone server to .\Appdata\JIRA\import.
Then went to System -> Import & Export -> Project Import where the fun began.
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 '813', but the supplied backup file was for build number '6001'.
JIRA OnDemand is always slightly newer than the Standalone released version, but the problem is that JIRA thinks the two backups are incompatible. To correct this, I had to edit the entities.xml file in the backup.
Actually, there’s was more work in that file, so what I did was deleting the data folder from the archive, so the extract - repack would go smoother. I’ve used Total Commander to open the zip because it allows you to edit the file directly in the archive. Configured Notepad++ as the editor because it’s faster with large files than Windows Notepad.
To fix the version info, I had to find this:
<OSPropertyString id="10047" value="6001"/>
and replace with:
<OSPropertyString id="10047" value="813"/>
The next problem was with the plugins, which were also newer on the source JIRA.
The backup project 'IPM' 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 '6.0.8', but in the backup it is at
version '6.0.8-rc2'.
The backup project 'IPM' 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.0.8', but in the backup it
is at version '6.0.8-rc2'.
The backup project 'IPM' 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.0.8', but in the backup it is at
version '6.0.8-rc2'.
The backup project 'IPM' requires custom field named
'\[CHART\] Date of First Response' with full key
'com.atlassian.jira.ext.charting:firstresponsedate'. In the current instance of
JIRA the plugin is at version '1.10', but in the backup it is at version
'1.10.4'.
The backup project 'IPM' requires custom field named
'\[CHART\] Time in Status' with full key
'com.atlassian.jira.ext.charting:timeinstatus'. In the current instance of JIRA
the plugin is at version '1.10', but in the backup it is at version '1.10.4'.
To fix this, I replaced all instances of "6.0.8-rc2" with "6.0.8" (including the double quotes) in entities.xml, being the latest public Greenhopper version. Also substituted "1.10.4" with "1.10"
The next issue was with user mapping. The users at atlassian.net had different usernames then those in Active Directory. JIRA gave me the list of users that have this problem, and I had to update entities.xml for those users. So I searched for example for "jsmith" and changed to "john.smith" which corresponds with the Active Directory username. Repeated this step for all users who were having issues.
I could have done the same with the mismatching groups, but I’ll just manually assign roles for the new groups after the project import.
There were a few unresolved issues left:
The custom field 'Billing Key' will not be imported because the custom field type 'is.origo.jira.tempo-plugin:billingKeys' is not installed.
We’re not using the Tempo plugin so this error can be ignored.
Unable to import custom field '[CHART] Time in Status'. The custom field type does not support project imports.
Unable to import custom field 'Sprint'. The custom field type does not support project imports.
This is a significant issue, it’s still under investigation. There’s a bug report at Atlassian JIRA-28748 for tracking this.
Originally posted to: http://www.thesysadminhimself.com/2012/12/importing-project-from-jira-ondemand-to.html
Comments