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

Add colors to Circuit Types model and use this when rendering cable traces #7885

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

Originally created by @decoupca on GitHub (Apr 10, 2023).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.4.6

Feature type

New functionality

Proposed functionality

As described in this discussion, make it possible to identify the type of circuit that's involved in a cable trace by color-coding circuit types, and including the circuit type's name in the circuit's block in the diagram.

This would involve:

  • Extending the circuit type model to include a color value (identical to how device roles are color-coded);
  • Updating the cable trace view to reflect the circuit type's color and name.

This FR proposes no changes to cable traces that do not involve a circuit.

Use case

Currently there is no way to identify the type of a circuit involved in a cable trace just by looking at the diagram. Color-coding and labeling circuit types adds convenience when looking at multiple cable traces, especially if the cable trace is exported or viewed by someone without access to NetBox, and hence can't resolve the circuit type by clicking on it, or looking it up.

Database changes

Circuit types need a field for color value.

External dependencies

None.

Originally created by @decoupca on GitHub (Apr 10, 2023). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.4.6 ### Feature type New functionality ### Proposed functionality As described in [this discussion](https://github.com/netbox-community/netbox/discussions/12035), make it possible to identify the type of circuit that's involved in a cable trace by color-coding circuit types, and including the circuit type's name in the circuit's block in the diagram. This would involve: * Extending the circuit type model to include a color value (identical to how device roles are color-coded); * Updating the cable trace view to reflect the circuit type's color and name. This FR proposes no changes to cable traces that do not involve a circuit. ### Use case Currently there is no way to identify the type of a circuit involved in a cable trace just by looking at the diagram. Color-coding and labeling circuit types adds convenience when looking at multiple cable traces, especially if the cable trace is exported or viewed by someone without access to NetBox, and hence can't resolve the circuit type by clicking on it, or looking it up. ### Database changes Circuit types need a field for color value. ### External dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 20:29:33 +01:00
adam closed this issue 2025-12-29 20:29:33 +01:00
adam commented 2025-12-29 20:29:34 +01:00
Author
Owner
Copy Link

@decoupca commented on GitHub (Apr 10, 2023):

Had some time to play with this, if approved I'd like to handle it.

image image image
@decoupca commented on GitHub (Apr 10, 2023): Had some time to play with this, if approved I'd like to handle it. <img width="442" alt="image" src="https://user-images.githubusercontent.com/94914780/230979417-b8079635-18ce-49c8-b79d-14afd96dd990.png"> <img width="428" alt="image" src="https://user-images.githubusercontent.com/94914780/230979554-c311ce5e-6e0a-4476-8f80-e19ab84322d5.png"> <img width="609" alt="image" src="https://user-images.githubusercontent.com/94914780/230979642-7ae4ebb8-ee83-4888-97b9-2a31ae506596.png">
adam commented 2025-12-29 20:29:34 +01:00
Author
Owner
Copy Link

@decoupca commented on GitHub (Jul 20, 2023):

@jeremystretch Is there anything I can contribute to assist the review? This feature has come up a few times on my team. Thanks!

@decoupca commented on GitHub (Jul 20, 2023): @jeremystretch Is there anything I can contribute to assist the review? This feature has come up a few times on my team. Thanks!
adam commented 2025-12-29 20:29:34 +01:00
Author
Owner
Copy Link

@jasonbothe-moodys commented on GitHub (Oct 11, 2023):

@jeremystretch I would really really like to like some traction on this. Would it be possible to elevate it? Many thanks to @decoupca for the willingness to contribute in making this feature a reality.

@jasonbothe-moodys commented on GitHub (Oct 11, 2023): @jeremystretch I would really really like to like some traction on this. Would it be possible to elevate it? Many thanks to @decoupca for the willingness to contribute in making this feature a reality.
adam commented 2025-12-29 20:29:34 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Oct 12, 2023):

Make sure you "thumbs up" the main issue, that is how we triage featurues

@DanSheps commented on GitHub (Oct 12, 2023): Make sure you "thumbs up" the main issue, that is how we triage featurues
adam commented 2025-12-29 20:29:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 19, 2023):

@decoupca I assigned this to @arthanson before I noticed your comment above. Would you like to own this one?

@jeremystretch commented on GitHub (Oct 19, 2023): @decoupca I assigned this to @arthanson before I noticed your comment above. Would you like to own this one?
adam commented 2025-12-29 20:29:35 +01:00
Author
Owner
Copy Link

@jasonbothe commented on GitHub (Oct 24, 2023):

Thank you gents!

@jasonbothe commented on GitHub (Oct 24, 2023): Thank you gents!
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#7885
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?