Update Issue
issue_updateModify an existing Yandex Tracker issue by updating only the fields you specify; omitted fields remain unchanged. Use the optional version for optimistic locking to prevent edit conflicts.
Instructions
Update an existing Yandex Tracker issue. Only fields that are provided will be updated; omitted fields remain unchanged. Use queue_get_fields to discover available fields before updating. The version parameter is optional optimistic locking: pass it only when you have a version read moments ago (issue_get), and never the one returned by issue_create - queue triggers and automation bump the version right after creation, which makes the update fail with an editing conflict.
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 fields without a dedicated parameter above. Call `queue_get_fields` for the fields configured on the queue and `get_global_fields` for the whole registry - system fields such as `parent` or `estimation` are settable but may be missing from the queue listing. Keys are Tracker field ids as those tools return them (camelCase, e.g. 'storyPoints'), which is also how they come back in issue responses. An entry here overrides the dedicated parameter of the same name, which is how a field is cleared: pass null (e.g. {'assignee': null, 'parent': null}), since a dedicated parameter left unset simply is not sent. Values are sent to Tracker as-is: reference fields expect numeric IDs as numbers (or {'id': ...} objects), because a bare string may be resolved 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; changes are only applied when it is the issue's current version, otherwise the call fails with an editing conflict. Read it with issue_get immediately before updating, and omit it when you just want the update to land on whatever the latest version is. The version returned by issue_create is not safe to use here: queue triggers and automation 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_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 | ||
| parent | No | ||
| sprint | No | ||
| 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 |