nus-pe-bot
commented
3 years ago Team's Response
Dear tester, this is an expected behaviour of our application. If a user do not remember the full name of a property, they can use other fields to search for it. If we allow matching with any names containing the keyword as a substring, it might lead to large numbers of false positives, making it annoying to use for the users.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Yes I know that it is an expected behaviour of our application, I am not trying to say that there is a functionality bug.
I am arguing that it is a feature flaw because a user is unable to find a property, given part of the property’s name, and this makes the find property command less useful to the user for normal usage.
If you allowed matching with any names containing the keyword as a substring, I disagree that it will lead to large numbers of false positives as it depends on the search string used by the user.
If the user uses "b" as a search string, of course there will be many false positives. However, the agent might only be remembering that the property name starts with "b", given his long list of properties to manage.
If the user uses "bishan" as a search string, there will be much less false positive, and the agent can gradually enhance his search to find the property he needs, instead of having to remember the whole name to search by name (which is the current implementation) that is more cumbersome.
A user might have forgotten the exact name of his/her property and would like to find it, given part of the property's name. However, the search feature can only find the property if it matches the name exactly. This can be considered a feature flaw of low severity as it makes the find property less useful to the user for normal usage