Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Is it possible to avoid the creation of new field in while bulk importing in Jira Cloud

Gregoire Cabioch
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 19, 2025

In my cloud Jira Company Managed, i've created some customs fields and i'm trying to import data via bulk import. The problem is if it not exactly the same name as one of the option, it will create an option with its  name. I found this doc https://support.atlassian.com/jira/kb/how-to-disable-bulk-create-non-admin-csv-import/ for data center jira, but i did not find anything for cloud.
My question would be : is it possible to either block the creation of new options for the field while bulk importing or even better, try to make kind of a regex that ack the field option that was initially wanted ? 

2 answers

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2025

Hi @Gregoire Cabioch 

Welcome to the community.

There is no option to block misspelled option in a CSV when on importing the column is mapped to a custom select field in Jira, if you are doing the import as an admin.

The option you describe for Jira DC, is not an option in Cloud.

Based on my knowledge if a user imports a cvs, from the project level, misspelled options for a select field won't be set as new options as the user doesn't have Jira admin permissions.

So are the users, doing imports also Jira admins?

If you are an admin and do the import, then yes, the options will be added based on your admin permissions allow this.

0 votes
Floyd Franklin
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 19, 2025

You can’t completely block new field creation during bulk operations, but you can control it with permissions and field configurations. Make sure only admins have rights to create custom fields, and restrict field context so bulk updates don’t trigger unnecessary new fields.

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 19, 2025

Hi @Floyd Franklin 

Th question is not around new fields, but options that are used in the fields or added by a typo in the csv.

Jira admins only have options to create custom fields, to be used by company managed projects, non Jira admins can't create custom fields for company managed projects

Custom field context can't be restricted, they are set for a work item(s) and/or project(s)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events