Able to add an invalid date

[LuYiting0913]

year 1000 is obviously not valid and should be handled properly. A legitimate user behavior is not handled

[soc-se-bot]

Team's Response

Problems caused by extreme user behaviors: If the problems can only happen in case of deliberate sabotage (e.g., user entered a 30-digit telephone number), in which case it should not be considered a bug. However, if such input can be entered by a user mistake, they should not cause harm e.g., such mistakes should not crash the app, corrupt the data, or make it unusable. Problems caused by integer overflows -- apply the guideline in the previous point.

We also believe that this behavior does not affect the user experience.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: there can be cases where the user input a wrong year (like 2002 or 2202 instead of 2022, not as extreme as a direct sabotage) but the application cannot catch such obvious mistakes. this can affect user experience because the user may not notice this himself and miss the deadline because of such small mistakes.

However, I feel feature flaw is more appropriate for this bug because of the lack of proper handling (either blocking or warning) for potentially invalid inputs.

And "the feature is implemented to work in a certain way but it could have been implemented to work in a better way (from the end-user's point of view) without much additional effort" (like display warnings when user inputs a seemingly wrong date)

---