How build a custom field with more than 400 itens

Hi guys,

I have developed an HR system. There is a custom field that I nned to have with the roles of the company employees with more than 400 roles. Is there a way to make this custom field?

The point is that I do need two similar fields with the same values to be usedd in form (I can't use a custom field twice in a form). So I am looking for a way to make or to fill the itens of these custom fields in a such simplest way.

Any help?

Thanks.

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

7 votes

Answer accepted

Due to the amount of options you want to add I would recommend using Assets and an Asset object custom field. It also makes it easier to maintain.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Adding to this...

With Assets there is a CSV import option for creating the objects once you set up the schema structure.

https://support.atlassian.com/assets/docs/what-are-imports/

400 is a bit of an unwieldy number for a selection list. Have you considered a Cascading Selection List where you have a higher level grouping a roles, to make interacting with the list more user friendly?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Marc -Devoteam- likes this

Dears @Trudy P Claspill and @Mikael Sandberg ,

for sure the best option is to consider a cascading selection. The point is that the project was already implemented with this custom field with a list and so I will need to change the logic. May be it is the way to make it easier to maintain.

At this moment, while I have not implemented the new logic, I ask if there is a way to add new items in batch in the current custom field in order to avoid many hard work.

Thank you.

Jader

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Technically there is no limit on the number of values you can add to a select list, but you will affect the performance once you go over 100, and that is why we suggest using Assets instead. If you continue down the road of using select list your only option to maintain that list is either manually or via the API.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Also note that Atlassian will implement limits on the number of options starting in September 2026, as announced here.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hello @Jader Peixoto Volkmer

The only method for adding options to a custom field outside of doing it through the UI is to use the Jira 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-post

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thank you all.

I will think which is the best way to move forward.

Rds.

Jader

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Was this helpful?

Thanks!

Jira Service Management

DEPLOYMENT TYPE

CLOUD

PRODUCT PLAN

PREMIUM

PERMISSIONS LEVEL

Product Admin

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

How build a custom field with more than 400 itens

1 answer

1 accepted

Comments for this post are closed

Was this helpful?

Thanks!

DEPLOYMENT TYPE

PRODUCT PLAN

PERMISSIONS LEVEL

TAGS

Atlassian Community Events