Update Issue
issue_updateChange specific fields of an existing Yandex Tracker issue without affecting the rest. Optionally pass a version for optimistic locking to prevent editing conflicts.
Instructions
Update an existing Yandex Tracker issue. Only the parameters you pass change; the rest stay as they are. Use queue_get_fields to discover the queue's fields. version is optional optimistic locking - pass one read moments earlier with issue_get, never the one issue_create returned, since triggers bump it right after creation.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Issue tags as array of strings. | |
| type | No | Issue type. Object with 'id' (type ID) and/or 'key' (type key like 'bug', 'task'), or the bare key/ID. Use `queue_get_metadata` tool with expand=['issueTypesConfig'] to get available issue types in this queue. | |
| fields | No | Additional fields to update, for those without a dedicated parameter above. Field ids come from `queue_get_fields` or `get_global_fields`, which also lists system fields such as `parent` or `estimation` that the queue listing may omit. Keys are Tracker's own camelCase ids, e.g. 'storyPoints'. An entry here overrides the dedicated parameter of the same name, which is how a field is cleared: pass null (e.g. {'assignee': null}), since a dedicated parameter left unset is simply not sent. Values are sent as-is: reference fields want numeric IDs as numbers or {'id': ...} objects, since a bare string may be read as a name. | |
| parent | No | Parent issue reference. Object with 'id' (parent issue ID) and/or 'key' (parent issue key like 'QUEUE-123'); when both are given Tracker resolves by 'id', or the bare key. | |
| sprint | No | Sprint assignments. Array of objects, each with 'id' field containing the sprint ID (integer). | |
| project | No | Project assignment. Object with 'primary' (int, main project shortId) and optional 'secondary' (list of ints, additional project shortIds). | |
| summary | No | New issue title/summary | |
| version | No | Issue version for optimistic locking: the change lands only if this is the issue's current version, otherwise the call fails with an editing conflict. Read it with `issue_get` right before updating, or omit it to update whatever the latest version is. The version `issue_create` returned is not safe here - triggers bump it right after creation. | |
| assignee | No | New assignee login or UID | |
| issue_id | Yes | Issue ID in the format '<project>-<id>', like 'SOMEPROJECT-1' | |
| priority | No | Issue priority. Object with 'id' (priority ID) and/or 'key' (priority key like 'critical', 'normal'), or the bare key/ID. Use get_priorities to find available priorities. | |
| followers | No | Issue followers/watchers. Array of objects, each with an 'id' field holding the user ID (uid) or login. Replaces the current follower list. | |
| components | No | Queue components. Array of objects with either 'id' (numeric component ID, from queue_get_components or queue_get_metadata with expand=['components']) or 'name' (component name). Tracker resolves numbers as IDs and strings as names, so the object form is required to avoid a 422 on a numeric-looking name. Replaces the current component list. | |
| description | No | New issue description (use markdown formatting) | |
| markup_type | No | Markup type for description text. Use 'md' for YFM (markdown) markup. | md |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| key | No | ||
| epic | No | ||
| tags | No | ||
| type | No | ||
| spent | No | ||
| start | No | ||
| votes | No | ||
| boards | No | Agile boards the issue shows up on. Tracker fills this in from the boards' own filters - an issue is not assigned to a board directly, so this is read-only. Use the board id with `board_get`, `board_get_columns` or `board_get_sprints`. | |
| parent | No | ||
| sprint | No | Sprints the issue is in. Use `board_get_sprints` to look up the sprints of a board, and pass a sprint id to `issue_update` to move the issue between them. | |
| status | No | ||
| unique | No | ||
| summary | No | ||
| version | No | ||
| assignee | No | ||
| deadline | No | ||
| priority | No | ||
| createdAt | No | ||
| createdBy | No | ||
| updatedAt | No | ||
| updatedBy | No | ||
| components | No | ||
| estimation | No | ||
| description | No | ||
| storyPoints | No | ||
| previousStatus | No |