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

[Bug]: Can't clear receiving end of an account transfer #1403

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

Originally created by @gschmidl on GitHub (Sep 9, 2024).

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

When transferring money between accounts, any 'set transaction cleared' rule is only applied to the sending account, not the receiving one.

To reproduce:

  1. Set up some kind of rule that classifies a transaction as a transfer, and make it clear the transaction.
  2. Enter a transaction that will trigger the rule.
  3. The transaction in the sending account will be cleared, but not in the receiving account.

Even trying to apply a "post" rule to the receiving account will not work, despite the rule pretending to apply to all those transactions:

image

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Windows 11

Originally created by @gschmidl on GitHub (Sep 9, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? When transferring money between accounts, any 'set transaction cleared' rule is only applied to the sending account, not the receiving one. To reproduce: 1) Set up some kind of rule that classifies a transaction as a transfer, and make it clear the transaction. 2) Enter a transaction that will trigger the rule. 3) The transaction in the sending account will be cleared, but not in the receiving account. Even trying to apply a "post" rule to the receiving account will not work, despite the rule pretending to apply to all those transactions: ![image](https://github.com/user-attachments/assets/683f4027-5b2a-41b5-b77e-71b3a019266a) ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Windows 11
GiteaMirror added the bug label 2026-02-28 19:42:46 -06:00
GiteaMirror commented 2026-02-28 19:42:46 -06:00
Author
Owner
Copy Link

@gschmidl commented on GitHub (Sep 9, 2024):

Dupe of #3229 - sorry.

@gschmidl commented on GitHub (Sep 9, 2024): Dupe of #3229 - sorry.
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 bug
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#1403
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?