Add an InventoryItemType #6657

Closed
opened 2025-12-29 19:43:35 +01:00 by adam · 3 comments
Owner

Originally created by @ryanmerolle on GitHub (Jul 14, 2022).

NetBox version

v3.2.6

Feature type

New functionality

Proposed functionality

Similar to DeviceType, add an InventoryItemType.

Use case

This would drive InventoryItem Standardization within user's NetBox.

Database changes

Add a new model for InventoryItemType and create a FK from InventoryItem to InventoryItemType.

External dependencies

N/A

Originally created by @ryanmerolle on GitHub (Jul 14, 2022). ### NetBox version v3.2.6 ### Feature type New functionality ### Proposed functionality Similar to DeviceType, add an InventoryItemType. ### Use case This would drive InventoryItem Standardization within user's NetBox. ### Database changes Add a new model for InventoryItemType and create a FK from InventoryItem to InventoryItemType. ### External dependencies N/A
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:43:35 +01:00
adam closed this issue 2025-12-29 19:43:35 +01:00
Author
Owner

@jeremystretch commented on GitHub (Jul 20, 2022):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (Jul 20, 2022): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
Author
Owner

@jeremystretch commented on GitHub (Aug 10, 2022):

Closing this as non-actionable, but @ryanmerolle feel free to re-open if you want to flesh it out.

@jeremystretch commented on GitHub (Aug 10, 2022): Closing this as non-actionable, but @ryanmerolle feel free to re-open if you want to flesh it out.
Author
Owner

@ryanmerolle commented on GitHub (Aug 10, 2022):

I'll flesh this out with a model soon and look to reopen

@ryanmerolle commented on GitHub (Aug 10, 2022): I'll flesh this out with a model soon and look to reopen
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#6657