Bug 37688

Summary: Staff biblio detail view shows last_seen_date as date instead of datetime
Product: Koha Reporter: Lucas Gass (lukeg) <lucas>
Component: Staff interfaceAssignee: Lucas Gass (lukeg) <lucas>
Status: RESOLVED DUPLICATE QA Contact: Paul Derscheid <paul.derscheid>
Severity: minor    
Priority: P5 - low CC: barbara.johnson, gmcharlt, laura, paul.derscheid
Version: Main   
Hardware: All   
OS: All   
Change sponsored?: --- Patch complexity: Trivial patch
Documentation contact: Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:
Attachments: Bug 37688: Change last_seen_date column to datetime
Bug 37688: Change last_seen_date column to datetime

Description Lucas Gass (lukeg) 2024-08-20 14:45:32 UTC
In the biblio detail view ( holdings table ) the "Last seen" column used to display a datetime, not it only displays a date. 

I suspect this was due to the change in Bug 33568.
Comment 1 Lucas Gass (lukeg) 2024-08-20 19:41:14 UTC
Created attachment 170505 [details] [review]
Bug 37688: Change last_seen_date column to datetime

To test:
1. Bring up some items in staff detail view ( holdings table )
2. If the "Last seen" column is hidden unhide it via Table settings
3. Notice that the column shows only the date.
4. APPLY PATCH
5. Look now and you should see it is datetime.
6. Make sure it is accurate.
Comment 2 ByWater Sandboxes 2024-08-20 20:11:16 UTC
Created attachment 170506 [details] [review]
Bug 37688: Change last_seen_date column to datetime

To test:
1. Bring up some items in staff detail view ( holdings table )
2. If the "Last seen" column is hidden unhide it via Table settings
3. Notice that the column shows only the date.
4. APPLY PATCH
5. Look now and you should see it is datetime.
6. Make sure it is accurate.

Signed-off-by: Laura ONeil <laura@bywatersolutions.com>
Comment 3 Paul Derscheid 2024-10-28 14:20:03 UTC
There's something weird going on here. When I wanted to QA this, git bz told me that the patch was already applied.

Bug 38146: commit d60057b429de3a522c5140002746a610150dc540.

*** This bug has been marked as a duplicate of bug 38146 ***