soc-pe-bot
commented
1 year ago Team's Response
Clearly stated in the UG that only complete strings will be matched. Therefore this is not in scope.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: The tester believes that this is still in scope as the tester is debating the choice in implementing find this way. Furthermore, it has been marked as a feature flaw as well and this feature was implemented within V1.4 so the tester does not see why the bug is out of scope. The effort needed to solve this bug is minimal as the namescontainkeywordpredicate class is the only thing that needs to be changed. This is also an inconvenience to the user as they need to remember and input long names. This is why it is a bug and the tester respectfully disagrees with the dev team.
Description: Usually when finding for a property you may not be sure of it's full name and this means that when an incorrect spelling or partial name is entered there are no results displayed
Steps to reproduce:
Image of bug:
Reason for bug level: In most cases the property manager will not remember the property name this will lead to multiple searches on the users part and frustrations. Furthermore by partial word matching in find you provide more search results thus increasing the possibility of the expected search appearing. This is even more problematic for long names such as pinnacle@duxton. Thus the level low.