Tracker MCP tools¶

187 tools.

tracker_me_get¶

Get current Tracker user · read-only

The authenticated Yandex Tracker user (a safe auth probe).

tracker_issues_get¶

Get Tracker issue · read-only

A single Tracker issue by key (raises if not found).

tracker_issues_list¶

List Tracker issues · read-only

Issues matching the supplied filters (omitted filters dropped), auto-paginated.

Returns at most limit issues; exactly limit back means more may match — narrow the filters or raise limit.

tracker_issues_search¶

Search Tracker issues (TQL) · read-only

Issues matching a TQL query string, auto-paginated.

Returns at most limit issues; exactly limit back means more may match — refine the query or raise limit.

tracker_issues_count¶

Count Tracker issues · read-only

Count of issues matching a TQL query or filters.

Pass query for a TQL query string (takes precedence over filters), or pass queue/status to filter by those fields. With no arguments the API counts every issue in the org.

tracker_issues_suggest¶

Suggest Tracker issues by title · read-only

Typeahead over visible issues — issues whose summary contains text.

A lightweight title match; for full TQL search use issues_search.

tracker_issues_create¶

Create Tracker issue · write

Create a Tracker issue; returns the new issue with its key.

tracker_issues_update¶

Update Tracker issue · idempotent write

Update fields of a Tracker issue; only the keys present in body are changed.

Status is NOT changed here — use transitions_execute. Returns the updated issue.

tracker_issues_move¶

Move Tracker issue · write

Move a Tracker issue to another queue (it gets a new key there; the old key redirects).

queue is the target queue key. Fields that do not exist in the target queue may be dropped. Returns the moved issue with its new key.

tracker_issues_scroll_clear¶

Clear Tracker search scroll · idempotent write

Release the server resources of a scrolled issue search (harmless housekeeping).

body maps each X-Scroll-Id to its X-Scroll-Token from a scrolled issues.search response. Returns an acknowledgement on success.

tracker_comments_list¶

List Tracker issue comments · read-only

All comments on a Tracker issue, auto-paginated via the relative id-cursor.

Capped at the configured item cap unless limit is given, so very long threads are truncated at the cap rather than fetched forever.

tracker_comments_get¶

Get Tracker issue comment · read-only

One comment of a Tracker issue: text, author, edit history and, on request, attachments.

tracker_comments_add¶

Add Tracker issue comment · write

Add a comment to a Tracker issue; returns the created comment.

tracker_comments_update¶

Edit Tracker issue comment · idempotent write

Replace the text of an existing comment on a Tracker issue.

Get comment_id from comments_list. Returns the updated comment.

tracker_comments_delete¶

Delete Tracker issue comment · destructive write

Permanently delete one comment from a Tracker issue (irreversible).

Get comment_id from comments_list. Returns an acknowledgement on success.

tracker_comments_react¶

React to Tracker issue comment · write

Add an emoji reaction to a comment on a Tracker issue.

name is the reaction name (e.g. like, dislike, fire). Returns the comment with its updated reactions.

tracker_links_list¶

List Tracker issue links · read-only

All links on a Tracker issue (linked issues, type, direction).

tracker_links_search¶

Search Tracker issue links · read-only

Links of a Tracker issue filtered by type, paged and capped (a read done via POST).

Prefer this over links_list for issues with many links or when only some link types or fields matter; it carries each link's author, dates, assignee and status.

tracker_links_add¶

Link Tracker issues · write

Link a Tracker issue to another issue; returns the created link.

tracker_links_delete¶

Delete Tracker issue link · destructive write

Remove a link between two Tracker issues (irreversible).

Get link_id from links_list. Returns an acknowledgement on success.

tracker_transitions_list¶

List Tracker issue transitions · read-only

Available workflow transitions for a Tracker issue.

tracker_transitions_execute¶

Execute Tracker issue transition · write

Move a Tracker issue through a workflow transition (change its status).

Get transition_id from transitions_list. body may be empty or carry issue fields to set on transition, e.g. a resolution when closing. Returns the transitions available from the new status.

tracker_worklog_list¶

List Tracker worklog · read-only

All time-tracking entries logged against a single Tracker issue.

Auto-paginated via the relative id-cursor. Capped at the configured item cap unless limit is given.

Scoped to one issue by key. To search worklog across the whole org (by author and/or a creation-time range) use worklog_search instead.

tracker_worklog_search¶

Search Tracker worklog · read-only

Org-wide worklog entries filtered by author and/or a creation-time range.

Unlike worklog_list (one issue), this searches every issue's worklog. Pass created_by to scope to a user and created_from / created_to for a time window; all are optional.

tracker_worklog_global_list¶

List Tracker org-wide worklog · read-only

Org-wide worklog entries via GET /worklog query filters (author / exact timestamp).

A lighter sibling of worklog_search (which takes a time range); both filters are optional.

tracker_worklog_create¶

Add Tracker worklog record · write

Log spent time on a Tracker issue; returns the created worklog record.

tracker_worklog_update¶

Edit Tracker worklog record · idempotent write

Edit a worklog record on a Tracker issue (duration and/or comment).

