Incorrect Issue Type Configuration for Custom Fields Stops CSV Import

Still need help?

The Atlassian Community is here for you.

Ask the community


During the import of a CSV file into an existing Project containing Custom Fields, the import process will encounter an error and stop.


The resulting error log reports:

2014-09-23 13:46:18,909 JiraTaskExectionThread-11 ERROR user 826x7970x1 1bl903h,, /secure/admin/ImporterLogsPage!import.jspa [imports.importer.impl.AbstractDataImporter$1Thread[http-bio-8080-exec-19,5,main]] Unexpected failure occurred. Importer will stop immediately. Data may be in an unstable state
	at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CustomFieldsUtil.createOptionIfDoesNotExist(
	at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CustomFieldsUtil.handleOptionsInHierarchy(
	at com.atlassian.jira.plugins.importer.imports.importer.impl.customfields.CustomFieldsUtil.addOptions(


JIRA 6.3.6 with JIRA Importers Plugin (JIM) version 6.2.3 (likely affects other versions)

Issues contained in the CSV file utilize custom fields that were already created/configured in JIRA.


The Custom Fields within JIRA do not have Issue Type associations to match the Issues being imported from the CSV file.


  1. Gather data from CSV file
    1. Identify Custom Fields to be imported
    2. Identify Issue Types used per Custom Field
  2. Go to Administration >> Issues >> Custom Fields
  3. For each Custom Field identified:
    1. Find custom field
    2. Click the 'cog' icon for the custom field
    3. Click Configure
    4. Click Edit Configuration

    5. Under 'Choose applicable issue types' heading, use the 'Issue Types' selection field to choose appropriate issue types for custom field

Check the 'applicable context' for custom fields on the same screen to ensure your custom field is compatible with your Project(s). 'Global Context' allows the custom field to be used with any Project.

Last modified on Feb 26, 2016

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.