Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Unable to set height to 0 when selecting multiple devices #14620

Closed
raphis opened this issue Dec 28, 2023 · 0 comments
Closed

Unable to set height to 0 when selecting multiple devices #14620

raphis opened this issue Dec 28, 2023 · 0 comments
Assignees
@jeremystretch
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

Comments

@raphis
Copy link

raphis commented Dec 28, 2023

Deployment Type

Self-hosted

NetBox Version

3.6.7

Python Version

3.8

Steps to Reproduce

  1. Go to devices-type list
  2. Select multiple device types
  3. Click on "edit selected"
  4. Try to add "0" as value for the U height
  5. 0 isn't accepted as value

Expected Behavior

0 can be set as value for height when the device itself is modified so I expect the same behavior when editing multiple devices.

For non-rack devices I usually set the U height to 0.

Observed Behavior

Message when clicking on save: Value must be greater than or equal to 1
2023-12-28 08_53_44-Editing 2 Device Types _ NetBox
@raphis raphis added the type: bug A confirmed report of unexpected behavior in the application label Dec 28, 2023
@jeremystretch jeremystretch added status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation severity: low Does not significantly disrupt application functionality, or a workaround is available labels Dec 28, 2023
@jeremystretch jeremystretch self-assigned this Dec 28, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation and removed status: needs owner This issue is tentatively accepted pending a volunteer committed to its implementation labels Dec 28, 2023
@jeremystretch jeremystretch mentioned this issue Dec 28, 2023
Merged
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 28, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jeremystretch jeremystretch

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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@raphis @jeremystretch