Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-35937

Project Import fails with "custom field xxx of type xxx is required for the import but does not exist"

XMLWordPrintable

      NOTE: This bug report is for JIRA Cloud. Using JIRA Server? 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

      1. Create backup on one instance using English (United States) language
      2. Start a new instance on English (UK) language
      3. Run project import onto the new instance

      Error message

      atlassian-jira.log
      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

        1. project import.png
          project import.png
          54 kB

            ohookins@atlassian.com Oliver Hookins (Inactive)
            cchan Chung Park Chan
            Votes:
            7 Vote for this issue
            Watchers:
            19 Start watching this issue

              Created:
              Updated:
              Resolved: