pangrwa / pe

0 stars 0 forks source link

Adding a new event in the past (Add) #5

Open pangrwa opened 1 year ago

pangrwa commented 1 year ago

Screenshot 2023-04-14 at 2.28.11 PM.png

Steps to replicate: add n/Tennis d/2023-02-28 s/17:00 e/17:00

Expected output: As shown in the picture

Reasoning: Doesn't fit well with managing and scheduling events. A user wouldn't want to schedule an event in the past, this might confuse the user. An error should come out instead.

nus-se-script commented 1 year ago

Team's Response

There should be no restriction that a user cannot manage events that have occurred in the past.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: [replace this with your reason] While I agree that there should be no restriction that a user can add events in the past. The bug that I have reported is a feature flaw, and looking at the intended goal of the application (to optimise and manage scheduling of upcoming events (future events)), there isn't a need to manage events in the past. Intuitively, it doesn't make sense for a person to add an event in the past since technically it's not suppose to happen.

Screenshot 2023-04-19 at 11.55.22 PM.png

Also, I feel that the severity of the bug after consideration should be severity.Medium as there is no warning to the user that he / she is adding an event in the past. Consider the situation where a person accidentally types a year off (eg: instead of 2023, he/she types 2022), this can severely impact the usage of the application as he/she will no longer remember that they have an upcoming event in the future, affecting them personally.