github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #292] Fill category based on payee #6983

New Issue
Closed
opened 2026-04-10 16:39:28 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-10 16:39:28 -05:00
Owner
Copy Link

Originally created by @bjornbostrom on GitHub (Feb 23, 2022).
Original GitHub issue: https://github.com/actualbudget/actual/issues/292

When adding a new transaction and selecting an existing payee, the category can be automatically populated by creating a rule.

However, it is time consuming having to go to the rules-editor every time to configure this categorypopulation when entering a payee without a rule.

Would it be possible to add a checkbox when entering a new transacation which (if checked) creates a new rule that autopopulates category for that payee (with the category chosen in the transaction)? The checkbox should only by visible/enabled if the selected payee does not already have a category-populating rule.

Originally created by @bjornbostrom on GitHub (Feb 23, 2022). Original GitHub issue: https://github.com/actualbudget/actual/issues/292 When adding a new transaction and selecting an existing payee, the category can be automatically populated by creating a rule. However, it is time consuming having to go to the rules-editor every time to configure this categorypopulation when entering a payee without a rule. Would it be possible to add a checkbox when entering a **new transacation** which (if checked) creates a new rule that autopopulates category for that payee (with the category chosen in the transaction)? The checkbox should only by visible/enabled if the selected payee does not already have a category-populating rule.
GiteaMirror commented 2026-04-10 16:39:30 -05:00
Author
Owner
Copy Link

@Deguello commented on GitHub (Feb 23, 2022):

My understanding is that Actual learns this association and does this automatically. It's doing it for my payees now, but, granted, it didn't happen right away.

<!-- gh-comment-id:1280036526 --> @Deguello commented on GitHub (Feb 23, 2022): My understanding is that Actual learns this association and does this automatically. It's doing it for my payees now, but, granted, it didn't happen right away.
GiteaMirror commented 2026-04-10 16:39:31 -05:00
Author
Owner
Copy Link

@bjornbostrom commented on GitHub (Feb 24, 2022):

Maybe I am doing something wrong, but I do not get any associations between payee and category by default. I always need to go to the rule manager and add them manually.

<!-- gh-comment-id:1280036529 --> @bjornbostrom commented on GitHub (Feb 24, 2022): Maybe I am doing something wrong, but I do not get any associations between payee and category by default. I always need to go to the rule manager and add them manually.
GiteaMirror commented 2026-04-10 16:39:32 -05:00
Author
Owner
Copy Link

@Deguello commented on GitHub (Feb 24, 2022):

You will eventually.

<!-- gh-comment-id:1280036531 --> @Deguello commented on GitHub (Feb 24, 2022): You will eventually.
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
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#6983
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?