Tracker workflows your agents can actually repeat

track turns issue trackers and knowledge bases into a scriptable execution surface: fetch every result, pipe JSON into audits, dry-run bulk plans, and resume long operations across YouTrack, Jira, GitHub, GitLab, and Linear.

Get started → View on GitHub

Install for your OS All install options

Homebrew

Package-manager install

$brew install OrekGames/tap/track

Native install

Verified release script

$curl -fsSL https://raw.githubusercontent.com/OrekGames/track-cli/main/scripts/install.sh | bash

zsh — track

# Pull every unresolved issue into a repeatable audit
$ track -o json i s "project: PROJ #Unresolved" --all \
  | jq 'group_by(.state.name)[] | "\(.[0].state.name) \(length)"'
Open         84
In Progress  12
Review        7

# Preview a multi-step change plan before it mutates anything
$ track apply cleanup-plan.json --dry-run --validate
Apply completed (dry run)
  14 operations: 6 update_issue, 5 comment, 3 link

# Resume the same plan after an interrupted run
$ track -o json apply cleanup-plan.json \
  --resume /tmp/track-apply-state.json
{ "resumed": true, "succeeded": 14, "failed": 0 }

Documentation workflows

Write Markdown. Publish real wiki pages.

For Jira teams, track makes Confluence feel like a developer-friendly documentation target. Agents can draft Markdown in the repo, review it like any other file, then publish it through standard article commands without hand-building wiki storage markup.

Markdown in, native wiki out

Jira/Confluence pages can be authored as Markdown files and converted to Confluence storage format on publish.

Docs stay attached to work

Agents can update the issue, publish the runbook, add a page comment, and attach evidence from the same CLI surface.

Wiki inventory is scriptable

List or search every article with `--all`, emit JSON, and use it for stale-doc reports, migration plans, or release audits.

zsh - wiki

# Publish agent-authored Markdown to Confluence
$ track -b j wiki create -p 65957 \
  -s "Rollback runbook" --body-file ./runbook.md
123456  Rollback runbook  published

# Update an existing page from the reviewed file
$ track -b j wiki update 123456 \
  --body-file ./runbook.md --tag release

# Audit docs at the same scale as issues
$ track -o json wiki search "rollback" --all
["123456", "123987", "124018"]

Why a CLI still matters

MCP is an interface. `track` is an execution surface.

MCP integrations are useful for interactive lookup and one-off edits. track covers the work that needs a contract: repeatable commands, shell pipelines, dry-runs, resumable state, and auditable JSON that can move from an agent session into a script, PR, or CI job.

--all

Backlog-scale reads

Fetch every matching issue or article page in one command, then pipe JSON into jq, CI checks, reports, or notebooks.

dry-run

Reviewable bulk changes

Turn create, update, comment, link, and guarded delete operations into a plan file that can be validated before it touches the tracker.

resume

Long-running execution

Use an explicit state file to continue after a network failure, auth refresh, or partial run instead of replaying completed operations.

JSON

Automation contracts

Every workflow can emit machine-readable output with stable exit behavior, so agents and scripts can reason from results instead of chat text.

One workflow for issues and docs, everywhere

Learn a single command set and use it against any supported tracker or knowledge base — no per-tool relearning.

🔌

Unified Interface

One command set that works the same against any supported issue tracker or knowledge base.

📚

Markdown Wiki Publishing

Publish Markdown files to YouTrack Knowledge Base or Jira/Confluence without hand-writing wiki storage markup.

⚡

Batch & Bulk Operations

Update, delete, or complete many issues at once, plus declarative bulk apply.

📄

Transparent Pagination

The --all flag auto-paginates to fetch every result, no manual offsets.

🤖

Agent Context

Context aggregation, workflow hints, query templates, and JSON output give agents the shape of the tracker before they act.

🧰

Text or JSON

Human-readable text by default, machine-readable JSON for scripting.

Compatible with the tools you already use

Switch backends with a config file, an environment variable, or a single -b flag. Documentation included — YouTrack Knowledge Base and Jira/Confluence articles work through the same commands. More backends on the way.

YouTrack Jira GitHub GitLab Linear