Get record_id from worklog_list. Returns the updated record.

tracker_worklog_delete¶

Delete Tracker worklog record · destructive write

Permanently delete a worklog record from a Tracker issue (irreversible).

Get record_id from worklog_list. Returns an acknowledgement on success.

tracker_changelog_list¶

List Tracker issue changelog · read-only

Full changelog (edit history) for a Tracker issue.

Auto-paginated via the relative id-cursor. Capped at the configured item cap unless limit is given.

tracker_checklists_get¶

Get Tracker issue checklist · read-only

The checklist items on a Tracker issue (text, done flag, assignee, per-item deadline).

Returns a flat array; an issue with no checklist yields an empty list. Item ids from here feed checklists_update / checklists_delete.

tracker_checklists_create¶

Add Tracker checklist item · write

Add an item to a Tracker issue's checklist (creates the checklist if absent).

Returns the issue with its full checklist.

tracker_checklists_update¶

Edit Tracker checklist item · idempotent write

Edit one checklist item on a Tracker issue (text, checked state, assignee, deadline).

Get item_id from checklists_get. Returns the issue with its updated checklist.

tracker_checklists_delete¶

Delete Tracker checklist item · destructive write

Permanently remove one item from a Tracker issue's checklist (irreversible).

Get item_id from checklists_get. Returns the issue with its remaining checklist.

tracker_checklists_clear¶

Clear Tracker issue checklist · destructive write

Permanently delete the ENTIRE checklist of a Tracker issue (all items, irreversible).

Returns the issue without its checklist.

tracker_columns_list¶

List Tracker board columns · read-only

Every column defined on the given agile board.

Each column carries the issue statuses whose cards land in it. Use this to inspect a board's column layout; use columns_get when you already know a column id, and boards_get for the board itself.

tracker_columns_get¶

Get Tracker board column · read-only

Look up a single board column by its numeric id.

The column includes the issue statuses grouped into it. Use this when you already know the board and column ids; use columns_list to enumerate every column on a board.

tracker_columns_create¶

Create Tracker board column · write

Add a column to an agile board; returns the new column.

name and statuses (the issue-status keys whose cards land in the column) are required; limit optionally caps the number of issues allowed in the column.

tracker_columns_update¶

Edit Tracker board column · idempotent write

Edit a board column; only the fields set in body are changed.

Get column_id from columns_list. Returns the updated column.

tracker_columns_delete¶

Delete Tracker board column · destructive write

Permanently remove a column from an agile board (irreversible).

Returns an acknowledgement on success.

tracker_priorities_list¶

List Tracker priorities · read-only

All available issue priorities in the organisation.

tracker_priorities_create¶

Create Tracker priority · write

Create an org-global issue priority.

CAUTION: priorities are organisation-wide and have no delete endpoint — creation leaves permanent residue. key is the latin identifier; name holds the ru/en display names.

tracker_priorities_update¶

Edit Tracker priority · idempotent write

Edit an issue priority; only the fields set in body are changed.

priority_id is the numeric id (not the key). Pass version to guard against concurrent edits (optimistic locking).

tracker_issuetypes_list¶

List Tracker issue types · read-only

All available issue types (e.g. task, bug, epic).

tracker_issuetypes_create¶

Create Tracker issue type · write

Create an org-global issue type (e.g. a new kind of task).

CAUTION: issue types are organisation-wide and have no delete endpoint — creation leaves permanent residue. key is the latin identifier; name holds the ru/en display names.

tracker_issuetypes_update¶

Edit Tracker issue type · idempotent write

Edit an org-global issue type; only the fields set in body are changed.

issue_type_id is the numeric id (not the key). Pass version to guard against concurrent edits (optimistic locking).

tracker_linktypes_list¶

List Tracker link types · read-only

All available link types (e.g. relates, depends on, blocks).

tracker_users_get¶

Get Tracker user · read-only

Look up a single organisation user account by login or uid.

The account includes name, email and licence/dismissal status. Use this when you already know one user; use users_list to browse or enumerate the whole directory. Pass expand="groups" to include the user's groups.

tracker_users_list¶

List Tracker users · read-only

All users registered in the organisation, sorted by ascending uid.

Auto-paginated via the relative id-cursor. Capped at the configured item cap unless limit is given; use users_get instead when you already know the specific login or uid.

tracker_statuses_list¶

List Tracker statuses · read-only

Every issue status configured in the organisation's workflows.

Each status has a key, a name and a type such as new/inProgress/done. Use this to resolve or validate a status key before filtering or transitioning issues; see resolutions_list for close-out results and priorities_list for priorities.

tracker_statuses_create¶

Create Tracker status · write

Create an org-global issue status for use in workflows.

CAUTION: statuses are organisation-wide and have no delete endpoint — creation leaves permanent residue. key is the latin identifier, name holds the ru/en display names, type is the stage kind (new/inProgress/paused/done/cancelled).

tracker_statuses_update¶

Edit Tracker status · idempotent write

Edit an issue status; only the fields set in body are changed.

status_id is the numeric id (not the key). Pass version to guard against concurrent edits (optimistic locking).

tracker_resolutions_list¶

