Jira Import Error: Duplicate Custom Field ID

Platform Notice: Data Center Only - This article only applies to Atlassian apps 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

Trying to import a project leads to similar following error in atlassian-jira.log and the importing fails:

2013-04-01 14:30:47,880 IssueIndexer:thread-5 ERROR anonymous 855x17x1 xxxxx 0:0:0:0:0:0:0:1 /secure/SetupImport.jspa [issue.customfields.impl.AbstractSingleFieldType] More than one value stored for custom field id 'customfield_11660' for issue 'TEST-2'. Values [2.5E7, 2.2E8] 2013-04-01 14:30:47,883 IssueIndexer:thread-7 ERROR anonymous 855x17x1 xxxxx 0:0:0:0:0:0:0:1 /secure/SetupImport.jspa [issue.customfields.impl.AbstractSingleFieldType] More than one value stored for custom field id 'customfield_11660' for issue 'TEST-3'. Values [3.125E7, 2.3E8] 2013-04-01 14:30:47,946 IssueIndexer:thread-5 ERROR anonymous 855x17x1 xxxxx 0:0:0:0:0:0:0:1 /secure/SetupImport.jspa [issue.customfields.impl.AbstractSingleFieldType] More than one value stored for custom field id 'customfield_11660' for issue 'TEST-12'. Values [1.225E8, 3.2E8]

Cause

You have encountered the bug reported in JRA-12796 where the customfield_11660 has multiple values in them. The customfield_11660 exist in the Target JIRA instance and may exist in Source XML backup.

Workaround

  • If you happen to encounter the issue while restoring the XML backup and/or doing a Project Import, then you can proceed in following the instructions to the workaround by Ian Daniel in this comment from the bug report.

  • If you happen to encounter the issue while doing a Project Import:

    1. Verify the name of the custom field by running the following SQL query (where the id would is taken from 'customfield_11660'):

      SELECT cfname FROM customfield WHERE id=11660;
    2. Do either of the following:

      1. Remove the custom field via JIRA UI

      2. Rename the custom field via JIRA UI

Updated on April 21, 2026

Still need help?

The Atlassian Community is here for you.