search

Joseph31416 / pe

0 stars 0 forks source link

Inconsistency in user guide #19

Open Joseph31416 opened 7 months ago

Joseph31416 commented 7 months ago

The guide clearly states whether the MEMBER_EMAIL field has to be unique but it does not specify whether the PHONE field has to be unique. This could confuse readers as there is no indication of the expected behaviour in terms of uniqueness.

bug 19.png

nus-se-bot commented 6 months ago

Team's Response

Thank you for this! Phone number does not indeed have to be unique! However, we feel that this is not really warranted as a bug as users will not run into errors if they don't know that a certain field needs to be unique (The lack of a constraint) compared to when a field must be unique (Presence of a constraint).

If you are talking about how our user guide is inconsistent, we think we can have it but it is not necessary

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your explanation]