-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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 location to rack clone fields #16786
Comments
I volunteer to work on a PR for this feature. |
Thanks @alehaa, I've assigned this to you. |
@alehaa It sounds like what you're after is a mechanism to easily filter for objects assigned to a location or any of its child locations. Is that accurate? |
No, the (device) objects are pretty easy for us to find. However, creating / editing them sometimes has pitfalls. Real life problem on our site:
This problem occurs because the Device edit form displays all racks in a location, including child locations. There are (at least) two possible solutions:
However, my inquiry was that solution 1 could make the workflow a bit difficult for employees: While it is clear to search for the location |
NetBox version
v4.0.6
Feature type
Change to existing functionality
Proposed functionality
When creating or editing a device, all racks in a location are selectable, including racks in child locations. If you select a rack in a child location, saving the device is rejected with this error message:
Therefore, I suggest that all racks of a location (including child locations) can be selected in the form. When saving, the location of the device will be replaced by the location of the rack, thus automatically correcting it if needed.
Steps to reproduce:
Use case
The structure of the locations is entirely up to the NetBox user. A typical scenario could be to have parent locations for the room and child locations for the rack rows named "R1", "R2", ... in each room. Searching for the room is quite easy because it is unique. Finding the right rack row is not as easy, as there are several with the same name.
Also, it seems a bit odd that the racks are selectable in the UI and the backend does not accept the user's choice.
Database changes
None
External dependencies
None
The text was updated successfully, but these errors were encountered: