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
Describe the bug
When searching for an email address, only exact matches should be returned. Since those searches may be done using a person's "alias email" there would be no clues if someone else's record is returned.
Expected behavior
When I enter a full email address, my expectation is that only exact matches will be returned. (I do appreciate the fuzzy matches for non-email fields.)
Screenshots none available without privacy issues The actual case involved a transposition of 2 characters in the name -- the one I wanted no longer existed, the non-match that was returned was "very close" w.r.t. all the other fields. I.e. a high likelihood of confusion.
The text was updated successfully, but these errors were encountered:
Describe the bug
When searching for an email address, only exact matches should be returned. Since those searches may be done using a person's "alias email" there would be no clues if someone else's record is returned.
To Reproduce
Steps to reproduce the behavior:
[email protected]
, start search[email protected]
returned. Not the same!Expected behavior
When I enter a full email address, my expectation is that only exact matches will be returned. (I do appreciate the fuzzy matches for non-email fields.)
Screenshots
none available without privacy issues The actual case involved a transposition of 2 characters in the name -- the one I wanted no longer existed, the non-match that was returned was "very close" w.r.t. all the other fields. I.e. a high likelihood of confusion.
The text was updated successfully, but these errors were encountered: