2.4 KiB
id, title, status, wave, depends_on, plan, requirements, acceptance_criteria, system_design
| id | title | status | wave | depends_on | plan | requirements | acceptance_criteria | system_design | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 01-implement-kanban-task-reordering | Implement Kanban task reordering | completed | 1 | plan.md |
|
|
|
Task 01: Implement Kanban task reordering
Scope
Add the persisted reorder contract across the task repository and service, HTTP and WebSocket transport, Kanban state, and desktop and mobile board surfaces. Keep band membership derived from task state and keep workflow-step changes on their existing path.
Implementation
- Validate task-write authorization and the complete band membership before writing positions.
- Lock the workspace, source, and target step rows in a stable order, then allocate dense positions for the two bands.
- Publish step revisions with the reordered task positions.
- Apply HTTP and WebSocket updates to both workflow snapshots and the main Kanban task projection, while retaining the newest buffered revision.
- Support pointer and keyboard reorder interactions in the Kanban surfaces; keep Pipeline display-only.
Verification
Focused backend service, handler, and repository tests cover authorization, HTTP errors, source-step lock drift, and persisted ordering. Focused frontend tests cover HTTP/WebSocket revision reconciliation and both Kanban projections. Web type checking, scoped lint and formatting, and the affected post-merge Kanban tests pass.
References
The requirement and system design define the complete ordering, validation, concurrency, and presentation contract. This work order records the delivery slice for that contract and its regression evidence.
Mobile follow-up
Remove mobile Kanban dragging replaces the phone drag interaction and positive mobile reorder test. This completed package retains its historical results; desktop/tablet and backend scope remain.