External Issue Id / External ID cannot be imported in JIRA

[Meghana_H]

As a user, i cannot import issues with column external ID. I would like to have the ID of requirements from other tool inside Jira. I can view external Id on my issue screen but field is empty.

[Jeff Abbott]

I recommend you name the field something else. "External ID" is a custom field name used by the Jira import manager. JIM is supposed to remove the field, but sometimes it stay behind. When that happens updates will no longer occur. You will need to delete the custom field "External ID" before the import will function properly.

[Petter Gonçalves]

Hello @Meghana_H

Thank you for reaching out.

Per your description, I understand you configured a custom field in your Jira site called "External ID". When you try to create new issues using CSV import,  the issues are successfully created, however, the field "External ID" does not get filled, although you mapped a valid value to it in the CSV file. Is that correct?

If that's the scenario you are facing, I suggest you check the following details:

1 - Check if the value you are trying to add is applicable to the custom field type of "External ID". Better explaining, check if the "external id" can be filled manually in the issue view with the values you mapped (e.g: SRS-1), confirming it is not from a type that would not accept those values, Like number field, User Picker, Select Lists, etc.

2 - If you are using a Classic project, check if the field is properly added to the Edit issue Screen under Project settings > Screens.

3 - Under Jira settings > Issues > Custom Fields, check if you don't have more than one custom field with the name "External ID", also confirming in the Import client if you are mapping the value to the correct field with the same uppercase letters and characters.

4 - As a site-admin, try to use the External Import Client under Jira Settings > System > External System Import and check if the same problem happens.

5 - If you are using a Next-gen project, you might be facing the following bug:

CSV import will fail if Next-gen custom field is mapped 

If that's the case, feel free to vote and watch the bug to increase its priority and also receive notifications about any updates.

If the steps above are not applied to your scenario, please let us know if you are using a Classic or a Next-gen project and provide us a screenshot on how you are mapping the field in the import client.

Let us know if you have any questions.