Custom Field <name> has multiple configuration schemes. Importer is unable to extend custom field context automatically.
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When importing a project into JIRA, the message "Custom Field <name> has multiple configuration schemes. Importer is unable to extend custom field context automatically." appears, with a warning that the import was incomplete. The following appears in the atlassian-jira.log:
1
2013-04-19 10:52:26,495 JiraTaskExectionThread-13 WARN username 652x369343x1 kgr84o 127.0.0.1 /secure/admin/views/ImporterLogsPage!import.jspa [imports.importer.impl.DefaultJiraDataImporter$1Thread[http-8080-22,5,main]] Custom field 'Rework Reason' has multiple configuration schemes. Importer is unable to extend custom field context automatically.Diagnosis
This occurs in the situation where a CSV or other import attempts to add data to a Custom field A for issueType B and all following conditions are met:
Custom field A has multiple Custom Field Configuration schemes
Custom field A has specific list of issues types (not 'Global (all issues)' )
Custom field A has no context which are applicable to Project and IssueType B.
Cause
If the issueType is not part of the context of this custom field, then the field data cannot be saved.
Resolution
Main step: Add issueType B into one of a Custom field A context.
Optional steps: If don't specify issueType during import, make sure that default project issueType has a valid context. Or make sure that issueType column is present and set:
Add an issueType column
Add an issueType in this column for every issue (if you're importing to existing issues, this should match the issues' current issueTypes)
Retry import
Was this helpful?