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

Restrict bulk edit dropdown choices to valid ones #9546

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

Originally created by @llamafilm on GitHub (Apr 26, 2024).

NetBox version

v3.7.3

Feature type

Change to existing functionality

Proposed functionality

When bulk editing multiple devices, it would be helpful to restrict the dropdown choices to valid ones.

Use case

For example, I have 10 devices in the same site, and I want to move them from one location to another location within that site. In the bulk edit page, the Location dropdown list shows all locations, which is several thousand to sort through. If I accidentally choose a location from a different site, I get an error like Location A Beautiful Life does not belong to site LA-EGT.

It's even more problematic if I have multiple locations with the same name.

Database changes

none

External dependencies

none

Originally created by @llamafilm on GitHub (Apr 26, 2024). ### NetBox version v3.7.3 ### Feature type Change to existing functionality ### Proposed functionality When bulk editing multiple devices, it would be helpful to restrict the dropdown choices to valid ones. ### Use case For example, I have 10 devices in the same site, and I want to move them from one location to another location within that site. In the bulk edit page, the `Location` dropdown list shows all locations, which is several thousand to sort through. If I accidentally choose a location from a different site, I get an error like _Location A Beautiful Life does not belong to site LA-EGT._ It's even more problematic if I have multiple locations with the same name. ### Database changes none ### External dependencies none
adam added the type: feature label 2025-12-29 20:51:18 +01:00
adam closed this issue 2025-12-29 20:51:18 +01:00
adam commented 2025-12-29 20:51:18 +01:00
Author
Owner
Copy Link

@jeffgdotorg commented on GitHub (Apr 29, 2024):

If you set the Site field during a bulk edit, the previously wide-open list of available Location values is automagically reduced to just ones at the selected Site. I just verified this in both 3.7.4 and 4.0-beta1. This auto-winnowing also applies to other hierarchical objects such as Manufacturer and Device Type.

Closing not-planned for this specific, narrow use case.

@jeffgdotorg commented on GitHub (Apr 29, 2024): If you set the Site field during a bulk edit, the previously wide-open list of available Location values is automagically reduced to just ones at the selected Site. I just verified this in both 3.7.4 and 4.0-beta1. This auto-winnowing also applies to other hierarchical objects such as Manufacturer and Device Type. Closing not-planned for this specific, narrow use case.
adam commented 2025-12-29 20:51:18 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Apr 30, 2024):

Thanks for testing. I did not think to try that, because when bulk editing I try to make the change as narrow as possible. But this makes perfect sense, so I agree there’s no need for a change.

@llamafilm commented on GitHub (Apr 30, 2024): Thanks for testing. I did not think to try that, because when bulk editing I try to make the change as narrow as possible. But this makes perfect sense, so I agree there’s no need for a change.
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 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#9546
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?