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; } } }

Alternate to Cascade Field

Muhammad Akram Sharifi_y6l7bk

Hello Everyone,

As we all know every Jira field has a limit to the number of options, if the number of options is growing in the Jira fields it is causing significant delays in Screens load, Linked issue creation process, and Bulk operations until every option of the Fields is loaded which technically makes sense.

I am using a Cascade field which is growing day by day, and looking to find an alternative to Jira cascade field.

your thoughts and recommendations are Highly appreciated.

Accepted answers

All comments

Mohamed Riza _ServiceRocket_

Hi @Muhammad Akram Sharifi

I would recommend looking into why there are several options in the first place and then look into if the issue type/request type can be broken down to several other issue type/request type which has the custom field with a subset of these options.

Another not so great way would be to change this to a text field, and in the description of the field, link this to a google doc with all the valid options to copy over. However, this method is error prone and not ideal.

Hope that contributes to some ideas that you can experiment with.

Joseph Chung Yin

@Muhammad Akram Sharifi -

In my opinion, any custom field (select list or cascade list data type etc.) that contains growing list of options, then it is hard to manage as Jira admins will need to maintain.

Have you look into using Atlassian Assets setup where you can create custom fields to source from Assets objects from Assets schema to support your operations?

However, the impact to the performance (i.e. loading etc..) should not be an issue. The only thing is that a long lists will have the impact where the users will have to scroll up and down to find the right values to use.

You may also want to take a look at Scriptrunner for Jira and their component named "Behaviors" to provide the ability where a field's option list choices can be based on another field's value.

Hope this also helps and give you some ideas...

Best, Joseph Chung Yin

Paul Pasler [Seibert]

Hi there,

as part of the Awesome Custom Fields team, I would recommend to give our app a try.

There's a Cascading Select custom field (with multiple levels), which can be used in the JSM form and view (read-only).

If you have any questions, do not hesitate to reach out: https://seibert.biz/acf-jira-demo

Cheers,

paul

John Funk

Hi Muhammad,

The way we solved it in the past was to find some way to group several of the top level options. Then create either a custom field for groups for those fields or use say the Components field and add Components for each group. Then create multiple Cascading custom fields - one for each group.

So that looks like this: Components: SE US, SW US, NW US, etc. Then custom cascade called SE US States. That has TN, AL, GA, etc. Then the next level down is Cities in TN, AL, etc.