Best Multi-Level Cascading Field Add-on
Asked by Chalsea Carroll-Lueschow:

We need an unlimited multi-level cascading field to support the way we do our work. We currently have a field which is 808 lines by 5 columns. It will continue to grow and expand over time. Which application would be the best to support this?


Answers:
author: Kate Pawlak _Appsvio_
body: Hi [@Chalsea Carroll-Lueschow](/t5/user/viewprofilepage/user-id/5345026)

You marked that you use Jira Service Management. Do you want to use this custom field on the request form? Let's considerate using combination of more than one custom field and Forms which allows you to create dynamic form. Also, explore Assets as you have a Premium plan. I don't know your use case in detail but I'll try to think about native solutions firstly.

In case of apps, I can recommend our [**Multilevel Select for Jira**](https://bit.ly/Multilevel_Select) which also works on the customer portal and allows you to create structures with options.


author: Paul Pasler
body: Hi [@Chalsea Carroll-Lueschow](/t5/user/viewprofilepage/user-id/5345026) ,

as a member of the [Awesome Custom Fields](https://marketplace.atlassian.com/apps/1228720) team, I highly recommend giving our [app](https://marketplace.atlassian.com/apps/1228720) a try! ?

Our [Cascading Select custom field](https://awesomecustomfields.wikipage.io/c/12288051) provides a versatile multi-level selection feature along with various customization options.

With the option to leverage the full capabilities of Forge storage, you can enjoy virtually unlimited levels and options. Plus, with our [extension for Jira Service Management](https://marketplace.atlassian.com/apps/1231484), you can seamlessly integrate it into your service requests.

If you have any questions or need further assistance, please don't hesitate to [reach out to us](https://seibert.biz/acf-jira-demo)!

Cheers,

paul


author: Walter Buggenhout
body: Hi [@Chalsea Carroll-Lueschow](/t5/user/viewprofilepage/user-id/5345026) and welcome to the Community!

Besides a UI element to let you make selections, it seems quite essential that you can maintain your data in a decent way. Without knowing your use case, just looking at the numbers of items I would strongly recommend you to look at the built-in assets in the premium plan (you seem to have that in place already). Asset custom fields - that you can configure yourself - can be configured to link to other assets custom fields.

There is a learning curve to AQL (the query language used to configure assets fields) and to building your asset schemas, but they are quite powerful. And flexible.

Hope this helps!

comments: author: Chalsea Carroll-Lueschow
body: Hello [@Walter Buggenhout](/t5/user/viewprofilepage/user-id/783225)

When we attempted to use the built-in asset functionality it did not seem to meet our needs. Can you provide more information? We have used cascading fields in the past with success. We are looking at a hierarchy that contains segment/subsegment/focus area/program/business team. We are currently at 800 plus levels. We also use it for a few 3 level fields as well.


Tags: cloud

jira-cloud

jira-service-management

jira-service-management-cloud