Feature flaw for expense value

[lil1n]

expense only take in an integer value, however, most of the time, transactions and expenses take on a double value. Could maybe consider allowing a double value for expense

[nus-pe-bot]

Team's Response

As the fractional part is small compared to the expense, the user can round the expense without causing major troubles most of the time. Therefore, the severity should be low

Items for the Tester to Verify

:question: Issue severity

Team chose [severity.Low] Originally [severity.Medium]

• [x] I disagree

Reason for disagreement: As per the module website:

• severity.Low : A flaw that is unlikely to affect normal operations of the product. Appears only in very rare situations and causes a minor inconvenience only.
• severity.Medium: A flaw that causes occasional inconvenience to some users but they can continue to use the product.

Yes, in terms of one transaction, a decimal point is considered small. But the value would be significant after combining multiple of such transactions. This would lead to inaccuracy of finance tracking in the long run. Additionally, in the real world, expense value are not always a whole number, hence I think this would cause occasional inconvenience as a user would have to think about whether to round the value up or down in order to reflect their spending accurately

What if users use this feature as an excuse to round down their expenses? This would lead to inaccurate logging of finances, allowing the user to spend even more as their true spending is diminished, causing them to believe that they have more than what they had

Being a personal financial tracker, I think that this issue is would be more than a medium. If it is not able to keep track of finance accurately, is the financial tracker even a financial tracker? Would you even need such a financial tracker?

---