soc-pe-bot
commented
1 year ago Team's Response
Before a user confirms a withdrawal that would cause them to fail their savings goal, they receive a warning message to confirm whether they want to proceed. If a user agrees to withdraw and fails to meet a particular savings goal, it's not relevant to continue reminding them of that goal, so it's best to remove it as the user is already made aware of their situation.
Continuing to display a warning message each time the user tries to further withdraw funds can slow down the process, especially since withdrawals tend to occur more frequently than deposits. Instead, it would be more useful to allow the user to create a new savings goal at their own discretion when they're ready(for example, whenever the deposits come in that allows you to pursue save goal again, such as to avoid unecessary reminders upon subsequent withdrawals), rather than constantly reminding them of a failed goal, which they are already aware of without the need of further reminder.
In summary, removing failed savings goals and allowing users to create new ones at their own pace would make the app more user-friendly and efficient, as constant warnings can be cumbersome, unnecessary and induce unwanted stress. I feel that the testers suggestion would be counterproductive in a fast-paced typing environment, which is why I have decided not to implement it.
Based on the reasons outlined above, I have decided to reject the suggestion. At worst, I may consider accepting it with a low severity level.
Items for the Tester to Verify
:question: Issue response
Team chose [response.Rejected]
- [x] I disagree
Reason for disagreement: If the savings goal was not deleted, that would not necessarily mean displaying a warning message for every additional withdrawal. Instead, it would make sense to display a warning message every time the user breaks the save goal. For example, let's say the save goal was $50:
Starting Balance: $70
Withdraw $30 -> WARN user
New Balance: $40
Withdraw $10 -> Do not Warn (Since the user was already below the savings limit)
New Balance: $30
Deposit $50
New Balance: $80 (Back above savings limit)
Withdraw $40 -> WARN user again (since they broke the savings limit again)
This would have a minimal impact on the speed of typing, and is more or less how the feature was described as working in the User Guide anyway. In the real world, people's finances change often, and they may need to temporarily withdraw below their savings goal. However, they will just try to go above their savings goal again whenever they deposit more. Cancelling the goal whenever the user goes under once is counterproductive and punishes the user instead of motivating them to save money.
To the point that the user could just make the savings goal again, that goes against the goal of making the program efficient in a fast-paced typing environment, as the user would realistically have to make the goal again every time they went under the amount. I'd accept it being a severity.Low bug, but I definitely think it is something that needs to be resolved to improve the effectiveness of the program.
When I withdraw below my save goal and say that I want to continue through with the withdrawal even though it will take me below my save goal, that should not automatically remove the save goal. See the following example:
This makes the tool much less useful to the end user because the user may still want to maintain their goal, but must temporarily withdraw money for a pressing bill or emergency. After they make more money back, they will want to continue saving for their goal.
To fix this, do not remove the save goal when the user withdraws below it. It should stay in place until the deadline unless removed by the user.