find address uses subset instead of direct match

[NeoHW]

find a/b, want to find people with address b but list all address with b inside

[soc-pe-bot]

Team's Response

The intended function of our find feature is to return ALL clients that contain the keyword at the start of a word in that parameter. This is to allow searching for words even if you don't remember the entire word.

However, what we do agree with is that direct matches should be listed before partial matches in order to cater to the problem described as above, we mark this as not in scope as sorting the find results would be a good feature to implement in future iterations but wasn't deemed important enough to ship in the current iteration.

We also recommend changing the severity from Medium to Low, as this is a minor inconvenience. The feature still works as intended, the only inconvenience is potentially having to scroll a bit to find the direct match client.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement:

• None of the condition are fulfilled for it to be a NotInScope.
• There was no mention that the support for this would be upcoming in later versions

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:**  According to the team's value proposition: it is to help social workers with **high caseloads**. In this case, if all 10,000 patients were to start their address with b (BLK..), there would be no increased efficiency or boosted productivity. It might instead serve the opposite purpose.  Why medium: Since it is built for social workers with high workloads, it does not only appear in very rare situations but would cause occasional inconvenience as they now have to scroll through thousands before they can reach their desired search results.

---