Bug 26117 - itemlost_on value should be updated when item changes from one lost value to another
Summary: itemlost_on value should be updated when item changes from one lost value to ...
Status: RESOLVED WONTFIX
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-31 16:09 UTC by Andrew Fuerste-Henry
Modified: 2023-09-16 17:04 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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