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

Only one device is displayed for multi-termination cables #8219

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

Originally created by @pobradovic08 on GitHub (Jun 21, 2023).

Originally assigned to: @pobradovic08 on GitHub.

NetBox version

v3.5.4

Python version

3.8

Steps to Reproduce

  1. Create a cable that has multiple one side terminations on different devices
  2. Go to the Cable page
  3. Observe side with multiple terminations (device and interface listed)

Expected Behavior

To display the device and it's interface (tightly coupled together) if there are multiple terminations, like in interface table view:
image
Something like:
image

Observed Behavior

Device is displayed only for first termination:
image

All interfaces are displayed, but it's not clear to which device they belong to.

Originally created by @pobradovic08 on GitHub (Jun 21, 2023). Originally assigned to: @pobradovic08 on GitHub. ### NetBox version v3.5.4 ### Python version 3.8 ### Steps to Reproduce 1. Create a cable that has multiple one side terminations on different devices 2. Go to the Cable page 3. Observe side with multiple terminations (device and interface listed) ### Expected Behavior To display the device and it's interface (tightly coupled together) if there are multiple terminations, like in interface table view: ![image](https://github.com/netbox-community/netbox/assets/5007811/ff0bd20c-d3d1-4d88-9901-5064d30a53c5) Something like: ![image](https://github.com/netbox-community/netbox/assets/5007811/dd468cd3-1f18-4ea0-98b2-db4b833f2d4a) ### Observed Behavior Device is displayed only for first termination: ![image](https://github.com/netbox-community/netbox/assets/5007811/e8d5e650-7555-49b2-adb4-971409d842cd) All interfaces are displayed, but it's not clear to which device they belong to.
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 20:33:57 +01:00
adam closed this issue 2025-12-29 20:33:57 +01:00
adam commented 2025-12-29 20:33:58 +01:00
Author
Owner
Copy Link

@pobradovic08 commented on GitHub (Jun 21, 2023):

I have 83fd181c26 as a quick fix* for this (but didn't want to open a PR yer since it's not assigned to me).

*This is more of an improvement then a fix of the root issue as the same applies to Rack (and maybe even Location and Site), as there is the possibility to have termination in different racks. The current format of Termination data presentation is not optimized for displaying multiple terminations, and might be better to have a table where each row would have all relevant information for each termination.

As the current interface list is really confusing, can we include this partial fix?

@pobradovic08 commented on GitHub (Jun 21, 2023): I have https://github.com/netbox-community/netbox/commit/83fd181c26304d0271bf0d480ea093a89f4ff88a as a quick fix* for this (but didn't want to open a PR yer since it's not assigned to me). *This is more of an improvement then a fix of the root issue as the same applies to Rack (and maybe even Location and Site), as there is the possibility to have termination in different racks. The current format of Termination data presentation is not optimized for displaying multiple terminations, and might be better to have a table where each row would have all relevant information for each termination. As the current interface list is really confusing, can we include this partial fix?
adam commented 2025-12-29 20:33:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 27, 2023):

@pobradovic08 sounds good, assigning this to you.

@jeremystretch commented on GitHub (Jun 27, 2023): @pobradovic08 sounds good, assigning this to you.
adam commented 2025-12-29 20:33:58 +01:00
Author
Owner
Copy Link

@pobradovic08 commented on GitHub (Jun 28, 2023):

Thank you @jeremystretch! I had some time to look at this further, and it seems that my concerns from the previous comment can be easily fixed by just chaging a couple of templates.

My proposal would be to have a table with each termination as a row. I would also move A and B sides to be horizontally distributed (instead of one above the other) as that looks better to me, but I would like to hear other's opinion.

Interface (with overall layout):
image

Power feed:
image

Power outlet:
image

Circuits:
image

@pobradovic08 commented on GitHub (Jun 28, 2023): Thank you @jeremystretch! I had some time to look at this further, and it seems that my concerns from the previous comment can be easily fixed by just chaging a couple of templates. My proposal would be to have a table with each termination as a row. I would also move A and B sides to be horizontally distributed (instead of one above the other) as that looks better to me, but I would like to hear other's opinion. Interface (with overall layout): <img width="1185" alt="image" src="https://github.com/netbox-community/netbox/assets/5007811/f4f69e8e-c991-48fc-8e9b-ff2ab688f235"> Power feed: <img width="1188" alt="image" src="https://github.com/netbox-community/netbox/assets/5007811/ab78797a-1840-4b6b-876f-5869a5760556"> Power outlet: <img width="1182" alt="image" src="https://github.com/netbox-community/netbox/assets/5007811/ad62d282-951e-4431-9e22-87b227a4ea4f"> Circuits: <img width="1182" alt="image" src="https://github.com/netbox-community/netbox/assets/5007811/145e9329-4a7b-40f0-8bf0-4f2b8bc0f6e1">
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 severity: low status: accepted type: bug
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#8219
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?