[Feature] Manually trigger rules / or trigger rules after the payee is set on an existing transaction #1324

Closed
opened 2026-02-28 19:40:30 -06:00 by GiteaMirror · 2 comments
Owner

Originally created by @esseti on GitHub (Aug 12, 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'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). ### 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-02-28 19:40:30 -06:00
Author
Owner

@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 👍!

@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 -->
Author
Owner

@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.

@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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#1324