github letehaha/budget-tracker v0.27.11
v0.27.11 – Apply automation rules to past transactions

7 hours ago

What's Changed

⏪ Apply automation rules to past transactions

Until now an automation rule in MoneyMatter only ran on transactions that arrived after you saved it. You can now run a saved rule over your existing history from three places: the rule's menu on the Automations page, the "Apply to past transactions" button in the rule editor, and a new card on the Optimizations page that first asks which rule to use.

Nothing changes without your review. MoneyMatter scans your recent transactions, lists the ones the rule matches, and lets you untick any you want to leave alone. Transactions the rule already fully describes stay off the list. A category you picked yourself, or one set by a subscription, is never overwritten. Transfers, planned transactions and manually entered transactions on non-bank accounts stay out of reach, the same as for live rules. Before anything is written, a confirmation reminds you the change cannot be undone. Each run reviews up to 500 matches, so run it again if a long history has more.

🐞 Bug Fixes

  • Connecting a bank account whose first import took longer than a minute failed with a 504 error, even though the import kept running and a second connect attempt then succeeded. Connecting now finishes right away and the import continues in the background, with progress shown in the header. Accounts with a short first import were never affected. Thanks to @algedabra for reporting this.

📝 Code Changes

  • feat: ways to apply rules to past transactions with a review step by @letehaha in #589
  • fix(bank-sync): run account syncs via BullMQ so connect never times out by @letehaha in #591
  • ci(preview): overwrite shard artifacts on re-run by @letehaha in b67afd1d

Full Changelog: v0.27.10...v0.27.11

Don't miss a new budget-tracker release

NewReleases is sending notifications on new releases.