Cascading select list, set default for sub-option or allow none?

[tim nixon]

We have a cascading select list "Feature/Subfeature" (Jira v9.4) that is a required field

Some "Features" do not have Subfeatures and some have many.

In Jira 8 the user could select a Feature with subfeatures and also leave the subfeature as 'none'. However since we upgraded from Jira 8 to Jira 9, it appears this is no lomger allowed. It looks like if a Feature has subfeatures then you must select one and not use 'none'.

Also, it does not appear the you can set a default for the second level subfeature for a given Feature.

We could add our own NONE to each Feature as an option, but without a way to have this be the default it wouldn't help much.

I have tried a behaviour to 'clearError' for the field but it does not seem to work.

Any Ideas?

Thanks

Tim Nixon

[Marc Koppelaar]

Hi Tim,

This is behaviour as I expect it to be.

The none option is an Atlassian option, but this can't be set as a default, this option disappears as an option if you use a default set option.

If you think this should not be the behaviour, I would ask you to raise an issue at Atlassian itself.