https://bugs.kde.org/show_bug.cgi?id=267990
--- Comment #5 from Bob Connell <bobbconnell yahoo com> 2011-12-13 17:55:44 --- Hi Jack, Thanks for getting back to me. I noticed that in my proofing exercise yesterday I actually documented the more generic case where a transaction that had its state changed from withdrawal to deposit was keeping the original withdrawal aspect around as a transaction after it had been updated to turn it into a deposit in the ledger portion of the application. I checked in the "Transactions by Account" report and it correctly does not show the original withdrawal transaction but only shows the updated deposit entry after changing the original withdrawal entry in the ledger. I took your advice and closed down KMM and restarted it to get any refresh issues out of the way and it still showed the wrong thing in the "Cash Flow Transactions this Month" report. So it seems like KMM is keeping this original transaction around in its transaction storage even though it shouldn't. Maybe it's marked for a deletion that never happens and some of the reports may look at this state and ignore this transaction while others might gloss over the transaction state and end up reporting it anyway even though it shouldn't. Of course it depends on what the coder's intent is (like keeping history around for some reason, but none the less results in problems being exposed like this) as to whether this original state is valuable or not. So this is probably the same original bug, just manifesting itself in a simpler and clearer way. Let me know if you need any other help or info on this. Bob Connell ________________________________ From: Jack <ostrof...@users.sourceforge.net> To: bobbconn...@yahoo.com Sent: Tuesday, December 13, 2011 8:59 AM Subject: [Bug 267990] NUM shows up in Cash Flow Transactions report when it shouldn't https://bugs.kde.org/show_bug.cgi?id=267990 --- Comment #4 from Jack <ostroffjh users sourceforge net> 2011-12-13 16:59:08 --- Sorry - some of my comments (widget placement) actually belong to a different bug I was looking at at the same time. There have been some changes to the report code, but it would be a new bug if a report didn't reflect the most recent state of the data. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. _______________________________________________ KMyMoney-devel mailing list KMyMoney-devel@kde.org https://mail.kde.org/mailman/listinfo/kmymoney-devel
