github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-10 04:02:38 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Feature] Rule action for basic calculation instead of only being able to set it #1391

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

Originally created by @dj-bauer on GitHub (Sep 6, 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?

When creating a rule there is already the possibility to set the amount transferred, but now i would like basic arithmetic functionality or at least multiplying by a factor.

My usecase is this:
I have an account for cash, and one for my Food court balance.
When I load up my food card with more than 20€ at a time, i get a 5% bonus.
So far we can add the following rule for this:

if
    account is Cash
    payee is Mensa
    amount is greater  equal 20€
then
    set amount to 21€

I believe this functionality could be useful to a number of applications, where you get bonuses or similar.

Describe your ideal solution to this problem

My imagined way of implementing this functionality in the user interface would be by adding a fourth action.
So far we have the action set, prepend to notes and append to notes.

We could add another field, that says calculate which lets you select an operation like for the start +, -, *, /.
Each of these operations obviously has two operands associated with it, so two fields show up, which can either be filled with variables associated with the transaction, or constant values.
This would allow an action like the following:
calculate amount as "amount * 1.05"
So the action would be calculate of the type Multiplication and it has the transaction field amount and the constant 1.05 associated with it.

Teaching and learning

We could expand the tab of actions in the Rule documentation entry.

Originally created by @dj-bauer on GitHub (Sep 6, 2024). ### 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 creating a rule there is already the possibility to set the amount transferred, but now i would like basic arithmetic functionality or at least multiplying by a factor. My usecase is this: I have an account for cash, and one for my Food court balance. When I load up my food card with more than 20€ at a time, i get a 5% bonus. So far we can add the following rule for this: ``` if account is Cash payee is Mensa amount is greater equal 20€ then set amount to 21€ ``` I believe this functionality could be useful to a number of applications, where you get bonuses or similar. ### Describe your ideal solution to this problem My imagined way of implementing this functionality in the user interface would be by adding a fourth action. So far we have the action *set*, *prepend to notes* and *append to notes*. We could add another field, that says **calculate** which lets you select an operation like for the start +, -, *, /. Each of these operations obviously has two operands associated with it, so two fields show up, which can either be filled with variables associated with the transaction, or constant values. This would allow an action like the following: `calculate amount as "amount * 1.05"` So the action would be calculate of the type Multiplication and it has the transaction field amount and the constant 1.05 associated with it. ### Teaching and learning We could expand the tab of actions in the Rule documentation entry.
GiteaMirror added the needs votesfeature labels 2026-02-28 19:42:23 -06:00
GiteaMirror commented 2026-02-28 19:42:24 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 6, 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 (Sep 6, 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#1391
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?