search

czhi-bin / pe

0 stars 0 forks source link

person with very long name gets cut off #3

Open czhi-bin opened 2 years ago

czhi-bin commented 2 years ago

When a person with very long name is entered, it gets cut off, while rare, it is possible to have a very long name

image.png

nus-pe-bot commented 2 years ago

Team's Response

The issue is NotInScope.

The 'Original' Bug

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

Long names get cut off and there is no way to view it

Step to reproduce:

  • Create a person with a very long name such that it cannot be viewed in the entire display.

Expected behaviour: Be able to scroll the display sideways to be able to view the entire name

Actual behaviour: No way to view the entire name of the person.

This is very low severity as it is extremely unlikely to happen and may be seen as a cosmetic issue. However it can be considered a bug if 2 people have the same long name except for the last few characters that cannot be visible thus the user cannot differentiate between the 2 people.

image.png

[original: nus-cs2103-AY2122S1/pe-interim#2137] [original labels: type.FunctionalityBug severity.VeryLow]

Their Response to the 'Original' Bug

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

Such a long name is too unlikely to occur and affect users; on top of this the user can edit the name once they see the problem. As such this was never in the scope of our app.

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 response

Team chose [response.NotInScope]

Reason for disagreement: I do agree that it is unlikely to happen, but I think it can be easily fixed with either a text wrap or setting a limit to the name and putting the reason for the limit in the UG. I believe this problem should not be a "Not in scope" problem as it does not fulfill the requirement of being a 'not in scope' problem. This is a bug of a feature that is already implemented and this issue wasn't mentioned in the UG as well. Perhaps a functionality bug would be more fitting instead of a feature flaw.

image.png

image.png

image.png

:question: Issue type

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

Reason for disagreement: [replace this with your explanation]

:question: Issue severity

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

Reason for disagreement: [replace this with your explanation]