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

Adding a filter by tenant on device components #11887

New Issue
Closed
opened 2025-12-29 21:51:14 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:51:14 +01:00
Owner
Copy Link

Originally created by @Etibru on GitHub (Dec 3, 2025).

Originally assigned to: @Etibru on GitHub.

NetBox version

v4.3.7

Feature type

New functionality

Proposed functionality

Add the ability to filter interfaces by tenant.

Use case

This would allow all interfaces for a given tenant to be listed.
This seems very practical in cases involving migration plans or fleet audits, etc.

Database changes

N/A

External dependencies

N/A

Originally created by @Etibru on GitHub (Dec 3, 2025). Originally assigned to: @Etibru on GitHub. ### NetBox version v4.3.7 ### Feature type New functionality ### Proposed functionality Add the ability to filter interfaces by tenant. ### Use case This would allow all interfaces for a given tenant to be listed. This seems very practical in cases involving migration plans or fleet audits, etc. ### Database changes N/A ### External dependencies N/A
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:51:14 +01:00
adam closed this issue 2025-12-29 21:51:14 +01:00
adam commented 2025-12-29 21:51:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 4, 2025):

I want to clarify that NetBox does not permit the assignment of tenants for individual interfaces; this is done via the parent device. So the proposed filter would need to account for this relationship.

Additionally, the filter should be implemented consistently for all device components, not just interfaces.

@jeremystretch commented on GitHub (Dec 4, 2025): I want to clarify that NetBox does not permit the assignment of tenants for individual interfaces; this is done via the parent device. So the proposed filter would need to account for this relationship. Additionally, the filter should be implemented consistently for _all_ device components, not just interfaces.
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: low netbox 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#11887
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?