Tsenrae / pe

0 stars 0 forks source link

Bug for adding a person with a very long name #3

Open Tsenrae opened 7 months ago

Tsenrae commented 7 months ago

Steps to reproduce:

  1. add n/Uvuvwevwevwe Onyetenyevwe Ugwemubwem Ossas p/98765432 e/johnd@example.com a/John street, block 123, #01-01

Expected: Able to see the person's full name Uvuvwevwevwe Onyetenyevwe Ugwemubwem Ossas in the UI as this person's name is valid

Actual: Only able to see the partial name and the rest of the name is replaced by...

Screenshot 2024-04-19 at 4.23.03 PM.png

soc-se-bot commented 6 months ago

Team's Response

image.png

It is stated in the UG that names will be truncated if they are too long.

Furthermore, in the screenshot, there are reasonably enough displayed characters in the contacts name for the user to recognize the contact.

Items for the Tester to Verify

:question: Issue response

Team chose [response.Rejected]

Reason for disagreement: Though I realise my mistake that I did not see in the UG that names will be truncated if they are too long, I still believe that there is a bug in adding a person with a long name. This is because even though there are reasonably enough displayed characters in the contacts name for the user to recognize the contact, this will no longer hold true when there are multiple people with a similar long name. Below is a screenshot of such an example:

Screenshot 2024-04-24 at 12.55.44 AM.png

To give more context, the 1st contact's name is Uvuvwevwevwe Onyetenyevwe Ugwemubwem Ossas while the second contact's name is Uvuvwevwevwe Onyetenyevwe Ugwemubwem Pddbt. Though the names are clearly different, due to the truncation, and the fact that all the other fields are the same, there is no way to tell which name belongs to which contact. As such, users trying to manage people with the same names except their surnames would struggle using your application. Having the same first/middle names is not a rare situation. Thus, I deem this a type.FeatureFlaw, as your current implementation of truncating the name would hinder the user as they would not be able to use your app properly in this case. You could have added a warning for such instances to tell the user that they would be unable to tell the difference between the long names.

Moreover, I would like to increase the severity from VeryLow to Low, as this is no longer just a cosmetic issue, and it affects the normal operations of the product in rare situations, like the example I just mentioned above.