Open teoks0199 opened 10 months ago
Thank you for raising this issue. However, we would like to refer you to CS2103T's website where it talks about problems caused by extreme user behavior.
As shown in the above image, it mentions that "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". As the year 1000 constitutes a "case of deliberate sabotage", this is hence an invalid bug.
Warmest Regards,
Team F.A.K.E.J.A.R.V.I.S.
Team chose [response.Rejected
]
Reason for disagreement: The year "1000" is not deliberate sabotage. Even if I input a year "1023", it is allowed, and "1023" could just be a typo when I try to type "2023". Given that there is also no edit task feature, I would then have to delete the task and then add it in again, posing an inconvenience, thus I still think that this is a low-severity bug.
Using addtask tn/test d/31/03/1000 tp/high, I can add in a task with date in the year 1000, and the app should not allow this.