List Tracker resolutions · read-only

Every issue resolution configured in the organisation.

A resolution is the close-out result such as fixed/duplicate/won't-fix. Use this to resolve or validate a resolution key when reading a closed issue or filtering; see statuses_list for workflow stages, not close-out reasons.

tracker_resolutions_create¶

Create Tracker resolution · write

Create an org-global issue resolution (a close-out reason such as fixed/duplicate).

CAUTION: resolutions are organisation-wide and have no delete endpoint — creation leaves permanent residue. key is the latin identifier; name holds the ru/en display names.

tracker_resolutions_update¶

Edit Tracker resolution · idempotent write

Edit an issue resolution; only the fields set in body are changed.

resolution_id is the numeric id (not the key). Pass version to guard against concurrent edits (optimistic locking).

tracker_queues_list¶

List Tracker queues · read-only

Every queue the caller can see, auto-paginated over the API's page/perPage pages.

Capped at the configured item cap unless limit is given. Each item's key is the queue key (e.g. TEST) you pass to queues_get and use as an issue prefix (TEST-123). Use queues_get for a single queue's full configuration (types, workflows, resolutions).

tracker_queues_get¶

Get Tracker queue · read-only

One queue's settings and configuration by key or id (raises if not found).

Returns the queue's owner, default type/priority, and — when expand is set — its issue types, versions, team, workflows and per-type resolution config. Sibling queues_list enumerates every queue; pass one of its key values here.

tracker_queues_tags_list¶

List Tracker queue tags · read-only

Every tag name that has been added to the queue, as a flat string array.

These are the tags selectable on the queue's issues (the tags field). Remove one everywhere with queues_tag_remove.

tracker_queues_versions_list¶

List Tracker queue versions · read-only

The queue's versions — release milestones issues can be assigned to.

Each item carries the version's name, date range and released/archived flags. Create one with queues_version_create.

tracker_queues_fields_list¶

List Tracker queue required fields · read-only

The queue's required/local fields with their schema, options and display order.

Use this to learn which fields an issue in the queue expects (and whether each is required) before creating or updating issues there.

tracker_queues_create¶

Create Tracker queue · write

Create a Tracker queue (the container issues live in; its key prefixes issue keys).

Required: key (latin, uppercase), name, lead (login), default_type (issue type key, e.g. task) and default_priority (priority key, e.g. normal). Returns the new queue.

tracker_queues_delete¶

Delete Tracker queue · destructive write

Delete a Tracker queue WITH ALL ITS ISSUES (recoverable via queues_restore).

The queue moves to the recycle bin and can be restored for a limited time. Returns an acknowledgement on success.

tracker_queues_restore¶

Restore Tracker queue · write

Restore a previously deleted Tracker queue (and its issues) from the recycle bin.

Returns the restored queue.

tracker_queues_set_permissions¶

Set Tracker queue permissions · idempotent write

Replace access rules on a Tracker queue (grant/revoke read/write/create/grant rights).

Each right block takes users/groups/roles arrays; omitted blocks stay unchanged. Returns the resulting permission set.

tracker_queues_tag_remove¶

Remove Tracker queue tag · destructive write

Remove a tag from EVERY issue of a queue (irreversible; the tag disappears queue-wide).

body is {"tag": "<name>"} — pick the name from queues_tags_list. Returns an acknowledgement on success.

tracker_queues_version_create¶

Create Tracker queue version · write

Create a version (release milestone) on a queue.

Required: queue (the queue key) and name; optional description, start_date / due_date (YYYY-MM-DD). Returns the new version.

tracker_queues_version_get¶

Get Tracker queue version · read-only

One queue version: name, description, dates and its released/archived flags.

tracker_queues_version_update¶

Edit Tracker queue version · idempotent write

Edit a queue version; only the fields set in body change. Returns the version.

tracker_queues_version_delete¶

Delete Tracker queue version · destructive write

Permanently delete a queue version (irreversible). Returns an acknowledgement.

tracker_queues_user_permissions_get¶

Get a user's rights in a Tracker queue · read-only

What one user may do in a queue (create, read, write, grant, deny) and why.

Each right lists who grants it: the user personally, a group or a role. To change rights use queues_set_permissions.

tracker_queues_group_permissions_get¶

Get a group's rights in a Tracker queue · read-only

What one group may do in a queue (create, read, write, grant, deny).

tracker_localfields_list¶

List Tracker local fields · read-only

Custom fields scoped to one queue (its local fields), as a flat list.

Each item's key is the field key you pass to localfields_get; field_schema describes the value type. Local fields differ from global fields (fields_list) in that they exist only inside the given queue. Pass a key from queues_list as queue_id.

tracker_localfields_get¶

Get Tracker local field · read-only

One local field's full definition (type, options, category) by queue and field key.

Raises if the field is not found. Returns the value schema, allowed-values provider and category of the field. Use localfields_list first to discover the field_key values available in a queue.

tracker_localfields_create¶

Create Tracker local field · write

Create a custom field scoped to one queue (a local field).

Required fields: id (latin key), name (ru/en display names), category (a category id from fields_list) and type (value type, e.g. ru.yandex.startrek.core.fields. StringFieldType). There is no delete endpoint — the field lives until its queue is deleted.

