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 support for customfield static choices with multiple select #4690

New Issue
Closed
opened 2025-12-29 19:19:33 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:19:33 +01:00
Owner
Copy Link

Originally created by @Urth on GitHub (Mar 23, 2021).

NetBox version

v2.10.4

Feature type

New functionality

Proposed functionality

Add support for custom field static choices with multiple select.

This resembles #2522 which was rejected before but with the revamp of custom fields this use case is much easier to support. Effectively it only adds a new type that uses a MultipleChoiceField and the StaticSelect2Multiple widget.

Note that CSV import is not yet supported because of #3637 and the multiple select custom fields are explicitly excluded.

Use case

It adds custom fields with multiple selection to allow for feature flags and similar properties while reducing the selection scope to the options given. In the past this was only supported with tags. But the downside of tags are that if your choices are different per model you need to validate them, add tags per model or train your users to only use choice X for model Y.

Now you can add a field with a specific set of choices and those are the only ones available to the user.

Database changes

No database changes required

External dependencies

No external dependencies required

Originally created by @Urth on GitHub (Mar 23, 2021). ### NetBox version v2.10.4 ### Feature type New functionality ### Proposed functionality Add support for custom field static choices with multiple select. This resembles #2522 which was rejected before but with the revamp of custom fields this use case is much easier to support. Effectively it only adds a new type that uses a MultipleChoiceField and the StaticSelect2Multiple widget. Note that CSV import is not yet supported because of #3637 and the multiple select custom fields are explicitly excluded. ### Use case It adds custom fields with multiple selection to allow for feature flags and similar properties while reducing the selection scope to the options given. In the past this was only supported with tags. But the downside of tags are that if your choices are different per model you need to validate them, add tags per model or train your users to only use choice X for model Y. Now you can add a field with a specific set of choices and those are the only ones available to the user. ### Database changes No database changes required ### External dependencies No external dependencies required
adam added the type: featurestatus: duplicate labels 2025-12-29 19:19:33 +01:00
adam closed this issue 2025-12-29 19:19:33 +01:00
adam commented 2025-12-29 19:19:34 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 29, 2021):

This looks like a duplicate of #5451, which has already been implemented for the upcoming v2.11 release.

@jeremystretch commented on GitHub (Mar 29, 2021): This looks like a duplicate of #5451, which has already been implemented for the upcoming v2.11 release.
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: duplicate 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#4690
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?