-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Chat search should prioritise a perfectly matching email above a partially matching one #8763
Comments
Triggered auto assignment to @laurenreidexpensify ( |
Current assignee @Julesssss is eligible for the Engineering assigner, not assigning anyone new. |
@Julesssss wanna apply the rest of the labels to get this on upwork? add |
Triggered auto assignment to @jliexpensify ( |
Out of interest Lauren, how come you unassigned yourself? Auto-assigner would have kept you on in that case right? Like it did for me |
Posted! Internal - https://www.upwork.com/ab/applicants/1519120845909348352/job-details |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
Current assignee @Julesssss is eligible for the Exported assigner, not assigning anyone new. |
I'm actually gonna grab this and work on it myself |
Nice, thanks Tim. I honestly wasn't sure if this was worth fixing. But it will inevitably catch users out so let's get it resolved. Feel free to tag me as a reviewer! |
Thanks @Julesssss! I'm having some issues reproducing the issue. I created three users:
When I search for "user1@" it selects the correct person: When I search for "newuser1@" it also selects the correct person: It appears to be working correctly, but maybe there is something specific about your setup that is causing the issue you're seeing. Do you think you could help me narrow down the exact case to reproduce this? |
Ah curious. I'll take another look at my env first thing tomorrow morning and get back to you. It's even more of an edge case than I originally thought :D |
Cancelling Upworks job. |
I tried again today and noticed that |
Aha! Maybe there is something there. I see we are setting |
Action Performed:
user7@expensify.com
&user2@expensify.com
Expected Result:
Actual Result:
Workaround:
NewDot-SearchShouldPrioritiseFullMatches.mov
Platform:
Version Number: v1.1.56-0
Reproducible in staging?: Yep
Reproducible in production?: Yep
Email or phone of affected tester (no customers): N/A
Logs: https://stackoverflow.com/c/expensify/questions/4856 N/A
Notes/Photos/Videos: See above
Expensify/Expensify Issue URL: N/A
Issue reported by: @Julesssss
Slack conversation: N/A
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: