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

[GH-ISSUE #7036] [Feature] allow unlinking manually linked transfer transactions #52076

New Issue
Closed
opened 2026-04-30 20:14:58 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-30 20:14:58 -05:00
Owner
Copy Link

Originally created by @zdimension on GitHub (Feb 20, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7036

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?

Say you have two transactions in your database. They already exist, for example from bank sync. You mark them as a transfer, using the transfer selection menu, but then later notice that was a mistake. Ctrl+Z only works immediately after, but assume you notice your mistake a long time later. There is no direct way to unlink the two transactions: changing the payee on one or the other of the transactions will delete the other.

The fastest way I found is to duplicate the first one, change its payee (which deletes the duplicated second), then change the payee of the original second (which deletes the original first one). You then end up with two transactions that are not linked. One could also simply delete both and recreate them from scratch, but this loses you the imported payee infio. Duplicating-and-deleting is currently the only lossless way to do this.

Describe your ideal solution to this problem

I think if exactly two transactions are selected, and the two are linked to each other, the "Make transfer" menu (which is currently greyed out in that case) simply should become something like "Unlink transfer" and clicking on it would just assign null to the payee and category of both, so the user can carry on.

I think this could also be made to show if exactly one transaction is selected and it's part of a transfer. Maybe clicking the action would then show "This will modify the matching transaction: [transaction info]".

Teaching and learning

I think putting it in the same place transfers are made is enough for discoverability. That's where I would look for it, at least.

Originally created by @zdimension on GitHub (Feb 20, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7036 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [x] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? Say you have two transactions in your database. They already exist, for example from bank sync. You mark them as a transfer, using the transfer selection menu, but then later notice that was a mistake. Ctrl+Z only works immediately after, but assume you notice your mistake a long time later. There is no direct way to unlink the two transactions: changing the payee on one or the other of the transactions will delete the other. The fastest way I found is to duplicate the first one, change its payee (which deletes the duplicated second), then change the payee of the original second (which deletes the original first one). You then end up with two transactions that are not linked. One could also simply delete both and recreate them from scratch, but this loses you the imported payee infio. Duplicating-and-deleting is currently the only lossless way to do this. ### Describe your ideal solution to this problem I think if exactly two transactions are selected, and the two are linked to each other, the "Make transfer" menu (which is currently greyed out in that case) simply should become something like "Unlink transfer" and clicking on it would just assign null to the payee and category of both, so the user can carry on. I think this could also be made to show if exactly one transaction is selected and it's part of a transfer. Maybe clicking the action would then show "This will modify the matching transaction: [transaction info]". ### Teaching and learning I think putting it in the same place transfers are made is enough for discoverability. That's where I would look for it, at least.
GiteaMirror added the needs votesfeature labels 2026-04-30 20:14:59 -05:00
GiteaMirror commented 2026-04-30 20:15:02 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 20, 2026):

✨ 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 👍!

<!-- gh-comment-id:3932435561 --> @github-actions[bot] commented on GitHub (Feb 20, 2026): :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#52076
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?