Open kyhjonathan opened 5 months ago
Thank you for your suggestion. I do acknowledge that using the terms for my prefixes as morethan/
and lessthan/
may be a little counterintuitive. However, this is actually an intended output. Stated in the UG,
Where MAXAMOUNT and MINAMOUNT are the values 167 and 0 respectively w.r.t your input.
Hence, when searching for expenses less than 167, this would actually include expenses with the value 167 too as stated in the UG. Making the output in your picture an intended output.
I do acknowledge that this is a valid flaw, in particular a "cosmetic" flaw as users may mistakenly associate the lessthan
prefix to not include their provided amount should they not read/have access to the UserGuide. However, as having a longer and clearer, prefix etc, lessthaneqto
, lessthanequalsto
would incur extra typing, the renaming of this prefix was not a huge priority in the implementation of v2.1.
Overall i agree with the VeryLow severity and classified this response as a NotInScope.
Team chose [response.NotInScope
]
Reason for disagreement: [replace this with your explanation]
Steps: