Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom fields: default value not being set for boolean type #769

Closed
Armadill0 opened this issue Jan 4, 2017 · 2 comments
Closed

Custom fields: default value not being set for boolean type #769

Armadill0 opened this issue Jan 4, 2017 · 2 comments
Labels
type: bug A confirmed report of unexpected behavior in the application

Comments

@Armadill0
Copy link

I have a custom field for devices of the type boolean. It is not required, but filterable and has the default value "false" like described on the admin site.

When I go to the page to add a new device, the default value is not set for this field. Instead only "---------" is displayed, but "True" and "False" are only selectable via the drop down menu. It seems boolean defaults don't work at all. I also testet "False", "true" and "True" as defaults and neither of them have been inserted as default value.

Text and integer fields work well. So it seems to be only an issue with the boolean type.

@jeremystretch
Copy link
Member

What version of NetBox are you running?

@Armadill0
Copy link
Author

Armadill0 commented Jan 4, 2017

1.8.0

I recognized this bug already on older versions, but forgot to report it.

@jeremystretch jeremystretch added type: bug A confirmed report of unexpected behavior in the application and removed awaiting reply labels Jan 4, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

No branches or pull requests

2 participants