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.

nus-cs2103-AY2122S1 / pe-dev-response

Extremely long remarks #271

Team's Response

Duplicate status (if any):