Open jmsandiegoo opened 4 months ago
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.
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.
Team chose [response.NotInScope
]
Reason for disagreement: Thank you for taking a look at the issue, if the address has no use cases for now then should it be considered a FeatureFlaw
? This can still be a legitimate issue due to the fact that there is no purpose in including address functionality within the application itself. This would end up confusing the end user on why there is a need to include address when making a record. Also, it being truncated by an ellipsis
would also make it unusable in the end user's perspective. Hope that the team would be able to reconsider the issue thank you.
Steps to Reproduce
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.