jira_update_issue
Update specified fields on an existing Jira issue—such as summary, description, assignee, priority, labels, components, fix versions, due date, or custom fields—while leaving unspecified fields unchanged.
Instructions
Modify an existing Jira issue's fields (summary, description, assignee, priority, labels, components, fix versions, due date, custom fields). Only the fields you specify will be changed - others remain unchanged. Custom fields use field ids (customfield_10006) or a unique name from jira_get_edit_meta, with raw REST values. Do not call jira_get_fields before writing. To change status/workflow state, use jira_transition_issue instead. To add comments, use jira_add_comment.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"issueKey": "<issueKey>"
},
"name": "jira_update_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| labels | No | New labels (replaces existing) | |
| dueDate | No | New due date in YYYY-MM-DD format | |
| summary | No | New issue title/summary | |
| assignee | No | Username to assign to (use empty string "" to unassign, use jira_get_assignable_users to find valid usernames) | |
| issueKey | Yes | Issue key to update (e.g., KP-123) | |
| priority | No | Priority name (e.g., Highest, High, Medium, Low, Lowest) | |
| components | No | New components (replaces existing) | |
| description | No | New description text | |
| fixVersions | No | New fix versions (replaces existing) | |
| customFields | No | Custom fields keyed by field id (e.g. customfield_10006) or a unique name from that issue type's meta. Values are raw Jira REST payloads, not display names. Call jira_get_edit_meta for schema/allowedValues and unique names. Examples: number 5, string "text", select {"value":"Yes"}, Server user {"name":"username"}, multi-select [{"value":"A"}], null to clear. Do not call jira_get_fields before update. |