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

Filter cables by connected device #2478

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

Originally created by @jeremystretch on GitHub (Mar 22, 2019).

Environment

  • Python version: 3.5.6
  • NetBox version: 2.5.8

Proposed Functionality

Extend the Cable filter set to allow filtering by the connected parent object at either end. For example: /api/dcim/cables/?connected_device=switch42.

Use Case

This would allow an operator to easily return a list of all cables connected to a device.

Database Changes

N/A

External Dependencies

N/A

Originally created by @jeremystretch on GitHub (Mar 22, 2019). ### Environment * Python version: 3.5.6 * NetBox version: 2.5.8 ### Proposed Functionality Extend the Cable filter set to allow filtering by the connected parent object at either end. For example: `/api/dcim/cables/?connected_device=switch42`. ### Use Case This would allow an operator to easily return a list of all cables connected to a device. ### Database Changes N/A ### External Dependencies N/A
adam added the status: acceptedtype: feature labels 2025-12-29 18:19:13 +01:00
adam closed this issue 2025-12-29 18:19:13 +01:00
adam commented 2025-12-29 18:19:13 +01:00
Author
Owner
Copy Link

@jbakklund commented on GitHub (Apr 8, 2019):

I have been thinking about suggesting a filter allowing the return of a list of all cables connected at a spesific site, rack, or device - adding two more options to your Use Case description, but I am not sure whether or not this justifies adding two more feature requests or expanding this one?

@jbakklund commented on GitHub (Apr 8, 2019): I have been thinking about suggesting a filter allowing the return of a list of all cables connected at a spesific site, rack, or device - adding two more options to your Use Case description, but I am not sure whether or not this justifies adding two more feature requests or expanding this one?
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#2478
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?