cancel

To cancel a story via API and revert uncommitted code, initiate the workflow by providing a STORYID. The process targets stories in todo or doing status, resolving arguments by UUID, timestamp, or title, and uses git checkout to safely revert uncommitted backend, frontend, or test changes.

If a story title lookup using case-insensitive substring matching returns ambiguous matches during API cancellation, the system returns a 409 error. This is treated as a permanent failure, requiring you to provide a more specific UUID or timestamp-based STORYID to proceed.

The API rejects cancellation requests for stories in done, archived, or canceled status. The workflow specifically targets and processes cancellations only for stories currently in todo or doing status to prevent invalid state transitions.

When you only have a partial title, resolve the story for API cancellation using case-insensitive substring matching. If the substring matches multiple stories, you will receive a 409 permanent failure and must retry with a unique UUID or timestamp-based STORYID.

A git revert may fail during story cancellation if the uncommitted changes in backend, frontend, or tests conflict with the checkout operation. The workflow provides error handling guidance to help preserve your edits and recover from these revert failures.

Yes, you can reactivate a story after canceling it via the API by using the transition endpoint. The cancellation workflow includes proper post-cancel steps that allow for potential reactivation if the story needs to be resumed later.