starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

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

New Issue
Closed
opened 2025-12-29 16:23:45 +01:00 by adam · 2 comments
adam commented 2025-12-29 16:23:45 +01:00
Owner
Copy Link

Originally created by @Armadill0 on GitHub (Jan 4, 2017).

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.

Originally created by @Armadill0 on GitHub (Jan 4, 2017). 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.
adam added the type: bug label 2025-12-29 16:23:45 +01:00
adam closed this issue 2025-12-29 16:23:45 +01:00
adam commented 2025-12-29 16:23:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 4, 2017):

What version of NetBox are you running?

@jeremystretch commented on GitHub (Jan 4, 2017): What version of NetBox are you running?
adam commented 2025-12-29 16:23:45 +01:00
Author
Owner
Copy Link

@Armadill0 commented on GitHub (Jan 4, 2017):

1.8.0

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

@Armadill0 commented on GitHub (Jan 4, 2017): 1.8.0 I recognized this bug already on older versions, but forgot to report it.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#604
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?