Custom fields for rack groups #1185

Closed
opened 2025-12-29 16:29:50 +01:00 by adam · 1 comment
Owner

Originally created by @flowdnb on GitHub (Aug 20, 2017).

Issue type

[x] Feature request

Environment

  • NetBox version: 2.1.2

Description

We use rack groups to group racks within a site by room. It would be useful to configure custom fields on rack groups as well to store extra information such as room number, locking info, floor level.

Originally created by @flowdnb on GitHub (Aug 20, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### Issue type [x] Feature request <!-- Requesting the implementation of a new feature --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * NetBox version: 2.1.2 <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description We use rack groups to group racks within a site by room. It would be useful to configure custom fields on rack groups as well to store extra information such as room number, locking info, floor level.
adam closed this issue 2025-12-29 16:29:50 +01:00
Author
Owner

@jeremystretch commented on GitHub (Aug 21, 2017):

This has come up before, so I've added a section in the FAQ for it. The short answer is that we don't associate extra data with organizational models because they don't have dedicated views, and including custom fields in a list view incurs a substantial performance penalty.

@jeremystretch commented on GitHub (Aug 21, 2017): This has come up before, so I've added a [section in the FAQ](https://github.com/digitalocean/netbox/wiki/Frequently-Asked-Questions#can-we-add-custom-fields-to-more-models) for it. The short answer is that we don't associate extra data with organizational models because they don't have dedicated views, and including custom fields in a list view incurs a substantial performance penalty.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1185