I volunteer to work on a PR for this feature.

Thanks @alehaa, I've assigned this to you.

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.

@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:

1. Employee creates new device.
2. Employee assigns device to location Data Center Room 01, rack Rack 17.
3. Operator saves the device.
4. NetBox displays error because Rack 17 is not in Datacenter Room 01, but in Datacenter Room 01 > Row A.

This problem occurs because the Device edit form displays all racks in a location, including child locations. There are (at least) two possible solutions:

1. Limit the racks in the device edit form to those of the location, NOT including child locations. This would reflect the implementation of dcim.models.Device.check().
2. Change the implementation of Device.check() / Device.save() so that the location (and perhaps the site) is copied from the rack. Since the rack has a defined location / site, its clear where the device should be located.

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 Data Center Room 01, searching for Row A might result in multiple items from different locations named the same. The device edit form doesn't display additional information about a location's parent locations. Also, a technician might not even know what row a rack is in, only the room (parent location). Typing the room into the location field of the device edit form wouldn't show the child locations, so you might be able to select them if you only know the parent location.