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

Implement a UI mechanism for advanced object selection #6831

New Issue
Closed
opened 2025-12-29 19:45:52 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:45:52 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Aug 17, 2022).

Originally assigned to: @jeremystretch on GitHub.

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:

Screenshot 2022-08-17 at 15-46-02 Add a new device NetBox

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:

  1. User clicks a button to create a new device
  2. User begins searching for the desired site
  3. If found, user selects the site and moves on. Otherwise, user clicks a "filter" button next to the site field, which opens a simple modal containing drop-down selections for region, site group, and site.
  4. User selects the desired region or site group, then finds the desired site from the filtered list.
  5. User dismisses the modal, and the desired site is now selected in the device form.

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:

  • The filters can be removed from form classes (as they do not play a direct role in object creation/modification)
  • It is more clear to the user exactly which attributes they are actually defining on the object
  • Screen space is saved by removing unneeded filters (e.g. in cases where searching for the related object suffices)
  • It will become more feasible to offer direct "add" links for child objects that were previously accessible only via a parent object (e.g. device components)

Database changes

No response

External dependencies

No response

Originally created by @jeremystretch on GitHub (Aug 17, 2022). Originally assigned to: @jeremystretch on GitHub. ### 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: ![Screenshot 2022-08-17 at 15-46-02 Add a new device NetBox](https://user-images.githubusercontent.com/13487278/185229200-ddfadaee-0f1d-4dd2-b296-c58bb728375f.png) 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: 1. User clicks a button to create a new device 2. User begins searching for the desired site 3. If found, user selects the site and moves on. Otherwise, user clicks a "filter" button next to the site field, which opens a simple modal containing drop-down selections for region, site group, and site. 4. User selects the desired region or site group, then finds the desired site from the filtered list. 5. User dismisses the modal, and the desired site is now selected in the device form. 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: - The filters can be removed from form classes (as they do not play a direct role in object creation/modification) - It is more clear to the user exactly which attributes they are actually defining on the object - Screen space is saved by removing unneeded filters (e.g. in cases where searching for the related object suffices) - It will become more feasible to offer direct "add" links for child objects that were previously accessible only via a parent object (e.g. device components) ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:45:52 +01:00
adam closed this issue 2025-12-29 19:45:52 +01:00
adam commented 2025-12-29 19:45:52 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 17, 2022):

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.

@github-actions[bot] commented on GitHub (Oct 17, 2022): 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](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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#6831
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?