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 Custom Field Choice Sets for Device Type #9394

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

Originally created by @Sergio-MT on GitHub (Mar 27, 2024).

NetBox version

v.3.7.4

Feature type

New functionality

Proposed functionality

Add Custom Field Choice Sets for once Device Type. When creating new Device Type add the ability add custom field with previously created custom choice set. Now I can add Custom field for all Device Types with Multiple Selection mode and choose one cusom choice set, but I need for each Device Type add self custom choice set. This will be used to indicate installed options for device.

Use case

Created Custom Field Choice Set named " options". Created Device Type for and add choice set with availability options which may be opened on this device. Create Device and choose installed options.
Also add any custom choice set for each Device Type

Database changes

No response

External dependencies

No response

Originally created by @Sergio-MT on GitHub (Mar 27, 2024). ### NetBox version v.3.7.4 ### Feature type New functionality ### Proposed functionality Add Custom Field Choice Sets for once Device Type. When creating new Device Type add the ability add custom field with previously created custom choice set. Now I can add Custom field for all Device Types with Multiple Selection mode and choose one cusom choice set, but I need for each Device Type add self custom choice set. This will be used to indicate installed options for device. ### Use case Created Custom Field Choice Set named "<Manufaturer><Model> options". Created Device Type for <Manufaturer><Model> and add choice set with availability options which may be opened on this device. Create Device and choose installed options. Also add any custom choice set for each Device Type ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:49:17 +01:00
adam closed this issue 2025-12-29 20:49:17 +01:00
adam commented 2025-12-29 20:49:18 +01:00
Author
Owner
Copy Link

@abhi1693 commented on GitHub (Apr 5, 2024):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@abhi1693 commented on GitHub (Apr 5, 2024): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 20:49:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 19, 2024):

I'm honestly not sure what is being proposed here; device types already support custom fields. I'm going to close this out as no further information has been provided in response to the request above.

@jeremystretch commented on GitHub (Apr 19, 2024): I'm honestly not sure what is being proposed here; device types already support custom fields. I'm going to close this out as no further information has been provided in response to the request above.
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: revisions needed 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#9394
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?