Open jeffrey-jian opened 12 months ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Names are not case-insensitive
I am able to add John Doe, john Doe and other variations with different capitalisations, as they are regarded as separate entities with different names. However, it would be more user friendly if such fields are case-insensitive, as there may be a rare occasion whereby the user accidentally adds someone who was already in the system, but with different "casing" .
[original: nus-cs2103-AY2324S1/pe-interim#4338] [original labels: severity.Low type.FunctionalityBug]
[This is the team's response to the above 'original' bug]
No details provided by team.
Items for the Tester to Verify
:question: Issue duplicate status
Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)
Reason for disagreement: The 2 issues raised are separate issues, dealing with "space-insensitivity" and "case-insensitivity".
I am able to add
John Doe
andJohn Doe
, as they are regarded as 2 separate entities with different names. However, it would be more user friendly if such fields are space-insensitive, as there may be a rare occasion whereby the user accidentally adds someone who was already in the system, but inputted additional spacing.From the naked eye, it might also be difficult to tell that the 2nd John Doe in the screenshot actually has 2 spacings between the first and last name. This may lead to confusion for the user as it is hard to figure out why there are duplicate entries.