Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Misleading Error Output #757

Open
nus-pe-bot opened this issue Nov 16, 2024 · 1 comment
Open

Misleading Error Output #757

nus-pe-bot opened this issue Nov 16, 2024 · 1 comment

Comments

@nus-pe-bot
Copy link

nus-pe-bot commented Nov 16, 2024

image.png

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]
@NigelYeoTW
Copy link
Contributor

NigelYeoTW commented Nov 17, 2024

Team's Response

Dear tester,

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:

  1. 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.

  2. 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.

Duplicate status (if any):

--

@NigelYeoTW NigelYeoTW self-assigned this Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment