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

Trace at front-port endpoint #5899

New Issue
Closed
opened 2025-12-29 19:34:00 +01:00 by adam · 1 comment
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 an interface connected to a front-port (or as many front/rear-ports as you wish in between), currently, you can only trace that path at the connected points, but not the last front.port. So it would be nice if the trace button at the front-port would be active although nothing is connected directly to it, only through the rear-port.

Use case

This would make cable tracing better, because you can see at a front-port overview which front-ports have a connection/interface at the other side

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 an interface connected to a front-port (or as many front/rear-ports as you wish in between), currently, you can only trace that path at the connected points, but not the last front.port. So it would be nice if the trace button at the front-port would be active although nothing is connected directly to it, only through the rear-port. ### Use case This would make cable tracing better, because you can see at a front-port overview which front-ports have a connection/interface at the other side ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:34:00 +01:00
adam closed this issue 2025-12-29 19:34:00 +01:00
adam commented 2025-12-29 19:34:01 +01:00
Author
Owner
Copy Link

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

You've opened several issues today regarding tracing cables, and honestly I'm not sure what you're trying to do. I'm going to close this one; please share more detail in #8277.

@jeremystretch commented on GitHub (Jan 7, 2022): You've opened several issues today regarding tracing cables, and honestly I'm not sure what you're trying to do. I'm going to close this one; please share more detail in #8277.
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#5899
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?