-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
6.1.3, 6.2.5, 6.4.4, 6.4.12, 7.0.10, 7.2.1, 7.2.6, 7.7.0, 7.0.0, 8.5.4, 8.13.18
-
6.01
-
82
-
Severity 3 - Minor
-
3
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
Diagnosis
Importing project from one JIRA + JIRA Agile instance with English (United States) to a new instance JIRA + JIRA Agile instance on English (UK)
Steps to reproduce
- Create backup on one instance using English (United States) language
- Start a new instance on English (UK) language
- Run project import onto the new instance
Error message
2013-11-25 09:28:23,298 JiraTaskExectionThread-6 ERROR admin 568x816x1 1m076so 0:0:0:0:0:0:0:1 /secure/admin/ProjectImportSelectProject.jspa [jira.imports.project.DefaultProjectImportService] The custom field 'Epic Color' of type 'Colour of Epic' is required for the import but does not exist in the current JIRA instance.
Cause of error
The difference of letter 'u' in Epic Color and Epic Colour causes JIRA to think that there are 2 different custom fields.
Workaround
Rename the custom field manually. Refer to this guide.
If the custom field is locked, unlock it first using the guide here - How to unlock a Locked field
- is duplicated by
-
JSWSERVER-10106 Cannot do Project Import between different language that have JIRA Agile values.
- Closed
- is related to
-
JSWSERVER-16571 The same field is spelled in two ways, "Epic Color" (American spelling) and "Epic Colour" (British spelling)
- Gathering Impact
- relates to
-
JRACLOUD-35937 Project Import fails with "custom field xxx of type xxx is required for the import but does not exist"
- Closed