Comment 5 for bug 2012669

Testing for bug squashing, I was able to test all reset reason scenarios, except for HOLD_TIMED_OUT and HOLD_BETTER_HOLD. These are so helpful!

A few comments:
- In the description above, it was noted that the workstation for the user would be listed, but I don't see that column in the Reset Entries tab
- Wondering if it would be possible or helpful to track the following within the HOLD_UPDATED reason to encompass all possible updates: Set Desired Item Quality, Edit Notification Settings, Set and Unset to Top of Queue, and Edit Hold Dates (currently, changing the activation date within Edit Hold Dates results in the HOLD_FROZEN reason, so that wouldn't need to be in HOLD_UPDATED, but I think it could be helpful to know if any of the dates changed and which ones). I love the "pickup_lib value changed" note in HOLD_UPDATED and think that would be very helpful in all update scenarios.
- In the same vein, I think it would be helpful to provide notes for the HOLD_MANUAL_RESET reason; in testing, Mark Item Damaged, Mark Item Missing, and Find Another Target triggered this reason