SaiChaitanya13 / pe

0 stars 0 forks source link

Budget can only be set for this month. And past transactions will still show this budget if you add in transactions. #3

Open SaiChaitanya13 opened 1 year ago

SaiChaitanya13 commented 1 year ago

I can only set the budget for this month. And when I add in a past transaction say a month ago, the budget is the same as the budget I set now ($50). image.png This hampers how I can use the application to store my transactions as I would want to set a budget for every month and may have different budgets each month. My budget may not have been $50 last month as I set it now. Furthermore, let's say I initially set budget to $21000 for last month, my transaction is within budget.

image.png AS shown above, assuming i set budget last month, it should be within budget. But now, let's say my budget is only $1000 for this month and I add in a transaction from last month that exceeds $1000, it would show that I have exceeded the budget even though it is not true as last month, I did not exceed the budget.

image.png

soc-se-bot commented 1 year ago

Team's Response

While it is a valid suggestion to improve, it is not within the scope of this iteration.

The monthly budget is not specific for each month as we found it unlikely that users will change their budget, and then make an edit to previous transactions. We treated monthly budget as a goal that you will set for yourself for extended periods of time. Hence, the monthly budget was assumed to be fixed and will not be frequently changed.

Items for the Tester to Verify

:question: Issue response

Team chose [response.NotInScope]

Reason for disagreement: While it may not have been implemented, I feel that this is an important thing that was missed out by the team. This is especially as it does not make any sense that someone's budget is the same for all months (especially with inflows and outflows being different every month eg. big purchases, more savings etc.). For a money-tracker application, budget is probably one of the most important things and it obviously cannot be the same for every month. This lack of rigor in the implementation of this feature would largely change the way a user could take benefit of this application.


## :question: Issue severity Team chose [`severity.Low`] Originally [`severity.Medium`] - [x] I disagree **Reason for disagreement:** I do not understand why the severity of the issue is reduced. Especially when the group themselves have mentioned in their Documentation that budget is an important part of their application. If that important feature is half done or not properly implemented, I believe that the severity should be at least medium.