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

Allow Custom Fields on Inventory Items. #900

New Issue
Closed
opened 2025-12-29 16:26:49 +01:00 by adam · 1 comment
adam commented 2025-12-29 16:26:49 +01:00
Owner
Copy Link

Originally created by @cimnine on GitHub (May 2, 2017).

Issue type: Feature Request

I'd like to ask if it can be allowed to define Custom Fields on Inventory Items. It would help us with tracking certain information, that is probably unique to our organisation, like the purpose of a disk (e.g. whether a disk is built-in but spare).

Custom Fields have proven to be ideally for such use-cases, which are specific to one's organisation. It would therefore be great to have them available on Inventory Items.

Originally created by @cimnine on GitHub (May 2, 2017). ### Issue type: Feature Request I'd like to ask if it can be allowed to define Custom Fields on Inventory Items. It would help us with tracking certain information, that is probably unique to our organisation, like the purpose of a disk (e.g. whether a disk is built-in but spare). Custom Fields have proven to be ideally for such use-cases, which are specific to one's organisation. It would therefore be great to have them available on Inventory Items.
adam closed this issue 2025-12-29 16:26:49 +01:00
adam commented 2025-12-29 16:26:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 3, 2017):

I don't think it makes sense to enable custom fields on inventory items. The model's role is still a bit ambiguous but it's intended to represent hardware components gleaned through some form of automated inventory. Additionally, due to the hierarchical arrangements of inventory items, including custom fields would introduce a substantial performance penalty.

You've also opened #1121 for the addition of some built-in fields for the InventoryItem model, which I think is preferable to enabling custom fields. I'm going to close out this ticket in favor of #1121; we can revisit the idea in the future if the agreed-upon built-in fields don't suffice.

@jeremystretch commented on GitHub (May 3, 2017): I don't think it makes sense to enable custom fields on inventory items. The model's role is still a bit ambiguous but it's intended to represent hardware components gleaned through some form of automated inventory. Additionally, due to the hierarchical arrangements of inventory items, including custom fields would introduce a substantial performance penalty. You've also opened #1121 for the addition of some built-in fields for the InventoryItem model, which I think is preferable to enabling custom fields. I'm going to close out this ticket in favor of #1121; we can revisit the idea in the future if the agreed-upon built-in fields don't suffice.
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
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#900
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?