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

Global Tenant Filter Dropdown #9668

New Issue
Open
opened 2025-12-29 21:20:39 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:20:39 +01:00
Owner
Copy Link

Originally created by @Yarli on GitHub (May 14, 2024).

NetBox version

3.6.6

Feature type

New functionality

Proposed functionality

Could we have a dropdown at the top, possibly next to the user dropdown menu, that defaults to "All Tenants" and allows you to select a tenant in which you can filter all data by. We frequently work between customers and our own internal systems within NetBox, and having this option would then set the tenant filter (where available) on all dropdowns when working on various records. For example: setting the tenant at the top from All to a specific tenant would mean when you add an IP address, it not only would auto set the tenant for the IP, it would also filter all the Devices or Virtual machines etc to only show ones from that tenant as well. If the default is set to All, then it would mean the current functionality of NetBox remains unchanged.
Users could then also set in their user preferences if they want a default tenant, which would mean upon logging in their tenant selection would be set for them as well, or just simply set a cookie to the last value selected perhaps ? either way some form of persistence would also be nice.

If the dropdown could also reflect the tenant groups too, that would be very nice, for example:

  • Tenant Group 1
    -- Tenant 1
    -- Tenant 2
  • Tenant Group 2
    -- Tenant 3
    -- Tenant 4 etc

Use case

At the moment it can be time consuming with a multi-tenanted NetBox instance, having to select the Tenant using the "Open Selector" icon next to the various drop downs.
Having the tenant preset using that dropdown would save users a lot of time.

Database changes

I don't think this would need any changes, unless you also offered a "Default Tenant" option in the user options section.
I think storing the last set value via a cookie would be sufficient, and negate the need for any DB changes.

External dependencies

No response

Originally created by @Yarli on GitHub (May 14, 2024). ### NetBox version 3.6.6 ### Feature type New functionality ### Proposed functionality Could we have a dropdown at the top, possibly next to the user dropdown menu, that defaults to "All Tenants" and allows you to select a tenant in which you can filter all data by. We frequently work between customers and our own internal systems within NetBox, and having this option would then set the tenant filter (where available) on all dropdowns when working on various records. For example: setting the tenant at the top from All to a specific tenant would mean when you add an IP address, it not only would auto set the tenant for the IP, it would also filter all the Devices or Virtual machines etc to only show ones from that tenant as well. If the default is set to All, then it would mean the current functionality of NetBox remains unchanged. Users could then also set in their user preferences if they want a default tenant, which would mean upon logging in their tenant selection would be set for them as well, or just simply set a cookie to the last value selected perhaps ? either way some form of persistence would also be nice. If the dropdown could also reflect the tenant groups too, that would be very nice, for example: - Tenant Group 1 -- Tenant 1 -- Tenant 2 - Tenant Group 2 -- Tenant 3 -- Tenant 4 etc ### Use case At the moment it can be time consuming with a multi-tenanted NetBox instance, having to select the Tenant using the "Open Selector" icon next to the various drop downs. Having the tenant preset using that dropdown would save users a lot of time. ### Database changes I don't think this would need any changes, unless you also offered a "Default Tenant" option in the user options section. I think storing the last set value via a cookie would be sufficient, and negate the need for any DB changes. ### External dependencies _No response_
adam added the type: featurenetboxstatus: backlogcomplexity: high labels 2025-12-29 21:20:39 +01:00
adam commented 2025-12-29 21:20:40 +01:00
Author
Owner
Copy Link

@djagoo commented on GitHub (Dec 15, 2025):

This feature would be awesome and it would safe us so much time. This way we could "switch" to a tenant while working there without applying the tenant filter every time. But I can't understand the tag "complexity:high". As a first step it would be just a dropdown of tenants whichs applies the tenant filter if anything other than "all" is selected. Or am I missing anything here?

@djagoo commented on GitHub (Dec 15, 2025): This feature would be awesome and it would safe us so much time. This way we could "switch" to a tenant while working there without applying the tenant filter every time. But I can't understand the tag "complexity:high". As a first step it would be just a dropdown of tenants whichs applies the tenant filter if anything other than "all" is selected. Or am I missing anything here?
adam commented 2025-12-29 21:20:40 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Dec 18, 2025):

But I can't understand the tag "complexity:high". As a first step it would be just a dropdown of tenants whichs applies the tenant filter if anything other than "all" is selected. Or am I missing anything here?

While the complexity: high determination was made before I joined the project, I suspect it was due to everything that comes after simply adding the actual dropdown and all of the expected complications that can arise from implementing a feature like this. In addition, a global feature like this would need to be tested thoroughly in all parts of the UI.

@jnovinger commented on GitHub (Dec 18, 2025): > But I can't understand the tag "complexity:high". As a first step it would be just a dropdown of tenants whichs applies the tenant filter if anything other than "all" is selected. Or am I missing anything here? While the `complexity: high` determination was made before I joined the project, I suspect it was due to everything that comes after simply adding the actual dropdown and all of the expected complications that can arise from implementing a feature like this. In addition, a global feature like this would need to be tested thoroughly in all parts of the UI.
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 complexity: high netbox status: backlog 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#9668
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?