nus-se-script
commented
2 years ago Team's Response
Dear Tester,
Thank you for your report. However, we don't quite understand the issue here. When a user edits their contact to have the exact same field input as before, there are no duplicate contacts created and the edited contact will remain the same as before. A contact will only be counted as a duplicate if their names, their emails, and their person category are the same. This is stated under the FAQ section in our user guide (please see the following screenshot below).
The following screenshot demonstrate that when the user is trying to edit a person's contact to have the same name and same email as someone else in the address book, there will be an error message thrown to show that this person already exists in the address book.
Thank you!
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: The name of the buyer is allowed to be edited to the same name as before as described. We should give a warning/prevent that as much as possible. Although no new duplicate contact is created, the fact that I can edit a contact to exactly the same field value as it was initially was should be disallowed/warned (because the user should not be doing this in real-life usage if he/she is using the edit command)
Here is a clearer description of my issue: Suppose I have Hongyi as a name in index 2, I can edit index 2 and rename it to Hongyi again. A warning should be given or this should not be allowed at all.
After running the command, it is a success with no warnings etc.
For example, I am allowed to edit the name
HongyitoHongyiagain. This is quite improbable in real life usage. No warnings was given when this happens.A warning/error would be helpful to the user to let them know they are keying in a duplicate