Making Required a Cascading Select field, the validation should control all levels of the field as soon as the selected Parent option has Child options.

It should be the default behaviour !

Other behaviours, detailed in JRA-10302 are improvement ...

• Be able to have some Parent option where the Child selection is mandatory
• Be able to have other Parent option where the Child selection is optional

My current use case is to see a Cascading Select mandatory (all existing levels) when entered from UI (in Create Transiton) and optional when created by a Mail Handler.

• Using the native Required option where only the 1st level is mandatory, we obtain an unwanted behviour for creation done from UI, and it lets the Mail Handler create the issue with the field not entered (as we want).
• Using the workaround based on Jira Workflows Toolbox plugin, we can make the 2 Levels mandatory with the Validator : Correct for UI. The Required option is not needed here. But it blocks the creation by Mail Handler.

V.