soc-se-bot
commented
5 months ago Team's Response
This is what we purposely designed such that no 2 event happens concurrently.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: If you purposely designed it this way, then it is indeed a feature flaw. The purpose of your application is a timetable to keep track of all your task that you have for each day. What if you have an ongoing task from morning till night, and you have to attend to things in between. Would you not want to be able to record it? This means that if you have a full day event, you will not be able to add other matters to your timetable as it does not allow for it. This severely reduces the purpose of your timetable which is meant to manage your tasks, not prevent you from working on them.
Furthermore, if this was intended, it was not included in the user guide. The user guide does not mention that users cannot add tasks that are clashing in timing. So this issue seems to be an idea that was not really well thought out. I understand the attempt that you are trying to make, but seems like you failed to think of the consequences of implementing this restriction, thus making it a feature flaw.
I am unable to add a task that clashes with any existing task. This may pose a problem, for example if I have an event from 11am to 3pm and I may need to run a quick errand from 11.30am to 12pm. I will not be able to add that into my timetable to track it.