ValenciaLim / pe

0 stars 0 forks source link

Name and Company characters does not allow names with / #2

Open ValenciaLim opened 5 months ago

ValenciaLim commented 5 months ago

Names with / such as John s/o Kumar is not allowed even though such names are common, especially for the indian community. Change prefix for salary to something less common.

image.png

nus-pe-script commented 5 months ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Names with / are not allowed

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.


[original: nus-cs2103-AY2324S2/pe-interim#274] [original labels: severity.Medium type.FeatureFlaw]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

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:

image.png

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 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]


## :question: Issue response Team chose [`response.NotInScope`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]
## :question: Issue type Team chose [`type.FeatureFlaw`] Originally [`type.FunctionalityBug`] - [x] I disagree **Reason for disagreement:** This is a functionality bug as a legitimate user bahaviour, in this case, allowing user to enter names with '/', is not handled.
## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]