Create Issue
issue_createCreate a new issue in a Yandex Tracker queue with a required summary, plus optional description, assignee, priority, components, and custom fields to match your workflow.
Instructions
Create a new issue in a Yandex Tracker queue. Check the queue's issue templates first (issue_templates_get_all with queue set): there is no template_id parameter, so a template is applied by copying its fieldTemplates values and description into the parameters below instead of inventing a structure of your own. Copy them field by field rather than wholesale: assignee comes as a user object, while this tool takes a login or uid, and Tracker does not expand the UI macros a template may contain ({{today}} and friends arrive literally). Prefer the dedicated parameters below over the fields map: they are sent in the same format issue_update uses, so a value that works here works there too. Note that the returned issue's version can be outdated as soon as it is returned - queue triggers and automation run right after creation and bump it - so do not reuse it for a follow-up issue_update; re-read the issue with issue_get or omit version.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Issue tags as array of strings. | |
| type | No | Issue type: an object with 'id' (type ID) and/or 'key' (e.g., 'bug', 'task'), or the bare key/ID (from get_issue_types tool). | |
| queue | Yes | Queue key where to create the issue (e.g., 'MYQUEUE') | |
| fields | No | Additional fields to set during issue creation, for fields without a dedicated parameter above. Call `queue_get_fields` for the fields configured on the queue (schema.required=true marks the mandatory ones) 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. 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 | Yes | Issue title/summary | |
| assignee | No | Assignee login or UID | |
| priority | No | Issue priority: an object with 'id' (priority ID) and/or 'key' (e.g., 'critical', 'normal'), or the bare key/ID (from get_priorities tool). | |
| followers | No | Issue followers/watchers. Array of objects, each with an 'id' field holding the user ID (uid) or login. | |
| 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. | |
| description | No | Issue description (use markdown formatting) | |
| markup_type | No | Markup type for description text. Use 'md' for YFM (markdown) markup. | md |
Output 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 |