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

[PR #2652] Template only the relevant amount in a split-schedule category #4435

New Issue
Closed
opened 2026-02-28 20:55:47 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-28 20:55:47 -06:00
Owner
Copy Link

Original Pull Request: https://github.com/actualbudget/actual/pull/2652

State: closed
Merged: Yes

As it says on the tin. For the logic, there are a few cases to consider; open to changing any of these, but these ones seem logical to me:

  • Category that corresponds to some parts of a split: the category gets the sum of all splits that match the category
    => e.g., if you have a split with "personal trainer" and "gym membership", you can template a "personal trainer" category that just receives the amount due there.
  • Category that corresponds to all parts of a split: the category gets the sum of all splits
    => self-explanatory, the split belongs to only one category

These ones are more subject to change:

  • Category that corresponds to no part of a split: the category gets the sum of all splits
    => this is so that if you write "#template schedule foo" in a category that's unrelated, you don't end up with "0" of the schedule
  • Category that contains a regular rule with a changed amount
    => I think this part is most open to change. This is so that if you add a schedule with a that overwrites the transaction amount, the overwritten amount will get used. I don't see a use-case for overwriting the transaction amount, but it's an option the UI supports so IMO it could be worth handling here
**Original Pull Request:** https://github.com/actualbudget/actual/pull/2652 **State:** closed **Merged:** Yes --- As it says on the tin. For the logic, there are a few cases to consider; open to changing any of these, but these ones seem logical to me: - Category that corresponds to some parts of a split: the category gets the sum of all splits that match the category => e.g., if you have a split with "personal trainer" and "gym membership", you can template a "personal trainer" category that just receives the amount due there. - Category that corresponds to all parts of a split: the category gets the sum of all splits => self-explanatory, the split belongs to only one category These ones are more subject to change: - Category that corresponds to no part of a split: the category gets the sum of all splits => this is so that if you write "#template schedule foo" in a category that's unrelated, you don't end up with "0" of the schedule - Category that contains a regular rule with a changed amount => I think this part is most open to change. This is so that if you add a schedule with a that _overwrites_ the transaction amount, the overwritten amount will get used. I don't see a use-case for overwriting the transaction amount, but it's an option the UI supports so IMO it could be worth handling here
GiteaMirror added the pull-request label 2026-02-28 20:55:47 -06:00
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 pull-request
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#4435
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?