Open SelwynAng opened 9 months ago
Considering that the UG has highlighted how duplicate applicants are defined:
We feel that the user would be able to find which duplicate applicant is clashing with the new applicant being added.
However, we acknowledge that a more specific error message that specifies the cause of duplication would be more helpful. This is a suboptimal design of the feature, and we argue that it is not in scope, as rectifying it is less important than the work already done. Since we already have graceful error messages in place, and the software does not crash, this bug is not in scope.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
When adding another person with a duplicate email address into the application, the error message shown is unspecific and only states that "This applicant already exists in the applicant book". I personally think that the error message shown to the user should be more specific, as the users will then know exactly why they cannot add the person into the application. The original error message shown does not highlight the fact that there was a duplicate email address.
Steps to reproduce:
add n/John Doe hp/1234567 e/example@gmail.com p/Software Engineer/tester
add n/Jane Doe hp/7654321 e/example@gmail.com p/Cyber Specialist