Required field validation works only on the first Cascading drop-down list

Atlassian Update – 17 April 2023 Hi everyone, We’re happy to announce that the fix for this bug has been released in Jira Server version 9.7. Initially, the validation of the Select List (cascading) custom field, when it was marked to be required, took into account only the first (parent) list. In the upcoming solution, it has been decided that: If there is only a parent option configured then validation requires only a parent option to be set, If there is a parent option and a sub-option (child) configured, then require both of them. We have decided that such implementation leaves flexibility to the users who can decide what’s most suitable for them. More detailed documentation can be found under the following link:  https://confluence.atlassian.com/adminjiraserver/specifying-field-behavior-938847255.html#Specifyingfieldbehavior-requirefieldMakingafieldrequiredoroptional The fix is going to be backported to Jira LTS versions 8.20.22 and 9.4.6 scheduled to be released on May 2023. Kind regards, Agata Kowal, Junior Software Engineer in Jira Server