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

UI Improvements for Cables with multiple terminations on different devices #6934

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

Originally created by @liquid-metal on GitHub (Sep 6, 2022).

NetBox version

v3.3.2

Feature type

Change to existing functionality

Proposed functionality

When a cable with multiple terminations is connected to different devices on the same side, the UI could be improved in two places:

  • On the "Add a new cable" page: When interfaces of multiple devices are selected, the associated device in the interface section is not clear. In the following screenshot, I have connected test-device1(i1) with test-device2(i1), test-device3(i2) and test-device3(i3). This is not clear in the selection. Proposal: if interfaces of multiple devices are present, add the device name (e.g. i1 (test-device2), i2 (test-device3), i3 (test-device3) in the example):
    2022-09-06_13 06 52_screenshot

  • In the cable trace view: Same scenario as described above. If I trace the cable now, it is not clear which termination belongs to which device. I would propose that the boxes for the terminations do not fill the entire width, but they should be grouped by the corresponding device.
    2022-09-06_13 11 32_screenshot

Use case

Improve visibility in the UI

Database changes

Probably none

External dependencies

none

Originally created by @liquid-metal on GitHub (Sep 6, 2022). ### NetBox version v3.3.2 ### Feature type Change to existing functionality ### Proposed functionality When a cable with multiple terminations is connected to different devices on the same side, the UI could be improved in two places: - On the "Add a new cable" page: When interfaces of multiple devices are selected, the associated device in the interface section is not clear. In the following screenshot, I have connected test-device1(i1) with test-device2(i1), test-device3(i2) and test-device3(i3). This is not clear in the selection. Proposal: if interfaces of multiple devices are present, add the device name (e.g. i1 (test-device2), i2 (test-device3), i3 (test-device3) in the example): ![2022-09-06_13 06 52_screenshot](https://user-images.githubusercontent.com/56035107/188621282-9d19813b-e459-45fb-b6f0-7ee75ab4110f.png) - ~In the cable trace view: Same scenario as described above. If I trace the cable now, it is not clear which termination belongs to which device. I would propose that the boxes for the terminations do not fill the entire width, but they should be grouped by the corresponding device.~ ![2022-09-06_13 11 32_screenshot](https://user-images.githubusercontent.com/56035107/188622181-8c96abcc-5ec6-4fe3-9aef-2915607763e1.png) ### Use case Improve visibility in the UI ### Database changes Probably none ### External dependencies none
adam added the status: acceptedtype: feature labels 2025-12-29 19:46:58 +01:00
adam closed this issue 2025-12-29 19:46:58 +01:00
adam commented 2025-12-29 19:46:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 6, 2022):

In the cable trace view

Please open a separate FR for this as it is unrelated to the first item.

@jeremystretch commented on GitHub (Sep 6, 2022): > In the cable trace view Please open a separate FR for this as it is unrelated to the first item.
adam commented 2025-12-29 19:46:59 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 6, 2022):

A similar issue happens with vlans. Perhaps it might be useful to have a "verbose" display name on all models which includes some parent model information (Device/Site/etc)

@DanSheps commented on GitHub (Sep 6, 2022): A similar issue happens with vlans. Perhaps it might be useful to have a "verbose" display name on all models which includes some parent model information (Device/Site/etc)
adam commented 2025-12-29 19:46:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 6, 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 6, 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:46:59 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 7, 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 7, 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.
adam commented 2025-12-29 19:46:59 +01:00
Author
Owner
Copy Link

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

I'd still like to tackle this. We just need to figure out how to implement the logic in the SVG rendering.

@jeremystretch commented on GitHub (Dec 7, 2022): I'd still like to tackle this. We just need to figure out how to implement the logic in the SVG rendering.
adam commented 2025-12-29 19:46:59 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Mar 30, 2023):

Pretty sure this should still be opened...

@DanSheps commented on GitHub (Mar 30, 2023): Pretty sure this should still be opened...
adam commented 2025-12-29 19:47:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 30, 2023):

This was closed for going stale. Happy to re-open it if someone would like to volunteer to own it.

@jeremystretch commented on GitHub (Mar 30, 2023): This was closed for going stale. Happy to re-open it _if_ someone would like to volunteer to own it.
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 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#6934
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?