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

Add Status field to inventory items #9930

New Issue
Closed
opened 2025-12-29 21:24:34 +01:00 by adam · 4 comments
adam commented 2025-12-29 21:24:34 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (Jul 2, 2024).

Originally assigned to: @arthanson on GitHub.

NetBox version

v4.0.6

Feature type

Data model extension

Proposed functionality

add a "status" field to the inventory item model

Use case

being able to document the state of inventory items would be useful.
example states:

  • active
  • failed
  • missing/removed (to document that an inventory item wasn't seen during last audit/check)

it would be great if this choices list could be extended like some of the status fields can be

Database changes

add a status field to the inventory item model

External dependencies

n/a

Originally created by @ITJamie on GitHub (Jul 2, 2024). Originally assigned to: @arthanson on GitHub. ### NetBox version v4.0.6 ### Feature type Data model extension ### Proposed functionality add a "status" field to the inventory item model ### Use case being able to document the state of inventory items would be useful. example states: - active - failed - missing/removed (to document that an inventory item wasn't seen during last audit/check) it would be great if this choices list could be extended like some of the status fields can be ### Database changes add a status field to the inventory item model ### External dependencies n/a
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:24:34 +01:00
adam closed this issue 2025-12-29 21:24:34 +01:00
adam commented 2025-12-29 21:24:34 +01:00
Author
Owner
Copy Link

@sleepinggenius2 commented on GitHub (Jul 2, 2024):

I think it would make sense for the default choices to match the ones for module status, but should allow for extension as well.

@sleepinggenius2 commented on GitHub (Jul 2, 2024): I think it would make sense for the default choices to match the ones for module status, but should allow for extension as well.
adam commented 2025-12-29 21:24:35 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Jul 9, 2024):

Couldnt the Custom Fields be leveraged for that?

@AnythingOverIP commented on GitHub (Jul 9, 2024): Couldnt the Custom Fields be leveraged for that?
adam commented 2025-12-29 21:24:35 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 16, 2024):

Module status fields are:

    STATUS_OFFLINE = 'offline'
    STATUS_ACTIVE = 'active'
    STATUS_PLANNED = 'planned'
    STATUS_STAGED = 'staged'
    STATUS_FAILED = 'failed'
    STATUS_DECOMMISSIONING = 'decommissioning'
@arthanson commented on GitHub (Jul 16, 2024): Module status fields are: ``` STATUS_OFFLINE = 'offline' STATUS_ACTIVE = 'active' STATUS_PLANNED = 'planned' STATUS_STAGED = 'staged' STATUS_FAILED = 'failed' STATUS_DECOMMISSIONING = 'decommissioning' ```
adam commented 2025-12-29 21:24:35 +01:00
Author
Owner
Copy Link

@ITJamie commented on GitHub (Jul 29, 2024):

Im happy to make a PR for this

@ITJamie commented on GitHub (Jul 29, 2024): Im happy to make a PR for this
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 complexity: low status: accepted type: feature
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#9930
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?