It feels like Cascade Select Lists were poor designed

[Marcel Toma]

I'm trying to use cascade select lists but it feels it was poorly implemented.

• It doesn't allow both options to be required in the form, just the first one.
• It doesn't show the child option in a way that I can order it by when you list the field in the ticket Queue
• when creating automations, you can't directly use it (ex: create a IF with a "work item field condition"), you have to use custom or smart value conditions.

Is there any plans to improve it?

[Mathew Lederman]

Honestly? I've mostly given up with cascading select lists unless it's an extremely simple requirement. 

If you have JSM/Assets, Asset custom fields allow you to go as many layers as you want, allows you to organize/sort, allows you to have both fields required, and many more. 

[Josh]

@Mathew Lederman agree with you 100%. Assets fields > Cascading fields for the hierarchical selection use case.

One annoyance is the fact multi-level asset fields do not "clean-up" selections in lower levels if the user goes back and changes selections at the higher levels. We work around that with user training but hope to one day see that bug fixed...

[John Funk]

Hi Marcel,

I am not aware of any plans to change/improve the field type. Why not just use two different fields in your form?