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 Cable Trace option in additional pages #4686

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

Originally created by @jcralbino on GitHub (Mar 19, 2021).

NetBox version

v2.10.5

Feature type

Change to existing functionality

The blue cable trace button used for the Cable trace is currently available only on:

image

Proposed functionality

In order to improve usability we should add this in more places. Namely on:

Use case

Utilization of the Cable trace functionality will be easier, and usability of the product increased.

Database changes

None

External dependencies

None

Originally created by @jcralbino on GitHub (Mar 19, 2021). ### NetBox version v2.10.5 ### Feature type Change to existing functionality The blue cable trace button used for the Cable trace is currently available only on: - https://netbox/dcim/interfaces/<interfaceID>/ ![image](https://user-images.githubusercontent.com/44149262/114060193-6cedb980-9895-11eb-93f1-3a9fa763d061.png) - https://netbox/dcim/interfaces/dcim/devices/<DeviceID>/interfaces/ ![image](https://user-images.githubusercontent.com/44149262/114060131-58a9bc80-9895-11eb-9120-e978d422e678.png) ### Proposed functionality In order to improve usability we should add this in more places. Namely on: - Within a cable page (https://netbox/dcim/cables/<CableID>/ ) as shown in the picture ![image](https://user-images.githubusercontent.com/44149262/114060502-bb9b5380-9895-11eb-9dac-c1b82068b22e.png) - Within the Interface connections page (https://netbox/dcim/interface-connections/ ) ![image](https://user-images.githubusercontent.com/44149262/114060648-e1285d00-9895-11eb-88eb-9c4db1d90776.png) ### Use case Utilization of the Cable trace functionality will be easier, and usability of the product increased. ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 19:19:30 +01:00
adam closed this issue 2025-12-29 19:19:30 +01:00
adam commented 2025-12-29 19:19:30 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 25, 2021):

What specific changes are you proposing? Screenshots would help. Also note that one of your URLs above is invalid.

@jeremystretch commented on GitHub (Mar 25, 2021): What specific changes are you proposing? Screenshots would help. Also note that one of your URLs above is invalid.
adam commented 2025-12-29 19:19:31 +01:00
Author
Owner
Copy Link

@jcralbino commented on GitHub (Apr 8, 2021):

I believe it is more clear now.
thanks.

@jcralbino commented on GitHub (Apr 8, 2021): I believe it is more clear now. thanks.
adam commented 2025-12-29 19:19:31 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 8, 2021):

Cable traces have to start from a specific termination point, not the cable itself. The two proposed locations for a "trace" button don't imply a specific termination point.

@jeremystretch commented on GitHub (Apr 8, 2021): Cable traces have to start from a specific termination point, not the cable itself. The two proposed locations for a "trace" button don't imply a specific termination point.
adam commented 2025-12-29 19:19:31 +01:00
Author
Owner
Copy Link

@jcralbino commented on GitHub (Apr 13, 2021):

Although i do not want to dwell on this, i would like to understand the scenarios where the interface is not a specific termination point.
I understand your comment in terms of cable page view, where a cable is just one component within an end to end path. But for something within the interface page view that is not correct i believe.

@jcralbino commented on GitHub (Apr 13, 2021): Although i do not want to dwell on this, i would like to understand the scenarios where the interface is not a specific termination point. I understand your comment in terms of cable page view, where a cable is just one component within an end to end path. But for something within the interface page view that is not correct i believe.
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 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#4686
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?