nus-pe-bot
commented
3 years ago Team's Response
The feature was designed such that the event is consider a duplicate if the name and the date matches only. This is because you can have the same event on a different day at the same time. This is so that each event added into the list are unique to the day.
Since its a CCA manager, examples of events we considered were: any kind of courses, day programs. Even cca sessions are mostly once a day.
For the examples given about recurring CCA sessions, we considered recurring sessions on different days, which is usually the case.
It was pointed under our developer guide, design considerations.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Thanks for clarifying that I am not allowed add same named events under same date. That does lower the severity of the problem, but I would still like to consider it as a feature flaw. Because by this logic, I can say that a CCA can have the same event on the same day but at a different time. For example if I were to have multiple break sessions in a day, I will be forced to name them as "break1", "break2", "break3" and etc. But yes in that case it should be a feature flaw with low severity.
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [ ] I disagree
Reason for disagreement: [replace this with your explanation]
No details provided.
As seen above, I was capable of adding two events of the same name under differnt dates, but when i try to add events of the same name under same date but differnt timing, i was told that i cant add an already exiting event. It doesnt make that much sense since i can have multiple event such as (do homework) under same day but differnt timing.