soc-pe-bot
commented
2 years ago Team's Response
It is unclear what exactly the bug in this case is. The tester simply just states Extremely long remarks take up a significant space in the UI, which is just a description of the screenshot and is simply stating the obvious. Of course, an extremely long remark would take up significant space in the UI. That is like saying an extremely large computer requires a significantly large bag to place it in. There is no description of what the problem is or how this impacts a potential user or what should have been done instead. The title is also meaningless, as it does not provide any description of the bug. On this basis alone, it is enough to classify this bug as unclear.
But if the user is saying that this makes the UI hard to read and inconvenient for the user, then the reason for this would be because this is an intended behaviour.
If we wanted to prevent such a situation as in the screenshot, there were two things that we could have done. Firstly is to limit the length of the remark field but we felt that this was an unnecessary constraint as we did not know what the length of a typical remark is. Some users may like entering long remarks and some users may prefer shorter ones. Furthermore, there may be some patients that have a lot of medical conditions and allergies, which requires the need of a long remark field to list down all this information. Hence, we found it to be unreasonable to impose an artificial upper bound on the length of the remark field. The second option would be to cut off the remark field if it is too long but again this would not have been a wise decision. Remarks are meant to store important information about a patient and doctor. If we choose to cut off the remarks, important information would have been cut off. Either of these 2 options would have been more inconvenient to the user than just simply showing the entire remark.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Okay the point is because since you mentioned that there is no lower or upper bound on the remarks, the receptionist could technically write an entire paragraph under it. Given that the app needs to store large amounts of patients, this is seriously gonna take up quite alot of space. This makes it extremely time consuming if I wanted to find the index of a person to edit, given that I have to scroll furiously to reach that index (maybe index 1000 or smth). The point is that this app is gonna store a lot of patients given the nature, and it is NOT optimal to the user if every remark is displayed.
My argument is that I'm not trying to limit the length of the remark. Its the GUI inability to optimise for huge chunks of text (which is why its a cosmetic issue and I graded it very low)
There are several ways to limit it obviously.
- Display the remark but cut off at the border of the window with trailing spaces e.g this is a very long rem.... Only display the FULL version if the user prompts to view it. This way, only 1 out of the 1000 patients would take up the huge block of space.
- Don't display the remark. Have a separate command to pull up the ENTIRE details of the contact, with the remark.
Its the same in almost every app that saves contacts. Highly required fields are only displayed on the main window to minimise clutter in the GUI (name, phone etc) to optimise user experience.No phone app shows the full details of every contact on the main window itself.
If I didn't make this clear in the PE, its cause I had no time to write this chunk to explain why i felt this was a flaw but I hope this makes sense.
Extremely long remarks take up a significant space in the UI.