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

Global Location Filter #7477

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

Originally created by @dutchman80 on GitHub (Jan 9, 2023).

NetBox version

v3.4.0

Feature type

New functionality

Proposed functionality

Add a global filter to the top of the page, such that you can filter all views by a selected Site.

Use case

When working in netbox, you are frequently only concerned with a single site or location at a time. Rather than having to set a site filter every time you visit a section (Devices, IP Addresses, etc.), a global location filter would automatically only show you the results for the sites or locations you are concerned with.

The filter could sit right next to the existing search bar, and would be a drop down box listing all defined sites, as well as a "Global" option. When a specific site is selected (i.e. "site_id=5"), then all links on the navigation pane would have "?site_id=5" amended to them. When "Global" is selected, nothing is appended to the nav links. This seems to work fine right now, even for nav links that don't normally filter by site.

This is a web UI only feature, not requiring any API changes. Also, since it's a modification to the existing header and nav pane, it would not require any new views.

Database changes

None expected

Originally created by @dutchman80 on GitHub (Jan 9, 2023). ### NetBox version v3.4.0 ### Feature type New functionality ### Proposed functionality Add a global filter to the top of the page, such that you can filter all views by a selected Site. ### Use case When working in netbox, you are frequently only concerned with a single site or location at a time. Rather than having to set a site filter every time you visit a section (Devices, IP Addresses, etc.), a global location filter would automatically only show you the results for the sites or locations you are concerned with. The filter could sit right next to the existing search bar, and would be a drop down box listing all defined sites, as well as a "Global" option. When a specific site is selected (i.e. "site_id=5"), then all links on the navigation pane would have "?site_id=5" amended to them. When "Global" is selected, nothing is appended to the nav links. This seems to work fine right now, even for nav links that don't normally filter by site. This is a web UI only feature, not requiring any API changes. Also, since it's a modification to the existing header and nav pane, it would not require any new views. ### Database changes None expected
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:23:52 +01:00
adam closed this issue 2025-12-29 20:23:52 +01:00
adam commented 2025-12-29 20:23:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 9, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Jan 9, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:23:53 +01:00
Author
Owner
Copy Link

@dutchman80 commented on GitHub (Jan 11, 2023):

I've fleshed out the Use Case section. Hopefully the additional detail clarifies things?

@dutchman80 commented on GitHub (Jan 11, 2023): I've fleshed out the Use Case section. Hopefully the additional detail clarifies things?
adam commented 2025-12-29 20:23:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2023):

@dutchman80 I'm afraid this is still far from an actionable FR. Please spend some time detailing the proposed implementation and how it would work under the hood.

@jeremystretch commented on GitHub (Jan 26, 2023): @dutchman80 I'm afraid this is still far from an actionable FR. Please spend some time detailing the proposed implementation and how it would work under the hood.
adam commented 2025-12-29 20:23:54 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 7, 2023):

I'm going to close this out as it does not provide a sufficiently detailed proposed implementation. If you would like to collaborate with others who may be interested in building this feature, consider starting a discussion to solicit feedback and ideas.

@jeremystretch commented on GitHub (Feb 7, 2023): I'm going to close this out as it does not provide a sufficiently detailed proposed implementation. If you would like to collaborate with others who may be interested in building this feature, consider [starting a discussion](https://github.com/netbox-community/netbox/discussions/new/choose) to solicit feedback and ideas.
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: revisions needed 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#7477
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?