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

Add selector button on bulk edit dropdown fields #11278

New Issue
Closed
opened 2025-12-29 21:42:48 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:42:48 +01:00
Owner
Copy Link

Originally created by @llamafilm on GitHub (Jun 10, 2025).

NetBox version

v4.3.2

Feature type

Data model extension

Proposed functionality

Add a selector button to the Location list in the bulk edit form.

Use case

I have a bunch of devices that need to be moved from one location to another. So I select them all in the webpage and try bulk edit. But if multiple locations have the same name, there is no way to tell the difference in the dropdown list. Adding a selector button next to the dropdown would help because then I could filter by site.

It's very common (for us) to have multiple locations with the same name at different sites. For example edit bays are typically numbered sequentially counting from 1. And every floor usually has an IDF room labeled by floor number.

Image

I only need this on the Location field, but I could imagine other users might want it on other fields as well.

Database changes

No response

External dependencies

No response

Originally created by @llamafilm on GitHub (Jun 10, 2025). ### NetBox version v4.3.2 ### Feature type Data model extension ### Proposed functionality Add a `selector` button to the Location list in the bulk edit form. ### Use case I have a bunch of devices that need to be moved from one location to another. So I select them all in the webpage and try bulk edit. But if multiple locations have the same name, there is no way to tell the difference in the dropdown list. Adding a `selector` button next to the dropdown would help because then I could filter by site. It's very common (for us) to have multiple locations with the same name at different sites. For example edit bays are typically numbered sequentially counting from 1. And every floor usually has an IDF room labeled by floor number. ![Image](https://github.com/user-attachments/assets/25fb96f2-e6c3-4fb0-9210-d76276275c8f) I only need this on the Location field, but I could imagine other users might want it on other fields as well. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under review labels 2025-12-29 21:42:48 +01:00
adam closed this issue 2025-12-29 21:42:49 +01:00
adam commented 2025-12-29 21:42:49 +01:00
Author
Owner
Copy Link

@pobk commented on GitHub (Jun 11, 2025):

Ass a workaround.... Add a description to the location. This is then presented in the dropdown too

@pobk commented on GitHub (Jun 11, 2025): Ass a workaround.... Add a description to the location. This is then presented in the dropdown too
adam commented 2025-12-29 21:42:49 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Jun 13, 2025):

This can be achieved by selecting a site in Site field (just above location) with the new site, which will then filter down the list of Locations to only those that exist for that site.

@jnovinger commented on GitHub (Jun 13, 2025): This can be achieved by selecting a site in Site field (just above location) with the new site, which will then filter down the list of Locations to only those that exist for that site.
adam commented 2025-12-29 21:42:50 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Jun 14, 2025):

@jnovinger that only works if you want to change the site. There is no uniqueness constraint for location names within a site, and I have hit this issue multiple times, so I have to resort to nbshell to move a device to a new location.

@llamafilm commented on GitHub (Jun 14, 2025): @jnovinger that only works if you want to change the site. There is no uniqueness constraint for location names within a site, and I have hit this issue multiple times, so I have to resort to nbshell to move a device to a new location.
adam commented 2025-12-29 21:42:51 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Jun 19, 2025):

I'll amend my last comment: There is a uniqueness constraint for the combination of site, parent, and name. But in this example, we have two IDF's on each floor named "IDF A" and "IDF B". The "floor" is the parent location. So if I want to move a device from IDF A on the 1st floor to IDF A on the 2nd floor, I can't do this with the GUI.

I'm reviewing this with my team internally to see if we can change the location naming convention to be more verbose. That would probably take care of this issue.

@llamafilm commented on GitHub (Jun 19, 2025): I'll amend my last comment: There _is_ a uniqueness constraint for the combination of site, parent, and name. But in this example, we have two IDF's on each floor named "IDF A" and "IDF B". The "floor" is the parent location. So if I want to move a device from IDF A on the 1st floor to IDF A on the 2nd floor, I can't do this with the GUI. I'm reviewing this with my team internally to see if we can change the location naming convention to be more verbose. That would probably take care of this issue.
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: under review 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#11278
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?