You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The image shows the spendings I have added to the application. The daily budget that I have entered is 50.
As you can see I have gone over budget for the date 2024-11-15. The app works as expected and tells me that I have gone over budget.
However, when I add a new spending for a different date, in this case, 2024-11-20. The app still informs me that I have gone over budget. This can be misleading as I wouldn't know what day they'd be talking about. Is it 2024-11-20 that I have gone over budget or is it 2024-11-15 where I went over budget?
The team has discussed and decided to accept the bug. However, we have changed it to feature flaw as well as downgrade it to severity low. The following are the justifications:
We feel that the concern you have is over the clarity of the overspend message. If we had rephrased daily to today it would have been clear to the user. This would also likely to only cause minor inconvenience to the users.
The usability of the program is unaffected thus we feel it is more of a feature flaw than functionality bug. It works as intended with the correct overspend amount as per today's date as seen in your screenshot after you added a entry of a future date, the overspending amount did not change.
The image shows the spendings I have added to the application. The daily budget that I have entered is 50.
As you can see I have gone over budget for the date 2024-11-15. The app works as expected and tells me that I have gone over budget.
However, when I add a new spending for a different date, in this case, 2024-11-20. The app still informs me that I have gone over budget. This can be misleading as I wouldn't know what day they'd be talking about. Is it 2024-11-20 that I have gone over budget or is it 2024-11-15 where I went over budget?
[original: nus-cs2113-AY2425S1/pe-interim#743] [original labels: severity.Medium type.FunctionalityBug]
The text was updated successfully, but these errors were encountered: