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

Add tenant group filter to sites list #2316

New Issue
Closed
opened 2025-12-29 17:24:44 +01:00 by adam · 2 comments
adam commented 2025-12-29 17:24:44 +01:00
Owner
Copy Link

Originally created by @tb-killa on GitHub (Jan 28, 2019).

Originally assigned to: @DanSheps on GitHub.

Environment

  • Python version: 3.6
  • NetBox version: 2.5.2

Proposed Functionality

On the acutally Views (list see below) you could only show "Tenant".
The "Tenant-Groups" doesn´t show up.

Extend the following Views with "Tenant-Groups" and include also the "Tenant-Group" Search on the right Side of every selected View-Template.
In the Table View you should see the Tenant-Group Member by show a Hover-Popup if you move the mouse on the Name of the Tenant-Group inside the "Table-View".

dcim/sites/
dcim/racks/
dcim/rack-elevations/
dcim/rack-reservations/
dcim/devices/
ipam/ip-addresses/
ipam/prefixes/
ipam/vrfs/
ipam/vlans/
virtualization/virtual-machines/
circuits/circuits/

Use Case

If you use different Tenant-Groups because actually you could only select ONE Tenant you wouldn´t see them in the actually views.

For example on Sites it should also show up like this:
image

and on the Search-Bar (right Side):
image

Database Changes

Dont know.

External Dependencies

No.

Originally created by @tb-killa on GitHub (Jan 28, 2019). Originally assigned to: @DanSheps on GitHub. ### Environment * Python version: 3.6 * NetBox version: 2.5.2 ### Proposed Functionality On the acutally Views (list see below) you could only show "Tenant". The "Tenant-Groups" doesn´t show up. Extend the following Views with "Tenant-Groups" and include also the "Tenant-Group" Search on the right Side of every selected View-Template. In the Table View you should see the Tenant-Group Member by show a Hover-Popup if you move the mouse on the Name of the Tenant-Group inside the "Table-View". dcim/sites/ dcim/racks/ dcim/rack-elevations/ dcim/rack-reservations/ dcim/devices/ ipam/ip-addresses/ ipam/prefixes/ ipam/vrfs/ ipam/vlans/ virtualization/virtual-machines/ circuits/circuits/ <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case If you use different Tenant-Groups because actually you could only select ONE Tenant you wouldn´t see them in the actually views. For example on Sites it should also show up like this: ![image](https://user-images.githubusercontent.com/932481/51827001-aeaf6c80-22e8-11e9-8e7e-fb939fc27abf.png) and on the Search-Bar (right Side): ![image](https://user-images.githubusercontent.com/932481/51827159-fe8e3380-22e8-11e9-8eb7-7c8709ee472a.png) <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Dont know. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies No.
adam added the status: acceptedtype: feature labels 2025-12-29 17:24:44 +01:00
adam closed this issue 2025-12-29 17:24:45 +01:00
adam commented 2025-12-29 17:24:45 +01:00
Author
Owner
Copy Link

@Grokzen commented on GitHub (Feb 21, 2019):

@jeremystretch Should tenant-group value be visible in the API call to these endpoint? Basically update the class of NestedTenantSerializer to output somethiing like

"tenant": {
    "id": 314,
    "url": "http://localhost:32770/api/tenancy/tenants/314/",
    "name": "Tenant A",
    "slug": "tenant-a",
    "group": "Customers"
},
@Grokzen commented on GitHub (Feb 21, 2019): @jeremystretch Should tenant-group value be visible in the API call to these endpoint? Basically update the class of `NestedTenantSerializer` to output somethiing like ``` "tenant": { "id": 314, "url": "http://localhost:32770/api/tenancy/tenants/314/", "name": "Tenant A", "slug": "tenant-a", "group": "Customers" }, ```
adam commented 2025-12-29 17:24:46 +01:00
Author
Owner
Copy Link

@Grokzen commented on GitHub (Feb 21, 2019):

Another question i have is that adding more columns always takes up a lot of screen width in the table. Would it be better to mangle both the name and the group into the already existing table Tenant by formatting it something like Tenant A -- Customers or Tenant A (Customers) or any other variant that would look good.

@Grokzen commented on GitHub (Feb 21, 2019): Another question i have is that adding more columns always takes up a lot of screen width in the table. Would it be better to mangle both the name and the group into the already existing table Tenant by formatting it something like `Tenant A -- Customers` or `Tenant A (Customers)` or any other variant that would look good.
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#2316
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?