Requires custom field named 'Epic Colour' with wrong version.

Hi All,

I found the following issue:

I try to import some projects to our enviromnent, but I got the following issues:

  • The backup project 'PROJECT1' 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.3', but in the backup it is at version '6.2'.
  • The backup project 'PROJECT1' 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.3', but in the backup it is at version '6.2'.
  • The backup project 'PROJECT1' 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.3', but in the backup it is at version '6.2'.
  • The backup project 'PROJECT1' 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.3', but in the backup it is at version '6.2'.
  • The backup project 'PROJECT1' 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.3', but in the backup it is at version '6.2'.
  • The backup project 'PROJECT1' 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.3', but in the backup it is at version '6.2'.

The problem is that I have installed the 6.2.3 version to the source Jira and re-indexed the issues, but get the messages above.

Did anyone get this issue before?

Thanks for your help!

Regards,

Norbert

3 answers

0 votes

Di you take a new backup after the 6.2.3 verison is installed in source JIRA?

0 votes
Ruchi Tandon Atlassian Team Nov 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.

Do we any other solution for this ???

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,723 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you