Past year can be added

[wowsiddanth]

Steps to reproduce:

1. Add task with year 1930

Low severity because it does not affect functionality, but might cause some minor inconvenience, especially in the case of typos.

Expected:

2. Some sort of checking for validity of year, and maybe a warning or complete rejection.

Actual: Accepted by system.

Screenshots:

[soc-se-bot]

Team's Response

We accept previous dates, for situations such as record keeping, etc. We do not want to validate inputs overzealously for no reason.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Thank you for your response.

Referring to the screenshot attached below, the purpose of the application is to tailor to the "needs of university students, who must keep track of a slew of different deadlines, commitments, and contacts". As such, it is only proper to assume that the date of the tasks added would be within a reasonable timeframe of a university student (not like the 1930 shown here).

This is also why I listed this as a FeatureFlaw instead, as this is an issue with the feature itself which does not provide an sort of proper checking. For example, if the user decides to type the date as 2021, but misspells it as 1021, it is still accepted! I wouldn't consider this to be overzealous checking as these dates are just too unrealistic.

However, I do agree that this issue is not as severe and so I attached a severity.Low tag to it.

That being said, this issue cannot be completely ignored.

---