add_schedule did not check for start and end date time

[yiwern5]

Output for: add_schedule title/TITLE d/DESCRIPTION end/2024-04-13 21:00 start/2024-04-13 22:00:

It might be better to check the end time is later than start time for better user experience by handling error in user input :)

[soc-se-bot]

Team's Response

No details provided by team.

The 'Original' Bug

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

Event Start Time can be after End Time

Currently, can event can be scheduled such that its start time is after its end time. There is no validation of the input start and end times of an event.

Steps to reproduce:

1. Input the command add_schedule title/Meeting d/CS2103T start/2024-04-14 21:00 end/2024-04-13 22:00

Expected result: The event should not be schedulable.

Actual Result: Such an event is scheduled, refer to events 3 and 4.

---

_{[original: nus-cs2103-AY2324S2/pe-interim#3878] [original labels: type.FeatureFlaw severity.High]}

Their Response to the 'Original' Bug

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

We reject this bug. The reasons are as follows:

• The user is responsible to ensure that the inputs are valid (i.e., that the start time can only be before the end time). Moreover, this qualifies as a "problem caused by extreme user behavior" by the same line of reasoning.

• Our reasoning is also based on https://github.com/nus-cs2103-AY2324S2/forum/issues/680.

  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)

• [ ] I disagree

Reason for disagreement: [replace this with your explanation]

---

## :question: Issue response Team chose [`response.Rejected`] - [x] I disagree **Reason for disagreement:** I believe this issue can be considered as NotInScope as prof has mentioned that this feature is a nice to have enhancement, which could be implemented in the future, as fixing the feature flaw is essential for the app to be reasonably useful.   

---

## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [ ] I disagree **Reason for disagreement:** [replace this with your explanation]

---