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

Improvement of moving devices #6150

New Issue
Closed
opened 2025-12-29 19:37:22 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:37:22 +01:00
Owner
Copy Link

Originally created by @PaulR282 on GitHub (Feb 28, 2022).

NetBox version

v3.1.8

Feature type

Data model extension

Proposed functionality

If you want to move a device and plan it in NetBox (Edit the device Location and set the status to planned) it would be nice to see the device still active in the current location and the same device in the new location as planned and maybe graded greyish.

Further, it would be nice to plan the device in rackspace that is currently used.

Use case

Right now, if you move a device like described above, NetBox doesn't represent the real world, because the rackspace of the current location would be free in NetBox, while it is used in real life. Currently, it is difficult to plan bigger moving while documenting the current state.

Database changes

One way to implement this would be to split the location attribute to something like current_location and new_location.

External dependencies

No response

Originally created by @PaulR282 on GitHub (Feb 28, 2022). ### NetBox version v3.1.8 ### Feature type Data model extension ### Proposed functionality If you want to move a device and plan it in NetBox (Edit the device Location and set the status to `planned`) it would be nice to see the device still active in the current location and the same device in the new location as `planned` and maybe graded greyish. Further, it would be nice to plan the device in rackspace that is currently used. ### Use case Right now, if you move a device like described above, NetBox doesn't represent the real world, because the rackspace of the current location would be free in NetBox, while it is used in real life. Currently, it is difficult to plan bigger moving while documenting the current state. ### Database changes One way to implement this would be to split the `location` attribute to something like `current_location` and `new_location`. ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:37:22 +01:00
adam closed this issue 2025-12-29 19:37:22 +01:00
adam commented 2025-12-29 19:37:23 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 1, 2022):

This is easily accomplished by creating a copy of the device to represent the planned installation, or by making a rack reservation. Attempting to represent a single device in two places at once would obviously not be an accurate representation of the real world.

@jeremystretch commented on GitHub (Mar 1, 2022): This is easily accomplished by creating a copy of the device to represent the planned installation, or by making a rack reservation. Attempting to represent a single device in two places at once would obviously not be an accurate representation of the real world.
adam commented 2025-12-29 19:37:23 +01:00
Author
Owner
Copy Link

@PaulR282 commented on GitHub (Mar 1, 2022):

Yes, this would be one way to solve this, but you can´t name two devices the same. Also, the IP would be duplicated (possible, but not optimal)

@PaulR282 commented on GitHub (Mar 1, 2022): Yes, this would be one way to solve this, but you can´t name two devices the same. Also, the IP would be duplicated (possible, but not optimal)
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#6150
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?