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 Rack to the Device Bulk Edit form #11854

New Issue
Open
opened 2025-12-29 21:50:44 +01:00 by adam · 5 comments
adam commented 2025-12-29 21:50:44 +01:00
Owner
Copy Link

Originally created by @llamafilm on GitHub (Nov 20, 2025).

NetBox version

v4.4.6

Feature type

Data model extension

Proposed functionality

When bulk editing multiple Devices, I should be able to change their Rack.

Use case

I have a few dozen devices, in 3 different Racks, that all need to be un-racked so that I can move them to a different Location. Netbox won't let me change their Location until the Rack is cleared.

Database changes

No response

External dependencies

No response

Originally created by @llamafilm on GitHub (Nov 20, 2025). ### NetBox version v4.4.6 ### Feature type Data model extension ### Proposed functionality When bulk editing multiple Devices, I should be able to change their Rack. ### Use case I have a few dozen devices, in 3 different Racks, that all need to be un-racked so that I can move them to a different Location. Netbox won't let me change their Location until the Rack is cleared. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: under reviewnetbox labels 2025-12-29 21:50:44 +01:00
adam commented 2025-12-29 21:50:45 +01:00
Author
Owner
Copy Link

@pheus commented on GitHub (Nov 20, 2025):

I’m happy to open a PR if it’s accepted.

@pheus commented on GitHub (Nov 20, 2025): I’m happy to open a PR if it’s accepted.
adam commented 2025-12-29 21:50:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 20, 2025):

IIRC we intentionally don't support this because there's no mechanism available to simultaneously modify devices' position: All devices being moved to the new rack would keep their same position. This is generally only useful when moving to an empty rack, otherwise physical conflicts are highly likely and cannot be resolved in bulk.

@jeremystretch commented on GitHub (Nov 20, 2025): IIRC we intentionally don't support this because there's no mechanism available to simultaneously modify devices' position: All devices being moved to the new rack would keep their same position. This is generally only useful when moving to an empty rack, otherwise physical conflicts are highly likely and cannot be resolved in bulk.
adam commented 2025-12-29 21:50:46 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Nov 20, 2025):

That's a good point, and may take more thought to reach a good solution.

We could allow the bulk edit form to null the rack field, which implies also nulling the rack position. Then the user can update the rack for each device one at a time. This would have saved me time in this case, because the rack assignment is blocking me from bulk editing the location.

Taking it one step further, we could automatically null the rack position when you move to a new rack. Then the user can manually update each position. This might be surprising to users though.

@llamafilm commented on GitHub (Nov 20, 2025): That's a good point, and may take more thought to reach a good solution. We could allow the bulk edit form to null the rack field, which implies also nulling the rack position. Then the user can update the rack for each device one at a time. This would have saved me time in this case, because the rack assignment is blocking me from bulk editing the location. Taking it one step further, we could automatically null the rack position when you move to a new rack. Then the user can manually update each position. This might be surprising to users though.
adam commented 2025-12-29 21:50:46 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 20, 2025):

This might be better served by FR #19737.

we could automatically null the rack position when you move to a new rack

I'm hesitant to introduce any logic that would nullify data without it being very clear to the user.

@jeremystretch commented on GitHub (Nov 20, 2025): This might be better served by FR #19737. > we could automatically null the rack position when you move to a new rack I'm hesitant to introduce any logic that would nullify data without it being very clear to the user.
adam commented 2025-12-29 21:50:47 +01:00
Author
Owner
Copy Link

@llamafilm commented on GitHub (Nov 21, 2025):

Ooh I really like the grid idea, for a variety of uses. So that would support this full workflow, moving both the rack, position, and location all in one go. That seems like a quite complex solution. In the meantime, maybe it's worthwhile to just add a way to null the rack and position on the existing bulk edit form.

@llamafilm commented on GitHub (Nov 21, 2025): Ooh I really like the grid idea, for a variety of uses. So that would support this full workflow, moving both the rack, position, and location all in one go. That seems like a quite complex solution. In the meantime, maybe it's worthwhile to just add a way to null the rack and position on the existing bulk edit form.
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 netbox 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#11854
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?