starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Add Rack Group field to Device Location form #4116

New Issue
Closed
opened 2025-12-29 18:33:13 +01:00 by adam · 2 comments
adam commented 2025-12-29 18:33:13 +01:00
Owner
Copy Link

Originally created by @garretwest on GitHub (Sep 18, 2020).

Originally assigned to: @jeremystretch on GitHub.

Environment

  • NetBox version: 2.8.8

Proposed Functionality

When editing a device's location, you can hierarchically drill down on the following currently:

  • Site

  • Rack

  • Rack Face

  • Position

The issue arises when you have the same naming convention in different rack groups (R01, for example). When you choose a site, then go to choose a rack, multiple instances of R01 will show up, with no indication of which rack group they are part of. Example:

image

I am proposing to add a Rack Group field between the Site and Rack fields, which would then only list racks that are part of the chosen rack group.

Use Case

The use case would be to filter out racks that are not part of the chosen rack group when editing a device location.

Database Changes

The proposal requires adding a new Rack Group field to the Device Location form.

Originally created by @garretwest on GitHub (Sep 18, 2020). Originally assigned to: @jeremystretch on GitHub. <!-- 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 * NetBox version: 2.8.8 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality When editing a device's location, you can hierarchically drill down on the following currently: - Site - Rack - Rack Face - Position The issue arises when you have the same naming convention in different rack groups (R01, for example). When you choose a site, then go to choose a rack, multiple instances of R01 will show up, with no indication of which rack group they are part of. Example: ![image](https://user-images.githubusercontent.com/29845853/93633903-f2b71f80-f9ac-11ea-8fa3-9a82035a8980.png) I am proposing to add a **Rack Group** field between the **Site** and **Rack** fields, which would then only list racks that are part of the chosen rack group. <!-- 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 The use case would be to filter out racks that are not part of the chosen rack group when editing a device location. <!-- 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 The proposal requires adding a new **Rack Group** field to the Device Location form.
adam added the status: acceptedtype: feature labels 2025-12-29 18:33:13 +01:00
adam closed this issue 2025-12-29 18:33:13 +01:00
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@ebusto commented on GitHub (Sep 18, 2020):

This would be very useful for us as well, since we use rack groups for rooms in buildings.

@ebusto commented on GitHub (Sep 18, 2020): This would be very useful for us as well, since we use rack groups for rooms in buildings.
adam commented 2025-12-29 18:33:14 +01:00
Author
Owner
Copy Link

@garretwest commented on GitHub (Sep 21, 2020):

Thanks @jeremystretch !

@garretwest commented on GitHub (Sep 21, 2020): Thanks @jeremystretch !
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: accepted 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#4116
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?