Issue with Epic Colour vs Epic Color

[Johnathan Smith]

We are trying to import a JIRA project from the cloud to a in-house version of JIRA..  

it looks like we are about 95% done... if I try to import the project to the new server I get the following:
Errors The data mappings have produced errors, you can not import this project until all errors have been resolved. See below for details. Custom Field Configuration The custom field 'Epic Colour' of type 'Color of Epic' is required for the import but does not exist in the current JIRA instance.... but I dont see any type "Color of Epic" please help

The issue is that:

Epic Colour LOCKED Epic Color field for JIRA Agile use only. Color of Epic but on the in-house version of JIRA Agile 6.7.2 installed we dont have "Epic Colour" we have: Epic Color LOCKED Epic Color field for JIRA Agile use only. Color of Epic so the fields dont match... what can we do?

[Juergen Lanner]

Hi Johnathan, did you find a way to overcome the problem then? How?
Thx Juergen 

[Juergen Lanner]

Renaming the field solved the problem for me. A howto can be found in https://jira.atlassian.com/browse/JRA-35937

[Michael Steiner]

you can update the table in the database of your JIRA

in SQL it is located here

"SELECT id,customfieldtypekey,cfname from customfield where cfname like 'epic%'"

[Michael Steiner]

it is the system language   EN US vs EN UK

[Martin Zdarsky]

yes it is US vs UK. Imagine you need to merge 2 instances of JIRA together. One with UK and the second with US.

[Martin Zdarsky]

still happening for JIRA 7.0.10

[Johnathan Smith]

We are running.. JIRA Agile 6.7.2 in-house and the cloud is running 6.5-OD-03-002... I was told to upgrade to 6.7.2 in-house

[Kian Stack Mumo Systems]

What versions are you using of JIRA Agile/Greenhopper on both?