Bug 446819 - Transaction details lost after split transaction with only one entry
Summary: Transaction details lost after split transaction with only one entry
Status: REPORTED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.1.2
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-11 08:10 UTC by Paul Menzel
Modified: 2021-12-17 14:32 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Menzel 2021-12-11 08:10:42 UTC
STEPS TO REPRODUCE
1. Have a transaction (Buchung) (transferred from Bank) with a comment/detail.
2. Edit it, and go into the split booking(?) (Split-Buchung) dialog
3. Only enter one entry, and confirm by pressing enter.

OBSERVED RESULT

The comment/detail is deleted.

EXPECTED RESULT

The comment/detail should be preserved, especially as there is no way to undo it, unless to close the file without saving it, and open the former version again.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian sid/unstable with Linux 5.16-rc3
KDE Plasma Version: no shown/installed
KDE Frameworks Version: 5.88.0-1
Qt Version: 5.15.2+dfsg-14
Comment 1 Thomas Baumgart 2021-12-11 17:33:05 UTC
Git commit 2d3a8217b6300e7b812919becfd62ec0739adb89 by Thomas Baumgart.
Committed on 11/12/2021 at 17:32.
Pushed by tbaumgart into branch 'master'.

Keep the memo of a split when opening the split editor

In case the split editor is opened and the transaction only consists out
of one split (missing category assignment) the user could accidently
clear the memo text. This change keeps the memo with the initial split.

M  +7    -0    kmymoney/views/newtransactioneditor.cpp

https://invent.kde.org/office/kmymoney/commit/2d3a8217b6300e7b812919becfd62ec0739adb89
Comment 2 Jack 2021-12-16 21:28:40 UTC
I see that commit went to master only.  Will it get backported to 5.x or is it only in the new ledger?  Should the commit close the bug?
Comment 3 Thomas Baumgart 2021-12-17 14:32:52 UTC
I left the bug open, because a possible 5.1 fix looks completely different. At the same time, I wanted to leave a trace that it is fixed in master.