Bugs

Repro: create some dummy transaction groups and some transactions into account: Cash transaction apply search filter: Account is Cash transaction observe how it shows both actual Cash transactions and unrelated groups with empty account field

On the Budget page, clicking the Outflow column header initially sorts categories alphabetically (A–Z) or in reverse alphabetical order (Z–A), as expected. However, after navigating to a different budget period, the sorting behavior changes. Instead of sorting alphabetically, clicking the Outflow column header appears to alternate between the custom category order configured on the Categories page and its reverse. This behavior persists even when navigating back to the original budget period.

Below (screenshot 1), I selected both the group (in category Sports classes) and an item in this group (marked GROUPED TRANSACTION). Note how the total 706.10… which is not even 440.81+265 = 705.81 but close (no idea where that value comes from). The Filtered Total tooltip (screenshot 2) indicates that it's properly removing redundant grouped items, but it's not doing that. In fact, I have no idea where the 492.01€ comes from. I hope that at least the budget is correct as it should only take into account the parent group's category, since grouped items don't even have their own category anymore… but considering all the sum errors, I can't be sure. In addition, right after grouping items (with some text filter active), the selection is very buggy, as selecting unrelated, non-group items will also select grouped and group items. For instance, selecting the Restaurant item below will also select the two items above. Even after clearing filter and looking at all, non-grouped transactions, click on the restaurant item would select unrelated items below (screenshot 3). I cannot repro the bad selection after refresh though. Maybe that bug only occurs just after grouping items, as it retains an old selection in the background.

When importing transactions via CSV and saving the import configuration, the selected date format isn't remembered for future imports to the same account, despite having "Save import configuration" enabled. The saved configuration should retain and correctly apply the selected date format on future imports. It should save whether proceeding with the automatic date parsing, or if using the 'Fix Dates' feature.

Updating the balance of a manually-managed account sometimes fails if the value is copied and pasted into the input field. The UI shows the balance was saved successfully, but the balance doesn't update. Manually typing the value works as expected. Might be a pasted input parsing/normalization issue.

Currently, rules ignore transactions that are associated with suggested recurring items. Since those transactions can be revised, split and grouped via the Transactions page, then those transactions should also accept revisions through Rules.

On the Transactions page, updating the Payee name of a transaction that is associated with a suggested recurring item, will lead to the Payee name only updating in the 'Transaction Details' panel. The payee name in the Transactions table cell will remain with the original value. If the suggested recurring is marked as "This is not a recurring item", the payee name in the table will then reflect correctly. On the other hand, if the suggested recurring is accepted, it will lock the listing with the two different payee names.

On the Overview page, the budget status card displays "No roll over to next period" even when General Pool rollovers are enabled. It displays correctly on the Budget page, but incorrectly on the Overview page. Additionally, when you set the Overview page to a period longer than one period (i.e. 3 months, or last year), it incorrectly displays "Balance for this period!".

When using the Lunch Money web app in Firefox for Android, the Save and Cancel buttons at the bottom of the Account Management overlay are not persistently visible.

When viewing the Rules page, editing and saving a rule on any page other than the first (e.g., page 2 or 3) causes the page to automatically jump back to page 1 instead of remaining on the current page.