Fix: Align task status selection with Kanban columns#142
Merged
Conversation
The status change dialog now only offers the 4 statuses that directly map to Kanban columns (Backlog, Queued/In Progress, Blocked, Done), removing the "Processing" status from user selection. Changes: - Remove StatusProcessing from status selection options in showChangeStatus() - Rename "Queued" label to "In Progress" to match Kanban column name - Add tests to verify only Kanban-mapped statuses are available - StatusProcessing remains a valid internal status for system use This resolves the confusion where users could manually select a status that didn't have a clear corresponding Kanban column, while maintaining the existing functionality where processing tasks are automatically displayed in the "In Progress" column. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
Looks like there are a few issues preventing this PR from being merged!
If you'd like me to help, just leave a comment, like Feel free to include any additional details that might help me get this PR into a better state. You can manage your notification settings |
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.
Summary
Fixes the mismatch between available task statuses when editing and Kanban column structure. The status change dialog now only offers the 4 statuses that directly map to Kanban columns, removing "Processing" from user selection.
Changes Made
StatusProcessingfrom the user-selectable status options inshowChangeStatus()StatusProcessingas a valid internal status for system useWhy This Fix?
Previously, users could manually select 5 different statuses when editing a task:
However, the Kanban board only has 4 columns. The "Processing" status was being mapped to the "In Progress" column through special logic, creating confusion about which status to use.
Solution
The status selection now matches the Kanban board structure:
queued) → In Progress columnThe
StatusProcessingstatus remains in the system and is still used internally when tasks are executing, but users can no longer manually select it.Testing
app_test.go:TestShowChangeStatus_OnlyIncludesKanbanStatuses- Verifies form creation and view stateTestShowChangeStatus_ExcludesCurrentStatus- Verifies current status is excluded from optionsRelated
Resolves task #287 - Match task statuses to Kanban column
🤖 Generated with Claude Code