Update Issue
jira_update_issueDestructive
Update Jira issues by changing fields, transitioning status, adding comments, logging work, and attaching files. Provide the issue key and optional details to modify the issue in one call.
Instructions
Update an issue and optionally transition, comment, and log work.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fields | No | JSON string of fields to update. For 'assignee', provide a string identifier (email, name, or accountId). For 'description', provide text in Markdown format; on Jira Cloud, use '{expand:Title}...{expand}' for a collapsible section. Example: '{"assignee": "user@example.com", "summary": "New Summary", "description": "## Updated\nMarkdown text"}' | |
| comment | No | (Optional) Comment text in Markdown format. | |
| worklog | No | (Optional) Time spent to log, such as '1h 30m'. | |
| issue_key | Yes | Jira issue key (e.g., 'PROJ-123', 'ACV2-642') | |
| components | No | (Optional) Comma-separated list of component names (e.g., 'Frontend,API') | |
| transition | No | (Optional) Transition name or ID. Transition names are resolved case-insensitively. | |
| attachments | No | (Optional) JSON string array or comma-separated list of file paths to attach to the issue. Example: '/path/to/file1.txt,/path/to/file2.txt' or ['/path/to/file1.txt','/path/to/file2.txt'] | |
| return_fields | No | (Optional) Controls which fields of the updated issue are returned, to reduce response size and token usage. Defaults to '*all' (the complete issue, which can be very large). TOKEN-SAVING TIP: after an update you usually do NOT need the whole issue back. Pass a comma-separated list of just the field(s) you care about (e.g., 'summary,duedate'), or a single light field such as 'status' for a minimal confirmation - this can cut the response by thousands of tokens. The issue 'key' is always returned regardless. If you later need other fields, fetch them on demand with jira_get_issue (which also supports field filtering). Use '*all' only when you genuinely need the full updated issue. | *all |
| worklog_started | No | (Optional) ISO datetime when the worklog started. | |
| additional_fields | No | (Optional) JSON string of additional fields to update. Use this for custom fields or more complex updates. Link to epic: {"epicKey": "EPIC-123"} or {"epic_link": "EPIC-123"}. | |
| comment_visibility | No | (Optional) Comment visibility as a JSON string, for example '{"type":"group","value":"jira-users"}'. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |