[Kmymoney-devel] [kmymoney4] [Bug 319807] New transaction from memorised carries old memo
Mark Blakeney
mark.blakeney at bullet-systems.net
Tue Sep 10 22:51:40 UTC 2013
https://bugs.kde.org/show_bug.cgi?id=319807
--- Comment #4 from Mark Blakeney <mark.blakeney at bullet-systems.net> ---
Oh no, the fact that you say "In your case", and then "you'd like" shows that I
have failed to communicate that this problem has nothing to do with anybody's
personal preferences and is just a straight out flaw. :(
KMM automatically copies the main transaction memo to the primary split of an
auto VAR/GST transaction (and it does the auto splitting well which is one of
the reasons I chose KMM over Gnucash 7 years ago when I migrated from Quicken).
The problem is that if you add a second or later transaction, based on that
original "memorised" transaction, and of course you add a new memo as well,
then KMM does not copy that new memo to the new primary split. The bug is that
it keeps the memo from the 1st original transaction.
So, e.g., I may buy a Macbook from Apple Store one month, next month I buy an
iPad, next month I buy an iPhone. When I produce an expenditure report all
those transactions are listed with a memo "Macbook" even though I explicitly
wrote "iPad", and then "iPhone" on the memo field of the new Apple Store
transactions (note the expenditure report lists per category, i.e. per split).
The only way around this is to edit the split of the new transactions and
manually rewrite the (hidden) memo field a second time for every entry. Surely
you can see this is a bug?
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the KMyMoney-devel
mailing list