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 #5715] [Bug]: Duplicating a split transaction does not respect the original split order #51589

New Issue
Closed
opened 2026-04-30 18:27:28 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-30 18:27:28 -05:00
Owner
Copy Link

Originally created by @cculbertson81 on GitHub (Sep 11, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5715

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Fairly self-explanatory. When duplicating a split transaction, the duplicate transaction creates the splits in a different order than the original.

How can we reproduce the issue?

  1. Create a split transaction. Creating several splits makes it easier to see the issue.
  2. Duplicate the split transaction.
  3. Compare the order of splits in the original and duplicate transaction.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @cculbertson81 on GitHub (Sep 11, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5715 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Fairly self-explanatory. When duplicating a split transaction, the duplicate transaction creates the splits in a different order than the original. ### How can we reproduce the issue? 1. Create a split transaction. Creating several splits makes it easier to see the issue. 2. Duplicate the split transaction. 3. Compare the order of splits in the original and duplicate transaction. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the transactionsbuggood first issue labels 2026-04-30 18:27:28 -05:00
GiteaMirror commented 2026-04-30 18:27:31 -05:00
Author
Owner
Copy Link

@guizaa commented on GitHub (Oct 12, 2025):

Hello, I have made a PR #5911 that fixes this issue. Let me know if there is any feedback!

<!-- gh-comment-id:3394540460 --> @guizaa commented on GitHub (Oct 12, 2025): Hello, I have made a PR #5911 that fixes this issue. Let me know if there is any feedback!
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#51589
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?