Skip to content

fix: resolve statuses from list before falling back to space#5

Merged
isaacrowntree merged 1 commit intomainfrom
fix/list-custom-statuses
Mar 11, 2026
Merged

fix: resolve statuses from list before falling back to space#5
isaacrowntree merged 1 commit intomainfrom
fix/list-custom-statuses

Conversation

@isaacrowntree
Copy link
Contributor

Summary

  • Status validation now checks list-level statuses first, falling back to space statuses only if the list has no custom overrides
  • Fixes lists with custom statuses (e.g. "in development", "verification+") being rejected because only space-level statuses were checked
  • Avoids redundant API calls in task create by reusing the already-fetched list object

Fixes #4

Test plan

  • All existing tests pass (go test ./...)
  • New status_test.go covers: exact match, case-insensitive, contains, fuzzy, no-match error, list-vs-space status scenarios
  • Manual: clickup status set "in development" <task-in-list-with-custom-statuses>
  • Manual: clickup task edit <id> --status "in development" on a list with custom statuses
  • Manual: clickup task create --list-id <list-with-custom-statuses> --status "in development"

🤖 Generated with Claude Code

Lists with custom status overrides were ignored — status validation
always used space-level statuses, causing valid list statuses like
"in development" to fail with "no matching status found".

Fixes #4

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@isaacrowntree isaacrowntree merged commit 3bf71b4 into main Mar 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

status set/edit fails for lists with custom statuses (uses space statuses only)

1 participant