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

Ability to move inventory items between different devices #1838

New Issue
Closed
opened 2025-12-29 17:19:38 +01:00 by adam · 7 comments
adam commented 2025-12-29 17:19:38 +01:00
Owner
Copy Link

Originally created by @uncleVALERA on GitHub (Jul 12, 2018).

Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation

Environment
Python version: 3.5.2
NetBox version: 2.3.5

Description
Create the ability to move inventory items between different devices.

Originally created by @uncleVALERA on GitHub (Jul 12, 2018). **Issue type** [X] Feature request [ ] Bug report [ ] Documentation **Environment** Python version: 3.5.2 NetBox version: 2.3.5 **Description** Create the ability to move inventory items between different devices.
adam added the status: accepted label 2025-12-29 17:19:38 +01:00
adam closed this issue 2025-12-29 17:19:38 +01:00
adam commented 2025-12-29 17:19:38 +01:00
Author
Owner
Copy Link

@xomka686 commented on GitHub (Jul 12, 2018):

Just wanted to request exactly that feature!
We currently have SFP transceivers being added in the "Inventory" section of the devices and are willing to be able to move them between the devices.
It's also useful to have a device registered like a "warehouse" with items like transceivers, power supplies, fan modules and so on and to have flexibility of moving these items from the "warehouse" to actual devices inventory.

@xomka686 commented on GitHub (Jul 12, 2018): Just wanted to request exactly that feature! We currently have SFP transceivers being added in the "Inventory" section of the devices and are willing to be able to move them between the devices. It's also useful to have a device registered like a "warehouse" with items like transceivers, power supplies, fan modules and so on and to have flexibility of moving these items from the "warehouse" to actual devices inventory.
adam commented 2025-12-29 17:19:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 18, 2018):

This needs much more detail to be actionable. Please describe the workflow and any other changes being proposed.

@jeremystretch commented on GitHub (Jul 18, 2018): This needs much more detail to be actionable. Please describe the workflow and any other changes being proposed.
adam commented 2025-12-29 17:19:39 +01:00
Author
Owner
Copy Link

@uncleVALERA commented on GitHub (Jul 19, 2018):

For example: the server has RAID-cards and HDD / SSD.
Periodically need to move them to another server.
If the equipment needs to be deleted on the first server and created on the second server - it will not be correct for inventory and it is not possible to have a history of equipments transfer.
Would like to have possibility detach inventory object from one server/device and attach to second.

@uncleVALERA commented on GitHub (Jul 19, 2018): For example: the server has RAID-cards and HDD / SSD. Periodically need to move them to another server. If the equipment needs to be deleted on the first server and created on the second server - it will not be correct for inventory and it is not possible to have a history of equipments transfer. Would like to have possibility detach inventory object from one server/device and attach to second.
adam commented 2025-12-29 17:19:39 +01:00
Author
Owner
Copy Link

@mmahacek commented on GitHub (Jul 20, 2018):

It is one thing to allow inventory items to be transferred from one device to another (which would be something nice to have) and a completely separate thing to have a history log of all the moves. I would see the latter as part of the upcoming change logging feature slated for 2.4.

@mmahacek commented on GitHub (Jul 20, 2018): It is one thing to allow inventory items to be transferred from one device to another (which would be something nice to have) and a completely separate thing to have a history log of all the moves. I would see the latter as part of the upcoming change logging feature slated for 2.4.
adam commented 2025-12-29 17:19:39 +01:00
Author
Owner
Copy Link

@mmahacek commented on GitHub (Jul 24, 2018):

Scenario 1: Allow Inventory items to be entered without being assigned to a specific device, with the option to edit the assigned device.
-or-
Scenario 2: From the Inventory Items page, add an action that would allow re-assigning the item to a different device.

Since inventory items are currently stored in a separate table, I wouldn't imagine the back end would need much modification. If an inventory item requires an assigned device, the user could create an "Inventory Storage" device to hold items that are not technically assigned to a device at the time.
My guess is the initial request is to accommodate tracking an item moving between devices, rather than deleting and re-creating the item as it moves.

@mmahacek commented on GitHub (Jul 24, 2018): Scenario 1: Allow Inventory items to be entered without being assigned to a specific device, with the option to edit the assigned device. -or- Scenario 2: From the Inventory Items page, add an action that would allow re-assigning the item to a different device. Since inventory items are currently stored in a separate table, I wouldn't imagine the back end would need much modification. If an inventory item requires an assigned device, the user could create an "Inventory Storage" device to hold items that are not technically assigned to a device at the time. My guess is the initial request is to accommodate tracking an item moving between devices, rather than deleting and re-creating the item as it moves.
adam commented 2025-12-29 17:19:39 +01:00
Author
Owner
Copy Link

@spyder372 commented on GitHub (Aug 2, 2018):

As mmahacek said, I would like to add both Scenario 1 and Scenario 2 to the Inventory Items.

This implementation will be the catalyst in ingratiating Netbox in our datacenter. Without a way to track the location of inventory and place it into hold or a "warehouse" status in netbox; and/or move it into another device, it has been turned down every time by our team.

@spyder372 commented on GitHub (Aug 2, 2018): As mmahacek said, I would like to add both Scenario 1 and Scenario 2 to the Inventory Items. This implementation will be the catalyst in ingratiating Netbox in our datacenter. Without a way to track the location of inventory and place it into hold or a "warehouse" status in netbox; and/or move it into another device, it has been turned down every time by our team.
adam commented 2025-12-29 17:19:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 30, 2018):

Scenario 1: Allow Inventory items to be entered without being assigned to a specific device, with the option to edit the assigned device.

This is going to be a hard "no," as it would cross the line into the realm of general inventory management. Our stance has always been that if the item isn't installed in a device, it shouldn't exist in NetBox.

Scenario 2: From the Inventory Items page, add an action that would allow re-assigning the item to a different device.

I'm going to mark this FR as accepted with the caveat that this is the limitation of its scope: Reassigning an existing InventoryItem from one device to another via the web UI.

@jeremystretch commented on GitHub (Nov 30, 2018): > Scenario 1: Allow Inventory items to be entered without being assigned to a specific device, with the option to edit the assigned device. This is going to be a hard "no," as it would cross the line into the realm of general inventory management. Our stance has always been that if the item isn't installed in a device, it shouldn't exist in NetBox. > Scenario 2: From the Inventory Items page, add an action that would allow re-assigning the item to a different device. I'm going to mark this FR as accepted with the caveat that this is the limitation of its scope: Reassigning an existing InventoryItem from one device to another via the web UI.
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: accepted
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#1838
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?