search

eugenetayyj / pe

0 stars 0 forks source link

Long scholarship names are not fully visible #6

Open eugenetayyj opened 2 years ago

eugenetayyj commented 2 years ago

To reproduce

Steps to reproduce:

  1. Create applicant add n/Superman p/98765432 e/johnd@example.com s/CN Yang NUS Overseas College NOC Philip Yeo Scholarship Grant cum laude as/pending m/science m/philo

Expected

I should be able to see the full name of scholarship

Actual

Cannot be seen. no ... either

Screenshots

image.png

OS

Windows 10

nus-se-bot commented 2 years ago

Team's Response

Justification for downgrading from severity.Low to severity.VeryLow:

Given that the above input value is unusually long, and that it is pretty rare that an administrative staff will key in the entire scholarship name instead of abbreviation of such names. Additionally, our application is able to display the entire scholarships for all scholarship names on a standard 1920x1080 screen for NUS related scholarships since our application is targetted at NUS administrative staff.

Hence, we considered it as an issue with severity of VeryLow, that affects the visibility of such inputs.

image.png

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.VeryLow] Originally [severity.Low]

Reason for disagreement: I would argue that being unable to see the full name of a field in my contact is not simply a cosmetic issue that does not affect usage. The purpose of the application is to help store information. Perhaps it is rare that a scholarship has such a long name.

However, the justification that the admin staff will use abbreviated names is not very useful as the CLI application is supposed to be faster than GUI for people that can type fast so I think that abbreviated names may not be relevant here.

Furthermore, the target audience for the application seems to be for administrative staff at Universities. There is no specification that NUS staff. Perhaps the team got mixed up on who their target audience is.

image.png

In general, I think that this is more than just a cosmetic issue as being unable to find information about the student that is input into the application just because there is a layout problem is something that deserves more than a low severity. This is an edge case that information given could very well be long and thus should be acknowledged as such - not as a very low severity problem.