tracker_localfields_update¶

Edit Tracker local field · idempotent write

Edit a queue-local field; only the fields set in body are changed.

Get field_key from localfields_list. Returns the updated field definition.

tracker_fields_list¶

List Tracker global fields · read-only

All global (organisation-wide) issue fields, both standard and custom.

Each field carries its value schema, category and provider metadata. Use this to discover which field keys exist before filtering or reading issues; use fields_get when you already know one field id.

tracker_fields_get¶

Get Tracker field · read-only

Parameters of a single issue field.

They include its value schema, read-only flag, allowed options and category. Use this when you already know the field id; use fields_list to enumerate every field in the organisation.

tracker_fields_create¶

Create Tracker field · write

Create an org-global custom issue field.

CAUTION: global fields are organisation-wide and NOT deletable — creation leaves permanent residue; prefer localfields_create for a single queue. Required: id (latin key), name (ru/en display names), category (a category id) and type (value type).

tracker_fields_update¶

Edit Tracker field · idempotent write

Edit an org-global issue field; only the fields set in body are changed.

Pass version to guard against concurrent edits (optimistic locking). Returns the updated field definition.

tracker_fields_category_create¶

Create Tracker field category · write

Create a field category (a grouping bucket for issue fields in the UI).

Required: name (ru/en display names) and order (display weight). CAUTION: org-global and not deletable via the API.

tracker_fields_category_update¶

Edit Tracker field category · idempotent write

Edit a field category; only the fields set in body are changed.

Pass version to guard against concurrent edits (optimistic locking).

tracker_components_list¶

List Tracker components · read-only

All components created by the organisation's users.

Each component carries its queue, owner and description. Components are sub-areas used to classify issues within a queue; use this to discover valid component names/ids before filtering or creating issues.

tracker_components_create¶

Create Tracker component · write

Create a component in a queue (a sub-area for classifying its issues).

name and queue (the queue key) are required; optional fields include description, lead and assignAuto.

tracker_components_update¶

Edit Tracker component · idempotent write

Edit a component; only the fields set in body are changed.

Get component_id from components_list. Pass version to guard against concurrent edits (optimistic locking).

tracker_components_list_for_queue¶

List components of a Tracker queue · read-only

The components of one queue, so you need not filter components_list by queue.

tracker_components_get¶

Get Tracker component · read-only

One component with its queue, owner, description and auto-assign flag.

tracker_components_delete¶

Delete Tracker component · destructive write

Permanently delete a component (irreversible). Returns an acknowledgement.

tracker_components_user_permissions_get¶

Get a user's rights on a Tracker component · read-only

What one user may do on a component (create, read, write, deny) and who grants it.

tracker_components_group_permissions_get¶

Get a group's rights on a Tracker component · read-only

What one group may do on a component (create, read, write, deny).

tracker_filters_get¶

Get Tracker filter · read-only

Parameters of a single saved issue filter.

They include its stored conditions, query-language string, owner, favourite flag and access permissions. Use this to inspect a filter a user references by id; the resulting conditions can then feed an issues_search query.

tracker_filters_create¶

Create Tracker filter · write

Create a saved issue filter owned by the calling user.

name is required; set query (a TQL string) or filter (a conditions object) for the stored search. Remove it later with filters_delete.

tracker_filters_update¶

Edit Tracker filter · idempotent write

Edit a saved issue filter; only the fields set in body are changed.

Get filter_id from filters_get / the Tracker UI. Returns the updated filter.

tracker_filters_delete¶

Delete Tracker filter · destructive write

Permanently delete a saved issue filter (irreversible).

Returns an acknowledgement on success.

tracker_applications_list¶

List Tracker external applications · read-only

External applications that Tracker issues can be linked to via external links.

Use this to discover which application ids/types are available before creating an external link; each application's id and type values are identical.

tracker_boards_list¶

List Tracker boards · read-only

All agile boards in the organisation, sorted by ascending board id.

Auto-paginated via the relative id-cursor. Capped at the configured item cap unless limit is given. Use boards_get when you know one board id, and sprints_list to list a board's sprints.

tracker_boards_get¶

Get Tracker board · read-only

Look up a single agile board by its numeric id.

The board includes its columns, estimation field and burndown calendar. Use this when you already know the board id; use boards_list to browse every board, and sprints_list to enumerate the sprints defined on this board.

tracker_boards_create¶

Create Tracker board · write

Create an agile board; returns the new board with its id.

name is required; optional fields include owner, the private/public permissions template, the backlog_available/sprints_available flags and status-backed columns.

tracker_boards_update¶

Edit Tracker board · idempotent write

Edit an agile board; only the fields set in body are changed.

Supports renaming, toggling backlog_available/sprints_available and replacing the columns layout. Returns the updated board.

tracker_boards_delete¶

Delete Tracker board · destructive write

Permanently delete an agile board (irreversible; its issues are not affected).

Returns an acknowledgement on success.

tracker_sprints_list¶

List Tracker board sprints · read-only

Every sprint defined on the given agile board, in the order Tracker returns them.

