CSV import of Jira issues with Insight custom field containing '-' or '(' or ')' failing
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
Summary
Problem
When trying to do a CSV import of issues with Insight custom field, user is getting an error :
1
Cannot add value [ [MyObject-1] ] to CustomField Configuration Item test in Issue with summary 'Test with error on -'. Probably value was in incorrect formatAt the end of the import, the issues get imported correctly, but the Insight custom field is not updated with values.
Diagnosis
Environment
Jira instance has Insight plugin installed
Diagnostic Steps
The Insight custom field value in the csv file contains special characters like '-' or '(' or ')'
Cause
Insight custom fields are different from the regular Jira custom fields. As mentioned in this documentation Insight stores the value of custom fields in 2 parts : "Key" and "Label".
If you create your own CSV file and want to connect an Insight object, you must use the "Key" or "Label (Key)" pattern. So, for a successful csv import, the user should provide either the "Key" or a combination of both "Label (Key)" in the CSV file.
In this case, the user CSV file only has a "Label" and not the "Key" value. So this import will not work.
Sample incorrect csv :
1
2
Issue key,Issue id,Status,Created,Updated,Custom field (Organizations),Custom field (Computer),Summary
SP-26,40424,Escalated,26/Jan/21 5:46 PM,12/Feb/21 11:46 AM,2,test-1234,test importIn this case the import failed because Jira is trying to map 'test-1234' which is a "Label" with the "Key" which it expects to receive and hence it is not able to map this value "test-1234" with an existing Insight custom field value.
Sample correct csv :
1
2
Issue key,Issue id,Status,Created,Updated,Custom field (Organizations),Custom field (Computer),Summary
SP-26,40424,Escalated,26/Jan/21 5:46 PM,12/Feb/21 11:46 AM,2,test-1234 (RPS-7971),test importSolution
Resolution
Provide either the "Key" or "Label (Key)" in the CSV file for a successful Insight custom field import.
Was this helpful?