Update Issue
issue_updateUpdate specific fields of an existing Yandex Tracker issue while leaving other fields unchanged. Discover available fields using queue_get_fields before updating.
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.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| issue_id | Yes | Issue ID in the format '<project>-<id>', like 'SOMEPROJECT-1' | |
| summary | No | New issue title/summary | |
| description | No | New issue description (use markdown formatting) | |
| markup_type | No | Markup type for description text. Use 'md' for YFM (markdown) markup. | md |
| parent | No | Parent issue reference. Object with 'id' (parent issue ID) and/or 'key' (parent issue key like 'QUEUE-123'). | |
| sprint | No | Sprint assignments. Array of objects, each with 'id' field containing the sprint ID (integer). | |
| type | No | Issue type. Object with 'id' (type ID) and/or 'key' (type key like 'bug', 'task'). Use `queue_get_metadata` tool with expand=['issueTypesConfig'] to get available issue types in this queue. | |
| priority | No | Issue priority. Object with 'id' (priority ID) and/or 'key' (priority key like 'critical', 'normal'). Use get_priorities to find available priorities. | |
| followers | No | Issue followers/watchers. Array of objects, each with 'id' field containing the user ID or login. | |
| project | No | Project assignment. Object with 'primary' (int, main project shortId) and optional 'secondary' (list of ints, additional project shortIds). | |
| tags | No | Issue tags as array of strings. | |
| version | No | Issue version for optimistic locking. Changes are only made to the current version of the issue. Always try to receive issue's version using issue_get tool first. | |
| fields | No | Additional fields to update. Use queue_get_fields to discover available fields. Use the field's 'id' property as the key (e.g., {'fieldId': 'value'}). |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| createdAt | No | ||
| updatedAt | No | ||
| createdBy | No | ||
| updatedBy | No | ||
| version | No | ||
| unique | No | ||
| key | No | ||
| summary | No | ||
| description | No | ||
| type | No | ||
| priority | No | ||
| assignee | No | ||
| status | No | ||
| previousStatus | No | ||
| deadline | No | ||
| components | No | ||
| start | No | ||
| storyPoints | No | ||
| tags | No | ||
| votes | No | ||
| sprint | No | ||
| epic | No | ||
| parent | No | ||
| estimation | No | ||
| spent | No |