Zhilin-Huang / pe

0 stars 0 forks source link

Wrong 'sufficient calories' standard when user is working towards a lower weight goal #4

Open Zhilin-Huang opened 4 years ago

Zhilin-Huang commented 4 years ago

Screen Shot 2020-04-15 at 12.35.17.png

110.00 cal is nowhere close to 2362.89cal and it's wrong to say that the user has consumed 'sufficient calories'. Note that this bug appears when the user is working towards a lower weight goal.

This flaw causes occasional inconvenience to some users who are working towards a lower weight goal but they can continue to use the product.

nus-pe-bot commented 4 years ago

Team's Response

Understand that we promised to give the user a picture of the amount of calories they consumed against the amount of calories required to inform them if they are consuming sufficient calories. However, we understand that sometimes the person might want to lose weight but is only willing to eat up to 500 calories lesser than what is required. This feature is definitely NOT what was promised in our current version. But it is a good feedback that we can implment for future versions to allow the users to customize even further. In the meantime, my group's stand is that this customization won't affect the user usage currently, and is NOT promised in our current version. Thank you nonetheless for your feedback.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: This issue reported is not about the team 'promised to give the user a picture of the amount of calories they consumed against the amount of calories required to inform them if they are consuming sufficient calories'. As a matter of fact, I had no idea that the team made this promise at the time I was testing this product and this is hardly relevant to the bug reported in this issue. Also, I literally have no idea how 'However, we understand that sometimes the person might want to lose weight but is only willing to eat up to 500 calories lesser than what is required' is even related to this issue because 2362.89 - 500 is still way higher than 110.00.

Just to reiterate, this issue is just about a bug I found when the calories intake is 110.00 cal and the goal is 2362.89 cal, yet the application still says that the user has consumed 'sufficient calories'. The dev response is rather irrelevant and does not address this bug reported. Also, if something in this version of the application appears to be wrong and confusing, it is definitely not 'NotInScope'.