Feature Flaw: Clash in Scheduling Times Not Handled.

[devivy]

On adding 2 users with the same scheduling date and time , no error message is thrown. As a business owner and a customer this would cause major inconvenience.

[nus-pe-script]

Team's Response

Hi tester, this was intentional as it is possible for business owners to have schedules at the same time. For example, a bakery expecting different suppliers to deliver goods at the same time or to send out orders in bulk at the same time. Additionally, all schedules with the same date but not SCHEDULE_TIME provided would be considered as the same schedule. But this is not a scenario we want to block the user from managing. E.g. if multiple schedules with different contacts occurs on the same date, but the time is unknown.

Thank you!

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

• [x] I disagree

Reason for disagreement: Dear Dev Team,

While I understand your consideration of bulk scheduling scenarios, I respectfully disagree with rejecting this issue for several important reasons:

• Business Process Reality:

  • While bulk deliveries exist, they typically require different time slots for practical reasons
  • Having multiple appointments at exactly the same time creates logistical problems:
    • Unable to give individual attention to each client
    • Resource allocation conflicts
    • Physical space limitations
    • Quality of service compromises

• Risk Management:

  • Current implementation allows accidental double-booking without warning
  • No way to distinguish between intentional and unintentional scheduling conflicts
  • At minimum, users should be notified of time conflicts to make informed decisions

• User Experience Impact:

  • Business owners need clear visibility of scheduling conflicts
  • Current behavior could lead to:
    • Missed appointments
    • Customer dissatisfaction
    • Scheduling errors
    • Resource management issues

Instead of rejecting the issue, perhaps ya'll could implement a warning system that allows same-time scheduling when explicitly confirmed? This would maintain the flexibility you want while adding necessary safeguards.

Thank you.

---

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

---