starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Possibility to change device when editing inventory item. #7020

New Issue
Closed
opened 2025-12-29 19:47:57 +01:00 by adam · 10 comments
adam commented 2025-12-29 19:47:57 +01:00
Owner
Copy Link

Originally created by @dsl81 on GitHub (Sep 23, 2022).

Originally assigned to: @kkthxbye-code on GitHub.

NetBox version

v3.3.4

Feature type

Change to existing functionality

Proposed functionality

Return ability to change device when editing inventory item.

Use case

We are using inventory items to account transceivers. When transceiver is moved to another device it should be reflected in netbox. Here it is said that this "feature" was removed for some reason, but if we have to recreate items we will lose history and the hole process of moving items becomes very burdensome.

inventory_item

Database changes

No response

External dependencies

No response

Originally created by @dsl81 on GitHub (Sep 23, 2022). Originally assigned to: @kkthxbye-code on GitHub. ### NetBox version v3.3.4 ### Feature type Change to existing functionality ### Proposed functionality Return ability to change device when editing inventory item. ### Use case We are using inventory items to account transceivers. When transceiver is moved to another device it should be reflected in netbox. [Here](https://github.com/netbox-community/netbox/issues/10437) it is said that this "feature" was removed for some reason, but if we have to recreate items we will lose history and the hole process of moving items becomes very burdensome. ![inventory_item](https://user-images.githubusercontent.com/3961842/191916313-f35d3259-1d09-4bd9-a475-f3b33a3430f4.png) ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:47:57 +01:00
adam closed this issue 2025-12-29 19:47:57 +01:00
adam commented 2025-12-29 19:47:57 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Sep 23, 2022):

Only Inventory items would require this ability to be reassigned, right ?

@jsenecal commented on GitHub (Sep 23, 2022): Only Inventory items would require this ability to be reassigned, right ?
adam commented 2025-12-29 19:47:57 +01:00
Author
Owner
Copy Link

@dsl81 commented on GitHub (Sep 26, 2022):

Sorry, I did not quite understand what you mean by "only". Things like device modules should also be able to be reassigned. Or I got you wrong?

@dsl81 commented on GitHub (Sep 26, 2022): Sorry, I did not quite understand what you mean by "only". Things like device modules should also be able to be reassigned. Or I got you wrong?
adam commented 2025-12-29 19:47:58 +01:00
Author
Owner
Copy Link

@cpmills1975 commented on GitHub (Oct 1, 2022):

Argh. Did this functionality go away? Perhaps as part of some larger change to standardise a bunch of forms?

I currently use inventory items to track line cards etc and until I'm able to migrate to using Modules, will continue to do so. Line cards move between devices from time to time and not having the ability to make this change without deleting and re-creating the inventory item is going to pain me greatly.

@cpmills1975 commented on GitHub (Oct 1, 2022): Argh. Did this functionality go away? Perhaps as part of some larger change to standardise a bunch of forms? I currently use inventory items to track line cards etc and until I'm able to migrate to using Modules, will continue to do so. Line cards move between devices from time to time and not having the ability to make this change without deleting and re-creating the inventory item is going to pain me greatly.
adam commented 2025-12-29 19:47:58 +01:00
Author
Owner
Copy Link

@dsl81 commented on GitHub (Oct 4, 2022):

Argh. Did this functionality go away? Perhaps as part of some larger change to standardise a bunch of forms?

I currently use inventory items to track line cards etc and until I'm able to migrate to using Modules, will continue to do so. Line cards move between devices from time to time and not having the ability to make this change without deleting and re-creating the inventory item is going to pain me greatly.

Yes it was removed. Besides the pain we will lose all history for the item. So we will not be to track them.

@dsl81 commented on GitHub (Oct 4, 2022): > Argh. Did this functionality go away? Perhaps as part of some larger change to standardise a bunch of forms? > > I currently use inventory items to track line cards etc and until I'm able to migrate to using Modules, will continue to do so. Line cards move between devices from time to time and not having the ability to make this change without deleting and re-creating the inventory item is going to pain me greatly. Yes it was removed. Besides the pain we will lose all history for the item. So we will not be to track them.
adam commented 2025-12-29 19:47:58 +01:00
Author
Owner
Copy Link

@robduffy2010 commented on GitHub (Oct 4, 2022):

We also made extensive use of this feature until it was removed. It would help a lot to have it added back.

@robduffy2010 commented on GitHub (Oct 4, 2022): We also made extensive use of this feature until it was removed. It would help a lot to have it added back.
adam commented 2025-12-29 19:47:58 +01:00
Author
Owner
Copy Link

@Xanawatt commented on GitHub (Oct 20, 2022):

Is there a reason that this was removed? With an inventory tracking program, the ability to track device history across locations is heavily desired.

@Xanawatt commented on GitHub (Oct 20, 2022): Is there a reason that this was removed? With an inventory tracking program, the ability to track device history across locations is heavily desired.
adam commented 2025-12-29 19:47:58 +01:00
Author
Owner
Copy Link

@kkthxbye-code commented on GitHub (Nov 1, 2022):

It's still possible to change the device id via. the API. At the very least we should align the UI and API.

See also: #9898

@kkthxbye-code commented on GitHub (Nov 1, 2022): It's still possible to change the device id via. the API. At the very least we should align the UI and API. See also: #9898
adam commented 2025-12-29 19:47:59 +01:00
Author
Owner
Copy Link

@dsl81 commented on GitHub (Nov 1, 2022):

It's still possible to change the device id via. the API. At the very least we should align the UI and API.

See also: #9898

Thanks for the link. So moving inventory item was disabled due to this bug?
If we align UI and API we will not be able to move items with api also?

@dsl81 commented on GitHub (Nov 1, 2022): > It's still possible to change the device id via. the API. At the very least we should align the UI and API. > > See also: #9898 Thanks for the link. So moving inventory item was disabled due to this bug? If we align UI and API we will not be able to move items with api also?
adam commented 2025-12-29 19:47:59 +01:00
Author
Owner
Copy Link

@cichutkiii commented on GitHub (Nov 17, 2022):

I updated yesterday from version 3.3.2 to 3.3.8 and I see this issue too.
Interesting thing is if you want to change it by bulk edit button, then it works.

@cichutkiii commented on GitHub (Nov 17, 2022): I updated yesterday from version 3.3.2 to 3.3.8 and I see this issue too. Interesting thing is if you want to change it by bulk edit button, then it works.
adam commented 2025-12-29 19:47:59 +01:00
Author
Owner
Copy Link

@phurrelmann commented on GitHub (Dec 11, 2022):

This is needed pretty much. We're assigning several hundreds of transceivers to interfaces. They all have custom fields for e.g. the programmed compatibility. Having to recreate all that data when a transceiver is moved to a different device is just a PITA. Ideally we even would like to create an inventory item without a device and assign it only later, when the transceiver is plugged. But of course this out of this ticket's scope.

@phurrelmann commented on GitHub (Dec 11, 2022): This is needed pretty much. We're assigning several hundreds of transceivers to interfaces. They all have custom fields for e.g. the programmed compatibility. Having to recreate all that data when a transceiver is moved to a different device is just a PITA. Ideally we even would like to create an inventory item without a device and assign it only later, when the transceiver is plugged. But of course this out of this ticket's scope.
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 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#7020
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?