Jira Cloud CSV Import Fails Though Custom Field Options Already Exist

[siddhesh B Lad]

Hello Support Team,

We are facing an issue while importing issues into our Jira Cloud company-managed project using CSV import.

Project Details

• Jira Cloud instance
• Company-managed project
• Target Project: SCM-MTP PRODUCTION

Problem

During CSV import, Jira shows errors like:

• Error in custom field option 'Major' for custom field Priority — not found
• Error in custom field option 'Air-Documents' for custom field Module — not found
• Error in custom field option 'Billing' for custom field Module — not found
• Error in custom field option 'Defect' for custom field TicketType — not found
• Error in custom field option 'WarehouseFree13MAR2022' for custom field CustomerName — not found

Important Note

All these dropdown values already exist in Jira and are visible in field configuration / custom field contexts.

We previously had duplicate fields from team-managed projects, but those duplicate fields have now been removed.

Still CSV import keeps saying options not found.

Questions

1. Does CSV importer cache old custom field IDs?
2. How can we confirm which custom field/context importer is using?
3. Is there any delay after deleting duplicate fields?
4. How can we force importer to use correct global custom fields?

Additional Observation

Some fields with same names existed earlier in team-managed and company-managed projects.

Request

Please help us identify why Jira importer cannot detect already existing options.

Thanks,

Siddhesh

[Marc -Devoteam-]

Hi @siddhesh B Lad 

What is you field mapping on importing.

you can't define custom field context on importing.

If you are importing work items in a space with custom field value, the custom field must be used in that space and the context of the custom field should referenc this

So if your custom field has 2 contexts:

one withe options: a,b and c and one with options 1,2 and 3

On the CSV import the options in the column for the custom field must be the ones used for the space where the import is done for

[siddhesh B Lad]

Thanks for the clarification.

Our target project is SCM-MTP PRODUCTION. The custom fields are configured with global/project contexts containing required options like Air-Documents, Billing, Major, etc.

Could you please help us verify whether the CSV importer is resolving a different field/context due to previously existing duplicate fields with same names (from team-managed projects)?

We’d also like to know how to confirm which exact custom field ID/context the importer is using.

[Marc -Devoteam-]

Hi @siddhesh B Lad 

Are the field you want to set on import on the create screen or the screen used in the target space?

[M Chandra Shekar]

@siddhesh B Lad All you mentioned fields are single select fields ? Also, 

Please check for any extra spaces in Jira or Excel values.

[siddhesh B Lad]

@M Chandra Shekar , Yes all these fields are Single select List. Also, I cross verify excel if there are any extra spaces in values but did not find any.

[M Chandra Shekar]

@siddhesh B Lad Is the field context for these fields set to Global, or limited to specific projects?

[siddhesh B Lad]

Yes, all field contexts are set to global