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

Add a to field type based on ColorChoices with associated widget to Custom Fields #11262

New Issue
Open
opened 2025-12-29 21:42:38 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:42:38 +01:00
Owner
Copy Link

Originally created by @pobk on GitHub (Jun 5, 2025).

NetBox version

v4.3.1

Feature type

Change to existing functionality

Proposed functionality

It's not currently possible to use colors effectively in Custom Fields. You can use create a select field and add a custom selection set, but it isn't currently possible to view those colors using the existing form widget.

I'm proposing to add an additional custom field type for color selection using the existing color choices making it possible to add a color selection to custom fields.

As an alternative approach, allow for overriding of which widget is used for a field and make the color choices available as a custom field base choice set (e.g. like IATA codes etc). This would provide greater flexibility and permit users to use custom color sets.

Use case

I have a requirement to assign color classifications to VRFs and some other models to enable some reporting outside of netbox.

This is presently done using a custom field, and I've manually extracted all the colours used by NetBox into extra field set, however, there is no rendering of the colors in the UI.

Database changes

None

External dependencies

None

Originally created by @pobk on GitHub (Jun 5, 2025). ### NetBox version v4.3.1 ### Feature type Change to existing functionality ### Proposed functionality It's not currently possible to use colors effectively in Custom Fields. You can use create a select field and add a custom selection set, but it isn't currently possible to view those colors using the existing form widget. I'm proposing to add an additional custom field type for color selection using the existing color choices making it possible to add a color selection to custom fields. As an alternative approach, allow for overriding of which widget is used for a field and make the color choices available as a custom field base choice set (e.g. like IATA codes etc). This would provide greater flexibility and permit users to use custom color sets. ### Use case I have a requirement to assign color classifications to VRFs and some other models to enable some reporting outside of netbox. This is presently done using a custom field, and I've manually extracted all the colours used by NetBox into extra field set, however, there is no rendering of the colors in the UI. ### Database changes None ### External dependencies None
adam added the type: featurestatus: needs ownernetboxcomplexity: low labels 2025-12-29 21:42:38 +01:00
adam commented 2025-12-29 21:42:39 +01:00
Author
Owner
Copy Link

@pobk commented on GitHub (Jun 13, 2025):

I don't mind picking this up...

Although I would appreciate with a steer as to whether it would be better for a new field type or allowing a custom widget?

@pobk commented on GitHub (Jun 13, 2025): I don't mind picking this up... Although I would appreciate with a steer as to whether it would be better for a new field type or allowing a custom widget?
adam commented 2025-12-29 21:42:39 +01:00
Author
Owner
Copy Link

@pobk commented on GitHub (Jun 19, 2025):

@jnovinger any particlar thoughts on which way would an apporpriate 'netbox' way of doing this?

@pobk commented on GitHub (Jun 19, 2025): @jnovinger any particlar thoughts on which way would an apporpriate 'netbox' way of doing this?
adam commented 2025-12-29 21:42:39 +01:00
Author
Owner
Copy Link

@reuben-thundergrid commented on GitHub (Aug 28, 2025):

it would be nice when adding a choice set to be able to specify a color.

For example, choice1:First Choice:red

@reuben-thundergrid commented on GitHub (Aug 28, 2025): it would be nice when adding a choice set to be able to specify a color. For example, `choice1:First Choice:red`
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: needs owner 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#11262
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?