Allow the use of multiple accounts in split transactions.

[dalaeance]

Currently, split transactions' parts can only be shown to come from the account in which the "New split" screen was opened. When you tap on the + icon to add a part, the "Account" field on the "New…split part" screen is greyed out.

Please allow us to be able to specify a different account per split part. A situation where this is handy—and I've found myself in this scenario often, the impetus for opening this issue—is when you're making a purchase at a store, restaurant, whatever, and you use a mixture of payment methods.

I often pay with cash from my wallet + my coin purse. I track the balance of each separately. Another common use case is someone using 2 cards to pay.

I guess, on the page of each account involved, it could show the something like {amount spent from account} of {total amount spent in split transaction}… or something like that.

[mtotschnig]

Thank you for the interesting suggestion. This would require a major redesign of the data structure. But I have been thinking about going into this direction which would potentially allow to use My Expenses for double entry book keeping.

[dalaeance]

No problem! I've been meaning to submit that bit of feedback for a couple weeks. Being able to use My Expenses for double entry bookkeeping would be amazing.

If/When you go down that route, I'd be happy to test and provide feedback.

[anon8675309]

I'm also willing to test (and maybe help dev) this feature. The multiple payment methods issue and double entry bookkeeping benefit are precisely the reasons I want this feature.

[anon8675309]

Can I vote to add this to the roadmap? I don't see it in the Roadmap Vote interface?

[mtotschnig]

It should appear now. I needed to add this specific label and then run the script the populates the database from issues labeled with it.

[mtotschnig]

It should appear now. I needed to add this specific label and then run the script that populates the database from issues labeled with it.

[mtotschnig]

FYI: I plan to restart a new iteration of the roadmap vote soon, so you'll likely have to recast your vote after some time.

[anon8675309]

It should appear now. I needed to add this specific label and then run the script the populates the database from issues labeled with it.

I gave it a couple days, but I don't see it. I tried restarting the app. If the new iteration is coming soon, I'll just cast my votes after the transition though, so no big deal

[mtotschnig]

Sorry for the nuisance. It seems that the app currently does not refresh from the network correctly, but sticks with an outdated cached response, even if you call Refresh from the menu. I'll investigate and fix for next version.

[mtotschnig]

@anon8675309 I also had problems receiving the updated issues for the roadmap on one device, but now I cannot reproduce the problem any more. Could you try to use the refresh menu entry on the roadmap screen and report how many issues are found and if this issue now appears?

[anon8675309]

Refreshed and it's there now. Whatever was causing the delay, but it seems to be resolved.

[dalaeance]

FYI: I plan to restart a new iteration of the roadmap vote soon, so you'll likely have to recast your vote after some time.

I'm just seeing this. Haha! I've recast my vote.