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 entire cable path from power port to upstream power panel #6556

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

Originally created by @LHBL2003 on GitHub (Jun 10, 2022).

NetBox version

v3.2.2

Feature type

New functionality

Proposed functionality

When I look at the wiring of the power port on the device, I only see the counterpart from the next system. However, I cannot follow the current path to the power panel.

Idee:
The entire course up to the Power Panel is displayed. See picture:

image

Alternative :

You can jump to the next Cabel Trace picture by clicking on the bottom.
This is not as nice as the first idea, but it is still helpful.

image

Use case

Faster and better traceability of the circuit diagram.

Database changes

No response

External dependencies

No response

Originally created by @LHBL2003 on GitHub (Jun 10, 2022). ### NetBox version v3.2.2 ### Feature type New functionality ### Proposed functionality When I look at the wiring of the power port on the device, I only see the counterpart from the next system. However, I cannot follow the current path to the power panel. **Idee:** The entire course up to the Power Panel is displayed. See picture: ![image](https://user-images.githubusercontent.com/46369917/173092125-174868e5-3049-467d-a153-ca507bde4019.png) **Alternative :** You can jump to the next Cabel Trace picture by clicking on the bottom. This is not as nice as the first idea, but it is still helpful. ![image](https://user-images.githubusercontent.com/46369917/173093330-30832bf9-dbae-457a-9e55-481977b21754.png) ### Use case Faster and better traceability of the circuit diagram. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:42:18 +01:00
adam closed this issue 2025-12-29 19:42:18 +01:00
adam commented 2025-12-29 19:42:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2022):

I think this should be feasible, but I need to dig into it more.

@jeremystretch commented on GitHub (Jul 27, 2022): I think this should be feasible, but I need to dig into it more.
adam commented 2025-12-29 19:42:19 +01:00
Author
Owner
Copy Link

@phurrelmann commented on GitHub (Jul 27, 2022):

if the full trace would now be feasible, what about summing the power usage like requested in #3377? maybe this could be realized now much more easily, too?

@phurrelmann commented on GitHub (Jul 27, 2022): if the full trace would now be feasible, what about summing the power usage like requested in #3377? maybe this could be realized now much more easily, too?
adam commented 2025-12-29 19:42:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 16, 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. 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 (Nov 16, 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. **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 19:42:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 17, 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 (Dec 17, 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: needs owner 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#6556
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?