nus-se-script
commented
3 hours ago [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
Our focus for this iteration is on ensuring that users can effectively edit and manage guests and vendors, with priority given to changes that alter the stored data meaningfully.
While the system does not notify the user when an attempted edit results in no changes, this scenario is uncommon and occurs only in rare cases where the input matches the existing value. It does not impact the core functionality of the application, as no erroneous data is introduced or saved. As such, the current implementation of edit does not affect the edit functionality, nor does it introduce any bugs.
Nevertheless, this can be a useful future enhancement that can be implemented in future iterations to improve the user experience.
Items for the Tester to Verify
:question: Issue response
Team chose [response.NotInScope]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
For example, when there is a guest called John, and the user tries to edit this guest's name to John again, the system does not let the user know that they have entered the exact same name.
This might cause slight inconvenience to user. they might have wanted to change another guest/vendor's name instead. there is no error message to indicate that the user has in fact not changed anything in the data and overlook it.
This is a flaw that is uncommon and appears in rare situations, hence tagged as severity low.