nus-se-bot
commented
3 years ago Team's Response
Thank you for the feedback. Firstly, as per the image below, we believe that this "issue" should be classified under Low instead of Medium as the condition to meet the "issue" is not one that will occur too often and is unlikely to affect normal operations of the product.
Secondly, we argue that this is not a bug as the user can consume the same food multiple times in the same day. In our user guide, we did not restrict users to keying in only one unique instance of a food item. As such, this is actually the expected behaviour.
Furthermore, the image used in this bug report does not coincide with the explanation. Additionally, the image shown is not a bug at all, it is simply a typo on the part of the bug tester having concatenated the words "add" and "-n" together to form "add-n" which is indeed an unknown command.
Therefore, we will be reducing the severity to Low and reject this bug report.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: Thank you for the reply.
I agree that I did not attach the correct screenshot with the correct add -n format, however, you also said that duplicate without detection is the "expected behavior" of the application, which means that you agree that adding duplicates will not give a warning, which is what I have tested as well.
I think that "users may forget that he has added the food once already and add again for the same purpose" is a valid concern, however. It is likely that for example, A has eaten a banana after lunch, but did not check that he or she has already added this banana into the app, then he or she may add again without noticing. If she could not remember clearly how many banana he or she has eaten, he or she may not notice that duplicates are entered for one consumption behavior. For a user, I do not think he or she will bother to check the entire list again everytime a new item is entered, thus duplicate may be added without detection from the user side.
Thus, an expected behavior of the application would be to inform the user that an exact duplicate has added and thus notify him or her about whether duplicate is what he or she has intended to have. Since the same food consumed yesterday, or even the current day at a different timing, would be not marked as duplicates as they would not have the same tags(eg "breakfast") or dates, duplicates detected is likely a repeated addition for the same food item consumed just now.
I believe that it would cause some degree of inconvenience given such scenario, since it is likely that duplicates may be entered repeatedly for the same purpose, which may cause the user into thinking that he or she has consumed more than what actaully is, which may not lead to a positive consequence.
:question: Issue severity
Team chose [severity.Low]
Originally [severity.Medium]
- [x] I disagree
Reason for disagreement: I think that the severity should be medium since "occasional inconvenience" is likely to be caused to some users.
If we imagine Amy as a user who uses the application everyday to record her food consumption, I do not think she would look at the list of food items every time after she recorded the food items for every lunch, for example. Then it may occur to her that she may not have added a sogurt yet, and since Amy is busy she would just add it.
If the app does not give a warning for exact duplicates(same date, same tag, for example), Amy may just add it without noticing that it has been accounted for, and if Amy do not check the whole list at that time, Amy may just forget that she have entered it twice. This may cause some trouble as the record of calories would likely to be more than what Amy has actually consumed.
Thus, not detecting duplicates could be occasionally inconvenient for the users who may be sometimes unsure of whether he or she has already added the food item. Since as said in the disagreement report about the team's rejection of this bug, the same food eaten yesterday, or even the current day, would be not marked as duplicates as they would have different tags(like "breakfast") or dates, duplicates of the same date and without tag (when adding a new food item) is likely a repeated addition for the same food item consumed just now.
Hence, I think that detecting exact duplicate is quite necessary and an expected behavior, and without it, some occasional inconveniences would be caused.
Duplicates of potato can be added without acknowledgement or feedback from the app showing that it is duplicate, which may be inconvenient as users may forget that he has added the food once already and add again for the same purpose.