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

Allow filtering of VLAN Groups by Cluster and Cluster Group #9232

New Issue
Closed
opened 2025-12-29 20:47:19 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:47:19 +01:00
Owner
Copy Link

Originally created by @Chiniquy on GitHub (Feb 12, 2024).

Originally assigned to: @Julio-Oliveira-Encora on GitHub.

NetBox version

v3.7.2

Feature type

New functionality

Proposed functionality

VLAN Groups can be scoped by Cluster or Cluster Group today, but it seems that the ability to filter VLAN Groups by these criteria in the Netbox frontend is missing.

image

I propose that Virtualization > Cluster and Virtualization > Cluster Group are added to the filter.
They may need a new category in the filter menu, in the same way that Region, Site, etc. have "Location" as a category in the filter menu.

Use case

This would allow Netbox users to filter VLAN Groups by Scope = Cluster and Scope = Cluster Group.

Database changes

I am not aware of any necessary database changes.

External dependencies

I am not aware of any external dependencies for this feature request.

Originally created by @Chiniquy on GitHub (Feb 12, 2024). Originally assigned to: @Julio-Oliveira-Encora on GitHub. ### NetBox version v3.7.2 ### Feature type New functionality ### Proposed functionality VLAN Groups can be scoped by Cluster or Cluster Group today, but it seems that the ability to filter VLAN Groups by these criteria in the Netbox frontend is missing. ![image](https://github.com/netbox-community/netbox/assets/10709382/04f3ce14-2796-4bf5-898c-4c8c3e965df3) I propose that Virtualization > Cluster and Virtualization > Cluster Group are added to the filter. They may need a new category in the filter menu, in the same way that Region, Site, etc. have "Location" as a category in the filter menu. ### Use case This would allow Netbox users to filter VLAN Groups by Scope = Cluster and Scope = Cluster Group. ### Database changes I am not aware of any necessary database changes. ### External dependencies I am not aware of any external dependencies for this feature request.
adam added the status: acceptedtype: feature labels 2025-12-29 20:47:19 +01:00
adam closed this issue 2025-12-29 20:47:19 +01:00
adam commented 2025-12-29 20:47:19 +01:00
Author
Owner
Copy Link

@xkilian commented on GitHub (Feb 12, 2024):

Same issue with Prefixes, vlans are exposed there but can't be filtered...

@xkilian commented on GitHub (Feb 12, 2024): Same issue with Prefixes, vlans are exposed there but can't be filtered...
adam commented 2025-12-29 20:47:19 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Mar 20, 2024):

Devices also cant be filtered in the UI by cluster or cluster group, the api/filtering URLs do support it however.
Its probably worth checking if there's more models that are missing these filter fields in the gui

@ITJamie commented on GitHub (Mar 20, 2024): Devices also cant be filtered in the UI by cluster or cluster group, the api/filtering URLs do support it however. Its probably worth checking if there's more models that are missing these filter fields in the gui
adam commented 2025-12-29 20:47:20 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 4, 2024):

Thanks for catching this mismatch between the API and the frontend. I verified that the requested enhancement has not been implemented in 4.0-b1, so I'm marking it as needs owner. If you are interested in working it through to a PR, please say so and somebody will assign it to you.

@jeffgdotorg commented on GitHub (Apr 4, 2024): Thanks for catching this mismatch between the API and the frontend. I verified that the requested enhancement has not been implemented in 4.0-b1, so I'm marking it as `needs owner`. If you are interested in working it through to a PR, please say so and somebody will assign it to you.
adam commented 2025-12-29 20:47:20 +01:00
Author
Owner
Copy Link

@Julio-Oliveira-Encora commented on GitHub (May 13, 2024):

Could you please assign it to me?

@Julio-Oliveira-Encora commented on GitHub (May 13, 2024): Could you please assign it to me?
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: feature
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#9232
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?