Change rack roles field from single select to multi select #8607

Closed
opened 2025-12-29 20:38:49 +01:00 by adam · 2 comments
Owner

Originally created by @amulheirn on GitHub (Sep 13, 2023).

NetBox version

v3.6.1

Feature type

New functionality

Proposed functionality

The current rack 'role' field is a single select drop down. Proposal is that this should become a multi-select drop down.

Use case

We like the 'rack roles' feature of Netbox, but sometimes a single rack in a small POP site has to have multiple roles because the site's size does not justify multiple racks.

Could the single-select drop-down for rack roles be changed to a multi-select?

At present, we have a custom field for this, but unlike the native rack roles field, this doesn't appear above the rack elevation view.

Database changes

This would require an existing field to change its type to multi select.

External dependencies

No known external dependencies.

Originally created by @amulheirn on GitHub (Sep 13, 2023). ### NetBox version v3.6.1 ### Feature type New functionality ### Proposed functionality The current rack 'role' field is a single select drop down. Proposal is that this should become a multi-select drop down. ### Use case We like the 'rack roles' feature of Netbox, but sometimes a single rack in a small POP site has to have multiple roles because the site's size does not justify multiple racks. Could the single-select drop-down for rack roles be changed to a multi-select? At present, we have a custom field for this, but unlike the native rack roles field, this doesn't appear above the rack elevation view. ### Database changes This would require an existing field to change its type to multi select. ### External dependencies No known external dependencies.
adam added the type: featurepending closure labels 2025-12-29 20:38:49 +01:00
adam closed this issue 2025-12-29 20:38:50 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Dec 13, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 13, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
Author
Owner

@github-actions[bot] commented on GitHub (Jan 22, 2024):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 22, 2024): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8607