starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add Color to PowerOutletTemplates #11647

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

Originally created by @blackphantom39 on GitHub (Sep 24, 2025).

Originally assigned to: @blackphantom39 on GitHub.

NetBox version

v4.3.5

Feature type

Data model extension

Proposed functionality

This Issue is to be seen as an extension to Issue #17195 which was implemented with PR 17623. The color field was only added to the PowerOutlet model itself meaning I can only assign colors to already instantiated Objects (i.e. PDUs). As I do not want to assign colors manually after instantiating i.e. a PDU DeviceType, colors should be assignable to the PowerOutletTemplates.

Use case

Lower the amount of manual actions to be performed when documenting i.e. PDUs that have colored outlets.

Database changes

Changes to the DeviceComponent Model for PowerOutlets and adding the corresponding migration to add the color field.

External dependencies

No response

Originally created by @blackphantom39 on GitHub (Sep 24, 2025). Originally assigned to: @blackphantom39 on GitHub. ### NetBox version v4.3.5 ### Feature type Data model extension ### Proposed functionality This Issue is to be seen as an extension to Issue #17195 which was implemented with [PR 17623](https://github.com/netbox-community/netbox/pull/17623). The color field was only added to the `PowerOutlet` model itself meaning I can only assign colors to already instantiated Objects (i.e. PDUs). As I do not want to assign colors manually after instantiating i.e. a PDU DeviceType, colors should be assignable to the PowerOutletTemplates. ### Use case Lower the amount of manual actions to be performed when documenting i.e. PDUs that have colored outlets. ### Database changes Changes to the DeviceComponent Model for PowerOutlets and adding the corresponding migration to add the color field. ### External dependencies _No response_
adam added the status: acceptedtype: featurenetboxcomplexity: low labels 2025-12-29 21:48:03 +01:00
adam closed this issue 2025-12-29 21:48:03 +01:00
adam commented 2025-12-29 21:48:03 +01:00
Author
Owner
Copy Link

@blackphantom39 commented on GitHub (Sep 29, 2025):

If this gets accepted, I can work on this Issue. As I already submitted a PR unaware of the process outlined in the contribution guide.

@blackphantom39 commented on GitHub (Sep 29, 2025): If this gets accepted, I can work on this Issue. As I already submitted a PR unaware of the process outlined in the contribution guide.
adam commented 2025-12-29 21:48:04 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 2, 2025):

Thanks for volunteering, @blackphantom39 . Please make sure the PR targets the feature branch since this will need to be part of v4.5.0.

@jnovinger commented on GitHub (Oct 2, 2025): Thanks for volunteering, @blackphantom39 . Please make sure the PR targets the `feature` branch since this will need to be part of v4.5.0.
adam commented 2025-12-29 21:48:04 +01:00
Author
Owner
Copy Link

@blackphantom39 commented on GitHub (Oct 10, 2025):

Oh, truly sorry that I also did not see this issue before and created a duplicate. Hopefully everything should be alright with the PR for this now.

@blackphantom39 commented on GitHub (Oct 10, 2025): Oh, truly sorry that I also did not see this issue before and created a duplicate. Hopefully everything should be alright with the PR for this now.
adam commented 2025-12-29 21:48:04 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Oct 10, 2025):

Oh, truly sorry that I also did not see this issue before and created a duplicate. Hopefully everything should be alright with the PR for this now.

No worries, we missed it too.

@jnovinger commented on GitHub (Oct 10, 2025): > Oh, truly sorry that I also did not see this issue before and created a duplicate. Hopefully everything should be alright with the PR for this now. No worries, we missed it too.
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 complexity: low netbox 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#11647
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?