jira_update_issue
Update fields on an existing Jira issue while leaving omitted fields unchanged; labels and components replace existing lists, and workflow status is not altered.
Instructions
WRITE: update supplied fields on an existing Jira issue. Omitted fields stay unchanged. Labels and components replace entire lists; [] clears them. Requires at least one field. Does not change workflow status. Assignee is a Server username; custom fields use raw IDs.
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 | Replaces all labels; [] clears them. | |
| summary | No | ||
| assignee | No | Jira Server username, not display name or Cloud accountId. | |
| issueKey | Yes | ||
| priority | No | Exact Jira priority name. | |
| components | No | Component names. Replaces all components; [] clears them. | |
| description | No | Jira text/wiki markup; empty string clears the description. | |
| customFields | No | Raw Jira custom field IDs and Jira-compatible values; null clears a field where Jira permits it. |