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?
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.
As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot