Netbox: Custom choice fields should be blank initially if no default choice has been designated

[itdependsnetworks]

Environment

• Python version: 3.7
• NetBox version: 2.9.4

Proposed Functionality

The ability to create a custom field as a selection with no functional default. While there may be no defined defined default, functionally there is a default option .

Use Case

Giving the administrator the ability to ensure requestors do not blindly accept which ever the first value is in a custom field selection. As an example, an administrator may require a zone to be applied, but want to ensure that that users do not ignore the value, and simply save/update the record.

Given:

Currently Results in:

Intended state:

Database Changes

I do not not believe there are any.

External Dependencies

N/A

[jeremystretch]

I'm going to classify this as a bug since it's fair to say that the current behavior is likely to lead to an unintended state.