Get Issue Templates
issue_templates_get_allRetrieve Yandex Tracker issue templates to align new issues with team-defined structure. Filter by queue to get applicable templates before creating an issue.
Instructions
Get the issue templates configured in Yandex Tracker. Templates hold the issue structure a team actually uses for bugs, incidents and other recurring work. Use this before creating an issue so that its summary and description follow the team's current template instead of an invented structure. Pass queue to get only the templates usable in that queue - the templates of that queue plus the ones not bound to any queue, which are usable everywhere. The issue body of each template is in fieldTemplates.description, not in the template's own description, which describes the template itself. Every page is retrieved by default; pass page to get a single page when the result does not fit the context window.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number to return, default is None which means to retrieve all pages. Specify page number to retrieve a specific page when context limit is reached. | |
| queue | No | Optional queue (Project ID) to scope the result to, like 'SOMEPROJECT'. Templates that are not bound to any queue are usable everywhere and are returned as well. | |
| per_page | No | The number of items per page. May be decreased if results exceed context window. If there is a change in per_page argument - retrieval must be started over with page = 1, as the paging could have changed. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| hits | No | Total items matching the request, across all pages. Null if unknown or filtered - then page on until a page comes back empty. | |
| pages | No | Total pages at the requested `per_page`; this is the last page when it equals `page`. Null together with `hits`. | |
| values | No |