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

Missing device field when editing inventory item #6306

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

Originally created by @dsl81 on GitHub (Apr 6, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.0

Python version

3.9

Steps to Reproduce

  1. Click Edit button on any inventory item.

Expected Behavior

Device field should exist with choice of devices.
device_field

Observed Behavior

Device field is not available.
no_device_field

There is no GUI way to change device for inventory item.

Originally created by @dsl81 on GitHub (Apr 6, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.0 ### Python version 3.9 ### Steps to Reproduce 1. Click Edit button on any inventory item. ### Expected Behavior Device field should exist with choice of devices. ![device_field](https://user-images.githubusercontent.com/3961842/161974008-f84f5e8b-3e17-4ce3-994f-303e6b288faa.png) ### Observed Behavior Device field is not available. ![no_device_field](https://user-images.githubusercontent.com/3961842/161974057-23f0ac75-4318-4101-9daf-8f192f20e19e.png) There is no GUI way to change device for inventory item.
adam added the type: bugstatus: accepted labels 2025-12-29 19:39:10 +01:00
adam closed this issue 2025-12-29 19:39:10 +01:00
adam commented 2025-12-29 19:39:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 6, 2022):

Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.

@jeremystretch commented on GitHub (Apr 6, 2022): Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.
adam commented 2025-12-29 19:39:11 +01:00
Author
Owner
Copy Link

@dsl81 commented on GitHub (Apr 6, 2022):

You mean that whole procedure of creating inventory item should be written starting from creating manufacturer of each device?

@dsl81 commented on GitHub (Apr 6, 2022): You mean that whole procedure of creating inventory item should be written starting from creating manufacturer of each device?
adam commented 2025-12-29 19:39:11 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 6, 2022):

You mean that whole procedure of creating inventory item should be written starting from creating manufacturer of each device?

Please at least start from creation of device, however going back to Site/Manufacturer is helpful for us

@DanSheps commented on GitHub (Apr 6, 2022): > You mean that whole procedure of creating inventory item should be written starting from creating manufacturer of each device? Please at least start from creation of device, however going back to Site/Manufacturer is helpful for us
adam commented 2025-12-29 19:39:11 +01:00
Author
Owner
Copy Link

@quixoten commented on GitHub (Apr 6, 2022):

This looks like it might be a regression (is that the right way to say it) of https://github.com/netbox-community/netbox/pull/3818. I don't see those changes in the v3.2.0 version of the code. Maybe this was intentionally left out?

@quixoten commented on GitHub (Apr 6, 2022): This looks like it might be a regression (is that the right way to say it) of https://github.com/netbox-community/netbox/pull/3818. I don't see those changes in the [v3.2.0 version](https://github.com/netbox-community/netbox/blob/v3.2.0/netbox/dcim/forms/models.py#L1364-L1404) of the code. Maybe this was intentionally left out?
adam commented 2025-12-29 19:39:11 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 6, 2022):

For reference, to recreate:

  • Create site (Site A)
  • Create Manufacturer (Cisco)
  • Create Device Type (ISR-4331-K9)
  • Create Device Role (Router)
  • Create Device (9055-test)
  • Create inventory item on device 9055-test (Inventory Item Test)
  • Edit inventory item "Inventory Item Test"
@DanSheps commented on GitHub (Apr 6, 2022): For reference, to recreate: * Create site (Site A) * Create Manufacturer (Cisco) * Create Device Type (ISR-4331-K9) * Create Device Role (Router) * Create Device (9055-test) * Create inventory item on device 9055-test (Inventory Item Test) * Edit inventory item "Inventory Item Test"
adam commented 2025-12-29 19:39:12 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 6, 2022):

This looks like it might be a regression (is that the right way to say it) of #3818. I don't see those changes in the v3.2.0 version of the code. Maybe this was intentionally left out?

You are correct

@DanSheps commented on GitHub (Apr 6, 2022): > This looks like it might be a regression (is that the right way to say it) of #3818. I don't see those changes in the [v3.2.0 version](https://github.com/netbox-community/netbox/blob/v3.2.0/netbox/dcim/forms/models.py#L1364-L1404) of the code. Maybe this was intentionally left out? You are correct
adam commented 2025-12-29 19:39:12 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 6, 2022):

@jeremystretch Do we want to disable moving for now, as there are now other considerations (the fact that other components can be tied to the inventoryitem) or do we want to fix this and still allow moving? I got a patch disabling (also have the partial patch for moving, just need to adjust logic to null any inventory tie-ins)

@DanSheps commented on GitHub (Apr 6, 2022): @jeremystretch Do we want to disable moving for now, as there are now other considerations (the fact that other components can be tied to the inventoryitem) or do we want to fix this and still allow moving? I got a patch disabling (also have the partial patch for moving, just need to adjust logic to null any inventory tie-ins)
adam commented 2025-12-29 19:39:12 +01:00
Author
Owner
Copy Link

@dsl81 commented on GitHub (Apr 7, 2022):

Moving inventory items is essential for tracking things like SFPs. Disabling it will brake accounting of such items for us. If we have to recreate items we will lose history for them. Not to mention that it will be very inconvenient. Besides moving is possible from api, so i hope it will not brake anything.

@dsl81 commented on GitHub (Apr 7, 2022): Moving inventory items is essential for tracking things like SFPs. Disabling it will brake accounting of such items for us. If we have to recreate items we will lose history for them. Not to mention that it will be very inconvenient. Besides moving is possible from api, so i hope it will not brake anything.
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: bug
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#6306
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?