This release focuses on reliability of the budget. A few edge cases have been found which affect the budget, and while these are rare edge cases, you should never have to worry about the budget being wrong. Reliability and robustness is always #1 priority. This release changes the transaction import process quite a bit, so let us know if you have any problems with that.
-
%BUG% When clicking on the "spent" amount in the budget to view transactions for that month's category, it wasn't showing transactions from closed accounts. This made you think the budget was wrong, but it wasn't showing all the transactions it takes into account. Now it shows transactions from closed accounts.
-
%BUG% Discovered a critical bug that could make budget values out-of-date. If you categorize a transaction, and then split the transaction and categorize the split transactions with different categories, the original transaction's category will be wrong in the budget. What should happen is the original transaction should be removed from category it uses when split, and only the split transactions should affect the budget. This is now what happens!
The issue is an out-of-date cached value for the category's budget. If you used that category again, it would recalculate to the correct value. If you suspect any problems with your budget, you can always go to Settings > Advanced > Reset budget cache to recalculate the entire budget.
-
%BUG% The transaction import process has been refactored again and fixes a few problems. Reconciliation/deduping of transactions should be improved. Previously it wasn't deduping transactions if the payee was different. Let us know if it doesn't dedupe transactions like you expect.
-
%BUG% Importing transactions should now always use the payee that you expect after running rules. There were a few edge cases here where sometimes it would not end up with the correct payee. Additionally, even if it uses the correct payee, previously sometimes it would internally create other payees while processing the rules. Now it will always only create one payee at the end (if it doesn't already exist).