Open jianrong7 opened 11 months ago
No details provided by team.
[The team marked this bug as a duplicate of the following bug]
Unreasonable constraints on the name
I am unable to add a perfectly valid name to the address field and might have to use a placeholder while having to remember in my head the missing special characters.
This affects almost all doctors as there is a reasonable population size with special characters in their name who are unaccounted for.
[original: nus-cs2103-AY2324S1/pe-interim#3410] [original labels: type.FunctionalityBug severity.Medium]
[This is the team's response to the above 'original' bug]
Firstly, we don't have an "address field".
Secondly, it has been stated clearly in the UG that names accept:
So for the tester to classify this as a "Functionality Bug" is inaccurate.
Tester can refer to course website (below) for the exactly definition and example of a "Functionality Bug"
If tester is suggesting we accept non-alphanumeric character, then classify it as a "Feature Flaw" instead.
As for severity, as mentioned by user there is work around for it like using placeholder or simply omitting special character, thus we will accept this feature flaw as low severity.
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: [replace this with your explanation]
Names should allow
/
as there are valid names with/
such as "... S/O ...".