To recreate: - set an item to lost=1 - get the itemlost_on value for your item from the database - change the item to lost=2 - get the itemlost_on value again, confirm that the time hasn't changed I'm sort of torn on this. Just now, we ran into an issue where it we needed to know when a lost value was changed. But I can also imagine a situation where one would want to know when an item became lost originally.
I think the current behaviour is correct. Maybe the cataloguing logs should be used to know when the lost's value has been edited?
(In reply to Jonathan Druart from comment #1) > I think the current behaviour is correct. Maybe the cataloguing logs should > be used to know when the lost's value has been edited? +1