Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Is there a recommended limit to number of values in a custom field?

Hello All,

I am just checking to see if there is a recommended amount of values that can be listed in a custom field before it starts to give the Jira application performance issues?

I currently have a custom field that has over 200 values as a select list and the list will continue to grow to possible over a 1,000 at some point. I know that most performance issues within Jira are because of too many custom fields. However in this case I just want to make sure I don't have start to have performance issues when I have a custom field that has over a thousand values or possibly more at some point.

Just looking for some guidance on this if any one else has experienced this situation.

Eventually we will enable autocomplete renderer for Multi-select custom field and use that option as this list will become entirely too long to scroll through and select options.

Do any of you all have guidance or experience enabling the autocomplete renderer for multi-select fields? Does that cause even more performance issues do the road?

Link for Reference: https://confluence.atlassian.com/jirakb/how-to-enable-autocomplete-renderer-for-multi-select-custom-field-in-jira-754978239.html

1 answer

0 votes
Brant Schroeder Community Leader Oct 30, 2020

Jeremy,

  I have experience with both but not as high as a 1000.  From my experience when the issue initially loads and when you save it is slower but not that noticeable.  If the issue has a lot of custom fields on it plus this one it will most likely load slower than if this was the only field.  You might experience slower indexes but this can be mitigated by only associating the field to the issue types and projects it needs to be associated with.  The most we have ever had in values was in a cascading select list.  My guess is we were around 800 options and like I said it was a little slower but not anything to complain about.

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you