https://bugs.kde.org/show_bug.cgi?id=359641
--- Comment #4 from Thomas Baumgart <tbaumg...@kde.org> --- A bit of clarification: the update of the price table is an option and there is no link of the price information stored with the transaction to that entry. Imagine you enter two transactions for the same investment on the same date with two different prices and in both cases the price table is updated. In that case, the last entered price information is recorded. Now you change the date of the first entered transaction but changing the price table in that case is simply wrong. Even though this may be rare it is a potential problem. I would rather not change the price table without user intervention/acknowledgement/.... With this said, so far the application behaves as designed. > It happens most when I copy a previous transaction and edit it. That's > faster than redefining all the fields. Well, that sounds to me that the price entry in the history already happens when the duplicate is created. In that case, that is the problem and can be fixed (i.e. remove price table entry generation upon duplication). -- You are receiving this mail because: You are the assignee for the bug.
