-
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
Implement a UI mechanism for advanced object selection #10054
Comments
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. |
…11952) * WIP * WIP * WIP * Make object selector functional * Replace extraneous form fields with selector widgets * Avoid overlap with filterset field names * Show checkmarks next to visibile filters * Update results automatically when searching * Include selector for device/VM component parent fields * Use selector for filtering VLAN group/site * Limit selector to 100 results
NetBox version
v3.3.0
Feature type
New functionality
Proposed functionality
This FR seeks to provide the user a more convenient and obvious method for selecting a related object when creating and editing NetBox object.
For example, when creating a new device, the user must select a site and may select a location and/or rack within that site. To aid the user in selecting a site, NetBox provides drop-down selections to filter by region and site group:
However, it is not obvious to the user that the site, location, and rack fields are attributes of the device, whereas region and site group are not. Ideally, the region and site group selections should be moved to a hidden modal that can be summoned if needed when selecting the site. I envision the following workflow:
I expect that we can render the modal via standard utility views rendered using HTMX requests for minimal overhead.
Use case
Abstracting the fields which exist solely for filtering has several benefits:
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: