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

Render Specified Front and Rear Port Colors During Cable Trace #7224

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

Originally created by @TheZackCodec on GitHub (Nov 14, 2022).

Originally assigned to: @dvigne on GitHub.

NetBox version

v3.3.7

Feature type

Change to existing functionality

Proposed functionality

Currently it is possible to specify colors for Front and Rear Ports. However, when running a cable trace, the port colors are not reflected in the rendered SVG. Cable colors can be specified and are already rendered during cable traces, it only makes sense that the same logic should apply for the Front and Rear Ports. Additionally, when no color is specified, the port color should revert to the current default.

Current Functionality

Current Functionality Netbox

Proposed Functionality

Proposed Functionality Netbox

Use case

Sometimes specific patch panel ports and/or network drop keystone colors are used to help identify specific traces in the real world. Adding this functionality would not only be simple but would further help users visualize and identify traces.

Database changes

None

External dependencies

None

Originally created by @TheZackCodec on GitHub (Nov 14, 2022). Originally assigned to: @dvigne on GitHub. ### NetBox version v3.3.7 ### Feature type Change to existing functionality ### Proposed functionality Currently it is possible to specify colors for Front and Rear Ports. However, when running a cable trace, the port colors are not reflected in the rendered SVG. Cable colors can be specified and are already rendered during cable traces, it only makes sense that the same logic should apply for the Front and Rear Ports. Additionally, when no color is specified, the port color should revert to the current default. ## Current Functionality ![Current Functionality Netbox](https://user-images.githubusercontent.com/31785616/201547734-59d5c121-0f96-4e1c-a880-d44082291507.png) ## Proposed Functionality ![Proposed Functionality Netbox](https://user-images.githubusercontent.com/31785616/201547772-8e37eef6-e21e-485b-a5a1-12ba65120920.png) ### Use case Sometimes specific patch panel ports and/or network drop keystone colors are used to help identify specific traces in the real world. Adding this functionality would not only be simple but would further help users visualize and identify traces. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:20:37 +01:00
adam closed this issue 2025-12-29 20:20:37 +01:00
adam commented 2025-12-29 20:20:38 +01:00
Author
Owner
Copy Link

@TheZackCodec commented on GitHub (Nov 14, 2022):

@dvigne get on this i'm too busy documenting my infrastructure 😆.

@TheZackCodec commented on GitHub (Nov 14, 2022): @dvigne get on this i'm too busy documenting my infrastructure 😆.
adam commented 2025-12-29 20:20:38 +01:00
Author
Owner
Copy Link

@TheZackCodec commented on GitHub (Nov 14, 2022):

Thank @dvigne

@TheZackCodec commented on GitHub (Nov 14, 2022): Thank @dvigne
adam commented 2025-12-29 20:20:38 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 14, 2022):

@dvigne please comment here so GitHub will let me assign the issue to you. Thanks!

@jeremystretch commented on GitHub (Nov 14, 2022): @dvigne please comment here so GitHub will let me assign the issue to you. Thanks!
adam commented 2025-12-29 20:20:39 +01:00
Author
Owner
Copy Link

@dvigne commented on GitHub (Nov 14, 2022):

@jeremystretch much appreciated. Thank you.

@dvigne commented on GitHub (Nov 14, 2022): @jeremystretch much appreciated. Thank you.
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#7224
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?