https://bugs.kde.org/show_bug.cgi?id=359641
Jack <ostrof...@users.sourceforge.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ostroffjh@users.sourceforge
| |.net
--- Comment #2 from Jack <ostrof...@users.sourceforge.net> ---
Jan,
Thanks for the update. Can you please let us know which recent version is
still showing the problem?
In case you haven't already figured it out, a workaround would be to edit the
price entry after editing the transaction, although I know that means you
would have to know/remember that the transaction created the price entry.
However, I don't imagine it is often necessary to change the date of such a
transaction, other then correcting a data entry error.
Just as a note, aside from correcting the price entry, it would be necessary to
check for any other transactions for the same security on the same date, to ask
the user if they also need to have their date changed. If not, then the action
would be to create a new price entry, not just to change the date of the
existing one.
--
You are receiving this mail because:
You are the assignee for the bug.
