You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@Roger-Ethyca@mfbrown@Kelsey-Ethyca Currently, the search field will bring any results based on Request Id value and status filters selected. The API endpoint uses a LIKE clause statement. Thoughts on changing this current behavior?
I will defer to @mfbrown for the final decision. My two cents are that today it is unclear what is being searched and there are two ways to fix this..
If we want to leave the placeholder saying "Search" it should search all fields that do not already have a filter (days left, request type, subject identity, and reviewed by). This will require backend work and could cause performance issues if the DSR list is incredibly long.
If we want to search request id only, removing status because there is already a status filter, we should update the search placeholder to say search "Search Request ID". Maybe consider reordering the filters and search to match the order of the column headers. This will still require a small bit of backend work but less likely to cause any performance issues.
Bug Description
Search field on the privacy request page isn't searching for anything.
Steps to Reproduce
Expected behavior
The searched DSR or Erasure request should be displayed.
If applicable, add screenshots to help explain your problem.
Environment
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: