Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Custom Field Choice Sets for Device Type #15545

Closed
Sergio-MT opened this issue Mar 27, 2024 · 2 comments
Closed

Add Custom Field Choice Sets for Device Type #15545

Sergio-MT opened this issue Mar 27, 2024 · 2 comments
Labels
status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application

Comments

@Sergio-MT
Copy link

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

@Sergio-MT Sergio-MT added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels Mar 27, 2024
@abhi1693
Copy link
Member

abhi1693 commented 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 abhi1693 added status: revisions needed This issue requires additional information to be actionable and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 5, 2024
@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Apr 8, 2024
@jeremystretch jeremystretch reopened this Apr 8, 2024
@jeremystretch
Copy link
Member

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 jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Apr 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants