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

[Feature] Show Pop-Up Confirmation for Created Automatic Rule #2317

New Issue
Closed
opened 2026-02-28 20:10:18 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 20:10:18 -06:00
Owner
Copy Link

Originally created by @nicorenaldo on GitHub (Jul 27, 2025).

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

When category learning is enabled, the system sometimes generates an incorrect rule for a payee. For example, it may wrongly associate "Simon Robert" with the Transportation category because he transferred taxi money to me, even though he may transfer me money for other stuff later on. From then on, all transactions from Simon are miscategorized.

Currently, users only discover this mistake later when syncing or creating new transactions — by then the incorrect rule has already been applied, requiring manual cleanup.

Describe your ideal solution to this problem

Every time the system automatically creates a new category rule, notify the user immediately display a toast or pop-up notification describing the rule.

Should include two action buttons:

  • Dismiss → accept the rule.
  • Delete → remove the rule if it was wrongly created.
  • Edit

This makes category learning transparent and lets users catch errors before they propagate.

Image
Originally created by @nicorenaldo on GitHub (Jul 27, 2025). ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? When category learning is enabled, the system sometimes generates an incorrect rule for a payee. For example, it may wrongly associate "Simon Robert" with the Transportation category because he transferred taxi money to me, even though he may transfer me money for other stuff later on. From then on, all transactions from Simon are miscategorized. Currently, users only discover this mistake later when syncing or creating new transactions — by then the incorrect rule has already been applied, requiring manual cleanup. ### Describe your ideal solution to this problem Every time the system automatically creates a new category rule, notify the user immediately display a toast or pop-up notification describing the rule. Should include two action buttons: - Dismiss → accept the rule. - Delete → remove the rule if it was wrongly created. - Edit This makes category learning transparent and lets users catch errors before they propagate. <img width="1536" height="1024" alt="Image" src="https://github.com/user-attachments/assets/30c880b5-21b9-4776-aaa1-0e9c93f6a696" />
GiteaMirror added the needs votesfeature labels 2026-02-28 20:10:18 -06:00
GiteaMirror commented 2026-02-28 20:10:19 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 27, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don’t forget to upvote the top comment with 👍!

@github-actions[bot] commented on GitHub (Jul 27, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don’t forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
GiteaMirror commented 2026-02-28 20:10:20 -06:00
Author
Owner
Copy Link

@RoLYroLLs commented on GitHub (Aug 1, 2025):

If it's decided to use a toast notification, add an EDIT or REVIEW button which will open the rule for review.

@RoLYroLLs commented on GitHub (Aug 1, 2025): If it's decided to use a toast notification, add an `EDIT` or `REVIEW` button which will open the rule for review.
GiteaMirror commented 2026-02-28 20:10:20 -06:00
Author
Owner
Copy Link

@gitchap commented on GitHub (Nov 1, 2025):

An additional option to " payee going forward" would probably be helpful to many.

@gitchap commented on GitHub (Nov 1, 2025): An additional option to "<ignore> payee going forward" would probably be helpful to many.
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 feature needs votes
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#2317
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?