Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[PE-D][Tester B] Allow repeated entries of the same name. #202

Closed
nus-pe-script opened this issue Apr 5, 2024 · 2 comments · Fixed by #159
Closed

[PE-D][Tester B] Allow repeated entries of the same name. #202

nus-pe-script opened this issue Apr 5, 2024 · 2 comments · Fixed by #159
Assignees
@yisiox
Labels
bug.NotAllowedToFix response.NotInScope It is a valid issue but not something the team should be penalized for severity.Low A flaw that is unlikely to affect normal operations of the product type.FeatureFlaw Some functionality missing from a feature delivered in v1.4 in a way that the feature becomes less u type.PlannedEnhancements Features that are planned for future development
Milestone
v1.4

Comments

@nus-pe-script
Copy link

UG states that Multiple people with the same name are not allowed.
However, the application allows John Doe to be entered despite John Doe already existing.
Obviously this is an extreme case but it is very possible for users to have accidentally double spaced when entering the name.
This error can also be encountered in edit.

image.png

Labels: severity.High type.FunctionalityBug
original: Austintjh19/ped#6
@aureliony
Copy link

Definitely not a high severity bug.

@aureliony aureliony added type.Bug A bug severity.Low A flaw that is unlikely to affect normal operations of the product labels Apr 5, 2024
@aureliony
Copy link

Consider adding "allow adding multiple people with the same name" to planned enhancements.

@aureliony aureliony mentioned this issue Apr 5, 2024
Closed
@aureliony aureliony added this to the v1.4 milestone Apr 6, 2024
@aureliony aureliony added bug.GoodToFix A bug that is good to fix, but it's fine to not fix type.FeatureFlaw Some functionality missing from a feature delivered in v1.4 in a way that the feature becomes less u response.NotInScope It is a valid issue but not something the team should be penalized for and removed type.Bug A bug labels Apr 8, 2024
@bryanyee33 bryanyee33 mentioned this issue Apr 10, 2024
Closed
@aureliony aureliony added bug.NotAllowedToFix and removed bug.GoodToFix A bug that is good to fix, but it's fine to not fix labels Apr 12, 2024
@bryanyee33 bryanyee33 added the type.PlannedEnhancements Features that are planned for future development label Apr 13, 2024
@yisiox yisiox self-assigned this Apr 15, 2024
@yisiox yisiox mentioned this issue Apr 15, 2024
Merged
@aureliony aureliony linked a pull request Apr 15, 2024 that will close this issue
Update DG for v1.4 release #159
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yisiox yisiox

Labels
bug.NotAllowedToFix response.NotInScope It is a valid issue but not something the team should be penalized for severity.Low A flaw that is unlikely to affect normal operations of the product type.FeatureFlaw Some functionality missing from a feature delivered in v1.4 in a way that the feature becomes less u type.PlannedEnhancements Features that are planned for future development
Projects
None yet
Milestone
v1.4
Development

Successfully merging a pull request may close this issue.

Update DG for v1.4 release AY2324S2-CS2103T-W12-3/tp
4 participants
@aureliony @nus-pe-script @bryanyee33 @yisiox