Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,739
Community Members
 
Community Events
168
Community Groups

How to add 3000 plus options to the custom field

I have a requirement, where I have to add more than 3000 option values to a custom field. How to do that. 

Can we do using a script runner plugin?

 

 

2 answers

Hi @Sravan Muppavarapu,

Welcome to Atlassian Community!

You could use the REST API to do this and Scriptrunner should work too, but you should really consider it you want to add those 3000 plus options. The select field doesn't have a hard limit, but you will run into performance issues, see this question.

Another option would be to use an external data source and an app like Elements Connect, I used that when I was on Data Center and we needed to add a field that had 10000+ part numbers.

Hi Mikael,

 

Thanks for the response. My situation is also the same. these 3000 options are like apart names and numbers.

To overcome the performance issues, can I update 400 values every day or something like that?

Mikael Sandberg Community Leader Sep 07, 2022

No, your issue is that you will run into performance issues when someone will try and use the field. I would consider using an external data source, or if you have access to Insight use that instead because the field values are populated when the user is typing in the field instead of having to wait for the list to first populate before you can see them. And by using external data source or Insight you can easily maintain the list rather than having to do it from the custom field.

Like Samuel likes this

okay. I will try it. Already that custom field had 2400 options and these 3000 values are added to it.

To add to @Mikael Sandberg 's advice, you should be aware that humans struggle with most lists longer than about 42 items.  Cloud Jira actively limits the number offered.  Your 5400 list is unlikely to be of any practical use - you will find that if humans are using the field rather than automation, it's mostly full of random junk.

Like Mikael Sandberg likes this

This field is updated by automation. I mentioned previously this field had 2400 already and it was updated by automation.

Yes, you did, but how you've ended up with way too many options for your people is not important.  The point is that your field is probably useless to your people.

Like Mikael Sandberg likes this

Also consider ScriptRunner database fields - https://docs.adaptavist.com/sr4js/latest/features/script-fields/built-in-script-fields/database-picker

It will lazily load values as the user types, they could be stored in an external database, or a csv/excel file etc.

Like Mikael Sandberg likes this

@Nic Brough _Adaptavist_ By the time I joined the organization It had already been added to the field. So No idea.

Hi All,

 

Thank you all for the responses and suggestions. I successfully completed this requirement and updated 3000+ options to the custom field using CSV file import.

 

Thank you

Sravan

Hi @Sravan Muppavarapu 

I am the Product Manager of Elements Connect

Elements Connect allows you to do that. If you would like to discuss your use case or have any further questions, feel free to book a call to my Calendar.

 

Best regards

Suggest an answer

Log in or Sign up to answer