Skip to content

resolve task statuses from list instead of space - #15

Closed
alexanderbailey wants to merge 1 commit into
krodak:mainfrom
alexanderbailey:fix/status-from-list
Closed

alexanderbailey wants to merge 1 commit into
krodak:mainfrom
alexanderbailey:fix/status-from-list

Conversation

@alexanderbailey

Copy link
Copy Markdown
Contributor

Closes #14

When validating --status on cu update, the CLI was fetching statuses from the task's space. Lists can define their own statuses that differ from the space defaults, causing valid statuses to be rejected.

This changes resolveStatus to fetch statuses from the task's list (GET /list/<id>) instead.

Fixes status validation when a list has custom statuses that differ
from the space defaults. Resolves against GET /list/<id> so the
available statuses reflect what the task's list actually supports.

Closes krodak#14
@krodak

krodak commented Mar 18, 2026

Copy link
Copy Markdown
Owner

Good catch - lists can have their own statuses that differ from space defaults, and validating against the wrong level causes false rejections. Merged with a small addition: updated the tests to mock getListWithStatuses instead of getSpaceWithStatuses and removed the no-space fallback test since every task has a list.id. Thanks for the fix.

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.

cu update --status fails when list has custom statuses

2 participants