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

Color of front and rear ports not nullable on bulk edit #11028

Closed
phurrelmann opened this issue Nov 25, 2022 · 0 comments · Fixed by #11054
Closed

Color of front and rear ports not nullable on bulk edit #11028

phurrelmann opened this issue Nov 25, 2022 · 0 comments · Fixed by #11054
Assignees
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@phurrelmann
Copy link
Contributor

NetBox version

V3.3.5

Python version

3.9

Steps to Reproduce

Colors defined on front and rearports are not nullable on bulk edit.

  1. Create more than 2 front or rear ports
  2. Select 2 or more front or rear ports and do a bulk edit
  3. Color can be changed but not cleared

I can prepare a PR, if accepted

Expected Behavior

Color field on bulk edit of front and rear ports should be nullable and the checkbox "Set Null" is visible

Observed Behavior

Color field on bulk edit of front and rear ports are not nullable. The check box "Set Null" is missing

@phurrelmann phurrelmann added the type: bug A confirmed report of unexpected behavior in the application label Nov 25, 2022
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Nov 28, 2022
phurrelmann pushed a commit to phurrelmann/netbox that referenced this issue Nov 30, 2022
jeremystretch pushed a commit that referenced this issue Nov 30, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application
Projects
None yet
2 participants