Skip to content

When moving to the next column, timestamp we sort by shou...#1787

Merged
lukemarsden merged 3 commits intomainfrom
feature/001412-when-moving-to-the-next
Mar 2, 2026
Merged

When moving to the next column, timestamp we sort by shou...#1787
lukemarsden merged 3 commits intomainfrom
feature/001412-when-moving-to-the-next

Conversation

@lukemarsden
Copy link
Collaborator

Helix: When moving to the next column, timestamp we sort by should be updated so that it appears at the top of the next column, otherwise it's hard to find. Kanban board in helix frontend

Add StatusUpdatedAt field to SpecTask that tracks when status last changed.
Tasks now appear at the top of their column when moved (via button clicks,
agent actions, or git triggers).

Changes:
- Add StatusUpdatedAt field to SpecTask struct
- Update all status change handlers to set StatusUpdatedAt
- Set StatusUpdatedAt on task creation in store layer
- Change ListSpecTasks sort order to status_updated_at DESC NULLS LAST, created_at DESC
- Regenerate OpenAPI client

Fixes: When moving to the next column, timestamp we sort by should be
updated so that it appears at the top of the next column

Spec-Ref: helix-specs@cdf007baa:001412_when-moving-to-the-next
Spec-Ref: helix-specs@d4681f38c:001412_when-moving-to-the-next
The test was failing because it expected exact match between the LLM's
exchange rate response and the live rate. Exchange rates fluctuate, so
we now use InDelta with 0.5 tolerance instead of exact equality.

Spec-Ref: helix-specs@d4681f38c:001412_when-moving-to-the-next
@lukemarsden lukemarsden merged commit 9aea80c into main Mar 2, 2026
2 of 3 checks passed
@lukemarsden lukemarsden deleted the feature/001412-when-moving-to-the-next branch March 2, 2026 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant