nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How build a custom field with more than 400 itens

Jader Peixoto Volkmer_r5c09o

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.

Accepted answers

Mikael Sandberg

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.

All comments

Mikael Sandberg

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.

Trudy P Claspill

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?

Jader Peixoto Volkmer_r5c09o

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

Mikael Sandberg

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management