Unable to map Issue Key when importing CSV to update existing issues

Hi @Ait Benhida Fatimaezzahra,

"Work item Key" being the renamed target is the answer. Two things about this import path are worth knowing before you run it on the full file, since both fail in ways that look unrelated to the mapping.

Permission level. Importing into an existing space is documented as available to site and organization admins only, and only from the external system import screen in admin settings. Jira administrator rights on their own aren't always the same thing, so if the option set you see differs from a colleague's, that's usually why.

Custom field options. No new configuration elements can be created during the import. Statuses, work types, custom fields and, importantly for you, custom field option values all have to exist beforehand. If Domain is a select or multi-select field and your CSV contains a value that isn't already in its option list, that row won't quietly create the option, it will error out. Worth diffing the distinct values in your Domain column against the field's configured options first.

Same reasoning applies to anything else in the file: everything has to match the target space's configuration.

I'd run it on a two-row copy of the CSV first and read the migration report before doing the whole set. It's much easier to see what the import did to two work items than to unpick it across several hundred.

All the best,

Ivan