[Feature] Ability to split transfer transactions #52

New Issue

GiteaMirror · 2026-02-28T18:46:43-06:00

GiteaMirror commented

2026-02-28 18:46:43 -06:00

Originally created by @irandamay on GitHub (Mar 12, 2022).

It's not immediately obvious if you want to create a new split transfer that you need to choose to split the transaction first before you enter the payee/transfer. Once you choose the transfer account as the payee, it's then locked into being a single transfer transaction, even though the category field can be selected like it can be changed.

Originally created by @irandamay on GitHub (Mar 12, 2022). It's not immediately obvious if you want to create a new split transfer that you need to choose to split the transaction first before you enter the payee/transfer. Once you choose the transfer account as the payee, it's then locked into being a single transfer transaction, even though the category field can be selected like it can be changed.

GiteaMirror closed this issue

2026-02-28 18:46:44 -06:00

GiteaMirror commented

2026-02-28 18:46:44 -06:00

@rich-howell commented on GitHub (Oct 21, 2022):

There was some confusion with this issue, I moved it to documentation as I thought it needed explaining better on how something worked, then tagged the wrong issue when resolving a docs PR.

Spoke to @irandamay who confirmed this should be more of a "you should be able to change it and you can't" type thing.

Raising as a bug.

@rich-howell commented on GitHub (Oct 21, 2022): There was some confusion with this issue, I moved it to documentation as I thought it needed explaining better on how something worked, then tagged the wrong issue when resolving a docs PR. Spoke to @irandamay who confirmed this should be more of a "you should be able to change it and you can't" type thing. Raising as a bug.

GiteaMirror commented

2026-02-28 18:46:45 -06:00

@MatissJanis commented on GitHub (May 5, 2023):

👋 I would consider this more of a feature request than a bug. So I'll label it as such and lets see if we can get more support from the community to get this implemented.

@MatissJanis commented on GitHub (May 5, 2023): :wave: I would consider this more of a feature request than a bug. So I'll label it as such and lets see if we can get more support from the community to get this implemented.

GiteaMirror commented

2026-02-28 18:46:45 -06:00

@github-actions[bot] commented on GitHub (May 5, 2023):

✨ Thanks for sharing your idea! ✨

This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 (May 5, 2023): :sparkles: Thanks for sharing your idea! :sparkles: This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open. This doesn’t mean we don’t accept feature requests, though! We will consider implementing ones that receive many upvotes, and we welcome contributions for any feature requests marked as needing votes (just post a comment first so we can help you make 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 👍!