Bug 472998

Summary: Cannot move transaction
Product: [Applications] kmymoney Reporter: Dawid Wróbel <me>
Component: generalAssignee: KMyMoney Devel Mailing List <kmymoney-devel>
Status: RESOLVED DUPLICATE    
Severity: normal CC: dev+kde
Priority: NOR    
Version First Reported In: git (master)   
Target Milestone: ---   
Platform: Other   
OS: Other   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dawid Wróbel 2023-08-04 13:31:36 UTC
SUMMARY
I accidentally imported a couple of transactions into an Asset account, instead a Liability (credit card) one. However, I cannot move them to the intended account. I can right-click and choose the destination account from the list, but clicking does nothing,  there's no reaction whatsoever.

Also, I just checked and neither can I move that transaction to any other Asset account. For what it's worth, the transaction is marked as "Imported" and has its category unassigned. 

STEPS TO REPRODUCE
1. Import a transaction
2. Attempt to move it to another account via right-click menu

OBSERVED RESULT
No reaction

EXPECTED RESULT
Transaction should be moved as expected.
ADDITIONAL INFORMATION
Comment 1 Jack 2025-05-05 21:14:03 UTC
May or may not be the same (or related) but currently (freshly compiled from master) if I right click on a transaction in the ledger of an Investment account, "Move transaction to..." is disabled.  This seems true for any transaction in any investment account.  Moving is possible for all other account types I have checked.  I also see I a sent a message to the devel list in Dec 2023 for which I do not see any reply.
Comment 2 Frank Steinmetzger 2025-07-30 09:37:29 UTC
I just used kmymoney for the first time since the big change to version 5, doing my monthly expenses update. I confirm the problem, using 5.2.0 from Arch packages. I added a transaction to the wrong account, right-click it → Move transaction → select destination. Nothing happens.
Comment 3 Thomas Baumgart 2025-07-30 09:45:14 UTC

*** This bug has been marked as a duplicate of bug 507611 ***