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

Adding a field choice for status does not show up in the filters page #7336

New Issue
Closed
opened 2025-12-29 20:22:05 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:22:05 +01:00
Owner
Copy Link

Originally created by @huasome on GitHub (Dec 9, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

3.3.9

Python version

3.10

Steps to Reproduce

  1. Using the docker netboxcommunity/netbox image, add a custom field choice for status by adding this stanza to the config:
FIELD_CHOICES = {"ipam.IPRange.status+": (("dhcp", "DHCP", "green"),)}
  1. The additional field choice shows up fine in the netbox/ipam/ip-ranges/add/ page.
  2. The additional field choice does NOT show up in the netbox/ipam/ip-ranges/ under the filter tab.

Expected Behavior

I would expect the DHCP choice to also show up under the Status field pull down choices.

Observed Behavior

The DHCP choice is not in the Status field pull down choices.

Originally created by @huasome on GitHub (Dec 9, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version 3.3.9 ### Python version 3.10 ### Steps to Reproduce 1. Using the docker netboxcommunity/netbox image, add a custom field choice for status by adding this stanza to the config: ``` FIELD_CHOICES = {"ipam.IPRange.status+": (("dhcp", "DHCP", "green"),)} ``` 2. The additional field choice shows up fine in the netbox/ipam/ip-ranges/add/ page. 3. The additional field choice does NOT show up in the netbox/ipam/ip-ranges/ under the filter tab. ### Expected Behavior I would expect the DHCP choice to also show up under the Status field pull down choices. ### Observed Behavior The DHCP choice is not in the Status field pull down choices.
adam added the type: bugstatus: accepted labels 2025-12-29 20:22:05 +01:00
adam closed this issue 2025-12-29 20:22:05 +01:00
adam commented 2025-12-29 20:22:05 +01:00
Author
Owner
Copy Link

@huasome commented on GitHub (Dec 9, 2022):

@jeremystretch Thank you!

@huasome commented on GitHub (Dec 9, 2022): @jeremystretch Thank you!
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 status: accepted 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#7336
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?