Skip to content

Inventory Item Bulk Add requires field "status" #19279

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
severgun opened this issue Apr 23, 2025 · 0 comments · Fixed by #19283
Closed

Inventory Item Bulk Add requires field "status" #19279

severgun opened this issue Apr 23, 2025 · 0 comments · Fixed by #19283
Assignees
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Milestone

Comments

@severgun
Copy link

Deployment Type

Self-hosted

NetBox Version

v4.2.8

Python Version

3.12

Steps to Reproduce

  1. select multiple devices
  2. press add inventory item
  3. fill required field "name"
  4. apply
  5. fail because "status" field is mandatory and missing.

Expected Behavior

Inventory items should be added with Active status by default or editable field should be available at UI form

Observed Behavior

<class 'ValueError'>
'InventoryItemBulkCreateForm' has no field named 'status'.

@severgun severgun added status: needs triage This issue is awaiting triage by a maintainer type: bug A confirmed report of unexpected behavior in the application labels Apr 23, 2025
@jeremystretch jeremystretch self-assigned this Apr 23, 2025
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: low Does not significantly disrupt application functionality, or a workaround is available and removed status: needs triage This issue is awaiting triage by a maintainer labels Apr 23, 2025
@jeremystretch jeremystretch added this to the v4.2.9 milestone Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity: low Does not significantly disrupt application functionality, or a workaround is available status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants