Open Originalidk opened 11 months ago
Thanks for the bug report. This is working as intended, as there are individuals with non-capitalized names, such as Michael van Gerwen. At the same time, another individual named Michael Van Gerwen could exist too!
By enforcing case sensitivity, we prevent individuals with different capitalizations from existing in our ManageHR system, which could be detrimental for organizations with individuals who have these names.
Team chose [response.Rejected
]
Reason for disagreement: Thank you for explaining your team's rationale behind this. Upon further review, I would like to change my stance on the type of bug this is. It should not be a functionality bug but instead considered a feature bug.
However, I disagree with the response. I would like to refer you back to CS2103T's website on this matter.
As shown in the image above, the example mentioned was how users like "John Doe
and john doe
are likely to be the same person". For such cases, the website suggests that the application should "give a warning in such near match cases so that the user can make the final decision". Your team's application, however, fails to do so.
The website also mentions that "If you app has a duplicate detection feature, make sure its limitations are made clear to the user". As this limitation was not made clear anywhere in your product, UG or DG, the website would consider this to be a feature flaw.
Even thought David Li already exists in the application, adding a david li is allowed despite them being the same name.