Our org has over 55 site locations that need to be captured in Jira. I've created a custom dropdown field for this purpose. It needs to be a dropdown so we can use the pie charts and two-dimensional gadgets in the Jira dashboards. I was told this limit can be adjusted.
Hi @Marcos ,
Custom fields can support up to 10.000 options (or something around that number). This is a high threshold and I'd say it's not recommended to have that many options for a single custom field.
Anyway, 55 options are definitely supported for single or multi-select fields. More on fields types can be found here: Field types you can create as a Jira admin 📚
Question from my side would be - are you experiencing a specific limitation or issue when trying to have those 55 options/locations? Either when using a custom field or when displaying those options on charts/gadgets. 👀
Cheers,Tobi
Hello @Marcos
Welcome to the Atlassian community.
Are you using a Team managed Space?
There is a limit of 55 options for Dropdown fields in a Team managed Space. There is an open change request about this to which you can add your vote:
https://jira.atlassian.com/browse/JRACLOUD-77917
The work around is to define a Global Custom Select List type of field, which has a higher limit, and use that field in your Team Managed space. Only Jira App Administrators can create such fields. If you are not a Jira App Administrator you will have to work with one to get the field created.
Thanks for responding Tobi.
55 values is a limitation for custom fields in a team-managed project environment but we have more than 55 locations we need to track. I understand that company-managed fields are more flexible, but we want to setup this field as team-managed. Is there any way to increase the total number of custom field values above 55?
Again, thank you.
Marcos
There is no way to increase the number of options in a Team Managed project custom Dropdown field. Refer to my answer for a work around.
https://community.atlassian.com/forums/Jira-questions/Increase-limit-for-custom-field-dropdown/qaa-p/3223150#M1176502
Another option if you have access to JSM and the Assets feature is to use Assets instead.
Thank you.
Yes, this 👆
Managing these 'large entities' is much easier if you have/are using Assets. If that's possible, I would choose this over select fields in company-managed spaces.
More info on Assets can be found here: Keep track of your organization's assets (with some neat examples as well) 📚
It looks like you're new here. Sign in or register to get started.
