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

Add Position to Cable trace #7605

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

Originally created by @davidoffx3m on GitHub (Feb 6, 2023).

Originally assigned to: @DanSheps on GitHub.

NetBox version

v3.4.4

Feature type

Change to existing functionality

Proposed functionality

It would be great to add the Position to Cable trace Output, that will show the Rack Unit. Output should contain following information:
Site/Location/Rack/Position

Use case

This can help to provide information for patching and troubleshooting connection in DataCenter for local staff.

Database changes

No response

External dependencies

No response

Originally created by @davidoffx3m on GitHub (Feb 6, 2023). Originally assigned to: @DanSheps on GitHub. ### NetBox version v3.4.4 ### Feature type Change to existing functionality ### Proposed functionality It would be great to add the Position to Cable trace Output, that will show the Rack Unit. Output should contain following information: Site/Location/Rack/Position ### Use case This can help to provide information for patching and troubleshooting connection in DataCenter for local staff. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 20:25:57 +01:00
adam closed this issue 2025-12-29 20:25:57 +01:00
adam commented 2025-12-29 20:25:58 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 2, 2023):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 2, 2023): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:25:58 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 8, 2023):

I would be willing to take this on. It might actually make things slightly more simple for some of the logic within the cable trace system.

I will do this after #13337 is merged in.

@DanSheps commented on GitHub (Aug 8, 2023): I would be willing to take this on. It might actually make things slightly more simple for some of the logic within the cable trace system. I will do this after #13337 is merged in.
adam commented 2025-12-29 20:25:58 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 9, 2024):

Going to wait on this until the other cable SVG work is done.

@DanSheps commented on GitHub (Jan 9, 2024): Going to wait on this until the other cable SVG work is done.
adam commented 2025-12-29 20:25:59 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Jan 9, 2024):

Blocked by PR: #14750

@DanSheps commented on GitHub (Jan 9, 2024): Blocked by PR: #14750
adam commented 2025-12-29 20:25:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 22, 2024):

@DanSheps could you take another look at this now?

@jeremystretch commented on GitHub (May 22, 2024): @DanSheps could you take another look at this now?
adam commented 2025-12-29 20:25:59 +01:00
Author
Owner
Copy Link

@davidoffx3m commented on GitHub (Oct 2, 2024):

Any updates regarding the issue?

@davidoffx3m commented on GitHub (Oct 2, 2024): Any updates regarding the issue?
adam commented 2025-12-29 20:26:00 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Oct 2, 2024):

Thanks for the bump. I re-read this and completely missed-understood the goal last time for some stupid reason. Simple one, should have a PR in for it shortly.

@DanSheps commented on GitHub (Oct 2, 2024): Thanks for the bump. I re-read this and completely missed-understood the goal last time for some stupid reason. Simple one, should have a PR in for it shortly.
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 complexity: low 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#7605
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?