Names with `/` are not allowed

[Dethada]

Bug Description

Names have the following constraint given in the UG.

Should only contain alphanumeric characters and spaces, and it should not be blank.

This means users are unable to add a name with / which is not rare in Singapore, such as John Doe s/o Mathur.

Steps to Reproduce

• add cn/Google n/John Doe s/o Mathur p/98765432 e/johnd@example.com a/311, Clementi Ave 2, #02-25 tt/121220221400 i/Birthday: 12 May 2001 s/5000 pl/Java t/friends t/owesMoney pri/2

Expected Behavior

The command should succeed.

[nus-se-script]

Team's Response

Thank you for raising this issue. While we acknowledge that this may cause inconvenience to some users, addressing this particular issue is currently not within our scope due to existing project priorities and resource constraints. We have mentioned also mentioned it as a parameter constraint in the UG. UG:

Our team is currently focused on addressing critical bugs and implementing essential features to enhance user experience. However, we have noted your feedback and will consider it for future updates to allow more flexible names. Thank you for your understanding.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

• [x] I disagree

Reason for disagreement: I believe that allowing of special characters is a necessary function as this is an app targeted at computing professionals for professional usage that does not contraint the targeted user base to people that only knows people with names without special characters, which is good, it should not be restricted that way, hence the limitation should be resolved instead.

Knowing contacts' names is a basic form of respect. To keep professionality, which is important for a professional app targeted to professional users, it is all the more important to respect other people's names and hence be able to store their name as is. And as an applicant, users do not really get to request for a contact for you with no special characters in their name, so such situations cannot be actively avoided by users.

This would not be an uncommon problem as even from a more localised point of view, in Singapore, many people have commas, hyphens and slashes in their names, and not to mention in a global context how different can naming conventions and formats be. Personally, my groupmate also has a comma in their name.

Thus, I believe by intentionally implementing this field to be discriminatory is a huge oversight of the team.

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** As I have mentioned before: >This would not be an uncommon problem as even from a more localised point of view, in Singapore, many people have commas, hyphens and slashes in their names, and not to mention in a global context how different can naming conventions and formats be. Personally, my groupmate also has a comma in their name.

---