search

KiatLun / pe

0 stars 0 forks source link

Cannot see full address of a user #5

Open KiatLun opened 5 months ago

KiatLun commented 5 months ago

When using the add command, i used a very long address and this resulted in the full address not being shown on the contacts list. It is not uncommon to have a very long address. image.png

nus-pe-bot commented 5 months ago

Team's Response

No details provided by team.

The 'Original' Bug

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

address of user in the gui is being cut off

Steps to Reproduce

  1. Start the application
  2. Edit the user index 1 with the following address: edit 1 a/Block 123 Street 21, Benson Ville San Mateo Rizal Region IV, Metro Manila Philippines

Expected Behavior

The application should be able to handle and display longer addresses that could exist without it being cut off. The example above is based on an address in Philippines.

Actual Behavior

The application is unable to display the address fully which might cause issue for the user if there are cases, he/she needs to send a mail to the library user's address.

image.png

[original: nus-cs2103-AY2324S2/pe-interim#319] [original labels: type.FunctionalityBug severity.Medium]

Their Response to the 'Original' Bug

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

Thank you for pointing this out.

After discussions within the team, we have decided that this bug is part of NotInScope.

The reason behind this is that the address is currently not in use, there are no functions or features that require the use off the address as of now. However, in the future, we may implement the use of the address for other features. Thus, as of now the issue with the address being truncated only serves as a minor cosmetic issue and therefore our team decided to classify this as severity.VeryLow.

image.png

Note that: While response.NotInScope are not counted against the dev team, they can earn a small amount of consolation marks for the tester. The other three do not affect marks of either the dev team or the tester.

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`] - [x] I disagree **Reason for disagreement:** Regardless of whether the address is being use by any function, it does not make sense for users to not be able to see their full address.
## :question: Issue type Team chose [`type.FunctionalityBug`] Originally [`type.FeatureFlaw`] - [x] I disagree **Reason for disagreement:** I feel that it is a feature flaw since its behaviour does not differ from what its stated in the user guide, however the address feature is flawed since its. trucated hence it should be a feature flaw.
## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** It is a issue that is at least of severity.medium because it is not uncommon for users to have a long address, hence if library managers or those using the product is not able to see the full address there could be implications such as not being able to mail the user due to truncated address.