Edit Events Handling for Duplicate Events

[nicljr]

When I use the Edit Event Command, it seems that if sometimes, I am not allowed to edit events such that I have a clash of events like here for example:

Here I tried to change the event to clash with the event 2, so here in fact I have already one hello event and a third event that starts at the same time and end at the same time, which allows the clash here as shown below.

When i try to add a new Event that has the same start time, it throws the duplicate error message.

Thus technically I am able to have clash of events here, I believe this is due to one of the issues mentioned about the start time and end time, which is affecting the expected result of clashing

[nus-se-bot]

Team's Response

Problem arose from the same issue of allowing same start and end time.

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

❓ 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]

---

❓ Issue type

Team chose [type.DocumentationBug]
Originally [type.FunctionalityBug]

• I disagree

Reason for disagreement: This should not only be a Documentation Bug, as I believe what the Team is trying to say is that the within the Documentation, we should let the user know that the application allows you to add events with same start time and end date time, however this will cause an erratic behaviour within the application, we should not just be a documentation error, as users are not able to add events that occur at that timing, due to the handling of event clashes, inhibiting user experience. Not too sure the change of issue type specifically as team never provide a response.

---

❓ Issue severity

Team chose [severity.VeryLow]
Originally [severity.Medium]

• I disagree

Reason for disagreement: Personally I feel the severity should not be very low as the application allows you to add events with same start time and end date time, however this will cause an erratic behaviour within the application, as users are not able to add events that occur at that timing, due to the handling of event clashes, inhibiting user experience.

---