yandex-tracker_skill

This skill helps you manage Yandex Tracker tasks by writing Python scripts that create, update, search, and bulk-operate issues.
  • Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill yandex-tracker

  • _meta.json282 B
  • README.md2.7 KB
  • SKILL.md13.7 KB

Overview

This skill provides programmatic access to Yandex Tracker using the yandex_tracker_client Python library. It lets you create, update, search, comment, link, attach files, log work, and run bulk operations on Tracker issues. Use it to automate common Tracker workflows from short scripts that initialize the client, call the API, and print structured results.

How this skill works

Write a self-contained Python script that initializes TrackerClient with TRACKER_TOKEN and org id, performs the required API calls, aggregates results into lists, then prints a concise summary or JSON. The client exposes dynamic objects (call .as_dict() to inspect fields), lazy iterables for paginated lists, and operations for issues, comments, attachments, links, worklogs, queues, users, sprints and bulk changes. Handle API exceptions (NotFound, Forbidden, BadRequest, Conflict) to provide robust scripts.

When to use it

  • Create, update, transition, or close issues programmatically.
  • Search and report on issues across queues using Tracker Query Language or structured filters.
  • Add, edit, or delete comments and upload or download attachments.
  • Record worklog entries or fetch aggregated time entries for reports.
  • Create and remove links between issues or manage parent/subtask relationships.
  • Perform bulk updates, transitions, or moves across many issues at once.

Best practices

  • Always set TRACKER_TOKEN and TRACKER_ORG_ID or TRACKER_CLOUD_ORG_ID in the environment and use least-privilege tokens.
  • Materialize lazy iterables with list() before counting, sorting, or applying joins across results.
  • Call .as_dict() on a real issue to discover queue-specific custom field keys before filtering or updating.
  • List transitions or resolution IDs before executing transitions; transition IDs are queue-specific.
  • Upload attachments by path in comments or use attachment.download_to() to fetch files.
  • Wait for bulk change completion with bc.wait() and check bc.status for success or failure.

Example use cases

  • Aggregate open issues per assignee in a queue and print the top contributors.
  • Create a bug with summary, description, assignee, tags and attach a logfile.
  • Search for issues updated in the last week with a custom field filter and export keys to CSV.
  • Bulk transition a set of issues to closed with a chosen resolution and comment.
  • Add a worklog entry for time spent and then list recent worklogs across specified issues.

FAQ

Set TRACKER_TOKEN and either TRACKER_ORG_ID (int) or TRACKER_CLOUD_ORG_ID (string). Use least-privilege OAuth or temporary IAM tokens.

How do I discover custom field names for a queue?

Fetch a real issue and call issue.as_dict() or iterate client.fields.get_all() to list field ids and display names.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational