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

All paths of device in Related Paths when cable tracing #5901

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

Originally created by @PaulR282 on GitHub (Jan 7, 2022).

NetBox version

v3.1.4

Feature type

Change to existing functionality

Proposed functionality

When you have a device and trace an interface, it would be nice if you see all interfaces traces of the device in the "Related Paths" section of a cable trace.

Use case

If you have e.g. a switch and want to click through all the cables that are connected to the switch, it would be nice to just have a list in the cable trace and not be forced to go back to the interface overview.

Database changes

No response

External dependencies

No response

Originally created by @PaulR282 on GitHub (Jan 7, 2022). ### NetBox version v3.1.4 ### Feature type Change to existing functionality ### Proposed functionality When you have a device and trace an interface, it would be nice if you see all interfaces traces of the device in the "Related Paths" section of a cable trace. ### Use case If you have e.g. a switch and want to click through all the cables that are connected to the switch, it would be nice to just have a list in the cable trace and not be forced to go back to the interface overview. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:34:00 +01:00
adam closed this issue 2025-12-29 19:34:01 +01:00
adam commented 2025-12-29 19:34:01 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 7, 2022):

I think this could be problematic for many reasons, not the least of which is you could have hundreds (or thousands) of interfaces on a single device.

@DanSheps commented on GitHub (Jan 7, 2022): I think this could be problematic for many reasons, not the least of which is you could have hundreds (or thousands) of interfaces on a single device.
adam commented 2025-12-29 19:34:01 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Jan 7, 2022):

Then you could make it optional in the device type to ensure performance with devices with a lot of interfaces

@PaulR282 commented on GitHub (Jan 7, 2022): Then you could make it optional in the device type to ensure performance with devices with a lot of interfaces
adam commented 2025-12-29 19:34:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 7, 2022):

This seems like it would be very redundant given that every components list already has a "trace" button next to each item already. I don't see much value in implementing this.

@jeremystretch commented on GitHub (Jan 7, 2022): This seems like it would be very redundant given that every components list already has a "trace" button next to each item already. I don't see much value in implementing this.
adam commented 2025-12-29 19:34:02 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Jan 10, 2022):

It´s not redundant, because the trace is already in the database. It´s just 2 ways to get it to display.

@PaulR282 commented on GitHub (Jan 10, 2022): It´s not redundant, because the trace is already in the database. It´s just 2 ways to get it to display.
adam commented 2025-12-29 19:34:02 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 10, 2022):

It´s just 2 ways to get it to display.

Yes, that's what I mean by redundant.

@jeremystretch commented on GitHub (Jan 10, 2022): > It´s just 2 ways to get it to display. Yes, that's what I mean by redundant.
adam commented 2025-12-29 19:34:02 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 12, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Mar 12, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:34:02 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 11, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Apr 11, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: under review 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#5901
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?