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

Element search bug in custom fields. #13859

Closed
penM000 opened this issue Sep 22, 2023 · 1 comment · Fixed by #13884
Closed

Element search bug in custom fields. #13859

penM000 opened this issue Sep 22, 2023 · 1 comment · Fixed by #13884
Assignees
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows status: accepted This issue has been accepted for implementation type: bug A confirmed report of unexpected behavior in the application

Comments

@penM000
Copy link

penM000 commented Sep 22, 2023

NetBox version

v3.6.2

Python version

3.10

Steps to Reproduce

  1. Create a selection list for a custom field.
  2. Create a custom field that can specify multiple selection lists.
  3. Go to the object to which the custom field is tied.
  4. Perform an edit and select the elements in the custom field.
  5. With the element selected, type in the search field something that does not exist in the selection list.
  6. An error message is displayed and what you have selected so far will disappear.

image
image
image
image
image
image

PS
This is not related to the bug, but when selecting elements, is there any way to select all of them, like "ALL"? I am currently clicking on elements one at a time and was wondering if there is such a feature.

Expected Behavior

NO Result" should appear and whatever you have selected so far should remain.

Observed Behavior

All selections made so far have disappeared.
I can also confirm that I am seeing errors.

@penM000 penM000 added the type: bug A confirmed report of unexpected behavior in the application label Sep 22, 2023
@jeremystretch jeremystretch self-assigned this Sep 25, 2023
@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation severity: medium Results in substantial degraded or broken functionality for specfic workflows labels Sep 25, 2023
@jeremystretch
Copy link
Member

This can be triggered by making a REST API request which includes a search filter which does not match any of the available choices, e.g.

GET /api/extras/custom-field-choice-sets/1/choices/?q=foo

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
severity: medium Results in substantial degraded or broken functionality for specfic workflows 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