bulk_update_stories
Destructive
Update multiple stories by setting status, appending notes, and patching acceptance criteria in a single atomic operation per file.
Instructions
Update multiple stories in one operation. Each entry may set status, append a note, and/or patch acceptance criteria. Updates are applied atomically per file. If a story does not exist, an error is recorded for that entry and processing continues. Returns an array of per-story result objects with fields: story_id, status_updated, old_status, new_status, note_appended, criteria_updated, criteria_errors, errors.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| updates | Yes | Array of story update objects. Each must include story_id; status, note, and criteria are optional. status must be one of: draft, in-progress, blocked, deferred (use complete_story to mark done). note is appended, not replaced. criteria is a map of criterion text (or AC ID) to boolean checked state — true = checked, false = unchecked. Example: {"User can log in": true, "User sees error on bad password": false}. Keys are matched case-insensitively with tolerance for Unicode dash variants (em-dash, en-dash, etc.). |