jylow / pe

0 stars 0 forks source link

High impracticality of finding appointments without having appointments be ordered by date #7

Open jylow opened 7 months ago

jylow commented 7 months ago

Screenshot 2023-11-17 at 4.59.04 PM.png

I have added several appointments while testing the product. Unfortunately, I have realised that as I add more appointments, there is no way of organising the appointments to make it easier to view which appointments are coming up next on the sidebar. The calander also provides little to no information about the appointment apart from the appointment name which makes this function quite unusable for a clinic/doctor who has little time to sit there and try to reorganise the information

nus-pe-script commented 7 months ago

Team's Response

The appointments are currently sorted according to the patient, however we can consider also sorting it according to date as a future enhancement and hence we chose to respond with NotInScope. However, we also feel that it does not warrant a High severity as it does not make the product unusable for users, just a minor inconvenience.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: I believe this bug is not out of scope.

Screenshot 2023-11-21 at 8.34.17 PM.png

This sorting could have been implemented in a way such that it sorts on a more logical way(eg. date) quite easily just by sorting all appointments by the date. Furthermore, for this function to view upcoming appointments to be reasonably useful, the user should be able to view the closest upcoming appointments first rather than to manually check as mentioned in the change in severity portion. As such, I believe that this is a legitimate feature flaw bug and banking on a trivial enhancement does not warrant being notinscope


## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.High`] - [x] I disagree **Reason for disagreement:** Might have misunderstood/misinterpreted `makes the product almost unusable for most users`. The calender and appointment list together served no purpose other than to store information. Displaying the information in a presentable manner was not done at all. Even if i wanted to reference the list to the calender, it would take quite some effort and inconvenience to manually go through the list and pick out the appointments on whatever day. I will give the benefit of the doubt that not all clinics will receive many appointments and more walk-in patients. However, physiotherapists and psychiatrists count as private clinics and will receive multiple appointments. The DG did state changes proposed for the calender part of the appointment window. I will not argue against that. However, fixing that does not necessarily solve this issue. The proposed solution is to only increase cell size to accommodate more appointment names and storing the full names. Details such as time of appointment will still need to be referenced in the appointment list which is not only unordered, but stores past appointments as well. Growing the list only makes finding appointments harder. Hence my original justification for not being usable. I, however, failed to realise that while one function does not work, it does not mean the whole product cannot be used. The User Guide clearly states that retrieving appointments should be convenient and i assume that this would be an important functionality for the clinic workers. ![Screenshot 2023-11-21 at 12.17.13 PM.png](https://raw.githubusercontent.com/jylow/pe/main/files/59616138-05e0-4315-91a3-d3b2085183b9.png) ![Screenshot 2023-11-21 at 12.33.48 PM.png](https://raw.githubusercontent.com/jylow/pe/main/files/4e84033b-aaf8-4174-b69a-990948daa180.png) However, I would definitely not consider this bug low. This inconvenience in seeing appointments will affect most users of the application. Having to scroll down to match the name to the truncated appointment name in the calendar will quite an inconvenience to someone looking to schedule appointments. I would like to acknowledge that my original rating of high is a little too overambitious. However, I genuinely feel this cannot be a minor feature flaw and deserves at least a `severity.Medium` as it would bring quite some inconvenience to a large number of users. Thus I would disagree with the low severity and revise this as a Medium severity bug.