Single project migration error

Venu Madhav April 21, 2013

Hi,

I have tried to migrate a single project from backup file to new JIRA instance but while importing the project I got below error because of greenhopper version error. How to resolve this?

Could you please help me which is hurry.

  • The backup project 'ALM Test' requires custom field named 'Epic Colour' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of JIRA the plugin is at version '6.2', but in the backup it is at version '6.1.3.1'.
  • The backup project 'ALM Test' requires custom field named 'Epic Link' with full key 'com.pyxis.greenhopper.jira:gh-epic-link'. In the current instance of JIRA the plugin is at version '6.2', but in the backup it is at version '6.1.3.1'.
  • The backup project 'ALM Test' requires custom field named 'Epic Name' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of JIRA the plugin is at version '6.2', but in the backup it is at version '6.1.3.1'.
  • The backup project 'ALM Test' requires custom field named 'Epic Status' with full key 'com.pyxis.greenhopper.jira:gh-epic-status'. In the current instance of JIRA the plugin is at version '6.2', but in the backup it is at version '6.1.3.1'.
  • The backup project 'ALM Test' 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.2', but in the backup it is at version '6.1.3.1'.
  • The backup project 'ALM Test' 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.2', but in the backup it is at version '6.1.3.1'.
  • The backup project 'ALM Test' 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.2', but in the backup it is at version '6.1.3.1'.

Venu

3 answers

0 votes
Michael_Lamb January 9, 2017

I have two 7.0.5 servers and I am trying to export a single project and import that project into the second server and get the following error. I have restarted both servers.

 

  • The backup project 'Sentry' requires custom field named 'Epic Colour' with full key 'com.pyxis.greenhopper.jira:gh-epic-color'. In the current instance of JIRA the plugin is at version '7.0.11', but in the backup it is at version '7.0.10'.
  • The backup project 'Sentry' requires custom field named 'Epic Link' with full key 'com.pyxis.greenhopper.jira:gh-epic-link'. In the current instance of JIRA the plugin is at version '7.0.11', but in the backup it is at version '7.0.10'.
  • The backup project 'Sentry' requires custom field named 'Epic Name' with full key 'com.pyxis.greenhopper.jira:gh-epic-label'. In the current instance of JIRA the plugin is at version '7.0.11', but in the backup it is at version '7.0.10'.
  • The backup project 'Sentry' requires custom field named 'Epic Status' with full key 'com.pyxis.greenhopper.jira:gh-epic-status'. In the current instance of JIRA the plugin is at version '7.0.11', but in the backup it is at version '7.0.10'.
  • The backup project 'Sentry' requires custom field named 'Gantt-Chart' with full key 'de.polscheit.jira.plugins.gantt:gantt-bar'. In the current instance of JIRA the plugin is at version '4.0.7.3-JIRA7', but in the backup it is at version '2.1.6-JIRA5.1-UPM2.7.7'.
  • The backup project 'Sentry' requires custom field named 'Rank (Obsolete)' with full key 'com.pyxis.greenhopper.jira:gh-global-rank'. In the current instance of JIRA the plugin is at version '7.0.11', but in the backup it is at version '7.0.10'.
  • The backup project 'Sentry' requires custom field named 'Rank' with full key 'com.pyxis.greenhopper.jira:gh-lexo-rank'. In the current instance of JIRA the plugin is at version '7.0.11', but in the backup it is at version '7.0.10'.
  • The backup project 'Sentry' 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 '7.0.11', but in the backup it is at version '7.0.10'.
  • The backup project 'Sentry' 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.0.11', but in the backup it is at version '7.0.10'.
0 votes
Ruchi Tandon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 26, 2013

Looks like you are running into a known problem mentioned here:https://confluence.atlassian.com/display/JIRAKB/Incompatible+Greenhopper+version+during+project+import+in+JIRA

Try restarting JIRA and hopefully that would fix it.

0 votes
Peter Van de Voorde
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 21, 2013

You will probably need to:

  1. uninstall Greenhopper in your new Jira instance
  2. reinstall Greenhopper version 6.1.3.1
  3. Import your project
  4. Upgrade Greenhopper to the latest version.

You might also search the backup file for all reverses to 6.1.3.1 and replace them with 6.2, this might or might not work and should be done at your own risk.

Suggest an answer

Log in or Sign up to answer