github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #6516] [Bug]: Unclearing the main Split Transaction does NOT unclear the splits #51877

New Issue
Closed
opened 2026-04-30 19:39:50 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-30 19:39:50 -05:00
Owner
Copy Link

Originally created by @SpookyUSAF on GitHub (Dec 31, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6516

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

A bug happened! If you unclear the main split transaction, all of it's splits should follow the same clear/unclear command as the main transaction.

How can we reproduce the issue?

How can we reproduce the issue? Simple... Create a split transaction, then clear and lock it. Then unclear the primary transaction and run an export. Notice in the CSV that the splits remain cleared.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Microsoft Edge

Operating System

Windows 11

Originally created by @SpookyUSAF on GitHub (Dec 31, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6516 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? A bug happened! If you unclear the main split transaction, all of it's splits should follow the same clear/unclear command as the main transaction. ### How can we reproduce the issue? How can we reproduce the issue? Simple... Create a split transaction, then clear and lock it. Then unclear the primary transaction and run an export. Notice in the CSV that the splits remain cleared. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Microsoft Edge ### Operating System Windows 11
GiteaMirror added the transactionsgood first issuebug labels 2026-04-30 19:39:53 -05:00
GiteaMirror commented 2026-04-30 19:39:58 -05:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Apr 29, 2026):

Fixed by #7453

<!-- gh-comment-id:4345649137 --> @youngcw commented on GitHub (Apr 29, 2026): Fixed by #7453
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 good first issue transactions
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#51877
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?