User Guide does not state the constraints for inputs

[axmszr]

I feel that users should not be made to figure out input constraints by themselves, or only after getting errors. The User Guide should contain useful information about what inputs are allowed (e.g. name, email, address).

Additionally, when the User Guide does provide a constraint, it is not followed in the app (e.g. date, comments).

[nus-se-bot]

Team's Response

Thanks for pointing out, will revise the UG again to match the actual behavior of constraints.

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

• [x] I disagree

Reason for disagreement: Apologies, I disagree that this should be downgraded to Low severity.

According to the CS2103 website,

The inconvenience caused by a lack of input constraints is neither rare (since it is present for almost every data field) nor minor (since the user is forced to learn from trial-and-error instead of from the User Guide). It is even more egregious when the provided input constraints are incorrect, as is the case for dates and comments. The product is still usable, but this poses a decent barrier to entry for new users.

---