Bug 26117

Summary: itemlost_on value should be updated when item changes from one lost value to another
Product: Koha Reporter: Andrew Fuerste-Henry <andrew>
Component: CatalogingAssignee: Bugs List <koha-bugs>
Status: CLOSED WONTFIX QA Contact: Testopia <testopia>
Severity: normal    
Priority: P5 - low CC: jonathan.druart, m.de.rooy
Version: Main   
Hardware: All   
OS: All   
GIT URL: Initiative type: ---
Sponsorship status: --- Comma delimited list of Sponsors:
Crowdfunding goal: 0 Patch complexity: ---
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:

Description Andrew Fuerste-Henry 2020-07-31 16:09:32 UTC
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.
Comment 1 Jonathan Druart 2020-08-03 10:50:35 UTC
I think the current behaviour is correct. Maybe the cataloguing logs should be used to know when the lost's value has been edited?
Comment 2 Katrin Fischer 2023-09-16 17:04:46 UTC
(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