github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-06-20 20:08:08 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #3244] [Feature] Manually trigger rules / or trigger rules after the payee is set on an existing transaction #8263

New Issue
Closed
opened 2026-04-10 18:28:14 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-10 18:28:14 -05:00
Owner
Copy Link

Originally created by @esseti on GitHub (Aug 12, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/3244

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've several rules that make conditions based on the payee.
i sync my account via bank sync and THEN i set the correct payee manually
done in this way, the rule are not triggered.
I would like to apply the rules AFTER is set manually the payee.

Describe your ideal solution to this problem

A butto that "triggers" the rules, if too heavy for the computation, then re-apply rules just for the selected transactions.

Teaching and learning

No response

Originally created by @esseti on GitHub (Aug 12, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/3244 ### 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've several rules that make conditions based on the payee. i sync my account via bank sync and THEN i set the correct payee manually done in this way, the rule are not triggered. I would like to apply the rules AFTER is set manually the payee. ### Describe your ideal solution to this problem A butto that "triggers" the rules, if too heavy for the computation, then re-apply rules just for the selected transactions. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-04-10 18:28:14 -05:00
GiteaMirror commented 2026-04-10 18:28:15 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 12, 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 👍!

<!-- gh-comment-id:2283411302 --> @github-actions[bot] commented on GitHub (Aug 12, 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 -->
GiteaMirror commented 2026-04-10 18:28:15 -05:00
Author
Owner
Copy Link

@esseti commented on GitHub (Aug 12, 2024):

Inside the rule page, when you see the editing, in the part below one can select all the transaction and apply the rule.

<!-- gh-comment-id:2283810301 --> @esseti commented on GitHub (Aug 12, 2024): Inside the rule page, when you see the editing, in the part below one can select all the transaction and apply the rule.
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
tech-support
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#8263
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?