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 a cable trace button on the Cable details page and/or a trace button next to each cable in the Cables list page #2782

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

Originally created by @ajsiersema on GitHub (Aug 6, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.2

Proposed Functionality

We'd like to be able to see the route (or trace) a cable is a part of by e.g. clicking on a trace button from https://netbox.example.com/dcim/cables/25/ , which will e.g. call the now nonexistent https://netbox.example.com/dcim/cables/20/trace/

Use Case

When reviewing the cables it would be very convenient and less error-prone to be able to see which trace/route this cable is a part of instead of having to do this in a multi step process by first having to click on one of the termination point, then looking up the cable and it's trace (button).

A similar issue has been addressed in #2758 but that doesn't quite cover this issue.

Originally created by @ajsiersema on GitHub (Aug 6, 2019). ### Environment * Python version: 3.6.8 * NetBox version: 2.6.2 ### Proposed Functionality We'd like to be able to see the route (or trace) a cable is a part of by e.g. clicking on a trace button from https://netbox.example.com/dcim/cables/25/ , which will e.g. call the now nonexistent https://netbox.example.com/dcim/cables/20/trace/ ### Use Case When reviewing the cables it would be very convenient and less error-prone to be able to see which trace/route this cable is a part of instead of having to do this in a multi step process by first having to click on one of the termination point, then looking up the cable and it's trace (button). A similar issue has been addressed in #2758 but that doesn't quite cover this issue.
adam closed this issue 2025-12-29 18:22:07 +01:00
adam commented 2025-12-29 18:22:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 13, 2019):

Closing due to inactivity.

@jeremystretch commented on GitHub (Dec 13, 2019): Closing due to inactivity.
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
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#2782
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?