[kmymoney] [Bug 435512] When matching an assigned and unassigned transaction, KMM may leave the resulting category empty

Thomas Baumgart bugzilla_noreply at kde.org
Fri Apr 23 06:25:34 BST 2021


Thomas Baumgart <tbaumgart at kde.org> changed:

           What    |Removed                     |Added
      Latest Commit|https://invent.kde.org/offi |https://invent.kde.org/offi
                   |ce/kmymoney/commit/2526004d |ce/kmymoney/commit/49e4e13a
                   |3ff6f80f014102fe76244190f5c |546a5b6bdfbbbcef65bdb59cc54
                   |44d7f                       |ae4ab

--- Comment #3 from Thomas Baumgart <tbaumgart at kde.org> ---
Git commit 49e4e13a546a5b6bdfbbbcef65bdb59cc54ae4ab by Thomas Baumgart.
Committed on 23/04/2021 at 05:25.
Pushed by tbaumgart into branch '5.1'.

Improve transaction merging

Transaction merging does not provide any visual feedback to the user.
This can lead to unwanted results. This mostly happeqns, when the user
selected transactions appear in an unexpected order to the matching
function and the category assignment disappears for no obvious reason.

The logic has been enhanced to check if an imported transaction which
usually does not have a category assigned shall replace an existing
transaction that has a category assignment. In this case, the selected
transactions are exchanged so that the category assignment does not
disappear. In case both transactions have more than one split, the user
is asked for confirmation of the operation.
FIXED-IN: 5.1.2

M  +5    -1    kmymoney/dialogs/kmergetransactionsdlg.cpp
M  +56   -53   kmymoney/views/kgloballedgerview_p.h


You are receiving this mail because:
You are the assignee for the bug.

More information about the KMyMoney-devel mailing list