Repository navigation
Drag task cards between status columns - #25
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Task cards can now be dragged between To do, In progress and Done, including empty columns. Destination highlighting, Escape cancellation and busy-state guards keep moves predictable. The board uses the existing revision-protected save and draft-conflict recovery; priorities, sharing and all other records remain unchanged.
Touch users can drag the handle onto fixed status targets at the top of the screen. The status dropdown remains available for keyboard use. Sorting continues to follow the selected priority/name/original order rather than introducing a separate card order.
Validation: npm run check passed (57 tests). Browser checks used native desktop drag actions into populated and empty columns, verified saved status and Escape cancellation, and exercised the touch pointer-event path at a mobile viewport with no horizontal overflow. No production data has been modified.