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

Be able to view port type (front, back, interface) in Cables view #2481

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

Originally created by @kitocole on GitHub (Mar 22, 2019).

Environment
Python version: 3.5.6
NetBox version: 2.5.8

Proposed Functionality
In Devices -> Cables, add a column that shows the port type (front/back/interface) for fast and easy viewing.

Use Case
This would allow an operator to easily know which side of each patchpanel a cable is connected to. Even someone new would be able to get this information quickly and accurately.

Database Changes
N/A

External Dependencies
N/A

Originally created by @kitocole on GitHub (Mar 22, 2019). Environment Python version: 3.5.6 NetBox version: 2.5.8 **Proposed Functionality** In Devices -> Cables, add a column that shows the port type (front/back/interface) for fast and easy viewing. **Use Case** This would allow an operator to easily know which side of each patchpanel a cable is connected to. Even someone new would be able to get this information quickly and accurately. Database Changes N/A External Dependencies N/A
adam closed this issue 2025-12-29 18:19:14 +01:00
adam commented 2025-12-29 18:19:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 28, 2019):

This is typically going to be conveyed by context (device and component name). Adding columns to state the types explicitly strikes me as overly verbose.

@jeremystretch commented on GitHub (Mar 28, 2019): This is typically going to be conveyed by context (device and component name). Adding columns to state the types explicitly strikes me as overly verbose.
adam commented 2025-12-29 18:19:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 1, 2019):

Closing this out as there's been no further feedback in the past month.

@jeremystretch commented on GitHub (May 1, 2019): Closing this out as there's been no further feedback in the past month.
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
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#2481
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?