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

Filter device components by Rack #6900

New Issue
Closed
opened 2025-12-29 19:46:30 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:46:30 +01:00
Owner
Copy Link

Originally created by @stef-liesmons on GitHub (Aug 29, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.3.0

Feature type

Change to existing functionality

Proposed functionality

It would be nice to have a "Rack" filter option in the Device Components lists...

Use case

If one wants to filter only all the front-ports of a certain rack to see all the cable patches of the rack in front of you, that would be a very "real-life" feature to have.

Database changes

No response

External dependencies

No response

Originally created by @stef-liesmons on GitHub (Aug 29, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.3.0 ### Feature type Change to existing functionality ### Proposed functionality It would be nice to have a "Rack" filter option in the Device Components lists... ### Use case If one wants to filter only all the front-ports of a certain rack to see all the cable patches of the rack in front of you, that would be a very "real-life" feature to have. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:46:30 +01:00
adam closed this issue 2025-12-29 19:46:30 +01:00
adam commented 2025-12-29 19:46:31 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Aug 31, 2022):

@jeremystretch does it make sense to add this filter to all device components (Interfaces, Front Ports, Rear Ports, Console Ports, Console Server Ports...). Also, if we are filtering by rack do we want to add rack to the list views? Would pull rack from device->rack for all items.

@arthanson commented on GitHub (Aug 31, 2022): @jeremystretch does it make sense to add this filter to all device components (Interfaces, Front Ports, Rear Ports, Console Ports, Console Server Ports...). Also, if we are filtering by rack do we want to add rack to the list views? Would pull rack from device->rack for all items.
adam commented 2025-12-29 19:46:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 31, 2022):

does it make sense to add this filter to all device components?

Yes; we'll add the filters to DeviceComponentFilterSet.

Also, if we are filtering by rack do we want to add rack to the list views?

This isn't strictly needed. For instance, there's no site column either, even though we permit filtering interfaces by site. (The filters are used for API requests as well.) The addition of any new columns to the table should be tracked in a separate FR.

@jeremystretch commented on GitHub (Aug 31, 2022): > does it make sense to add this filter to all device components? Yes; we'll add the filters to DeviceComponentFilterSet. > Also, if we are filtering by rack do we want to add rack to the list views? This isn't strictly needed. For instance, there's no site column either, even though we permit filtering interfaces by site. (The filters are used for API requests as well.) The addition of any new columns to the table should be tracked in a separate FR.
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#6900
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?