Update issue
jira_update_issueUpdate selected fields of an existing Jira issue while leaving all other fields unchanged. Use it to change summary, description, labels, priority, due date, parent, components, or custom fields.
Instructions
Update fields of an issue. Only the provided fields change. Use jira_transition_issue to change status and jira_assign_issue to change assignee.
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": {
"issue": "<issue>"
},
"name": "jira_update_issue"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| issue | Yes | Issue key ('ABC-123'), instance-prefixed key ('work:ABC-123') or full browse URL ('https://acme.atlassian.net/browse/ABC-123'). | |
| labels | No | Replaces all labels. | |
| parent | No | ||
| dueDate | No | YYYY-MM-DD, or empty string to clear. | |
| summary | No | ||
| instance | No | Jira instance name (see jira_list_instances). Optional: calls are routed automatically by 'name:KEY' prefixes, issue URLs, project-key mapping, the default instance, or when only one instance exists. | |
| priority | No | ||
| components | No | ||
| description | No | Replaces the description (light Markdown supported). | |
| customFields | No | Extra raw Jira fields, e.g. {"customfield_10016": 5}. Values are sent as-is. |