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

[Feature] merging transactions should maintain splits #2294

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

Originally created by @sexyskinnybitch on GitHub (Jul 20, 2025).

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?

Currently, the merge function maintains the imported transaction, losing any splits in the manually entered one. Several times I have manually entered a transaction with splits, later merged it with the one imported from the bank, only to discover that my splits disappeared.

Describe your ideal solution to this problem

When merging transactions, if one has splits, the splits should be kept.

Teaching and learning

No response

Originally created by @sexyskinnybitch on GitHub (Jul 20, 2025). ### 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? Currently, the merge function maintains the imported transaction, losing any splits in the manually entered one. Several times I have manually entered a transaction with splits, later merged it with the one imported from the bank, only to discover that my splits disappeared. ### Describe your ideal solution to this problem When merging transactions, if one has splits, the splits should be kept. ### Teaching and learning _No response_
GiteaMirror added the needs votesfeature labels 2026-02-28 20:09:23 -06:00
GiteaMirror commented 2026-02-28 20:09:24 -06:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 20, 2025):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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 (Jul 20, 2025): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward 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#2294
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?