Performance Impact Of custom field with 2000 values

Is there any performance impact when aa custom field single select drop down list is populated with 2000 values?

2 answers

1 accepted

Hi Roger

In that case we would recommend you spliting this custom field im more thatn one if possible. What happens is that every time an issue with this custom field is created, all the 2000 values will be loaded and it will impact in your performance but it will depend on the number os users and hardware that you have for it.

Hope it Helps,

Ricardo Carracedo.

I am researching anotherr field that has 18000 values. Impact to issue creaation was about 2 seconds to display the creaate screen.

Question about updaating this field directly via DB update: if we another option and update the sort order to alphabeticaally sort these vaalues, will this impact population of this value in other issues?



Value A, sort order 1

Value C, sort order 2


Value A, sort order 1

Value B, sort order 2

Value C, sort order 3

Issue 1 originally has Value C, then I update the list, is it still Value C?

Just want to verify that sort order does not impact value selection.

18,000 values is suicidal - it's completely unusable for your humans (actually 2,000 is unusable and pointless for your humans), and is going to put quite load on everything.

You can't update a field via DB updates, unless Jira is completely offline (I don't know if that's the plan, but it needs to be), but amending the sort order won't affect the values.

It is a part of how we use Jira. We are transportation company that deals with any and aall shippers globally. We have a global list of carriers and that is the list. We want to bee able to ceentrally manage the options in this list. Sure some of them are not activve and willl not make the final list, just investigating and testing worste case. Performance impact to create an issue (granted it is in a project with low usage) was only 2 seconds to display the create isssue screen

Is it possible to have an auto-complete search be performed. Natively or via a plugin that allows for a new type of custom field that can autocomplete or lazy load values via search?

With 18,000 options, it's not going to be 2 seconds.

Essentially, your data model is unusable as it is, you need to break it down in a useful way for your humans. There are no plugins that are going to be able to handle 18k options in a useful way.

You might be better off simply telling your users to use labels, and then reporting on them.

Thanks your your time today. We will investigate otheer options.

Who is able to browse 2000 values, anyway? I have a mental overflow at 100.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,168 views 5 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you