ycli tracker¶

Yandex Tracker: issues, queues, boards, sprints, fields, automation.

Usage:

$ ycli tracker [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• auth: Check that the token works for tracker.
• me: Tracker authenticated user.
• issues: Tracker issues.
• comments: Tracker issue comments.
• links: Tracker issue links.
• transitions: Tracker issue transitions.
• worklog: Tracker issue worklog.
• changelog: Tracker issue changelog.
• checklists: Tracker issue checklists.
• columns: Tracker agile board columns.
• priorities: Tracker priorities.
• issuetypes: Tracker issue types.
• linktypes: Tracker link types.
• users: Tracker organisation users.
• statuses: Tracker issue statuses.
• resolutions: Tracker issue resolutions.
• queues: Tracker queues.
• localfields: Tracker per-queue local fields.
• fields: Tracker global fields.
• components: Tracker components.
• filters: Tracker saved filters.
• applications: Tracker external applications.
• boards: Tracker agile boards.
• sprints: Tracker board sprints.
• attachments: Tracker issue attachments.
• macros: Tracker queue macros.
• triggers: Tracker queue triggers.
• autoactions: Tracker queue autoactions.
• bulk: Tracker async bulk changes.
• remotelinks: Tracker issue external-app links.
• import: Tracker data import (admin).
• dashboards: Tracker dashboards.
• entities: Tracker projects, portfolios and goals.
• workflows: Tracker workflows.
• projects: Tracker projects (legacy API).
• gaps: Tracker employee absences (admin).

ycli tracker auth¶

Check that the token works for tracker.

Usage:

$ ycli tracker auth [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• status: Probe tracker with its own read; exit 1...

ycli tracker auth status¶

Probe tracker with its own read; exit 1 when the token is rejected.

Usage:

$ ycli tracker auth status [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker me¶

Tracker authenticated user.

Usage:

$ ycli tracker me [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• get: Print the authenticated user (a safe auth...

ycli tracker me get¶

Print the authenticated user (a safe auth probe).

Usage:

$ ycli tracker me get [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues¶

Tracker issues.

Usage:

$ ycli tracker issues [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• get: Print a single issue (full model) for KEY.
• list: List issues matching the supplied filters...
• search: Search issues by a TQL query string...
• count: Count issues matching a TQL query or...
• create: Create an issue (POST /issues/).
• update: Update issue KEY (PATCH /issues/{key}) —...
• move: Move issue KEY to another QUEUE (POST...
• suggest: Suggest issues whose summary contains...
• scroll-clear: Release search-scroll resources (POST...

ycli tracker issues get¶

Print a single issue (full model) for KEY.

Usage:

$ ycli tracker issues get [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --expand TEXT: Extra blocks to include in the reply.
• --fields TEXT: Comma-separated fields to include in the reply.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues list¶

List issues matching the supplied filters (auto-paginated; --all for everything).

Usage:

$ ycli tracker issues list [OPTIONS]

Options:

• --queue TEXT: Queue key.
• --status TEXT: Status key.
• --assignee TEXT: Assignee login.
• --epic TEXT: Epic key.
• --type TEXT: Issue type key.
• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues search¶

Search issues by a TQL query string (auto-paginated; --all for everything).

Usage:

$ ycli tracker issues search [OPTIONS] QUERY

Arguments:

• QUERY: TQL query. [required]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• --expand TEXT: Extra blocks to include in the reply.
• --scroll-type TEXT: sorted or unsorted: scroll through the results (no 10 000 cap).
• --per-scroll INTEGER: Issues per scroll page (1000 at most).
• --scroll-ttl-millis INTEGER: How long the scroll stays open, in milliseconds.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues count¶

Count issues matching a TQL query or filters (bare integer).

With no --query and no filters this sends an empty filter — the API then counts EVERY issue in the org. Pass --queue/--status (or --query) to narrow.

Usage:

$ ycli tracker issues count [OPTIONS]

Options:

• --query TEXT: TQL query (mutually exclusive with filters).
• --queue TEXT: Queue key.
• --status TEXT: Status key.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues create¶

Create an issue (POST /issues/). type/priority wrap to {"key": …}; queue/parent stay bare.

Usage:

$ ycli tracker issues create [OPTIONS]

Options:

• --queue TEXT: Target queue key. [required]
• --summary TEXT: Issue summary (title). [required]
• --type TEXT: Issue type key, e.g. task.
• --priority TEXT: Priority key, e.g. normal.
• --parent TEXT: Parent issue key.
• --description TEXT: Markdown body — pass "$(cat file.md)".
• --tag TEXT: Tag (repeatable).
• -F, --field TEXT: Extra field key=value (JSON-coerced; repeatable).
• --notify / --no-notify: Notify the users in the fields of the object (the API notifies by default).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues update¶

Update issue KEY (PATCH /issues/{key}) — only supplied fields are sent.

Usage:

$ ycli tracker issues update [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --summary TEXT: New summary.
• --type TEXT: New issue type key.
• --priority TEXT: New priority key.
• --parent TEXT: New parent issue key.
• --description TEXT: New markdown body — pass "$(cat file.md)"; "" clears it.
• --tag TEXT: Tag (repeatable).
• -F, --field TEXT: Extra field key=value (JSON-coerced; repeatable).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues move¶

Move issue KEY to another QUEUE (POST /issues/{key}/_move?queue=QUEUE).

Usage:

$ ycli tracker issues move [OPTIONS] KEY QUEUE

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• QUEUE: Target queue key, e.g. NEW. [required]

Options:

• --expand TEXT: Extra blocks to include in the reply.
• --initial-status / --no-initial-status: Reset the status to the new queue's initial one.
• --move-all-fields / --no-move-all-fields: Keep the versions, components and projects the new queue also has.
• --notify / --no-notify: Notify the users in the fields of the object (the API notifies by default).
• --notify-author / --no-notify-author: Notify the author of the change (the API does not by default).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues suggest¶

Suggest issues whose summary contains INPUT (GET /issues/_suggest?input=INPUT).

Usage:

$ ycli tracker issues suggest [OPTIONS] INPUT

Arguments:

• INPUT: Text fragment to match in titles. [required]

Options:

• --queue TEXT: Key of the queue to search in.
• --full / --no-full: Return each issue in full; needed for --fields, --expand, --embed.
• --fields TEXT: Comma-separated fields to include in the reply.
• --expand TEXT: Extra blocks to include in the reply.
• --embed TEXT: Blocks of --expand to return in more detail.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issues scroll-clear¶

Release search-scroll resources (POST /system/search/scroll/_clear).

Pass each --pair scrollId=scrollToken from a scrolled issues search.

Usage:

$ ycli tracker issues scroll-clear [OPTIONS]

Options:

• --pair TEXT: scrollId=scrollToken pair to release (repeatable).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker comments¶

Tracker issue comments.

Usage:

$ ycli tracker comments [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all comments on issue KEY...
• get: Print comment COMMENT_ID of issue KEY.
• add: Add a comment to issue KEY.
• update: Edit comment COMMENT_ID on issue KEY.
• delete: Delete comment COMMENT_ID from issue KEY.
• react: Add reaction NAME to comment COMMENT_ID on...

ycli tracker comments list¶

List all comments on issue KEY (auto-paginated; --all for everything).

Usage:

$ ycli tracker comments list [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• --expand TEXT: Extra blocks to include in the reply.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker comments get¶

Print comment COMMENT_ID of issue KEY.

Usage:

$ ycli tracker comments get [OPTIONS] KEY COMMENT_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• COMMENT_ID: Comment id (numeric id or longId). [required]

Options:

• --expand TEXT: Extra fields: attachments, html or all (comma-separated).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker comments add¶

Add a comment to issue KEY.

Usage:

$ ycli tracker comments add [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --text TEXT: Comment text — pass "$(cat note.md)" for markdown. [required]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker comments update¶

Edit comment COMMENT_ID on issue KEY.

Usage:

$ ycli tracker comments update [OPTIONS] KEY COMMENT_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• COMMENT_ID: Comment id (numeric id or longId). [required]

Options:

• --text TEXT: New comment text (YFM markdown supported). [required]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker comments delete¶

Delete comment COMMENT_ID from issue KEY.

Usage:

$ ycli tracker comments delete [OPTIONS] KEY COMMENT_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• COMMENT_ID: Comment id (numeric id or longId). [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker comments react¶

Add reaction NAME to comment COMMENT_ID on issue KEY.

Usage:

$ ycli tracker comments react [OPTIONS] KEY COMMENT_ID NAME:{LIKE|DISLIKE|LAUGH|HOORAY|CONFUSED|HEART|ROCKET|EYES|FIRE|OK|FACEPALM|CHECK}

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• COMMENT_ID: Comment id (numeric id or longId). [required]
• NAME:{LIKE|DISLIKE|LAUGH|HOORAY|CONFUSED|HEART|ROCKET|EYES|FIRE|OK|FACEPALM|CHECK}: Reaction name, e.g. LIKE, HEART, ROCKET. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker links¶

Tracker issue links.

Usage:

$ ycli tracker links [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List links for issue KEY.
• search: List links of issue KEY, filtered and...
• add: Link issue KEY to TARGET with RELATIONSHIP.
• delete: Delete link LINK_ID from issue KEY.

ycli tracker links list¶

List links for issue KEY.

Usage:

$ ycli tracker links list [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker links search¶

List links of issue KEY, filtered and paged (POST …/links/_list; --all for everything).

Usage:

$ ycli tracker links search [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --type TEXT: Keep only links with this relationship, e.g. relates (repeatable).
• --field TEXT: Field to include in each link (repeatable).
• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker links add¶

Link issue KEY to TARGET with RELATIONSHIP.

Usage:

$ ycli tracker links add [OPTIONS] KEY RELATIONSHIP:{depends on|is dependent by|relates|duplicates|is duplicated by|subtask|parent} TARGET

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• RELATIONSHIP:{depends on|is dependent by|relates|duplicates|is duplicated by|subtask|parent}: Relationship verb. [required]
• TARGET: Target issue key, e.g. DATAENGINEERING-2. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker links delete¶

Delete link LINK_ID from issue KEY.

Usage:

$ ycli tracker links delete [OPTIONS] KEY LINK_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• LINK_ID: Link id to remove. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker transitions¶

Tracker issue transitions.

Usage:

$ ycli tracker transitions [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List available transitions for issue KEY.
• execute: Execute transition ID on issue KEY...

ycli tracker transitions list¶

List available transitions for issue KEY.

Usage:

$ ycli tracker transitions list [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker transitions execute¶

Execute transition ID on issue KEY (optional body via --field).

Usage:

$ ycli tracker transitions execute [OPTIONS] KEY ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• ID: Transition id (from transitions list). [required]

Options:

• -F, --field TEXT: Transition body field key=value (JSON-coerced; repeatable).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker worklog¶

Tracker issue worklog.

Usage:

$ ycli tracker worklog [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all worklog entries for issue KEY...
• search: Search org-wide worklog by author and/or...
• global-list: List org-wide worklog via GET /worklog...
• create: Log time spent on issue KEY (POST...
• update: Edit worklog RECORD_ID on issue KEY — only...
• delete: Delete worklog RECORD_ID from issue KEY.

ycli tracker worklog list¶

List all worklog entries for issue KEY (auto-paginated; --all for everything).

Usage:

$ ycli tracker worklog list [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker worklog search¶

Search org-wide worklog by author and/or time range (POST /worklog/_search).

Usage:

$ ycli tracker worklog search [OPTIONS]

Options:

• --created-by TEXT: Author login or id.
• --from TEXT: Range start, YYYY-MM-DDThhss.
• --to TEXT: Range end, YYYY-MM-DDThhss.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker worklog global-list¶

List org-wide worklog via GET /worklog (createdAt filters need --created-by).

Usage:

$ ycli tracker worklog global-list [OPTIONS]

Options:

• --created-by TEXT: Author login or id.
• --from TEXT: Range start, YYYY-MM-DDThhss.
• --to TEXT: Range end, YYYY-MM-DDThhss.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker worklog create¶

Log time spent on issue KEY (POST /issues/{key}/worklog).

Usage:

$ ycli tracker worklog create [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --duration TEXT: Time spent, ISO-8601 duration (e.g. PT2H, PT300M, P1DT3H). [required]
• --start TEXT: Work start time, YYYY-MM-DDThhss.sss±hhmm; now when omitted.
• --comment TEXT: Optional note saved in the time report.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker worklog update¶

Edit worklog RECORD_ID on issue KEY — only supplied fields are sent.

Usage:

$ ycli tracker worklog update [OPTIONS] KEY RECORD_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• RECORD_ID: Worklog record id to edit/delete. [required]

Options:

• --duration TEXT: New time spent, ISO-8601 duration.
• --comment TEXT: New note for the time report.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker worklog delete¶

Delete worklog RECORD_ID from issue KEY.

Usage:

$ ycli tracker worklog delete [OPTIONS] KEY RECORD_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• RECORD_ID: Worklog record id to edit/delete. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker changelog¶

Tracker issue changelog.

Usage:

$ ycli tracker changelog [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all changelog entries for issue KEY...

ycli tracker changelog list¶

List all changelog entries for issue KEY (auto-paginated; --all for everything).

Usage:

$ ycli tracker changelog list [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• --field TEXT: Only changes of this field, e.g. status.
• --type TEXT: Only changes of this type, e.g. IssueWorkflow.
• --sort TEXT: Order of the changes: asc or desc.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker checklists¶

Tracker issue checklists.

Usage:

$ ycli tracker checklists [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• get: List the checklist items on issue KEY.
• create: Add a checklist item to issue KEY (creates...
• update: Edit checklist item ITEM_ID on issue KEY —...
• delete: Delete checklist item ITEM_ID from issue KEY.
• clear: Delete the entire checklist from issue KEY.

ycli tracker checklists get¶

List the checklist items on issue KEY.

Usage:

$ ycli tracker checklists get [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker checklists create¶

Add a checklist item to issue KEY (creates the checklist if absent).

Usage:

$ ycli tracker checklists create [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --text TEXT: Item text. [required]
• --checked / --no-checked: Done flag.
• --assignee TEXT: Assignee login or id.
• --deadline TEXT: Deadline date, YYYY-MM-DDThhss.sss±hhmm.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker checklists update¶

Edit checklist item ITEM_ID on issue KEY — only supplied fields are sent.

Usage:

$ ycli tracker checklists update [OPTIONS] KEY ITEM_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• ITEM_ID: Checklist item id. [required]

Options:

• --text TEXT: Item text.
• --checked / --no-checked: Done flag.
• --assignee TEXT: Assignee login or id.
• --deadline TEXT: Deadline date, YYYY-MM-DDThhss.sss±hhmm.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker checklists delete¶

Delete checklist item ITEM_ID from issue KEY.

Usage:

$ ycli tracker checklists delete [OPTIONS] KEY ITEM_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• ITEM_ID: Checklist item id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker checklists clear¶

Delete the entire checklist from issue KEY.

Usage:

$ ycli tracker checklists clear [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker columns¶

Tracker agile board columns.

Usage:

$ ycli tracker columns [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all columns on board BOARD_ID.
• get: Get one column COLUMN_ID on board BOARD_ID.
• create: Create a column on board BOARD_ID (POST...
• update: Edit column COLUMN_ID on board BOARD_ID...
• delete: Delete column COLUMN_ID on board BOARD_ID...

ycli tracker columns list¶

List all columns on board BOARD_ID.

Usage:

$ ycli tracker columns list [OPTIONS] BOARD_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker columns get¶

Get one column COLUMN_ID on board BOARD_ID.

Usage:

$ ycli tracker columns get [OPTIONS] BOARD_ID COLUMN_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]
• COLUMN_ID: Numeric column identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker columns create¶

Create a column on board BOARD_ID (POST /boards/{board_id}/columns/).

Usage:

$ ycli tracker columns create [OPTIONS] BOARD_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]

Options:

• --name TEXT: Name of the new column. [required]
• --status TEXT: Status key for the column (repeatable). [required]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker columns update¶

Edit column COLUMN_ID on board BOARD_ID (PATCH) — only supplied fields are sent.

Usage:

$ ycli tracker columns update [OPTIONS] BOARD_ID COLUMN_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]
• COLUMN_ID: Numeric column identifier. [required]

Options:

• --name TEXT: New column name.
• --status TEXT: Replacement status key (repeatable).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker columns delete¶

Delete column COLUMN_ID on board BOARD_ID (DELETE /boards/{board_id}/columns/{column_id}).

Usage:

$ ycli tracker columns delete [OPTIONS] BOARD_ID COLUMN_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]
• COLUMN_ID: Numeric column identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker priorities¶

Tracker priorities.

Usage:

$ ycli tracker priorities [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all priorities.
• create: Create a priority (POST /priorities/).
• update: Edit priority PRIORITY_ID (PATCH...

ycli tracker priorities list¶

List all priorities.

Usage:

$ ycli tracker priorities list [OPTIONS]

Options:

• --localized / --no-localized: --no-localized returns the names in every language.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker priorities create¶

Create a priority (POST /priorities/).

Usage:

$ ycli tracker priorities create [OPTIONS]

Options:

• --key TEXT: Key of the new priority. [required]
• --name-ru TEXT: Priority name in Russian.
• --name-en TEXT: Priority name in English.
• --order INTEGER: Display-order weight of the priority.
• --description TEXT: Description of the priority.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker priorities update¶

Edit priority PRIORITY_ID (PATCH /priorities/{id}?version=).

Usage:

$ ycli tracker priorities update [OPTIONS] PRIORITY_ID

Arguments:

• PRIORITY_ID: Priority id or key. [required]

Options:

• --name-ru TEXT: New priority name in Russian.
• --name-en TEXT: New priority name in English.
• --description TEXT: New description of the priority.
• --version INTEGER: Current version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issuetypes¶

Tracker issue types.

Usage:

$ ycli tracker issuetypes [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all issue types.
• create: Create an issue type (POST /issuetypes/).
• update: Edit issue type ISSUE_TYPE_ID (PATCH...

ycli tracker issuetypes list¶

List all issue types.

Usage:

$ ycli tracker issuetypes list [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issuetypes create¶

Create an issue type (POST /issuetypes/).

Usage:

$ ycli tracker issuetypes create [OPTIONS]

Options:

• --key TEXT: Key of the new issue type. [required]
• --name-ru TEXT: Issue type name in Russian.
• --name-en TEXT: Issue type name in English.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker issuetypes update¶

Edit issue type ISSUE_TYPE_ID (PATCH /issuetypes/{id}?version=).

Usage:

$ ycli tracker issuetypes update [OPTIONS] ISSUE_TYPE_ID

Arguments:

• ISSUE_TYPE_ID: Issue type id or key. [required]

Options:

• --name-ru TEXT: New issue type name in Russian.
• --name-en TEXT: New issue type name in English.
• --version INTEGER: Current version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker linktypes¶

Tracker link types.

Usage:

$ ycli tracker linktypes [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all link types.

ycli tracker linktypes list¶

List all link types.

Usage:

$ ycli tracker linktypes list [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker users¶

Tracker organisation users.

Usage:

$ ycli tracker users [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• get: Get one user account by LOGIN_OR_ID.
• list: List all organisation users...

ycli tracker users get¶

Get one user account by LOGIN_OR_ID.

Usage:

$ ycli tracker users get [OPTIONS] LOGIN_OR_ID

Arguments:

• LOGIN_OR_ID: User login or uid (login:12345 if numeric). [required]

Options:

• --expand TEXT: Extra data to include, e.g. groups.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker users list¶

List all organisation users (auto-paginated; --all for everything).

Usage:

$ ycli tracker users list [OPTIONS]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• --expand TEXT: Extra data to include, e.g. groups.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker statuses¶

Tracker issue statuses.

Usage:

$ ycli tracker statuses [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all issue statuses.
• create: Create an issue status (POST /statuses/).
• update: Edit issue status STATUS_ID (PATCH...

ycli tracker statuses list¶

List all issue statuses.

Usage:

$ ycli tracker statuses list [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker statuses create¶

Create an issue status (POST /statuses/).

Usage:

$ ycli tracker statuses create [OPTIONS]

Options:

• --key TEXT: Key of the new status (Latin, lower-case start). [required]
• --name-ru TEXT: Status name in Russian.
• --name-en TEXT: Status name in English.
• --type TEXT: Status type: new/inProgress/paused/done/cancelled. [default: new]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker statuses update¶

Edit issue status STATUS_ID (PATCH /statuses/{id}?version=).

Usage:

$ ycli tracker statuses update [OPTIONS] STATUS_ID

Arguments:

• STATUS_ID: Status id or key. [required]

Options:

• --name-ru TEXT: New status name in Russian.
• --name-en TEXT: New status name in English.
• --description TEXT: New status description.
• --type TEXT: New status type.
• --order INTEGER: New display-order weight.
• --version INTEGER: Current version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker resolutions¶

Tracker issue resolutions.

Usage:

$ ycli tracker resolutions [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all issue resolutions.
• create: Create an issue resolution (POST...
• update: Edit issue resolution RESOLUTION_ID (PATCH...

ycli tracker resolutions list¶

List all issue resolutions.

Usage:

$ ycli tracker resolutions list [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker resolutions create¶

Create an issue resolution (POST /resolutions/).

Usage:

$ ycli tracker resolutions create [OPTIONS]

Options:

• --key TEXT: Key of the new resolution (Latin, lower-case start). [required]
• --name-ru TEXT: Resolution name in Russian.
• --name-en TEXT: Resolution name in English.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker resolutions update¶

Edit issue resolution RESOLUTION_ID (PATCH /resolutions/{id}?version=).

Usage:

$ ycli tracker resolutions update [OPTIONS] RESOLUTION_ID

Arguments:

• RESOLUTION_ID: Resolution id or key. [required]

Options:

• --name-ru TEXT: New resolution name in Russian.
• --name-en TEXT: New resolution name in English.
• --description TEXT: New resolution description.
• --order INTEGER: New display-order weight.
• --version INTEGER: Current version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues¶

Tracker queues.

Usage:

$ ycli tracker queues [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all queues (auto-paginated over...
• get: Print one queue's settings for QUEUE_ID.
• tags-list: List the tags added to QUEUE_ID.
• versions-list: List the versions defined on QUEUE_ID.
• fields-list: List the required/local fields of QUEUE_ID.
• create: Create a queue (POST /queues/).
• delete: Delete QUEUE_ID (DELETE /queues/{queue_id}).
• restore: Restore a deleted QUEUE_ID (POST...
• set-permissions: Manage access to QUEUE_ID (PATCH...
• tag-remove: Remove TAG from QUEUE_ID (POST...
• version-create: Create a queue version (POST /versions/).
• version-get: Print queue version VERSION_ID (GET...
• version-update: Edit queue version VERSION_ID (PATCH...
• version-delete: Delete queue version VERSION_ID (DELETE...
• user-permissions-get: Show what USER may do in QUEUE_ID (GET...
• group-permissions-get: Show what GROUP_ID may do in QUEUE_ID (GET...

ycli tracker queues list¶

List all queues (auto-paginated over pages; --all for everything).

Usage:

$ ycli tracker queues list [OPTIONS]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• --expand TEXT: Extra blocks to include in the reply.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues get¶

Print one queue's settings for QUEUE_ID.

Usage:

$ ycli tracker queues get [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --expand TEXT: Extra blocks to include, e.g. all or types,team,versions.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues tags-list¶

List the tags added to QUEUE_ID.

Usage:

$ ycli tracker queues tags-list [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues versions-list¶

List the versions defined on QUEUE_ID.

Usage:

$ ycli tracker queues versions-list [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues fields-list¶

List the required/local fields of QUEUE_ID.

Usage:

$ ycli tracker queues fields-list [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues create¶

Create a queue (POST /queues/).

Usage:

$ ycli tracker queues create [OPTIONS]

Options:

• --key TEXT: Key of the new queue (case-sensitive, e.g. DESIGN). [required]
• --name TEXT: Human-readable name of the queue. [required]
• --lead TEXT: Login or id of the queue owner (lead). [required]
• --default-type TEXT: Key/id of the default issue type. [required]
• --default-priority TEXT: Key/id of the default priority. [required]
• --issue-type-config TEXT: issueTypesConfig row as JSON, e.g. '{"issueType":"task","workflow":"oicn"}' (repeatable).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues delete¶

Delete QUEUE_ID (DELETE /queues/{queue_id}).

Usage:

$ ycli tracker queues delete [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues restore¶

Restore a deleted QUEUE_ID (POST /queues/{queue_id}/_restore; admin only).

Usage:

$ ycli tracker queues restore [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues set-permissions¶

Manage access to QUEUE_ID (PATCH /queues/{queue_id}/permissions).

Each scope is a JSON object of users/groups/roles, e.g. --grant '{"roles": {"add": ["author"]}}'. Pass at least one scope.

Usage:

$ ycli tracker queues set-permissions [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --create TEXT: Create-issue permission scope as a JSON object.
• --write TEXT: Edit-issue permission scope as a JSON object.
• --read TEXT: Read-issue permission scope as a JSON object.
• --grant TEXT: Change-settings permission scope as a JSON object.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues tag-remove¶

Remove TAG from QUEUE_ID (POST /queues/{queue_id}/tags/_remove; admin only).

Usage:

$ ycli tracker queues tag-remove [OPTIONS] QUEUE_ID TAG

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• TAG: Name of the tag to remove. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues version-create¶

Create a queue version (POST /versions/).

Usage:

$ ycli tracker queues version-create [OPTIONS]

Options:

• --queue TEXT: Key of the queue to create the version in. [required]
• --name TEXT: Name of the new version. [required]
• --description TEXT: Description of the version.
• --start-date TEXT: Version start date (YYYY-MM-DD).
• --due-date TEXT: Version due date (YYYY-MM-DD).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues version-get¶

Print queue version VERSION_ID (GET /versions/{id}).

Usage:

$ ycli tracker queues version-get [OPTIONS] VERSION_ID

Arguments:

• VERSION_ID: Numeric id of the queue version. [required]

Options:

• --fields TEXT: Comma-separated fields to return, e.g. name,dueDate,released.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues version-update¶

Edit queue version VERSION_ID (PATCH /versions/{id}); only the given options change.

Usage:

$ ycli tracker queues version-update [OPTIONS] VERSION_ID

Arguments:

• VERSION_ID: Numeric id of the queue version. [required]

Options:

• --name TEXT: New name of the version.
• --description TEXT: New description of the version.
• --start-date TEXT: New version start date (YYYY-MM-DD).
• --due-date TEXT: New version due date (YYYY-MM-DD).
• --fields TEXT: Comma-separated fields to return, e.g. name,dueDate,released.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues version-delete¶

Delete queue version VERSION_ID (DELETE /versions/{id}).

Usage:

$ ycli tracker queues version-delete [OPTIONS] VERSION_ID

Arguments:

• VERSION_ID: Numeric id of the queue version. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues user-permissions-get¶

Show what USER may do in QUEUE_ID (GET /queues/{id}/permissions/users/{user}).

Usage:

$ ycli tracker queues user-permissions-get [OPTIONS] QUEUE_ID USER

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• USER: Login or numeric uid of the user. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker queues group-permissions-get¶

Show what GROUP_ID may do in QUEUE_ID (GET /queues/{id}/permissions/groups/{group}).

Usage:

$ ycli tracker queues group-permissions-get [OPTIONS] QUEUE_ID GROUP_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• GROUP_ID: Numeric id of the group. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker localfields¶

Tracker per-queue local fields.

Usage:

$ ycli tracker localfields [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List the local fields of queue QUEUE_ID.
• get: Print one local field FIELD_KEY of queue...
• create: Create a local field in queue QUEUE_ID...
• update: Edit local field FIELD_KEY of queue...

ycli tracker localfields list¶

List the local fields of queue QUEUE_ID.

Usage:

$ ycli tracker localfields list [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker localfields get¶

Print one local field FIELD_KEY of queue QUEUE_ID.

Usage:

$ ycli tracker localfields get [OPTIONS] QUEUE_ID FIELD_KEY

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• FIELD_KEY: Local field key (from localfields list). [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker localfields create¶

Create a local field in queue QUEUE_ID (POST /queues/{id}/localFields).

Usage:

$ ycli tracker localfields create [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --id TEXT: Identifier (key) of the new local field. [required]
• --type TEXT: Field type FQN, e.g. …StringFieldType. [required]
• --category TEXT: Category id (from GET /fields/categories). [required]
• --name-ru TEXT: Field name in Russian.
• --name-en TEXT: Field name in English.
• --description TEXT: Description of the local field.
• --order INTEGER: Position in the org's field list.
• --readonly / --no-readonly: Whether the field value is read-only.
• --option TEXT: Allowed drop-down value (repeatable).
• --options-type TEXT: Drop-down provider type for --option values. [default: FixedListOptionsProvider]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker localfields update¶

Edit local field FIELD_KEY of queue QUEUE_ID (PATCH …/localFields/{key}; no version lock).

Usage:

$ ycli tracker localfields update [OPTIONS] QUEUE_ID FIELD_KEY

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• FIELD_KEY: Local field key (from localfields list). [required]

Options:

• --name-ru TEXT: New field name in Russian.
• --name-en TEXT: New field name in English.
• --category TEXT: New category id.
• --description TEXT: New description of the local field.
• --order INTEGER: New position in the field list.
• --readonly / --no-readonly: Read-only value.
• --visible / --no-visible: Always show the field.
• --hidden / --no-hidden: Fully hide the field.
• --option TEXT: Allowed drop-down value (repeatable).
• --options-type TEXT: Drop-down provider type for --option values. [default: FixedListOptionsProvider]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker fields¶

Tracker global fields.

Usage:

$ ycli tracker fields [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all global fields of the organisation.
• get: Get parameters of one issue field by...
• create: Create a global field (POST /fields).
• update: Edit a global field FIELD_ID — rename...
• category-create: Create a field category (POST...
• category-update: Edit a field category CATEGORY_ID (PATCH...

ycli tracker fields list¶

List all global fields of the organisation.

Usage:

$ ycli tracker fields list [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker fields get¶

Get parameters of one issue field by FIELD_ID.

Usage:

$ ycli tracker fields get [OPTIONS] FIELD_ID

Arguments:

• FIELD_ID: Identifier of the issue field. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker fields create¶

Create a global field (POST /fields).

Usage:

$ ycli tracker fields create [OPTIONS]

Options:

• --id TEXT: Identifier (key) of the new field. [required]
• --type TEXT: Field type FQN, e.g. …StringFieldType. [required]
• --category TEXT: Category id (from fields categories). [required]
• --name-ru TEXT: Field name in Russian.
• --name-en TEXT: Field name in English.
• --description TEXT: Description of the field.
• --order INTEGER: Position in the org's field list.
• --readonly / --no-readonly: Whether the field value is read-only.
• --option TEXT: Allowed drop-down value (repeatable).
• --options-type TEXT: Drop-down provider type for --option values. [default: FixedListOptionsProvider]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker fields update¶

Edit a global field FIELD_ID — rename and/or change options (PATCH /fields/{id}?version=).

Usage:

$ ycli tracker fields update [OPTIONS] FIELD_ID

Arguments:

• FIELD_ID: Identifier of the field. [required]

Options:

• --name-ru TEXT: New field name in Russian.
• --name-en TEXT: New field name in English.
• --option TEXT: Allowed drop-down value (repeatable).
• --options-type TEXT: Drop-down provider type for --option values. [default: FixedListOptionsProvider]
• --version INTEGER: Current version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker fields category-create¶

Create a field category (POST /fields/categories).

Usage:

$ ycli tracker fields category-create [OPTIONS]

Options:

• --order INTEGER: Display-order weight of the category. [required]
• --name-ru TEXT: Category name in Russian.
• --name-en TEXT: Category name in English.
• --description TEXT: Description of the category.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker fields category-update¶

Edit a field category CATEGORY_ID (PATCH /fields/categories/{id}?version=).

Usage:

$ ycli tracker fields category-update [OPTIONS] CATEGORY_ID

Arguments:

• CATEGORY_ID: Identifier of the field category. [required]

Options:

• --name-ru TEXT: New category name in Russian.
• --name-en TEXT: New category name in English.
• --order INTEGER: New display-order weight.
• --description TEXT: New description of the category.
• --version INTEGER: Current version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components¶

Tracker components.

Usage:

$ ycli tracker components [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all components created in the...
• create: Create a component (POST /components).
• update: Edit component COMPONENT_ID (PATCH...
• list-for-queue: List the components of one queue (GET...
• get: Print component COMPONENT_ID (GET...
• delete: Delete component COMPONENT_ID (DELETE...
• user-permissions-get: Show what USER may do on a component (GET...
• group-permissions-get: Show what GROUP_ID may do on a component...

ycli tracker components list¶

List all components created in the organisation.

Usage:

$ ycli tracker components list [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components create¶

Create a component (POST /components).

Usage:

$ ycli tracker components create [OPTIONS]

Options:

• --name TEXT: Display name of the new component. [required]
• --queue TEXT: Key of the queue the component is created in. [required]
• --description TEXT: Text description of the component.
• --lead TEXT: Login of the component's owner (lead).
• --assign-auto / --no-assign-auto: Auto-assign the owner to issues.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components update¶

Edit component COMPONENT_ID (PATCH /components/{id}?version=).

Usage:

$ ycli tracker components update [OPTIONS] COMPONENT_ID

Arguments:

• COMPONENT_ID: Numeric id of the component. [required]

Options:

• --name TEXT: New display name of the component.
• --description TEXT: New text description of the component.
• --lead TEXT: New login of the component's owner (lead).
• --assign-auto / --no-assign-auto: Auto-assign the owner to issues.
• --version INTEGER: Current version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components list-for-queue¶

List the components of one queue (GET /queues/{id}/components).

Usage:

$ ycli tracker components list-for-queue [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --fields TEXT: Comma-separated fields to return, e.g. name,description,lead.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components get¶

Print component COMPONENT_ID (GET /components/{id}).

Usage:

$ ycli tracker components get [OPTIONS] COMPONENT_ID

Arguments:

• COMPONENT_ID: Numeric id of the component. [required]

Options:

• --fields TEXT: Comma-separated fields to return, e.g. name,description,lead.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components delete¶

Delete component COMPONENT_ID (DELETE /components/{id}).

Usage:

$ ycli tracker components delete [OPTIONS] COMPONENT_ID

Arguments:

• COMPONENT_ID: Numeric id of the component. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components user-permissions-get¶

Show what USER may do on a component (GET /components/{id}/permissions/users/{user}).

Usage:

$ ycli tracker components user-permissions-get [OPTIONS] COMPONENT_ID USER

Arguments:

• COMPONENT_ID: Numeric id of the component. [required]
• USER: Login or numeric uid of the user. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker components group-permissions-get¶

Show what GROUP_ID may do on a component (…/permissions/groups/{group}).

Usage:

$ ycli tracker components group-permissions-get [OPTIONS] COMPONENT_ID GROUP_ID

Arguments:

• COMPONENT_ID: Numeric id of the component. [required]
• GROUP_ID: Numeric id of the group. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker filters¶

Tracker saved filters.

Usage:

$ ycli tracker filters [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• get: Get parameters of one saved filter by...
• create: Create a saved filter (POST /filters/).
• update: Edit filter FILTER_ID (PATCH...
• delete: Delete saved filter FILTER_ID (DELETE...

ycli tracker filters get¶

Get parameters of one saved filter by FILTER_ID.

Usage:

$ ycli tracker filters get [OPTIONS] FILTER_ID

Arguments:

• FILTER_ID: Identifier of the saved filter. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker filters create¶

Create a saved filter (POST /filters/).

Usage:

$ ycli tracker filters create [OPTIONS]

Options:

• --name TEXT: Display name of the new filter. [required]
• --query TEXT: Filtering conditions in Tracker query language.
• --filter TEXT: Filtering conditions as a JSON object.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker filters update¶

Edit filter FILTER_ID (PATCH /filters/{id}) — no version lock; filter is replaced whole.

Usage:

$ ycli tracker filters update [OPTIONS] FILTER_ID

Arguments:

• FILTER_ID: Identifier of the saved filter. [required]

Options:

• --name TEXT: New display name of the filter.
• --query TEXT: New filtering conditions in query language.
• --filter TEXT: Replacement filtering conditions as a JSON object.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker filters delete¶

Delete saved filter FILTER_ID (DELETE /filters/{id}).

Usage:

$ ycli tracker filters delete [OPTIONS] FILTER_ID

Arguments:

• FILTER_ID: Identifier of the saved filter. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker applications¶

Tracker external applications.

Usage:

$ ycli tracker applications [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List external applications that issues can...

ycli tracker applications list¶

List external applications that issues can be linked to.

Usage:

$ ycli tracker applications list [OPTIONS]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker boards¶

Tracker agile boards.

Usage:

$ ycli tracker boards [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all agile boards (auto-paginated;...
• get: Get one agile board by BOARD_ID.
• create: Create an agile board (POST /liveBoards/).
• update: Edit an agile board BOARD_ID (PATCH...
• delete: Delete an agile board BOARD_ID (DELETE...

ycli tracker boards list¶

List all agile boards (auto-paginated; --all for everything).

Usage:

$ ycli tracker boards list [OPTIONS]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker boards get¶

Get one agile board by BOARD_ID.

Usage:

$ ycli tracker boards get [OPTIONS] BOARD_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker boards create¶

Create an agile board (POST /liveBoards/).

Usage:

$ ycli tracker boards create [OPTIONS]

Options:

• --name TEXT: Name of the new board. [required]
• --owner TEXT: Login or uid of the board owner.
• --permissions TEXT: Access template: 'private' or 'public'.
• --backlog / --no-backlog: Enable the board backlog.
• --sprints / --no-sprints: Enable board sprints.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker boards update¶

Edit an agile board BOARD_ID (PATCH /boards/{board_id}) — only supplied fields are sent.

Usage:

$ ycli tracker boards update [OPTIONS] BOARD_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]

Options:

• --name TEXT: New board name.
• --backlog / --no-backlog: Enable the board backlog.
• --sprints / --no-sprints: Enable board sprints.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker boards delete¶

Delete an agile board BOARD_ID (DELETE /boards/{board_id}).

Usage:

$ ycli tracker boards delete [OPTIONS] BOARD_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker sprints¶

Tracker board sprints.

Usage:

$ ycli tracker sprints [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List all sprints on board BOARD_ID.
• get: Get one sprint by SPRINT_ID.
• create: Create a sprint (POST /sprints).
• update: Edit a sprint SPRINT_ID (PATCH...
• delete: Delete a sprint SPRINT_ID (DELETE...
• start: Start a sprint SPRINT_ID (POST...
• archive: Archive a sprint SPRINT_ID (POST...

ycli tracker sprints list¶

List all sprints on board BOARD_ID.

Usage:

$ ycli tracker sprints list [OPTIONS] BOARD_ID

Arguments:

• BOARD_ID: Numeric board identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker sprints get¶

Get one sprint by SPRINT_ID.

Usage:

$ ycli tracker sprints get [OPTIONS] SPRINT_ID

Arguments:

• SPRINT_ID: Numeric sprint identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker sprints create¶

Create a sprint (POST /sprints).

Usage:

$ ycli tracker sprints create [OPTIONS]

Options:

• --board-id TEXT: Identifier of the board the sprint belongs to. [required]
• --name TEXT: Name of the new sprint. [required]
• --start-date TEXT: Planned start date (YYYY-MM-DD). [required]
• --end-date TEXT: Planned end date (YYYY-MM-DD). [required]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker sprints update¶

Edit a sprint SPRINT_ID (PATCH /sprints/{id}?version=) — only supplied fields are sent.

Usage:

$ ycli tracker sprints update [OPTIONS] SPRINT_ID

Arguments:

• SPRINT_ID: Numeric sprint identifier. [required]

Options:

• --name TEXT: New sprint name.
• --start-date TEXT: New start date (YYYY-MM-DD).
• --end-date TEXT: New end date (YYYY-MM-DD).
• --status TEXT: New status: draft/in_progress/released/archived.
• --version INTEGER: Current sprint version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker sprints delete¶

Delete a sprint SPRINT_ID (DELETE /sprints/{sprint_id}).

Usage:

$ ycli tracker sprints delete [OPTIONS] SPRINT_ID

Arguments:

• SPRINT_ID: Numeric sprint identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker sprints start¶

Start a sprint SPRINT_ID (POST /sprints/{id}/_start?version=; status → in_progress).

Usage:

$ ycli tracker sprints start [OPTIONS] SPRINT_ID

Arguments:

• SPRINT_ID: Numeric sprint identifier. [required]

Options:

• --version INTEGER: Current sprint version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker sprints archive¶

Archive a sprint SPRINT_ID (POST /sprints/{id}/_archive?version=; status → archived).

Usage:

$ ycli tracker sprints archive [OPTIONS] SPRINT_ID

Arguments:

• SPRINT_ID: Numeric sprint identifier. [required]

Options:

• --version INTEGER: Current sprint version for the optimistic lock (?version=).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker attachments¶

Tracker issue attachments.

Usage:

$ ycli tracker attachments [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List files attached to an issue (GET...
• download: Download an attachment's raw bytes to...
• thumbnail: Download a graphic attachment's preview...
• get: Print an attachment's metadata (GET...
• delete: Delete an attachment from an issue (DELETE...
• upload: Attach a local file to an issue (POST...
• upload-temp: Upload a temporary file (POST...

ycli tracker attachments list¶

List files attached to an issue (GET /issues/{issue}/attachments).

Usage:

$ ycli tracker attachments list [OPTIONS] ISSUE

Arguments:

• ISSUE: Issue key or id, e.g. JUNE-2. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker attachments download¶

Download an attachment's raw bytes to --output (or stdout). Binary is CLI/SDK-only.

Usage:

$ ycli tracker attachments download [OPTIONS] ISSUE FILE_ID FILENAME

Arguments:

• ISSUE: Issue key or id, e.g. JUNE-2. [required]
• FILE_ID: Attachment file id. [required]
• FILENAME: Attachment file name. [required]

Options:

• -O, --output TEXT: Write to this path; omit or '-' for stdout.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker attachments thumbnail¶

Download a graphic attachment's preview thumbnail to --output (or stdout).

Usage:

$ ycli tracker attachments thumbnail [OPTIONS] ISSUE FILE_ID

Arguments:

• ISSUE: Issue key or id, e.g. JUNE-2. [required]
• FILE_ID: Attachment file id. [required]

Options:

• -O, --output TEXT: Write to this path; omit or '-' for stdout.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker attachments get¶

Print an attachment's metadata (GET /issues/{issue}/attachments/{file_id}).

Usage:

$ ycli tracker attachments get [OPTIONS] ISSUE FILE_ID

Arguments:

• ISSUE: Issue key or id, e.g. JUNE-2. [required]
• FILE_ID: Attachment file id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker attachments delete¶

Delete an attachment from an issue (DELETE /issues/{issue}/attachments/{file_id}).

Usage:

$ ycli tracker attachments delete [OPTIONS] ISSUE FILE_ID

Arguments:

• ISSUE: Issue key or id, e.g. JUNE-2. [required]
• FILE_ID: Attachment file id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker attachments upload¶

Attach a local file to an issue (POST /issues/{issue}/attachments).

Usage:

$ ycli tracker attachments upload [OPTIONS] ISSUE FILE_PATH

Arguments:

• ISSUE: Issue key or id, e.g. JUNE-2. [required]
• FILE_PATH: Local file to upload. [required]

Options:

• --rename-to TEXT: Store the file under this name instead of its own.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker attachments upload-temp¶

Upload a temporary file (POST /attachments); its id attaches once to an issue or comment.

Usage:

$ ycli tracker attachments upload-temp [OPTIONS] FILE_PATH

Arguments:

• FILE_PATH: Local file to upload. [required]

Options:

• --rename-to TEXT: Store the file under this name instead of its own.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker macros¶

Tracker queue macros.

Usage:

$ ycli tracker macros [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List the macros of QUEUE_ID.
• get: Get macro MACRO_ID of QUEUE_ID.
• create: Create a macro on QUEUE_ID (POST...
• update: Edit macro MACRO_ID of QUEUE_ID (PATCH) —...
• delete: Delete macro MACRO_ID of QUEUE_ID (DELETE).

ycli tracker macros list¶

List the macros of QUEUE_ID.

Usage:

$ ycli tracker macros list [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker macros get¶

Get macro MACRO_ID of QUEUE_ID.

Usage:

$ ycli tracker macros get [OPTIONS] QUEUE_ID MACRO_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• MACRO_ID: Numeric macro identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker macros create¶

Create a macro on QUEUE_ID (POST /queues/{queue_id}/macros).

Usage:

$ ycli tracker macros create [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --name TEXT: Name of the new macro. [required]
• --body TEXT: Comment text created when the macro runs.
• --issue-update TEXT: Field→value issue changes as a JSON object.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker macros update¶

Edit macro MACRO_ID of QUEUE_ID (PATCH) — only supplied fields are sent.

Usage:

$ ycli tracker macros update [OPTIONS] QUEUE_ID MACRO_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• MACRO_ID: Numeric macro identifier. [required]

Options:

• --name TEXT: New name of the macro.
• --body TEXT: New comment text created when the macro runs.
• --issue-update TEXT: Replacement field→value issue changes as a JSON object.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker macros delete¶

Delete macro MACRO_ID of QUEUE_ID (DELETE).

Usage:

$ ycli tracker macros delete [OPTIONS] QUEUE_ID MACRO_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• MACRO_ID: Numeric macro identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker triggers¶

Tracker queue triggers.

Usage:

$ ycli tracker triggers [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List the triggers of QUEUE_ID...
• get: Get trigger TRIGGER_ID of QUEUE_ID.
• create: Create a trigger on QUEUE_ID (POST...
• update: Edit trigger TRIGGER_ID of QUEUE_ID (PATCH...
• webhook-log-list: List the HTTP-action (Webhook) run logs of...

ycli tracker triggers list¶

List the triggers of QUEUE_ID (auto-paginated; --all for everything).

Usage:

$ ycli tracker triggers list [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --limit INTEGER RANGE: Max items to fetch; 0 uses the default cap. [default: 0; x>=0]
• --all: Fetch everything, ignoring the cap.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker triggers get¶

Get trigger TRIGGER_ID of QUEUE_ID.

Usage:

$ ycli tracker triggers get [OPTIONS] QUEUE_ID TRIGGER_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• TRIGGER_ID: Numeric trigger identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker triggers create¶

Create a trigger on QUEUE_ID (POST /queues/{queue_id}/triggers).

Pass one or more --action JSON objects (and optional --condition JSON objects), e.g. --action '{"type": "Transition", "status": {"key": "open"}}'.

Usage:

$ ycli tracker triggers create [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --name TEXT: Name of the new trigger. [required]
• --action TEXT: Trigger action as a JSON object (repeatable).
• --condition TEXT: Trigger condition as a JSON object (repeatable).
• --active / --inactive: Start active or disabled.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker triggers update¶

Edit trigger TRIGGER_ID of QUEUE_ID (PATCH ...?version=) — only supplied fields are sent.

Usage:

$ ycli tracker triggers update [OPTIONS] QUEUE_ID TRIGGER_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• TRIGGER_ID: Numeric trigger identifier. [required]

Options:

• --name TEXT: New name of the trigger.
• --action TEXT: Trigger action as a JSON object (repeatable).
• --condition TEXT: Trigger condition as a JSON object (repeatable).
• --active / --inactive: Activate or disable the trigger.
• --version INTEGER: Current trigger version (optimistic lock). [default: 0]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker triggers webhook-log-list¶

List the HTTP-action (Webhook) run logs of trigger TRIGGER_ID.

Usage:

$ ycli tracker triggers webhook-log-list [OPTIONS] QUEUE_ID TRIGGER_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• TRIGGER_ID: Numeric trigger identifier. [required]

Options:

• --issue-id TEXT: Scope the logs to one issue key/id.
• --limit INTEGER: Max records (API default 10, max 100). [default: 0]
• --from TEXT: Range start (YYYY-MM-DDThhss.sss±hhmm).
• --to TEXT: Range end (YYYY-MM-DDThhss.sss±hhmm).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker autoactions¶

Tracker queue autoactions.

Usage:

$ ycli tracker autoactions [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• get: Get autoaction ACTION_ID of QUEUE_ID.
• create: Create an autoaction on QUEUE_ID (POST...
• logs-list: List the run summaries of autoaction...
• logs-get: List the per-issue outcomes of run RUN_ID...

ycli tracker autoactions get¶

Get autoaction ACTION_ID of QUEUE_ID.

Usage:

$ ycli tracker autoactions get [OPTIONS] QUEUE_ID ACTION_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• ACTION_ID: Numeric autoaction identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker autoactions create¶

Create an autoaction on QUEUE_ID (POST /queues/{queue_id}/autoactions).

Supply --query or --filter to select issues, and one or more --action JSON objects, e.g. --action '{"type": "Transition", "status": {"key": "needInfo"}}'.

Usage:

$ ycli tracker autoactions create [OPTIONS] QUEUE_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]

Options:

• --name TEXT: Name of the new autoaction. [required]
• --query TEXT: TQL query selecting the issues to act on.
• --filter TEXT: Field-based filter as a JSON object.
• --action TEXT: Autoaction action as a JSON object (repeatable).
• --active / --inactive: Start active or disabled.
• --notify / --no-notify: Send notifications when the autoaction runs.
• --interval-millis INTEGER: Run interval in ms (default 3600000). [default: 0]
• --calendar-id INTEGER: Working-calendar id for the active window. [default: 0]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker autoactions logs-list¶

List the run summaries of autoaction ACTION_ID.

Usage:

$ ycli tracker autoactions logs-list [OPTIONS] QUEUE_ID ACTION_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• ACTION_ID: Numeric autoaction identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker autoactions logs-get¶

List the per-issue outcomes of run RUN_ID of autoaction ACTION_ID.

Usage:

$ ycli tracker autoactions logs-get [OPTIONS] QUEUE_ID ACTION_ID RUN_ID

Arguments:

• QUEUE_ID: Queue key (case-sensitive) or numeric id. [required]
• ACTION_ID: Numeric autoaction identifier. [required]
• RUN_ID: Autoaction run identifier. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker bulk¶

Tracker async bulk changes.

Usage:

$ ycli tracker bulk [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• update: Mass-edit issues (POST /bulkchange/_update).
• move: Mass-move issues to another QUEUE (POST...
• transition: Mass status transition (POST...
• get: Print the current status of bulk-change...
• issues-list: List issues that a bulk change failed on...

ycli tracker bulk update¶

Mass-edit issues (POST /bulkchange/_update). Set fields with repeated -F key=value.

Usage:

$ ycli tracker bulk update [OPTIONS]

Options:

• --issue TEXT: Issue key to include (repeatable; omit when using --query).
• --query TEXT: Query-language filter selecting issues (instead of --issue).
• -F, --field TEXT: Field to set, key=value (JSON-coerced; repeatable).
• --notify / --no-notify: Notify affected users. [default: no-notify]
• --wait / --no-wait: Poll to a terminal status before printing. [default: wait]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker bulk move¶

Mass-move issues to another QUEUE (POST /bulkchange/_move).

Usage:

$ ycli tracker bulk move [OPTIONS] QUEUE

Arguments:

• QUEUE: Target queue key, e.g. CHECK. [required]

Options:

• --issue TEXT: Issue key to include (repeatable; omit when using --query).
• --query TEXT: Query-language filter selecting issues (instead of --issue).
• -F, --field TEXT: Field to set, key=value (JSON-coerced; repeatable).
• --move-all-fields: Carry versions/components/projects across.
• --initial-status: Reset each issue's status to the initial one.
• --notify / --no-notify: Notify affected users. [default: no-notify]
• --wait / --no-wait: Poll to a terminal status before printing. [default: wait]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker bulk transition¶

Mass status transition (POST /bulkchange/_transition). -F resolution=fixed for close.

Usage:

$ ycli tracker bulk transition [OPTIONS] TRANSITION

Arguments:

• TRANSITION: Transition id, e.g. close. [required]

Options:

• --issue TEXT: Issue key to include (repeatable; omit when using --query).
• --query TEXT: Query-language filter selecting issues (instead of --issue).
• -F, --field TEXT: Field to set, key=value (JSON-coerced; repeatable).
• --notify / --no-notify: Notify affected users. [default: no-notify]
• --wait / --no-wait: Poll to a terminal status before printing. [default: wait]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker bulk get¶

Print the current status of bulk-change BULK_ID (GET /bulkchange/{id}).

Usage:

$ ycli tracker bulk get [OPTIONS] BULK_ID

Arguments:

• BULK_ID: Bulk-change operation id from a trigger. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker bulk issues-list¶

List issues that a bulk change failed on (GET /bulkchange/{id}/issues).

Usage:

$ ycli tracker bulk issues-list [OPTIONS] BULK_ID

Arguments:

• BULK_ID: Bulk-change operation id from a trigger. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker remotelinks¶

Tracker issue external-app links.

Usage:

$ ycli tracker remotelinks [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• list: List external links on issue KEY (GET...
• create: Add an external link to issue KEY (POST...
• delete: Delete external link LINK_ID from issue...

ycli tracker remotelinks list¶

List external links on issue KEY (GET /issues/{key}/remotelinks).

Usage:

$ ycli tracker remotelinks list [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker remotelinks create¶

Add an external link to issue KEY (POST /issues/{key}/remotelinks).

Usage:

$ ycli tracker remotelinks create [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --key TEXT: Key of the object in the external app. [required]
• --origin TEXT: Identifier of the external application. [required]
• --relationship TEXT: Link type (RELATES recommended). [default: RELATES]
• --backlink / --no-backlink: Also create the mirror link in the app. [default: no-backlink]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker remotelinks delete¶

Delete external link LINK_ID from issue KEY (DELETE /issues/{key}/remotelinks/{id}).

Usage:

$ ycli tracker remotelinks delete [OPTIONS] KEY LINK_ID

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• LINK_ID: Remote-link id to delete. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker import¶

Tracker data import (admin).

Usage:

$ ycli tracker import [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• task: Import an issue preserving its history...
• comment: Import a comment onto issue KEY (POST...
• link: Import a link on issue KEY (POST...
• worklog: Import a worklog onto issue KEY (POST...
• file: Import a file attachment onto issue KEY...
• comment-file: Import a file onto comment COMMENT_ID of...

ycli tracker import task¶

Import an issue preserving its history (POST /issues/_import).

Usage:

$ ycli tracker import task [OPTIONS]

Options:

• --queue TEXT: Target queue key. [required]
• --summary TEXT: Issue title. [required]
• --created-at TEXT: Original creation time, YYYY-MM-DDThhss.sss±hhmm. [required]
• --created-by TEXT: Login or id of the original author. [required]
• --key TEXT: Explicit issue key (must belong to the queue).
• --description TEXT: Issue description (YFM).
• --assignee TEXT: Assignee login or id.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker import comment¶

Import a comment onto issue KEY (POST /issues/{key}/comments/_import).

Usage:

$ ycli tracker import comment [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --text TEXT: Comment text. [required]
• --created-at TEXT: Original creation time, YYYY-MM-DDThhss.sss±hhmm. [required]
• --created-by TEXT: Login or id of the original author. [required]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker import link¶

Import a link on issue KEY (POST /issues/{key}/links/_import).

Usage:

$ ycli tracker import link [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --relationship TEXT: Link type, e.g. relates. [required]
• --issue TEXT: Key or id of the issue to link to. [required]
• --created-at TEXT: Original creation time, YYYY-MM-DDThhss.sss±hhmm. [required]
• --created-by TEXT: Login or id of the original author. [required]
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker import worklog¶

Import a worklog onto issue KEY (POST /issues/{key}/worklogs/_import).

Usage:

$ ycli tracker import worklog [OPTIONS] KEY

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]

Options:

• --duration TEXT: Time spent, ISO-8601 duration (e.g. PT1H). [required]
• --created-at TEXT: Original creation time, YYYY-MM-DDThhss.sss±hhmm. [required]
• --created-by TEXT: Login or id of the original author. [required]
• --start TEXT: Work start time, YYYY-MM-DDThhss.sss±hhmm. [required]
• --comment TEXT: Optional note saved in the time report.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker import file¶

Import a file attachment onto issue KEY (POST /issues/{key}/attachments/_import).

Usage:

$ ycli tracker import file [OPTIONS] KEY PATH

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• PATH: Local file to attach. [required]

Options:

• --created-at TEXT: Original creation time, YYYY-MM-DDThhss.sss±hhmm. [required]
• --created-by TEXT: Login or id of the original author. [required]
• --filename TEXT: Override the attachment name (default: basename).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker import comment-file¶

Import a file onto comment COMMENT_ID of issue KEY (…/comments/{id}/attachments/_import).

Usage:

$ ycli tracker import comment-file [OPTIONS] KEY COMMENT_ID PATH

Arguments:

• KEY: Issue key, e.g. DATAENGINEERING-1. [required]
• COMMENT_ID: Id of the comment. [required]
• PATH: Local file to attach. [required]

Options:

• --created-at TEXT: Original creation time, YYYY-MM-DDThhss.sss±hhmm. [required]
• --created-by TEXT: Login or id of the original author. [required]
• --filename TEXT: Override the attachment name (default: basename).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker dashboards¶

Tracker dashboards.

Usage:

$ ycli tracker dashboards [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• create: Create a dashboard (POST /dashboards/).
• add-cycle-time-widget: Add a cycle-time widget to DASHBOARD_ID...

ycli tracker dashboards create¶

Create a dashboard (POST /dashboards/).

Usage:

$ ycli tracker dashboards create [OPTIONS]

Options:

• --name TEXT: Dashboard name. [required]
• --layout TEXT: Layout mode, e.g. two-columns.
• --owner TEXT: Owner login or id (defaults to creator).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker dashboards add-cycle-time-widget¶

Add a cycle-time widget to DASHBOARD_ID (POST /dashboards/{id}/widgets/cycleTime).

Usage:

$ ycli tracker dashboards add-cycle-time-widget [OPTIONS] DASHBOARD_ID

Arguments:

• DASHBOARD_ID: Target dashboard id. [required]

Options:

• --description TEXT: Widget name. [required]
• --query TEXT: Query-language filter selecting issues.
• --from-status TEXT: Status key work starts from (repeatable).
• --to-status TEXT: Status key work ends at (repeatable).
• --mode TEXT: Display mode, e.g. common-lines.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities¶

Tracker projects, portfolios and goals.

Usage:

$ ycli tracker entities [OPTIONS] COMMAND [ARGS]...

Options:

• --help: Show this message and exit.

Commands:

• get: Print a single entity...
• create: Create an entity (POST /entities/TYPE).
• update: Edit entity ID (PATCH /entities/TYPE/ID) —...
• delete: Delete entity ID (DELETE /entities/TYPE/ID).
• search: Search entities of TYPE (POST...
• events-list: Print an entity's event history (GET...
• permissions-get: Print an entity's access settings (GET...
• set-permissions: Set an entity's access settings (PATCH...
• direct-permissions-get: Print an entity's direct READ/WRITE/GRANT...
• set-direct-permissions: Grant and revoke an entity's direct rights...
• bulk-update: Mass-edit entities (POST...
• bulk-status-get: Print a bulk-change operation's status...
• create-report: Build an issue report (POST...
• comments: Entity comments.
• checklists: Entity checklists.
• links: Entity links.
• attachments: Entity attachments.

ycli tracker entities get¶

Print a single entity (project/portfolio/goal) by ID.

Usage:

$ ycli tracker entities get [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• --expand TEXT: Extra info, e.g. attachments.
• --fields TEXT: Comma-separated extra fields to include.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities create¶

Create an entity (POST /entities/TYPE). summary is required; other fields optional.

Usage:

$ ycli tracker entities create [OPTIONS] TYPE

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]

Options:

• --summary TEXT: Entity name (required). [required]
• --description TEXT: Description.
• --lead TEXT: Responsible user id/login.
• --author TEXT: Author user id/login.
• --status TEXT: entityStatus key to set.
• --start TEXT: Start date, YYYY-MM-DDThhss.sss±hhmm.
• --end TEXT: Deadline date, YYYY-MM-DDThhss.sss±hhmm.
• --parent TEXT: Primary parent portfolio/goal id.
• --team-user TEXT: Participant id/login (repeatable).
• --tag TEXT: Tag (repeatable).
• -F, --field TEXT: Extra fields entry key=value (JSON-coerced; repeatable).
• --fields TEXT: Comma-separated fields to include in the reply.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities update¶

Edit entity ID (PATCH /entities/TYPE/ID) — only supplied fields are sent.

Usage:

$ ycli tracker entities update [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• --summary TEXT: New name.
• --description TEXT: New description.
• --lead TEXT: New responsible user id/login.
• --author TEXT: New author user id/login.
• --status TEXT: New entityStatus key.
• --start TEXT: New start date.
• --end TEXT: New deadline date.
• --parent TEXT: New primary parent portfolio/goal id.
• --team-user TEXT: Participant id/login (repeatable).
• --tag TEXT: Tag (repeatable).
• --comment TEXT: Comment to add with the change.
• -F, --field TEXT: Extra fields entry key=value (JSON-coerced; repeatable).
• --expand TEXT: Extra blocks to include in the reply.
• --fields TEXT: Comma-separated fields to include in the reply.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities delete¶

Delete entity ID (DELETE /entities/TYPE/ID).

Usage:

$ ycli tracker entities delete [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• --with-board: Also delete the entity's board.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities search¶

Search entities of TYPE (POST /entities/TYPE/_search).

Usage:

$ ycli tracker entities search [OPTIONS] TYPE

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]

Options:

• --input TEXT: Substring in the entity name.
• --filter TEXT: Filter key=value (JSON-coerced; repeatable).
• --order-by TEXT: Field key to sort by.
• --order-asc: Sort ascending.
• --root-only: Only top-level entities.
• --fields TEXT: Comma-separated extra fields to include.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities events-list¶

Print an entity's event history (GET …/events/_relative, auto-paginated).

Usage:

$ ycli tracker entities events-list [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• --limit INTEGER: Max events (0 = all). [default: 0]
• --selected TEXT: Event id to build the list around.
• --new-events-on-top / --no-new-events-on-top: Newest events first.
• --direction TEXT: forward (the default) or backward.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities permissions-get¶

Print an entity's access settings (GET …/extendedPermissions).

Usage:

$ ycli tracker entities permissions-get [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities set-permissions¶

Set an entity's access settings (PATCH …/extendedPermissions).

The API accepts only grant / revoke actions, each mapping an access level (READ/WRITE/GRANT) to users/groups/roles, e.g. --acl 'grant={"READ":{"users":["8000000000000002"]}}'.

Usage:

$ ycli tracker entities set-permissions [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• --acl TEXT: ACL change ACTION= where ACTION is grant or revoke, e.g. grant={"READ":{"users":["8000000000000002"]}} (repeatable).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities direct-permissions-get¶

Print an entity's direct READ/WRITE/GRANT rights, no inheritance (GET …/permissions).

Usage:

$ ycli tracker entities direct-permissions-get [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities set-direct-permissions¶

Grant and revoke an entity's direct rights (PATCH …/permissions); pass --grant/--revoke.

Usage:

$ ycli tracker entities set-direct-permissions [OPTIONS] TYPE ID

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]
• ID: Entity id (or shortId). [required]

Options:

• --grant TEXT: Rights to add as JSON, e.g. '{"READ":{"users":["ann"]}}'.
• --revoke TEXT: Rights to remove as JSON, e.g. '{"GRANT":{"roles":["OWNER"]}}'.
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities bulk-update¶

Mass-edit entities (POST …/bulkchange/_update) — returns the async operation handle.

Usage:

$ ycli tracker entities bulk-update [OPTIONS] TYPE

Arguments:

• TYPE: Entity type: project, portfolio or goal (report: search only). [required]

Options:

• --entity TEXT: Entity id (repeatable). [required]
• --comment TEXT: Comment to add to every entity.
• -F, --field TEXT: Extra fields entry key=value (JSON-coerced; repeatable).
• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities bulk-status-get¶

Print a bulk-change operation's status (GET /bulkchange/OPERATION_ID).

Usage:

$ ycli tracker entities bulk-status-get [OPTIONS] OPERATION_ID

Arguments:

• OPERATION_ID: Bulk-change id. [required]

Options:

• -o, --format [auto|json|yaml|pretty]: Output format (auto = pretty on a TTY, JSON when piped).
• --jq EXPR: Filter the JSON result through a jq expression; strings print raw, like jq -r. Needs the jq extra.
• -y, --yes: Do not ask before an operation that deletes data.
• --dry-run: Do not send a write: print the request it would send instead. Reads still run, and only the first write of a command is shown.
• --help: Show this message and exit.

ycli tracker entities create-report¶

Build an issue report (POST /entities/report/) from a TQL query and column fields.

Usage:

$ ycli tracker entities create-report [OPTIONS]