search

dayn-1 / pe

0 stars 0 forks source link

Appointment does not account for date, only day of the week #5

Open dayn-1 opened 3 months ago

dayn-1 commented 3 months ago

Appointment details in TutorRec contains only start, end time and day of the week.

This could work for regular tutoring sessions scheduled at the exact same time, week on week. However, should there be last minute changes, or one-off changes to the schedule, there is no way to differentiate the "regular" timings and the "last-minute updated" timings.

This issue is not describing the issues related to conflicting appointments, as seen in the planned enhancements section of the DG. Rather, the feature flaw it imposes in being restrictive for the user. Furthermore, this means that appointments can only be managed week by week, and not in advance.

nus-se-script commented 2 months ago

Team's Response

We have stated this as one of our planned enhancements.

image.png

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Hello, as mentioned in the original bug report,

This issue is not describing the issues related to conflicting appointments, as seen in the planned enhancements section of the DG.

This issue is describing the restrictive options of day (i.e. "MON", "TUE", ... "SUN" instead of a date). Therefore, the user is restricted to only being able to plan for a maximum one week period. Because "WED" as of now, Tuesday, would mean tomorrow, and cannot otherwise mean last Wednesday or next Wednesday. This leads to an overall confusing experience of whether the days are updated or not, as in "WED" could be updated for the upcoming Wednesday, or not updated as in it was untouched since last Wednesday - we cannot tell.

While I understand that the potential solution in the planned enhancements section could help solve some of these ambiguities, the section does not describe how these appointment conflicts will be solved. Hence, the bug report was still raised because it is unclear whether that planned enhancement will solve this feature flaw as well.