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

Improve inventory-items' description field #2846

New Issue
Closed
opened 2025-12-29 18:22:44 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:22:44 +01:00
Owner
Copy Link

Originally created by @juan-vg on GitHub (Sep 2, 2019).

Environment

  • Python version: 3.5.3
  • NetBox version: 2.6.2

Proposed Functionality

  • Allow multi-line (line breaks)
  • Allow more than 100 chars

Use Case

A perfect use case is a RAM (memory) module. Apart from the already present fields I would like to store some details about the module itself such as capacity, speed, class, etc..

Be able to store something like this json example would be awesome

{
   "size": "8 GiB",
   "type": "DIMM DDR3 Synchronous Registered (Buffered)",
   "ecc": true,
   "speed": "1333 MHz",
   "latency": "0.8 ns",
   "width": 64
}

Database Changes

Extend the size of the inventory-items' description field

External Dependencies

None

Originally created by @juan-vg on GitHub (Sep 2, 2019). ### Environment * Python version: 3.5.3 * NetBox version: 2.6.2 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality * Allow multi-line (line breaks) * Allow more than 100 chars ### Use Case A perfect use case is a RAM (memory) module. Apart from the already present fields I would like to store some details about the module itself such as capacity, speed, class, etc.. Be able to store something like this json example would be awesome ```json { "size": "8 GiB", "type": "DIMM DDR3 Synchronous Registered (Buffered)", "ecc": true, "speed": "1333 MHz", "latency": "0.8 ns", "width": 64 } ``` ### Database Changes Extend the size of the inventory-items' description field ### External Dependencies None
adam closed this issue 2025-12-29 18:22:44 +01:00
adam commented 2025-12-29 18:22:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 3, 2019):

I would like to store some details about the module itself such as capacity, speed, class, etc..

It sounds like you're trying to squeeze inventory management functions out of an application that isn't designed for it. This is one reason some of the fields intentionally restrict length: to dissuade users from trying to store data which extends beyond the model.

@jeremystretch commented on GitHub (Sep 3, 2019): > I would like to store some details about the module itself such as capacity, speed, class, etc.. It sounds like you're trying to squeeze inventory management functions out of an application that isn't designed for it. This is one reason some of the fields intentionally restrict length: to dissuade users from trying to store data which extends beyond the model.
adam commented 2025-12-29 18:22:45 +01:00
Author
Owner
Copy Link

@bcohee commented on GitHub (Sep 3, 2019):

Hmmm - then why track inventory-items at all in Netbox if there is not a future path to properly manage them?

Netbox has DCIM, and proper DCIM is infrastructure / inventory management.

I don’t agree this should be immediately closed instead of backlogged for a future future version.

@bcohee commented on GitHub (Sep 3, 2019): Hmmm - then why track inventory-items at all in Netbox if there is not a future path to properly manage them? Netbox has DCIM, and proper DCIM is infrastructure / inventory management. I don’t agree this should be immediately closed instead of backlogged for a future future version.
adam commented 2025-12-29 18:22:45 +01:00
Author
Owner
Copy Link

@juan-vg commented on GitHub (Sep 4, 2019):

@jeremystretch The description of this project is: "IP address management (IPAM) and data center infrastructure management (DCIM) tool.". It's clear, IPAM & DCIM. DCIM stands for DataCenter Infrastructure Management, which means all the stuff you have there and not only devices. So my question is.. Why the model is limiting people to store useful data instead of encouraging it?

@juan-vg commented on GitHub (Sep 4, 2019): @jeremystretch The description of this project is: "IP address management (IPAM) and data center infrastructure management (DCIM) tool.". It's clear, IPAM & DCIM. DCIM stands for DataCenter Infrastructure Management, which means all the stuff you have there and not only devices. So my question is.. **Why the model is limiting people to store useful data instead of encouraging it?**
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#2846
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?