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.

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

Power port bulk edit: missing "set null" on maximum power draw / allocated power draw #13092

Closed
candlerb opened this issue Jul 5, 2023 · 0 comments · Fixed by #13098
Closed
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

Comments

@candlerb
Copy link
Contributor

candlerb commented Jul 5, 2023

NetBox version

v3.5.4

Python version

3.8

Steps to Reproduce

  1. Go to a device which has power ports
  2. Click on the power ports tab
  3. Click the checkboxes besides one or more (or all) ports
  4. Use the bulk "Edit" facility, e.g. e.g. /dcim/power-ports/edit/?device=5&return_url=/dcim/devices/5/power-ports/
  5. Try to set the Allocated Draw or Maximum Draw to null for all those ports

Expected Behavior

Be able to click "Set null" to unset the value

Observed Behavior

The "Set null" checkbox is missing. (And setting zero is not allowed).

WORKAROUND: edit each port individually, blank out the power draw fields individually, and save each one.

@candlerb candlerb added the type: bug A confirmed report of unexpected behavior in the application label Jul 5, 2023
@DanSheps DanSheps 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 Jul 5, 2023
@arthanson arthanson self-assigned this Jul 6, 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 Jul 6, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 5, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
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.

4 participants