nus-pe-bot
commented
22 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
Thank you for bringing this up. We accept this as a valid issue, as the app currently allows adding two individuals with similar names that differ only in letter casing (e.g., "John Doe" and "John doe"). However, we have classified this as a low-severity issue, as it does not hinder any core functionality or prevent users from performing operations as intended.
In real-world scenarios, having two individuals with such similar names is exceedingly rare. Additionally, restaurants, our primary users use consistent casing when entering names into the system, as operational efficiency relies on clear and accurate data entry. This greatly reduces the likelihood of this issue arising during normal usage.
At most, this could cause minor inconvenience, and it can be easily resolved by users ensuring consistent casing during data entry. While we acknowledge this as a feature flaw, its impact on the app’s overall functionality and usability is minimal, and it does not interfere with the core tasks the app is designed to handle.
We appreciate your feedback and will consider this for future iterations to further enhance the user experience. Thank you for helping us improve!
Items for the Tester to Verify
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your reason]
When adding names into NomNomNotifier, I was allowed to add two different people with similar names using the inputs,
add n/John Doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01 pc/666234
followed by
add n/John doe p/98765432 e/johnd@example.com a/John street, block 123, #01-01 pc/666234
This resulted in there being 2 different persons in NomNomNotifier, John Doe, and John doe, which doesn't follow the real life logic where peoples name in real life aren't case sensitive
According to the CS2103T website, under feature flaws, this is considered as one, hence the categorisation of it