search

rui-han-crh / pe

0 stars 0 forks source link

Email Descriptor Cut Off If Too Long #4

Open rui-han-crh opened 2 years ago

rui-han-crh commented 2 years ago

Description

A very long email fails to render fully in the space provided.

Justification for Severity: Very Low

In the worse case, the user cannot see the full email. In the best case, the user may try to read the json file instead.

Steps to reproduce

  1. Enter an extremely long email.

  2. Observe that the email is cutoff (does not wrap) in the GUI.

image.png

soc-se-bot commented 2 years ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

Long scholarship names are not fully visible

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

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

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

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 duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

:question: Issue type

Team chose [type.FeatureFlaw] Originally [type.FunctionalityBug]

Reason for disagreement: [replace this with your explanation]