MultiChoiceVar support for Custom fields #4073

Closed
opened 2025-12-29 18:32:58 +01:00 by adam · 1 comment
Owner

Originally created by @garnser on GitHub (Sep 8, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.9.3

Proposed Functionality

Currently for custom fields a few subset of types is allowed. Although tags could support this particular feature it would be a nice addition to have Custom Fields supporting MultiChoiceVar in addition to this.

Use Case

In our particular use-case we separate tags for administrative purposes but we've additional information which would be preferable to display graphically through text rather than a configcontext or tags which may be applicable to multiple objects.

Database Changes

Unknown

External Dependencies

Unknown

Originally created by @garnser on GitHub (Sep 8, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.8 * NetBox version: 2.9.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Currently for custom fields a few subset of types is allowed. Although tags could support this particular feature it would be a nice addition to have Custom Fields supporting MultiChoiceVar in addition to this. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case In our particular use-case we separate tags for administrative purposes but we've additional information which would be preferable to display graphically through text rather than a configcontext or tags which may be applicable to multiple objects. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Unknown <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies Unknown
adam closed this issue 2025-12-29 18:32:58 +01:00
Author
Owner

@garnser commented on GitHub (Sep 8, 2020):

Closing due to #4878

@garnser commented on GitHub (Sep 8, 2020): Closing due to #4878
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#4073