Open Ramanathan0908 opened 2 years ago
The bug report is unclear:
Having said that, this is a valid feature flaw but we argue this is not in scope as the User Guide clearly states that we can only sort by one attribute.
In the creation of FoodRem, we do not want to restrict users on what unit is possible. E.g “Container”, “Boxes” are accepted. There is no way to include conversion rates for all units to have the same comparison without confusing the user further. Thus we decided to strictly compare by quantity and ignore units. The behaviour is stated in the UG as well.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
If two items of same unit, e.g litres but different prefixes were inputed, e.g litres for item 1 vs ml for item 2. it shows the litres before the ml even if the magnitude are the same (see picture). This could lead to the wrong conclusion that item 1 is of lower quantity than item 2.