Bug #219
closed
Sleep sessions are sorted incorrectly on the reports page
Added by Sam Pearson 23 days ago.
Updated 19 days ago.
Description
Similar to ticket #214 but everything appears to be in order except the "snooze cruise" event:
Report for 2026-06-23:
Snooze Cruise
2026-06-23T21:00:00 - 2026-06-23T00:00:00
This is the first item on the list, but 9pm to midnight should be the last event. It also displays the same date for start and end time.
- Target version set to V2.2.1 - Usability MVP
- Status changed from New to Open
The timestamps are both on the same day
2026-06-23T21:00:00 - 2026-06-23T00:00:00
But this ticket is still valid; the frontend seems to be reordering the sessions or something; the API puts this session at the end of the day, because the API sorts by start_time , end time doesn't matter.
- Status changed from Open to Resolved
Sessions were being sorted by creation_date instead of start_time.
Fixed, tested locally, works great.
Also the search tool was adjusting timestamps to account for timezones, fixed that as well.
All session sorting now matches the provided timestamps and is sorted correctly.
- Status changed from Resolved to Closed
Also available in: Atom
PDF