finding keywords may not be efficient

[dnardnar]

Expected: finding a person with surname ang should be fast
Actual: a lot of addresses have ang and the person surname is not easily found
Suggestion/ Why it is problematic: possible to find keywords by the field instead
Steps to reproduce:
add a lot of people with addresses that has ang in it, serangoon, ang mo kio...
find ang
Screenshot:

[nus-pe-script]

[IMPORTANT!: Please do not edit or reply to this comment using the GitHub UI. You can respond to it using CATcher during the next phase of the PE]

Team's Response

As they are both duplicates that talk about this intended feature to include our broad search results, please refer to the results in #1110 for our thought process as this is an intended behaviour.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Find command format

Find command should take in some parameters, so that it can better find people. if I'm finding for people with specific characters in their name, and it returns me people who also have those characters in their address, it is more difficult to find the person I am looking for.

Might even have to use scrollbar if all i can remember is that the name contains "lak", and there are 8 people living in lakeside. Then it does not suit people who use only keyboard anymore

---

_{[original: nus-cs2103-AY2425S2/pe-interim#993] [original labels: type.FeatureFlaw severity.High]}

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

This current design intentionally provides a broader search result set, ensuring that users do not inadvertently miss records by restricting the search to a single field. While we understand that having too many results can be inconvenient, the current behavior is aligned with our User Guide and overall design philosophy to encourage more specific searches for better precision.

As stated in the user guide,

We appreciate your suggestion for modifying our filtering capabilities and will keep it in mind for possible future improvements. For now, for our users to achieve focused results, we aim for them to refine their search keywords to simplify the process and not complicate them through using extraneous parameters.

Hence we reject this.

Items for the Tester to Verify

❓ Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

• I disagree

Reason for disagreement: the duplicate issue use lak which is clearly not specific, however I believe that the surname ang is very specific which matches the description in your tip.

---

❓ Issue response

Team chose [response.Rejected]

• I disagree

Reason for disagreement: the duplicate issue use lak which is clearly not specific, however I believe that the surname ang is very specific which matches the description in your tip.

---

❓ Issue type

Team chose [type.FeatureFlaw]
Originally [type.FunctionalityBug]

• I disagree

Reason for disagreement: [replace this with your explanation]

---

❓ Issue severity

Team chose [severity.Low]
Originally [severity.VeryLow]

• I disagree

Reason for disagreement: [replace this with your explanation]

---