Error: "The custom field 'Location' requires option 'Amsterdam' for the import but it does not exist in the current JIRA instance." on project import

Duane Mattos May 30, 2012

The following error appears when trying to carry out a project import:

{code}

Custom Fields

OK Trac Ticket #

OK Developer(s)

OK Trac Ticket #

ErrorLocation

The custom field 'Location' requires option 'Amsterdam' for the import but it does not exist in the current JIRA instance.

The custom field 'Location' requires option 'Chicago' for the import but it does not exist in the current JIRA instance.

The custom field 'Location' requires option 'Sydney' for the import but it does not exist in the current JIRA instance.

OK Start Date

OK Release Notes

{code}

Both the xml export of the target and original instance contain the following lines:

{code}

<customfieldoption id="10043" customfield="10121" customfieldconfig="10152" sequence="0" value="Amsterdam/">

<customfieldoption id="10044" customfield="10121" customfieldconfig="10152" sequence="1" value="Chicago/">

<customfieldoption id="10045" customfield="10121" customfieldconfig="10152" sequence="2" value="Sydney/">

{code}

both instances have identical values for id, customfield, customfield, customfieldconfig and value.

2 answers

2 votes
Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
June 4, 2012

Bug: https://jira.atlassian.com/browse/JRA-28480

1 vote
Foong
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 30, 2012

Check the target instace whether there is a space in the table customfieldoption:

SELECT * FROM customfieldoption WHERE CUSTOMFIELD IN (SELECT id FROM customfield WHERE cfname='Location');

Suggest an answer

Log in or Sign up to answer