search

pangrwa / pe

0 stars 0 forks source link

Adding an event that starts and end at the same time (Add) #4

Open pangrwa opened 1 year ago

pangrwa commented 1 year ago

Screenshot 2023-04-14 at 2.24.50 PM.png

Steps to replicate: add n/Tennis d/2023-12-20 s/17:00 e/17:00

Actual output: Given in the screenshot

Reasoning Does not seem to fit well into the product in terms of scheduling events because it does not make sense for an event to start and end at the same time, in that case it shouldn't be recorded at all.

nus-se-bot commented 1 year ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Program specifies end time must be later than start time, but both may be equal

Upon attempting to add an event with start time later than end time, the program reports in the error message that the end time should be later than the start time. However, events with start time equal to the end time are accepted; the error message should instead specify that the end time should be no earlier than the start time.

[original: nus-cs2103-AY2223S2/pe-interim#1320] [original labels: severity.VeryLow type.DocumentationBug]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

No details provided by team.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your reason]

The other issue mentions that there is an error message given is wrong and hence it's a functionality bug which is different from mine.

## :question: Issue type Team chose [`type.DocumentationBug`] Originally [`type.FeatureFlaw`] - [x] I disagree **Reason for disagreement:** [replace this with your reason] This bug is related to how adding an event doesn't fit well with the product simply because an event can't start and end at the same time, it just simply means it is as good as not having an event.
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Low`] - [x] I disagree **Reason for disagreement:** [replace this with your reason] This bug can cause inconvenience to the user because it could flood the application with multiple tasks since the user can now add at least 60 events in 1 hour, that is every event starts and end at the same time. Having that much events did cause some lag in the usage of the application as tested before hand.