Stop Creating new values in custom field when external system import

[Vignesh Jayagopal]

Hello,

I am trying to import the large list of issues from csv file using Admin-->External system import.

i could see that new values are creating in custom field after import if the value mentioned in the csv is not present in JIRA.

Is there anyway to stop that? i don't want new values to be created. If the value is not present in jira, i need to get some error so that i can correct the csv and upload it.

[Seon Shakespeare]

Hi Vignesh,

Have you tried the "Map field value" option during the import? It lets you map specific values from your CSV to the corresponding values in your Jira field. This is useful for transforming values, but it won't prevent new values from being created if they don't already exist in Jira.

For that, I recommend pre-processing your CSV:

1. Compare: Open your CSV in a spreadsheet program (like Excel or Google Sheets). Look at the column containing your custom field values and compare them to the exact options available in your Jira field.
2. Correct: Use spreadsheet tools like sorting, filtering, and find-and-replace to easily spot and fix any mismatches. For example, you can sort your custom field column alphabetically to quickly see if any values are out of place. Or, use "Find" to locate misspellings like "Mktg" and replace them with the correct "Marketing".

Hope this helps!

[John Funk]

Hi Vignesh,

Make sure to update one of the fields so that it has a Global context - no particular project or issue type identity.

Maybe temporarily change the name to add a 1 to the end of the name so you can identify it.

Copy the values of the current field for each project to the field you just named.

Then delete the other fields. Then rename the field back to the original name.

Now when you do imports it will use this field and update it instead creating a new field for the import of the project.