github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-11 04:32:39 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Automatic rule for categorizing transactions is not working #1552

New Issue
Closed
opened 2026-02-28 19:47:01 -06:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-02-28 19:47:01 -06:00
Owner
Copy Link

Originally created by @kerhbal on GitHub (Oct 31, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

So according to doc https://actualbudget.org/docs/budgeting/rules/#automatic-rules

Actual also creates/updates rules for categorizing transactions. When you categorize a transaction, it will determine the best category for a transaction (basically the most common one) and create a rule that sets the category for the payee. If a rule already exists for the payee, it updates the category to set.

But after playing with it for a couple days, I find out that it did not automatically create rule when I categorized transactions.
Steps to reproduce:

  1. import csv from bank
  2. change category manually
  3. check if there is any rule auto-created for this payee
    Thanks

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Safari

Operating System

Mac OSX

Originally created by @kerhbal on GitHub (Oct 31, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? So according to doc https://actualbudget.org/docs/budgeting/rules/#automatic-rules > Actual also creates/updates rules for categorizing transactions. When you categorize a transaction, it will determine the best category for a transaction (basically the most common one) and create a rule that sets the category for the payee. If a rule already exists for the payee, it updates the category to set. But after playing with it for a couple days, I find out that it did not automatically create rule when I categorized transactions. Steps to reproduce: 1. import csv from bank 2. change category manually 3. check if there is any rule auto-created for this payee Thanks ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome, Safari ### Operating System Mac OSX
GiteaMirror added the bug label 2026-02-28 19:47:01 -06:00
GiteaMirror commented 2026-02-28 19:47:02 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Oct 31, 2024):

Have you set the same payee to the same category multiple times? It wont make a rule unless you do the same thing a few times

@youngcw commented on GitHub (Oct 31, 2024): Have you set the same payee to the same category multiple times? It wont make a rule unless you do the same thing a few times
GiteaMirror commented 2026-02-28 19:47:03 -06:00
Author
Owner
Copy Link

@kerhbal commented on GitHub (Nov 1, 2024):

@youngcw thanks for the lightning comment. No I probably didn't do multiple times for the same payee as I was also trying to create my own rules at the same time.
I tried again with some test samples and it worked! It created rule at around 3rd/4th categorizing
Will close the issue. Though it will be even better if there is a frontend msg to tell user a rule has just been created.

@kerhbal commented on GitHub (Nov 1, 2024): @youngcw thanks for the lightning comment. No I probably didn't do multiple times for the same payee as I was also trying to create my own rules at the same time. I tried again with some test samples and it worked! It created rule at around 3rd/4th categorizing Will close the issue. Though it will be even better if there is a frontend msg to tell user a rule has just been created.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1552
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?