Sort schedules by creation date (newest first) in Shift Build view #97

New issue

Closed

opened 2026-05-21 19:23:48 -04:00 by owlburtoe · 1 comment

owlburtoe commented

2026-05-21 19:23:48 -04:00

Owner

Problem

In the Shift Build → Schedules section, schedules are currently ordered with the oldest created schedule at the top and newest at the bottom. This forces users to scroll to find the most recently created schedule, which is typically the one they're actively working on.

Expected Behavior

Schedules should be sorted by creation date in descending order (newest first). The most recently created schedule appears at the top without requiring scrolling.

Acceptance Criteria

Schedules in the Build → Schedules view display newest-created first
Sort order is consistent across page reloads
All existing tests pass
No new test failures introduced

Notes

This is a simple ordering change; no data model or API contract changes needed
The change should be applied at the query/sort level, not in post-fetch filtering
The most common use case is the newest schedule being the actionable one

## Problem In the Shift Build → Schedules section, schedules are currently ordered with the oldest created schedule at the top and newest at the bottom. This forces users to scroll to find the most recently created schedule, which is typically the one they're actively working on. ### Expected Behavior Schedules should be sorted by creation date in descending order (newest first). The most recently created schedule appears at the top without requiring scrolling. ### Acceptance Criteria - [ ] Schedules in the Build → Schedules view display newest-created first - [ ]Sort order is consistent across page reloads - [ ] All existing tests pass - [ ] No new test failures introduced #### Notes This is a simple ordering change; no data model or API contract changes needed The change should be applied at the query/sort level, not in post-fetch filtering The most common use case is the newest schedule being the actionable one

owlburtoe added the

feature

agent:hermes

labels

2026-05-21 19:23:48 -04:00

owlburtoe added the

status:ready

label

2026-05-21 20:27:28 -04:00

owlburtoe commented

2026-05-21 20:34:41 -04:00

Author

Owner

Hermes saw this issue and queued it for attention.

Labels detected: agent:hermes + status:ready.
Telegram notification sent by the Shiftd Hermes issue watchdog.

Next step: ask Hermes to work issue #97 when you want implementation to start.

Hermes saw this issue and queued it for attention. Labels detected: `agent:hermes` + `status:ready`. Telegram notification sent by the Shiftd Hermes issue watchdog. Next step: ask Hermes to `work issue #97` when you want implementation to start.

owlburtoe referenced this issue from a pull request that will close it,

2026-05-21 21:00:51 -04:00

fix: sort schedules newest-first #98

owlburtoe closed this issue

2026-05-21 21:19:34 -04:00