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

Show peer interfaces in circuit detail view #9236

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

Originally created by @pv2b on GitHub (Feb 13, 2024).

NetBox version

v3.7.2

Feature type

New functionality

Proposed functionality

When viewing details for a circuit, you will see where the circuit terminations are connected. The way we model things, we'll almost always terminate a circuit in a rear port of a patch panel or similar. It would be handy if we could have a direct link to the interface connected at the end of the path on each end.

For example: In addition to showing "Termination: #123 to Patch Panel 456, 7-8", add a row to this view to show "Termination Interface: router123, 4/5" with links to the appropriate device and interface.

This functionality is already in Netbox, but it's an extra step to have to do a trace of the cable on either end to get the interface.

Use case

Quickly identifying associated interfaces and devices, given a circuit ID.

Database changes

None, all the data is already in Netbox since it can already be accessed using a cable trace.

External dependencies

None.

Originally created by @pv2b on GitHub (Feb 13, 2024). ### NetBox version v3.7.2 ### Feature type New functionality ### Proposed functionality When viewing details for a circuit, you will see where the circuit terminations are connected. The way we model things, we'll almost always terminate a circuit in a rear port of a patch panel or similar. It would be handy if we could have a direct link to the interface connected at the end of the path on each end. For example: In addition to showing "Termination: #123 to Patch Panel 456, 7-8", add a row to this view to show "Termination Interface: router123, 4/5" with links to the appropriate device and interface. This functionality is already in Netbox, but it's an extra step to have to do a trace of the cable on either end to get the interface. ### Use case Quickly identifying associated interfaces and devices, given a circuit ID. ### Database changes None, all the data is already in Netbox since it can already be accessed using a cable trace. ### External dependencies None.
adam closed this issue 2025-12-29 20:47:21 +01:00
adam commented 2025-12-29 20:47:22 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 4, 2024):

Chipping away at this kind of "papercut" UI struggle is something I'd like to see us focus on during the v4.1 development period. Moving along to needs owner. If you're interested in working it through to a PR, just say so and someone will assign it to you. Otherwise another person with the requisite skills and spare capacity can pick it up at any time, even before 4.1 work gets into full swing.

@jeffgdotorg commented on GitHub (Apr 4, 2024): Chipping away at this kind of "papercut" UI struggle is something I'd like to see us focus on during the v4.1 development period. Moving along to `needs owner`. If you're interested in working it through to a PR, just say so and someone will assign it to you. Otherwise another person with the requisite skills and spare capacity can pick it up at any time, even before 4.1 work gets into full swing.
adam commented 2025-12-29 20:47:23 +01:00
Author
Owner
Copy Link

@pv2b commented on GitHub (Apr 4, 2024):

Jeff, I assume you're addressing me on this one.

I'm glad that you agree that this is a worthwhile feature. However, I'm afraid I'm going to pass on the opportunity to work on this. My previous experiences of contributing to this project have, because of personality clashes, not been productive or positive for me nor the project.

@pv2b commented on GitHub (Apr 4, 2024): Jeff, I assume you're addressing me on this one. I'm glad that you agree that this is a worthwhile feature. However, I'm afraid I'm going to pass on the opportunity to work on this. My previous experiences of contributing to this project have, because of personality clashes, not been productive or positive for me nor the project.
adam commented 2025-12-29 20:47:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 21, 2024):

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 21, 2024): 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:47:23 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 20, 2024):

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 (Sep 20, 2024): 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 complexity: low pending closure status: needs owner topic: UI/UX 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#9236
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?