https://bugs.kde.org/show_bug.cgi?id=359641
--- Comment #9 from Jan ---
I understand. Nothing urgent indeed, but it remains undesirable to have
obviously incorrect data in the database and do nothing about it. Which is why
I would consider it a bug rather than a wish after all. Issuing a warni
https://bugs.kde.org/show_bug.cgi?id=359641
--- Comment #7 from Jan ---
> When you duplicate a transaction, the new duplicate always gets the current
> date.
Correct, but he mere fact of duplicating a transaction DOES NOT create a new
price entry.
This is not just an issue with duplicated tran
https://bugs.kde.org/show_bug.cgi?id=359641
--- Comment #5 from Jan ---
(In reply to Thomas Baumgart from comment #4)
> Well, that sounds to me that the price entry in the history already happens
> when the duplicate is created.
Not quite. The problem only happens if at first the date is wrong
https://bugs.kde.org/show_bug.cgi?id=359641
--- Comment #3 from Jan ---
> Can you please let us know which recent version is still showing the problem?
The bug is in 5.08. I would be surprised it was fixed in newer versions.
> In case you haven't already figured it out, a workaround would be t
https://bugs.kde.org/show_bug.cgi?id=359641
Jan changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |CONFI
https://bugs.kde.org/show_bug.cgi?id=238454
--- Comment #22 from Jan ---
(In reply to Jack from comment #21)
> Any objections to closing this?
Not me.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=447474
Bug ID: 447474
Summary: Stored price not fixed when transaction date is
changed
Product: kmymoney
Version: 5.0.8
Platform: Other
OS: Linux
Status: REPO
