Bulk import custom field values

[Jithesh]

I have a list of more than 500 values to be add in "Select List (Single Choice)" custom field.

I have tried adding by import issues using CSV file and mapping the Custom field name to the values but its throwing an error:

The value [ {null=Test 2} ] can't be added to the Custom Field. The value [ {null=Test 2} ] can't be found or is in the incorrect format

Scriprunner option is also not available for free.

I am using Jira Cloud free option as of now exploring the possibility to automate a process.

Is there any other option to get this done.

[Dave Bosman [Realdolmen]]

Hi Jitesh,

To be honest, it is not a good idea to have so many values as it will impact performance. Is there any specific reason that you need this many values? Can it be done in another way? 

That being said, you should check the REST API. https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options/#api-rest-api-3-field-fieldid-context-contextid-option-put

Regards

Dave

[Jithesh]

Its a list of items based on which next course of action will be decided.

Not sure if there is a better way other than, putting it under choice dropdown values, as we don't want type errors in the selection.

[Curt Holley]

Have I got this right.. you want a list of over 500 options placed into a single choice select list, that is based on (over 500) options for the "next course of action" of something.

How many of these options would ever be selected? How many stories/issues will ever have any selected?

A list of over 500 anything should not be loaded in any one field, I would argue.

Sounds more like a confluence page to me. From there the options that are going to be the next course of action can be curated and then the shortlist added to a Jira field.

Alternatively, if you believe all will be actioned at some point, why not make them tasks? As seeing you are intending making them a single select filed, any Jira issue could only pertain to one option anyway, By doing it this way you could load them via CSV via the import issues functionality.

[Jithesh]

The workflow which I am exploring is to get automation Training lifecycle.

We have a requestor IDelivery Team) we have Training team and we have COEs / SMEs.

We have two drop downs one for customer (500 + values) and another for Skills (1000 + values) Customer field will guide to whom the ticket should be assigned (SMEs teams) for recommendations and  Skills will tell SMEs team what should be the recommendations. 

I've not worked on or explored Confluence yet.

[Curt Holley]

Do the "customers" have a Jira license? If so, you could make use of a User Picker field.
If not, I would recommend grouping them and adding those groups to a picklist.

Same for the skills, as you definitely do not want a picklist with over 1000 entries.

As @Dave Bosman [Realdolmen] has suggested, these two fields could be really sluggish re performance.

Actually, just remembered. You are using a free Jira plan, so you have less than 10 licensed users. So my initial question is redundant. Which leads me to; This seems to be a very scaled desire, for a Jira set-up used by such a small number of people.  

[Jithesh]

As mentioned I am exploring the possibility of using Jira that's why I am using a free version. once I share a POC we will go for a licensed version as well. I will try to explore various options shared. Thanks to @Curt Holley and @Dave Bosman [Realdolmen] for your suggestions.

[Sebastian Krzewiński]

Hi @Jithesh 

You should consider to use REST API. See these docs:

- https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-custom-field-options/#api-rest-api-3-field-fieldid-context-contextid-option-put

- https://community.developer.atlassian.com/t/how-can-i-add-options-to-a-select-list-custom-field-via-rest-api/47285/2

Regards,

Seba