Open lrongyi opened 1 week ago
We believe that the severity should be set to Low since it is unlikely for 2 people to have the same exact name.
As for the rejection:
The actual behaviour is supposed to be the expected behaviour. In this case, "Adding patients of the same name, but with different casing is allowed" ONLY IF there is a change in the number or email, according to the duplicate person logic, as mentioned in the User Guide.
Hence, in order to delete Alex yeoh, there needs to be a different attribute (phone or email) that can differentiate Alex yeoh from Alex Yeoh
This is proven in the video below.
Team chose [response.Rejected
]
Reason for disagreement: This bug was more of to highlight the misleading command result output. The user guide also does not highlight whether the names should be case sensitive or not, hence confusing the user.
Description
Adding patients of the same name, but with different casing is allowed (Case sensitve). i.e. Alex Yeoh and Alex yeoh are different people.
However, deleting patients is not case sensitive. i.e.
delete n/Alex yeoh
will not delete Alex yeoh, but will throw an error.Steps to Reproduce
(Assuming sample data is there)
delete n/Alex yeoh
Expected Behavior
Alex yeoh should be deleted, Alex Yeoh should be unaffected
Actual Behavior
Error message:
Multiple patients with the same details found. Use more attributes (name, phone number, email) to identify the exact person.