nus-pe-bot
commented
1 year ago Team's Response
This would be a good to have, but this is not ambiguous. The message describes exactly what has happened. If the client wishes to know if the fields are duplicated, fuzzy search makes it easy for the them to find that particular client and examine their fields. Thus, it would not hinder common usage.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [x] I disagree
Reason for disagreement: Thank you for your response. Though the error message does indeed describe what exactly happened, it does not explain why so. The user may genuinely have wrongly entered the exact same details without realising, thus would be confused by the error message. You mentioned that the user could use fuzzy search to know if the fields are duplicated, but it incurs an additional step for the user, and they would have to scrutinise to compare with their input details, which actually hinders usage due to lowered convenience. If the error message directly tells the user that the fields are exactly the same, then it is much clearer to the user and it is more convenient for them to rectify it, saving them time from trying to figure out via alternative ways.
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
When I tried to edit a client's information and included the old details for some fields, the error message given was "Client not updated", which is quite unclear because it does not tell me why it is so. It should tell me that I have specified exactly the same details.