Each sprint carries its status, planned dates and parent board. Use this to enumerate a board's sprints; use sprints_get when you already know a sprint id, and boards_get for the board itself.

tracker_sprints_get¶

Get Tracker sprint · read-only

Look up a single sprint by its numeric id.

The sprint includes its status, planned start/end dates, actual start/end datetimes and parent board. Use this when you already know the sprint id; use sprints_list to enumerate all sprints on a board.

tracker_sprints_create¶

Create Tracker sprint · write

Create a sprint on an agile board; returns the new sprint.

Required fields: name, board ({"id": "<board id>"}), start_date and end_date (YYYY-MM-DD). The board must have sprints enabled.

tracker_sprints_update¶

Edit Tracker sprint · idempotent write

Edit a sprint; only the fields set in body (name, dates) are changed.

Get sprint_id from sprints_list. Pass version (the sprint's current version, from sprints_get) — the API requires it for optimistic locking and answers 428 without one. Returns the updated sprint.

tracker_sprints_delete¶

Delete Tracker sprint · destructive write

Permanently delete a sprint (irreversible; its issues are not affected).

Returns an acknowledgement on success.

tracker_sprints_start¶

Start Tracker sprint · write

Start a sprint (sets its status to inProgress and stamps the actual start time).

Pass version (the sprint's current version, from sprints_get) — the API requires it for optimistic locking and answers 428 without one. Returns the updated sprint.

tracker_sprints_archive¶

Archive Tracker sprint · write

Archive a finished sprint (hides it from the board's active sprint list).

Pass version (the sprint's current version, from sprints_get) — the API requires it for optimistic locking and answers 428 without one. Returns the updated sprint.

tracker_attachments_list¶

List Tracker issue attachments · read-only

Files attached to a Tracker issue — name, size, MIME type, uploader, download URLs.

Returns metadata only (an ItemList[Attachment]); use it to discover a file's id and name. Downloading the file's or thumbnail's raw bytes is CLI/SDK-only — run ycli tracker attachments download <ISSUE> <FILE_ID> <FILENAME> — because binary blobs are not an MCP payload.

tracker_attachments_get¶

Get Tracker attachment metadata · read-only

One attachment's metadata (name, size, MIME type, uploader, download URL).

Downloading the bytes is CLI/SDK-only: ycli tracker attachments download.

tracker_attachments_delete¶

Delete Tracker issue attachment · destructive write

Permanently delete one attachment from a Tracker issue (irreversible).

Get file_id from attachments_list. Returns an acknowledgement on success.

tracker_attachments_upload¶

Attach file to Tracker issue · write

Attach a small file to a Tracker issue; returns the created attachment.

The file travels as base64 in the request, so keep it small; for a large file run ycli tracker attachments upload instead.

tracker_attachments_upload_temp¶

Upload temporary Tracker file · write

Upload a small temporary file to attach when creating an issue or a comment.

The returned id goes into attachmentIds of the issue or comment body, and works once. The file travels as base64 in the request, so keep it small.

tracker_macros_list¶

List Tracker queue macros · read-only

Every macro configured on a queue — each a canned comment plus field updates.

Each item's id is what you pass to macros_get for the full body and issueUpdate rows.

tracker_macros_get¶

Get Tracker queue macro · read-only

One queue macro by id — its comment body and the field updates it applies.

Sibling macros_list enumerates every macro in the queue; pass one of its id values here.

tracker_macros_create¶

Create Tracker queue macro · write

Create a macro on a queue (a canned comment plus field updates applied on demand).

name is required; optional fields are body (the comment template) and fieldChanges rows. Returns the new macro.

tracker_macros_update¶

Edit Tracker queue macro · idempotent write

Edit a queue macro; only the fields set in body are changed.

Get macro_id from macros_list. Returns the updated macro.

tracker_macros_delete¶

Delete Tracker queue macro · destructive write

Permanently delete a macro from a queue (irreversible).

Returns an acknowledgement on success.

tracker_triggers_list¶

List Tracker queue triggers · read-only

Every trigger of a queue, ascending by id: name, actions, conditions and active flag.

Auto-paginated and capped at the configured item cap unless limit is given. Use triggers_get for one trigger by id.

tracker_triggers_get¶

Get Tracker queue trigger · read-only

One queue trigger by id — its actions, firing conditions, order and active flag.

Triggers run actions on an issue when their conditions match. The webhook-action run log is triggers_webhook_log_list.

tracker_triggers_webhook_log_list¶

List Tracker trigger webhook logs · read-only

The execution log of a trigger's HTTP-request (Webhook) action, newest first.

Each record holds the outbound request and received response for one run. Only Webhook actions produce these; a trigger with no HTTP action returns an empty list.

tracker_triggers_create¶

Create Tracker queue trigger · write

Create a trigger on a queue — actions that fire when an issue event matches conditions.

Required: name and actions (e.g. [{"type": "Transition", …}]); optional conditions scope when it fires. Returns the new trigger.

tracker_triggers_update¶

Edit Tracker queue trigger · idempotent write

Edit a queue trigger; only the fields set in body are changed.

Get trigger_id from triggers_get / the queue settings. Pass version to guard against concurrent edits (optimistic locking).

tracker_autoactions_get¶

Get Tracker queue autoaction · read-only

One queue autoaction by id — its filter/query, actions, schedule and run stats.

An autoaction periodically applies its actions to every issue matching its filter/query. For run history use autoactions_logs_list (summaries) then autoactions_logs_get (per-issue outcomes of one run).

tracker_autoactions_logs_list¶

List Tracker autoaction runs · read-only

Run summaries for an autoaction — one record per launch with hit/success/failure counts.

Each record's id is the run id you pass to autoactions_logs_get for that run's per-issue outcomes.

tracker_autoactions_logs_get¶

Get Tracker autoaction run · read-only

The per-issue outcomes of one autoaction run — each issue touched and its result status.

Get the run_id from autoactions_logs_list. Only autoactions that auto-update issues produce these detail logs.

tracker_autoactions_create¶

Create Tracker queue autoaction · write

Create an autoaction on a queue — actions applied on a schedule to matching issues.

Required: name and actions (e.g. [{"type": "Update", …}]); scope the issues with filter or query and set the cadence via intervalMillis / calendar. CAUTION: autoactions have no delete endpoint — the action persists until its queue is deleted (it can be disabled in the UI).

tracker_bulk_get¶

Get Tracker bulk-change status · read-only

Current status of an async bulk-change operation (update/move/transition).

status runs CREATED → COMPLETE / FAILED; totalIssues / totalCompletedIssues show progress. Poll this after a bulk trigger returns an id; once it reports FAILED, call bulk_issues_list for the per-issue errors.

tracker_bulk_issues_list¶

List Tracker bulk-change failed issues · read-only

The issues a bulk-change operation could NOT change, each with its per-field error.

Use after bulk_get reports a non-zero failure count to see why specific issues were rejected (e.g. an invalid resolution for the target queue/type). Successful issues are not listed here.

tracker_bulk_update¶

Bulk-update Tracker issues · write

Start an async bulk field update over many Tracker issues; returns the operation.

Poll the returned operation id with bulk_get and inspect failures with bulk_issues_list.

tracker_bulk_move¶

Bulk-move Tracker issues · write

Start an async bulk move of many Tracker issues to another queue; returns the operation.

Poll with bulk_get.

tracker_bulk_transition¶

Bulk-transition Tracker issues · write

Start an async bulk status transition over many Tracker issues; returns the operation.

Poll with bulk_get.

tracker_remotelinks_list¶

List Tracker issue remote links · read-only

Links from a Tracker issue to objects in external applications (Bitbucket, etc.).

Each entry carries the link type, direction, and the external object's key plus its owning application. This is the external link list — for issue-to-issue links use links_list.

tracker_remotelinks_create¶

Create Tracker issue remote link · write

Link a Tracker issue to an object in an external application; returns the created link.

Get the application id (origin) from applications_list. Pass backlink="true" to also create the mirror link in the external app.

tracker_remotelinks_delete¶

Delete Tracker issue remote link · destructive write

Remove a remote (external-application) link from a Tracker issue (irreversible).

Get link_id from remotelinks_list. Returns an acknowledgement on success.

tracker_import_task¶

Import Tracker issue · write

Import an issue preserving its original history (admin-only back-fill).

Returns the imported issue.

tracker_import_comment¶

Import Tracker issue comment · write

Import a comment onto an issue preserving its original author and timestamp (admin-only).

Returns the imported comment.

tracker_import_link¶

Import Tracker issue link · write

Import an issue link preserving its original creation metadata (admin-only).

Returns the imported link.

tracker_import_worklog¶

Import Tracker worklog record · write

Import a worklog record preserving its original author and timestamps (admin-only).

Returns the imported record(s) — the endpoint answers with a JSON array.

tracker_import_file¶

Import Tracker issue attachment · write

Import a text-file attachment onto an issue preserving its original metadata (admin-only).

data is the file content as text (UTF-8-encoded on upload) — for binary files use the CLI (ycli tracker import file), which reads raw bytes from disk. created_at uses YYYY-MM-DDThh:mm:ss.sss±hhmm. Returns the imported attachment.

tracker_dashboards_create¶

Create Tracker dashboard · write

Create a personal Tracker dashboard; returns it with the id used to add widgets.

NOTE: dashboard deletion is not wrapped by ycli, so the dashboard stays on the account until removed in the UI.

tracker_dashboards_add_cycle_time_widget¶

Add Tracker cycle-time widget · write

Add a cycle-time widget to a Tracker dashboard; returns the created widget.

Get dashboard_id from dashboards_create.

tracker_entities_get¶

Get Tracker entity · read-only

A single Tracker entity (project, portfolio or goal) by id, with its fields block.

Pass fields to pull extra parameters into the response — keyResultItems for a goal's key results, checklistItems for a project/portfolio checklist, metricItems for its metric widgets, or summary,description,entityStatus for the basics. Use entities_search to discover ids first.

tracker_entities_search¶

Search Tracker entities · read-only

Entities of a given type matching a name substring, sorted server-side.

Returns a flat list of entities. Pass input_text to match part of the name and order_by (e.g. entityStatus) to sort. For richer filtering (by author, status, followers, …) use the CLI tracker entities search --filter which accepts an arbitrary filter object.

tracker_entities_events_list¶

List Tracker entity history · read-only

An entity's event history (created/updated/commented/…), auto-paginated.

Each event carries an author, a timestamp, a display title and the individual field changes. Capped at the configured item cap unless limit is given.

tracker_entities_permissions_get¶

Get Tracker entity permissions · read-only

An entity's access settings — the READ/WRITE/GRANT ACL plus inheritance sources.

acl lists the users, groups and roles granted each level; permissionSources names the parent entities this one inherits permissions from. Change them with entities_set_permissions.

tracker_entities_direct_permissions_get¶

Get Tracker entity direct permissions · read-only

An entity's direct READ / WRITE / GRANT rights — the users, groups and roles holding each.

Unlike entities_permissions_get this leaves out inheritance (permissionSources). Change the rights with entities_set_direct_permissions.

tracker_entities_comments_list¶

List Tracker entity comments · read-only

All comments on an entity — author, text, timestamps and summoned users.

tracker_entities_comments_get¶

Get Tracker entity comment · read-only

A single comment on an entity by id.

tracker_entities_links_list¶

List Tracker entity links · read-only

An entity's links to other entities — the link type and the linked entity's summary + id.

tracker_entities_attachments_list¶

List Tracker entity attachments · read-only

Files attached to an entity — name, size, MIME type, uploader and download URL.

Returns metadata only. Downloading the raw bytes is CLI/SDK-only — run ycli tracker entities attachments download <FILE_ID> <FILENAME> — because binary blobs are not an MCP payload.

tracker_entities_attachments_get¶

Get Tracker entity attachment · read-only

One attachment's metadata (name, size, MIME type, download URL).

Downloading the raw bytes is CLI/SDK-only (tracker entities attachments download).

tracker_entities_bulk_status_get¶

Get Tracker entity bulk-change status · read-only

Current status of an async entity bulk-change operation started by entities_bulk_update.

status runs CREATED → COMPLETE / FAILED; poll until it settles.

tracker_entities_comments_relative_list¶

List Tracker entity comments (relative) · read-only

An entity's comments via the cursor-paginated …/comments/_relative endpoint.

Prefer this over entities_comments_list when the comment thread is long — it drains pages up to limit (the configured item cap by default).

tracker_entities_create¶

Create Tracker entity · write

Create a Tracker entity (project, portfolio or goal); returns it with its id.

tracker_entities_update¶

Edit Tracker entity · idempotent write

Edit a Tracker entity; only the fields keys present in body are changed.

Returns the updated entity.

tracker_entities_delete¶

Delete Tracker entity · destructive write

Permanently delete a Tracker entity (project/portfolio/goal) — irreversible.

Pass with_board=true to also delete a project's linked agile board. Returns an acknowledgement on success.

tracker_entities_set_permissions¶

Set Tracker entity permissions · idempotent write

Change an entity's access rules; returns the resulting permission set.

body is the raw API payload; its acl object accepts only grant / revoke actions, each mapping an access level (READ/WRITE/GRANT) to users/groups/roles, e.g. {"acl": {"grant": {"READ": {"users": ["8000000000000002"]}}}}. Read the current ACL first with entities_permissions_get.

NOTE: intentionally dict (not a typed model) — the wire shape nests READ/WRITE/GRANT under grant/revoke verbs (see references/yandex-360/tracker/ru/api-ref/entities/ patch-access.md); the existing ExtendedPermissionsUpdate/AclInput models describe a different (direct READ/WRITE/GRANT) shape and would misrepresent this endpoint's real body. Allowlisted in tests/test_architecture.py pending a correctly shaped model.

tracker_entities_set_direct_permissions¶

Set Tracker entity direct permissions · idempotent write

Grant and revoke an entity's direct rights; the rest stay as they are.

grant and revoke each map READ / WRITE / GRANT to users (logins or ids), groups (ids) and roles (AUTHOR, OWNER, CLIENT, FOLLOWER, MEMBER). Returns the resulting rights. Read them first with entities_direct_permissions_get.

tracker_entities_bulk_update¶

Bulk-update Tracker entities · write

Start an async bulk field update over many entities; returns the operation.

Poll the returned operation id with entities_bulk_status_get.

tracker_entities_create_report¶

Create Tracker entity report · write

Request a report over Tracker entities (POST /entities/report/).

Returns the report entity.

tracker_entities_comments_create¶

Add Tracker entity comment · write

Add a comment to a Tracker entity; returns the created comment.

tracker_entities_comments_update¶

Edit Tracker entity comment · idempotent write

Edit a comment on a Tracker entity; returns the updated comment.

comment_id addresses the comment (get it from entities_comments_list).

tracker_entities_comments_delete¶

Delete Tracker entity comment · destructive write

Permanently delete one comment from a Tracker entity (irreversible).

Returns an acknowledgement on success.

tracker_entities_checklists_create¶

Add Tracker entity checklist items · write

Add checklist item(s) to a Tracker entity; returns the entity with its checklist.

body is a bare array of items, e.g. [{"text": "…"}].

tracker_entities_checklists_update¶

Edit Tracker entity checklist · idempotent write

Replace/update a Tracker entity's checklist items in one call.

body is a bare array of items, each with id/text/checked. To edit a single item by id use entities_checklists_update_item. Returns the entity with its checklist.

tracker_entities_checklists_update_item¶

Edit Tracker entity checklist item · idempotent write

Edit one checklist item on a Tracker entity (text, checked state, assignee, deadline).

Returns the entity with its updated checklist.

tracker_entities_checklists_delete¶

Delete Tracker entity checklist · destructive write

Permanently delete the ENTIRE checklist of a Tracker entity (all items, irreversible).

To remove a single item use entities_checklists_delete_item. Returns the entity.

tracker_entities_checklists_delete_item¶

Delete Tracker entity checklist item · destructive write

Permanently remove one item from a Tracker entity's checklist (irreversible).

Returns the entity with its remaining checklist.

tracker_entities_checklists_move¶

Move Tracker entity checklist item · write

Reorder a checklist item within a Tracker entity's checklist.

Returns the entity with its reordered checklist.

tracker_entities_links_create¶

Link Tracker entities · write

Link a Tracker entity to another entity (e.g. relates, depends on).

Returns an acknowledgement on success.

tracker_entities_links_delete¶

Delete Tracker entity link · destructive write

Remove the link between a Tracker entity and another entity (irreversible).

right is the id of the entity on the other end (see entities_links_list). Returns an acknowledgement on success.

tracker_entities_attachments_attach¶

Attach Tracker entity file · write

Attach a previously uploaded temporary file to a Tracker entity.

Requires a temp_file_id from the Tracker temporary-upload endpoint (not wrapped by ycli — files are usually seeded via the UI). Returns the entity.

tracker_entities_attachments_delete¶

Delete Tracker entity attachment · destructive write

Permanently delete an attachment from a Tracker entity (irreversible).

The API answers with an empty body; returns an acknowledgement on success.

tracker_workflows_list¶

List Tracker workflows · read-only

Every workflow of the organization (deleted ones excluded) with its steps and actions.

A workflow is the status graph an issue type follows. Use workflows_get for one by id and workflows_for_queue to see which workflow each issue type of a queue uses.

tracker_workflows_get¶

Get Tracker workflow · read-only

One workflow with its steps, initial action, queue binding and version.

A step is a status with the transitions leaving it; version is needed to edit the workflow.

tracker_workflows_for_queue¶

List workflows of a Tracker queue · read-only

The workflows a queue uses: a map from workflow id to the issue types that follow it.

tracker_workflows_create¶

Create Tracker workflow · write

Create a workflow; returns it with its generated id and version.

Required: name, initialAction (name and target status) and steps (each a status with its actions). Statuses are given as keys such as open and must exist; names are {"ru": …, "en": …} objects.

tracker_workflows_update¶

Edit Tracker workflow · idempotent write

Edit a workflow.

Only the fields set in body change, and a given steps list replaces the whole step list. Returns the workflow with its incremented version.

tracker_workflows_update_action¶

Edit Tracker workflow action · idempotent write

Edit one action (transition) of a workflow step; only the fields set in body change.

Returns the whole workflow with its incremented version.

tracker_workflows_delete¶

Delete Tracker workflow · destructive write

Delete a workflow (irreversible). Returns an acknowledgement.

tracker_projects_list¶

List Tracker projects · read-only

Every project of the organization (the legacy Projects API).

entities_search is the newer way to find projects and portfolios.

tracker_projects_get¶

Get Tracker project · read-only

One project: name, lead, stage, dates and version (needed to edit it).

tracker_projects_queues¶

List queues of a Tracker project · read-only

The queues whose issues belong to a project.

tracker_projects_create¶

Create Tracker project · write

Create a project (legacy Projects API).

name and queues (a queue key) are required, status is DRAFT, IN_PROGRESS, LAUNCHED or POSTPONED. Returns the project.

tracker_projects_update¶

Edit Tracker project · idempotent write

Edit a project; queues is required on every edit, other fields change when set.

Returns the project with its incremented version.

tracker_projects_delete¶

Delete Tracker project · destructive write

Delete a project (irreversible). Returns an acknowledgement.

tracker_gaps_search¶

Search Tracker employee absences · read-only

The absences (vacation, illness, trips, duty, …) of the given users that overlap a window.

A read done via POST; needs Tracker administrator rights. Every requested user appears, with an empty gaps list when they are not absent.

tracker_gaps_create¶

Create Tracker employee absences · write

Create up to 100 employee absences; needs Tracker administrator rights.

Each gap needs user, workflow (vacation, paid_day_off, illness, absence, trip, conference_trip, conference, learning, maternity or duty), from and to (ISO 8601, from earlier). Returns the absences actually saved.

tracker_gaps_delete¶

Delete Tracker employee absences · destructive write

Delete employee absences by id (irreversible); ids the API does not know are ignored.

Needs Tracker administrator rights. Returns an acknowledgement.