soc-pe-bot
commented
2 years ago Team's Response
A case of deliberate sabotage. This instance of sabotage does not cause the application to fail or make it unusable. Also, if you read the DG, it is stated that hall admins or masters that would be the ones inputting this data and thus a student wouldn't have direct access to the database. Therefore, the case of a sabotage is not possible. Thank you
The 'Original' Bug
[The team marked this bug as a duplicate of the following bug]
Email overflow
User 11 has an overflowed email address.
This is not a major bug as it is unlikely that an email address is this long, i am not sure about the constraints of email providers on the length of the email however, this should not be allowed in the app. A long email would be cut off and the user will not be able to see it in future. However, given the rarity of such a long email, it would only cause a minor inconvenience to a small amount of users.
Steps to reproduce: edit 11 e/12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890012345678900123456789001234567890012345678900123456789001234567890012345678900123456789001234567890@01234567890.com
[original: nus-cs2103-AY2122S2/pe-interim#136] [original labels: severity.Low type.FunctionalityBug]
Their Response to the 'Original' Bug
[This is the team's response to the above 'original' bug]
Hi thanks for raising the issue. Please refer to the screenshot below regarding extreme user behaviors.
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)
- [x] I disagree
Reason for disagreement: It cannot be fixed at the same time, and thus is not a duplicate.
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: I have already given a scenario in the original response where this issue might occur, i do not believe that this is a case of deliberate sabotage as a student could be an exchange/overseas student, thus they might need to type in multiple addresses into the app. Their local address as well as their foreign address, this could cause the text to overflow as there are multiple addresses entered.
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: This would be a medium severity as it would inconvenience the user a lot when this happens, there is no way to obtain the original address back when this truncation of a long address occurs. Thus, it is a medium severity.
There is an overflow of the address if the address provided is too long.
Although the example used might not be the best, but there could be cases where some addresses are too long and cannot fit into the given application. For example, a student could be an exchange/overseas student, thus they might need to type in multiple addresses into the app. Their local address as well as their foreign address, this could cause the text to overflow as there are multiple addresses entered.
There is no mention of a character limit either, thus making the user feel as if they would be able to type in a long address and the application would be able to show them the address without any issues, however it is not able to do so. Thus, i feel that it is A flaw that causes occasional inconvenience to some users but they can continue to use the product.
Steps to recreate: edit 11 a/12345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890