[kmymoney] [Bug 359641] Inconsistent date in price table

[Jan]

https://bugs.kde.org/show_bug.cgi?id=359641

--- Comment #3 from Jan <jan_cecile at verizon.net> ---
> 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 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.

The price is correct.  Only the date is wrong.

> However, I don't imagine it is often necessary to change the date of
> such a transaction, other then correcting a data entry error.

It happens most when I copy a previous transaction and edit it.  That's faster
than redefining all the fields.

> 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.

So the prices stored as a history are not linked to transactions, if that's how
they have been defined.

I think there should be no confusion possible, as the price for which the date
needs to be changed must be exactly the same as in the transaction that is
being edited.  If there is another transaction for the same security on the
same day, either the price will be different, or else it does not matter which
one is changed (that is, if both the date and the price are the same).

If the edit changes both date and price,  the same applies.

-- 
You are receiving this mail because:
You are the assignee for the bug.