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

Importing a project/CSV is failing due to a Custom Field restricted to Issue Types



    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      When performing a project import if there are some custom fields that are only applicable to some issue types the import will fail.

      The following error is received:

      2012-06-13 14:02:29,491 JiraTaskExectionThread-39 ERROR jsteeves 840x577987x5 hez62m /secure/admin/ProjectImportSelectProject.jspa [jira.imports.project.DefaultProjectImportService] The custom field 'Program Phase' in the backup project is used by issue types 'Document, Document Revision' but the field with the same name in the current JIRA instance is not available to those issue types in this project.

      In this example it means that the custom field 'Program Phase' is failing because it is restricted to the issue type 'Document, Document Revision'

      When the import occurs JIRA thinks that it can't use that custom field because of the restrictions.


      Follow the error messages and make the fields in the error applicable to all issue types, the import should succeed from there. In the example above 'Program Phase' needs to be applicable to all issue types.


        1. Import_Error.png
          100 kB
          Pamela Stanfield
        2. jira230911091255-stdout.2012-04-23.zip
          264 kB
          Pamela Stanfield
        3. Severity_Values.png
          71 kB
          Pamela Stanfield

        Issue Links



              Unassigned Unassigned
              0d036eb0581b Pamela Stanfield
              3 Vote for this issue
              12 Start watching this issue