search

rynlwhh / pe

0 stars 0 forks source link

Specific Find command #6

Open rynlwhh opened 1 week ago

rynlwhh commented 1 week ago

When using specific find command, when i input find s/Test it gave me the clients with lower case t also, even though in the UG it states that it should find one-to-one, this could prove a problem to some users as some people may have the same name but just different capital letters and users may take the wrong info for their work purpose Suggestion: To make it so that the find s/ command actually is case sensitive

Screenshot 2024-11-15 at 4.47.17 PM.png Screenshot 2024-11-15 at 4.46.50 PM.png Screenshot 2024-11-15 at 4.46.59 PM.png

soc-pe-bot commented 3 days ago

Team's Response

Thank you for the bug report. However, we have concluded that this issue is Not In Scope.

Firstly, we have stated that all searches are case-insensitive in the 1st bullet point of your UG screenshot. This applies to the specific find command as well, as it is an extension of the find command and hence inherits all properties of the find command.

Additionally, we do not think that we should make the specific find case-sensitive only because realistically, the user would have trouble remembering exactly how he saved the contact in terms of capitalisation.

Hence, perhaps a feature improve in the future to allow the user to toggle between case-sensitive and case-insensitive specific finds might improve user experience. Hence, we have decided to classify this issue as Not In Scope.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: "Firstly, we have stated that all searches are case-insensitive in the 1st bullet point of your UG screenshot. This applies to the specific find command as well, as it is an extension of the find command and hence inherits all properties of the find command."

According to the Team's response, specific find command inherits all properties of the find command which should mean that specific find command should obey the following properties as per the UG: The search is case-insensitive. e.g hans will match Hans . By default, the find command conduct a general search for the individual. Hence, the order of the keywords does not matter. e.g. Hans Bo will match Bo Hans . A client’s name, phone number, address, email and tag can be searched. Only full words will be matched e.g. Han will not match Hans . clients matching at least one keyword will be returned (i.e. OR search). e.g. Hans Bo will return Hans Gruber , Bo Yang

However, the specific find command does not have all of the following properties, and I believe it is not the purpose of specific find. Thus, I do not agree with the NotInScope label as the argument that because it is stated in the first bullet point of the find command does not mean it applies to the specific find command. This makes it even more confusing to the user and can cause inconvenience when they use specific find command.