github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 12:28:57 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[Feature] Improvements in the Rules interface #970

New Issue
Closed
opened 2026-02-28 19:26:49 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-28 19:26:49 -06:00
Owner
Copy Link

Originally created by @lucharo on GitHub (Mar 7, 2024).

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?

I think the Rules capability and UX are too simple and confusing to use. I believe some features could be added to improve how rules behave and are designed.

Describe your ideal solution to this problem

  • Rule notifications, in-browser notification when the rule gets executed and/or progress bar for it.
  • Rule history, a readable log of what rules have been run
  • Rule reversibility, the ability to reverse a rule being applied with a corresponding notification (much life Ctrl-Z generally would benefit from an in-browser notification displayed)
  • "Complex" rules + naming rules, basically more conditions for a single rule statement, e.g. account is A and (imported payee is XXX or imported payee contains XYZ, etc)
  • Button to run all rules manually
  • Ability to reorder rules, given they "are always run in the order that you see them"
  • Rule Flow diagram, to visualise rule order in the three phases

Teaching and learning

More examples of Rules and better informing on how to deduplicate transactions, these features I described would improve issues and frictions I have faced trying to deduplicate, recategorise transactions, etc

Originally created by @lucharo on GitHub (Mar 7, 2024). ### Verified feature request does not already exist? - [X] I have searched and found no existing issue ### 💻 - [X] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? I think the Rules capability and UX are too simple and confusing to use. I believe some features could be added to improve how rules behave and are designed. ### Describe your ideal solution to this problem - Rule notifications, in-browser notification when the rule gets executed and/or progress bar for it. - Rule history, a readable log of what rules have been run - Rule reversibility, the ability to reverse a rule being applied with a corresponding notification (much life Ctrl-Z generally would benefit from an in-browser notification displayed) - "Complex" rules + naming rules, basically more conditions for a single rule statement, e.g. account is A and (imported payee is XXX or imported payee contains XYZ, etc) - Button to run all rules manually - Ability to reorder rules, given they "are always run in the order that you see them" - Rule Flow diagram, to visualise rule order in the three phases ### Teaching and learning More examples of Rules and better informing on how to deduplicate transactions, these features I described would improve issues and frictions I have faced trying to deduplicate, recategorise transactions, etc
GiteaMirror added the needs votesfeature labels 2026-02-28 19:26:49 -06:00
GiteaMirror commented 2026-02-28 19:26:50 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 7, 2024):

✨ Thanks for sharing your idea! ✨

This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 (Mar 7, 2024): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses lodash style issue management for enhancements. That means enhancement issues are automatically closed. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 -->
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#970
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?