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

Drag and Drop Moving of Devices in Rack Elevations #4167

New Issue
Closed
opened 2025-12-29 18:33:35 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:33:35 +01:00
Owner
Copy Link

Originally created by @jameno123 on GitHub (Oct 7, 2020).

Environment

  • Python version: 3.6
  • NetBox version: 2.9.3

Proposed Functionality

When performing rack migrations it is cumbersome to migrate alot of machines manually requiring several steps in the netbox UI. The purpose of this feature would be to enable drag and drop support inside the rack elevations page so that you can click a server drag it onto a new rack position (in same rack or a different rack) and the netbox system will then set the new rack location in the db.

Use Case

Consolidating one rack into 3 others in the same rack row reducing rack space foot print servers from 1 rack are going into various different racks drag and drop would speed up the process of moving these servers significantly

Database Changes

none

External Dependencies

none

Originally created by @jameno123 on GitHub (Oct 7, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6 * NetBox version: 2.9.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality When performing rack migrations it is cumbersome to migrate alot of machines manually requiring several steps in the netbox UI. The purpose of this feature would be to enable drag and drop support inside the rack elevations page so that you can click a server drag it onto a new rack position (in same rack or a different rack) and the netbox system will then set the new rack location in the db. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Consolidating one rack into 3 others in the same rack row reducing rack space foot print servers from 1 rack are going into various different racks drag and drop would speed up the process of moving these servers significantly <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes none <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies none
adam closed this issue 2025-12-29 18:33:35 +01:00
adam commented 2025-12-29 18:33:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 7, 2020):

Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #124 for further discussion.

@jeremystretch commented on GitHub (Oct 7, 2020): Thank you for submitting this issue, however it appears that this topic has already been raised. Please see issue #124 for further discussion.
adam commented 2025-12-29 18:33:36 +01:00
Author
Owner
Copy Link

@chicks-net commented on GitHub (Oct 7, 2020):

Issue #124 is closed to comments from non-collaborators. Since the current collaborators are not interested in this feature this seems like a good way to avoid further discussion or potential new contributors that might have the skills and interest to add this feature. Should #124 be unlocked?

@chicks-net commented on GitHub (Oct 7, 2020): Issue #124 is closed to comments from non-collaborators. Since the current collaborators are not interested in this feature this seems like a good way to avoid further discussion or potential new contributors that might have the skills and interest to add this feature. Should #124 be unlocked?
adam commented 2025-12-29 18:33:36 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 7, 2020):

No. We've opted not to pursue that feature.

@jeremystretch commented on GitHub (Oct 7, 2020): No. We've opted not to pursue that feature.
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
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#4167
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?