Description
Dragging a card on the Kanban board to a different column does not always update the work item state. The drag sometimes succeeds and sometimes silently fails — the card snaps back to its original column with no visible error.
Steps to Reproduce
- Go to
/kanban
- Drag a card from one column to another (e.g. Active → Resolved)
- Repeat several times across different cards / columns
Expected Behavior
Every successful drop should trigger a state change in Azure DevOps and the card should remain in the new column after the next refresh.
Actual Behavior
Intermittently the card snaps back to the original column. The state PATCH either does not fire or fails silently — no error toast is shown to the user.
Environment
- OS: Windows 11 Pro
- Browser: Edge
- Version: 0.8.1 (current
main)
Additional Context
Needs investigation — possibly related to:
- The dnd-kit drag-end vs drag-cancel handlers in
KanbanGroupSection.tsx
- Race condition between optimistic local state and the server PATCH / refetch
- Pointer activation distance (currently 8px) interpreting click-and-release as a non-drag
The user should see a clear failure indicator if the PATCH fails, instead of silently snapping back.
Description
Dragging a card on the Kanban board to a different column does not always update the work item state. The drag sometimes succeeds and sometimes silently fails — the card snaps back to its original column with no visible error.
Steps to Reproduce
/kanbanExpected Behavior
Every successful drop should trigger a state change in Azure DevOps and the card should remain in the new column after the next refresh.
Actual Behavior
Intermittently the card snaps back to the original column. The state PATCH either does not fire or fails silently — no error toast is shown to the user.
Environment
main)Additional Context
Needs investigation — possibly related to:
KanbanGroupSection.tsxThe user should see a clear failure indicator if the PATCH fails, instead of silently snapping back.