nus-cs2103-AY2324S1 / pe-dev-response

0 stars 0 forks source link

UI stays frozen at details of the last command, instead of allowing viewing of another person #4408

Open nus-se-script opened 10 months ago

nus-se-script commented 10 months ago

Screenshot 2023-11-17 at 4.31.32 PM.png

UI does not allow the navigation across the different persons, as seen from the screenshot here, even though I wish to see the details of Charlotte Oliveiro, it does not change the screen on the panel on the right, which is frozen on the details of John Doe.

This is a feature flaw because user would expect the UI to display the details of the person clicked, however, here, the UI is frozen on the most recent command which is adding a patient called John Doe

I would give this a Medium severity as this is an incomplete behaviour by the UI which is not included in the Planned Enhancements section in the DG or the Known Issues section in the UG and users should be made aware of the limitations, however because it does not hinder functionality of the rest of the app, giving it a low severity


[original: nus-cs2103-AY2324S1/pe-interim#3380] [original labels: severity.Low type.FeatureFlaw]

sk2001git commented 10 months ago

Team's Response

Reason for why the severity been downgraded to Very Low:

  1. Under the TP obligation, JABPro is a CLI-based app. Therefore, most operations are done fast by typing and the clicking functionality is by that definition, meant to be limited.
  2. There was no promise in the UG or any mention that clicking on the UI, especially the list of cards will change the view. Instead, the commands that change view panels are view and all the comamnds mentioned in this tip box shown below.

I agree that the app can be made better in terms of UI in this aspect where we allow clicking. However, the functionality of viewing is possible with the commands and no such promises was made. I understand that the person list card might light up when pressed also which may be misleading.
Thus, I accept this as a Very Low feature flaw (As there is a cosmetic issue) , but it is by the above argument not a feature flaw warranting Low

image.png

Duplicate status (if any):

--