1f58786c1a
The dashboard task-edit route destructured every editable body field except priority, so changing priority via the task-detail modal was silently dropped before reaching store.updateTask. Wire priority through with isTaskPriority validation (null resets to default). Without this fix the priority-aware triage/scheduler/merge ordering shipped previously had no effect for tasks edited in the dashboard. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
6 lines
663 B
Markdown
6 lines
663 B
Markdown
---
|
|
"@runfusion/fusion": patch
|
|
---
|
|
|
|
Fix `PATCH /tasks/:id` silently dropping task priority updates. The route handler in the dashboard server was destructuring every editable field from the request body except `priority`, so changing a task's priority via the dashboard task-detail modal had no effect on disk. The handler now accepts `priority`, validates it against the allowed values (`urgent`, `high`, `normal`, `low`) — `null` resets to the default — and forwards it to `store.updateTask`. Combined with the priority-aware merge queue and sweep ordering shipped earlier, dashboard priority changes now actually shift triage, scheduling, and merge order.
|