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 Unit A and B at cables table #11526

New Issue
Closed
opened 2025-12-29 21:46:23 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:46:23 +01:00
Owner
Copy Link

Originally created by @vikeshavel on GitHub (Aug 25, 2025).

NetBox version

4.3.5

Feature type

New functionality

Proposed functionality

I propose showing Unit A and Unit B in which respective Side A/Side B Devices are installed. For Circuits (which do not have a Unit) the field could be empty or null.

Use case

Employees operating cables often need to know not only from which rack the cable is routed to and from which rack, but also to immediately see which unit the device is located in. Outputting units right in the table with cable properties will make things more convenient and faster.

Database changes

No response

External dependencies

No response

Originally created by @vikeshavel on GitHub (Aug 25, 2025). ### NetBox version 4.3.5 ### Feature type New functionality ### Proposed functionality I propose showing Unit A and Unit B in which respective Side A/Side B Devices are installed. For Circuits (which do not have a Unit) the field could be empty or null. ### Use case Employees operating cables often need to know not only from which rack the cable is routed to and from which rack, but also to immediately see which unit the device is located in. Outputting units right in the table with cable properties will make things more convenient and faster. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:46:24 +01:00
adam closed this issue 2025-12-29 21:46:24 +01:00
adam commented 2025-12-29 21:46:24 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 28, 2025):

Unfortunately this would exceed scope of the cables table, however you might consider writing an export template to export the required additional detail for specific use cases.

@jeremystretch commented on GitHub (Aug 28, 2025): Unfortunately this would exceed scope of the cables table, however you might consider writing an [export template](https://netboxlabs.com/docs/netbox/customization/export-templates/) to export the required additional detail for specific use cases.
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 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#11526
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?