update_issue
Update an existing issue by patching its fields: change status, priority, title, description, or type. Automatically move cards through triage columns without extra confirmation.
Instructions
Patch fields on an existing issue. Use to change status (move it across columns), reprioritize, retitle, etc.
STATUS CHANGES: moving a card to in_progress (you're picking it up to work on) or in_review (it's ready for the reporter to verify) is part of the normal triage flow. Just do it when it's warranted; you do not need to ask the user for confirmation first. The same goes for moving a stalled card back to new.
When NOT to move silently: terminal states. Moving an in_review card to done / wont_fix is blocked server-side unless the reporter has signed off (this is intentional). For human reporters, post a comment asking them to confirm. For service-account reporters (e.g. yourself), use a non-terminal status or ask the developer.
AUDIENCE: when editing title or description, the same plain-language rules from create_issue apply (non-developer testers read these too). Don't rewrite a reporter-friendly title into a developer-friendly one.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| url | No | ||
| type | No | ||
| title | No | ||
| status | No | ||
| priority | No | ||
| description | No |