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

Inventory Items in v3.2 beta 2 #6259

New Issue
Closed
opened 2025-12-29 19:38:39 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:38:39 +01:00
Owner
Copy Link

Originally created by @tomwoodcraft on GitHub (Mar 25, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.2.0 beta2

Python version

3.9

Steps to Reproduce

(Python v3.10 but not an option on drop down)

A couple of issues with inventory items.

(1) Trying to nest inventory items on a Device Type doesn't appear to work. You can create inventory items against the type but if you try to specify a parent on a second inventory item in the drop down, the first item doesn't show (nor do any others).

(2) If you go to create an inventory item on a device type there's an option to add a module type at the top of the form (indicating they should be creatable against module types?) but they are only created against the device type still. There is no inventory item in the components drop down when creating a module type.

(This was observed and tested in the beta demo)

Expected Behavior

From my understanding, the inventory items for device types and module types should both behave the same way as device (instances)? So you would be able to add nested inventory items to track components making up a device and then when you create devices or modules from these types, inventory items are created automatically, in the same way as the rest of components - interfaces, ports etc.

Observed Behavior

Nesting inventory items not possible for device types

Inventory items not possible for modules

Originally created by @tomwoodcraft on GitHub (Mar 25, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.2.0 beta2 ### Python version 3.9 ### Steps to Reproduce (Python v3.10 but not an option on drop down) A couple of issues with inventory items. (1) Trying to nest inventory items on a Device Type doesn't appear to work. You can create inventory items against the type but if you try to specify a parent on a second inventory item in the drop down, the first item doesn't show (nor do any others). (2) If you go to create an inventory item on a device type there's an option to add a module type at the top of the form (indicating they should be creatable against module types?) but they are only created against the device type still. There is no inventory item in the components drop down when creating a module type. (This was observed and tested in the beta demo) ### Expected Behavior From my understanding, the inventory items for device types and module types should both behave the same way as device (instances)? So you would be able to add nested inventory items to track components making up a device and then when you create devices or modules from these types, inventory items are created automatically, in the same way as the rest of components - interfaces, ports etc. ### Observed Behavior Nesting inventory items not possible for device types Inventory items not possible for modules
adam added the type: bugstatus: acceptedbeta labels 2025-12-29 19:38:39 +01:00
adam closed this issue 2025-12-29 19:38:39 +01:00
adam commented 2025-12-29 19:38:40 +01:00
Author
Owner
Copy Link

@tomwoodcraft commented on GitHub (Mar 29, 2022):

Hi @jeremystretch, thanks for the prompt response for this. Tried testing the changes, the nested inventory now works on device types but when trying to create a device of that type seeing this error:

Field error: Cannot resolve keyword 'device' into field. Choices are: _name, child_items, component, component_id, component_type, component_type_id, created, description, device_type, device_type_id, id, label, last_updated, level, lft, manufacturer, manufacturer_id, name, parent, parent_id, part_id, rght, role, role_id, tree_id

@tomwoodcraft commented on GitHub (Mar 29, 2022): Hi @jeremystretch, thanks for the prompt response for this. Tried testing the changes, the nested inventory now works on device types but when trying to create a device of that type seeing this error: Field error: Cannot resolve keyword 'device' into field. Choices are: _name, child_items, component, component_id, component_type, component_type_id, created, description, device_type, device_type_id, id, label, last_updated, level, lft, manufacturer, manufacturer_id, name, parent, parent_id, part_id, rght, role, role_id, tree_id
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 beta 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#6259
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?