Bug 6 - Find results return does not order by closest to search fill

[Karen-Lam]

Expected: As a user, if i find n/a, and there is a contact with name a, I expect to see it pop up first, because that is what im searching for.

Actual: Since most names contain "a", and the contact for name "a" was added very much later, "a" appears last in list.

[soc-pe-bot]

Team's Response

Sorting by relevance was not a feature mentioned in the UG, however it can be considered as an improvement for the app in a future release, and hence a response of NotInScope was given.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: I disagree that this reported bug is not in scope. While sorting by relevance is not a feature mentioned in the user guide, as a user using the find function, I would expected that find n/a returns me results of the person named "a" first. However, I have to end up scrolling through many farfetched search results like "Charlotte" or "David" to confirm that there is someone named "a" in my contact's list.

---