Yes, but also the configuration - you can give an issue type a "field configuration" that differes from other issue types in the same project (and, of course, across different projects).
When I mess up fields, 75% of the time it's because I have associated the wrong field configuration, and 24% of the time, I've got the context wrong.
You must be missing something in the configuration.
I've just created a new radio button field with three options, and made it mandatory in the field configuration (for all issue types in the project).
None is no longer an option when creating a new issue.
One other thought though - could someone have added "none" as an option in the list of options for the field?
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot