Cascading Select: Doesn't accept default None value as a value

I'm using a cascading field that is required by post function validation to be required during a transition. This works just fine but I've noticed that both levels of the field are required. This is also fine, makes sense. However, the default None value that appears in the list will not be accepted as a allowed value when the field is required. Selecting JIRA->None for example will not allow you to finish the transition. Is this a bug or am I doing something wrong?

1 answer

1 accepted

Accepted Answer
1 vote

None is basically the translation of a Null value on the database side. Since a value is required it must not be Null (or translated None).

However, you can add your own 'None' value and set it as default.

I want to be able to register that zero value, but it seems that JIRA is requiring me to create a zero value rather than using EMPTY or NULL as a zero value. This is fine, I will do that. I guess it is just a pet peev of mine that now I will have two None values in all my lists creating confusion for those making selections in this field. They will wonder why chosing one None will fail but the other will work.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted 7 hours ago in Canada

TOPIC TUESDAY - Fav Scary Monster!

Hey folks and happy Topic Tuesday! In the spirit of Halloween and all things scary, today's topic is what is your favourite horror movie monster. My personal choice here would be Jason from the Frida...

11 views 0 0
View post

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you