jiraya issue

Referência do comando jiraya issue da CLI do Jiraya: subcomandos, uso, flags e exemplos, gerados a partir da ajuda.

Work with issues

Subcomandos

Comando	Descrição
`jiraya issue assign`	Assign an issue to a member, agent, or squad
`jiraya issue cancel-task`	Cancel an in-progress or queued run (interrupts in-flight agent)
`jiraya issue children`	List an issue's sub-issues grouped by stage
`jiraya issue comment`	Work with issue comments
`jiraya issue create`	Create a new issue
`jiraya issue draft`	Read or update the issue draft of the current conversation
`jiraya issue get`	Get issue details
`jiraya issue label`	Manage labels on an issue
`jiraya issue list`	List issues in the workspace
`jiraya issue metadata`	Manage per-issue metadata (KV)
`jiraya issue property`	Manage custom property values on an issue
`jiraya issue pull-requests`	List pull requests linked to an issue
`jiraya issue reorder`	Move an issue within its status column
`jiraya issue rerun`	Re-enqueue an issue's current agent assignment as a fresh run
`jiraya issue review`	Record your decision on a sub-issue review requested by the platform
`jiraya issue run-messages`	List messages for an execution
`jiraya issue runs`	List execution history for an issue
`jiraya issue search`	Search issues by title, description, or comments
`jiraya issue status`	Change issue status
`jiraya issue subscriber`	Work with issue subscribers
`jiraya issue timeline`	Chronological issue history — when status/assignee changed, how long it has been stuck
`jiraya issue update`	Update an issue
`jiraya issue usage`	Show aggregated token usage for an issue
`jiraya issue wakeup`	Manage event and time wakeups that start ordinary runs

jiraya issue assign

Assign an issue to a member, agent, or squad

Uso

jiraya issue assign <id> [flags]

Flags

Flag	Descrição	Padrão
`--no-start`	Assign ownership without starting an agent run
`--output string`	Output format: table or json	`json`
`--to string`	Assignee name (member, agent, or squad; fuzzy match)
`--to-id string`	Assignee UUID — member, agent, or squad (mutually exclusive with --to)
`--unassign`	Remove current assignee

jiraya issue cancel-task

Cancel an in-progress or queued run (interrupts in-flight agent)

Cancel a single run by its ID. Accepts the short ID prefix shown by `issue runs`. Use --issue to scope short-ID resolution to a specific issue when ambiguous. Triggers daemon-side interrupt of any in-flight agent so it stops emitting tool calls promptly.

Uso

jiraya issue cancel-task <run-id> [flags]

Flags

Flag	Descrição	Padrão
`--issue string`	Issue ID/key to scope short run ID prefix resolution
`--output string`	Output format: table or json	`json`

jiraya issue children

List an issue's sub-issues grouped by stage

Uso

jiraya issue children <id> [flags]

Aliases: subissues

Flags

Flag	Descrição	Padrão
`--full-id`	Show full UUIDs in table output
`--output string`	Output format: table or json	`table`

jiraya issue comment

Work with issue comments

jiraya issue comment add

Add a comment to an issue

Uso

jiraya issue comment add <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--allow-external-file`	Allow --content-file / --attachment to read a path outside the current working directory. Off by default so a stale file from another run/environment can't be picked up (MUL-4252).
`--attachment strings`	File path(s) to attach (can be specified multiple times)
`--content string`	Comment content (decodes \n, \r, \t, \\; pipe via --content-stdin for multi-line bodies or to preserve literal backslashes)
`--content-file string`	Read comment content from a UTF-8 file (preserves multi-line content verbatim; use this on Windows when stdin piping mangles non-ASCII bytes). The path must be inside the current working directory unless --allow-external-file is set.
`--content-stdin`	Read comment content from stdin (preserves multi-line content verbatim)
`--output string`	Output format: table or json	`json`
`--parent string`	Parent comment ID to reply under. A comment-triggered agent run must reply under its trigger comment; omitting --parent to post a top-level comment is rejected

jiraya issue comment delete

Delete a comment

Delete a single comment. Its replies are kept: a comment that has replies stays in the thread as an empty placeholder (deleted_at set) so they keep their place.

Uso

jiraya issue comment delete <comment-id>

jiraya issue comment list

List comments on an issue

Uso

jiraya issue comment list <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--before string`	Cursor (RFC3339Nano timestamp). With --recent: thread cursor (last_activity_at). With --thread + --tail: reply cursor (reply created_at). Read from the X-Jiraya-Next-Before response header, printed on stderr as "Next thread cursor" / "Next reply cursor"; must be paired with --before-id.
`--before-id string`	Cursor UUID. With --recent: thread root UUID. With --thread + --tail: oldest reply UUID. Read from the X-Jiraya-Next-Before-Id response header; must be paired with --before.
`--compact`	JSON output only: drop response fields that carry no information for a reader — the issue_id echoed from the request path, source_task_id, updated_at when identical to created_at, null-valued fields, and empty arrays. Content and identity fields pass through untouched. Recommended for agent reads; composes with any mode.
`--full`	Escape hatch: return every comment in resolved threads verbatim. By default the complete-thread reads (default list, --recent, --thread without --tail) are folded — a resolved thread collapses to its root + conclusion, with the dropped count reported on the root — so you do not pay tokens for settled discussion. Pass --full when you need the folded discussion. No effect on --since/--tail/--roots-only reads, which are never folded.
`--output string`	Output format: table or json	`table`
`--recent int`	Return the N most recently active threads. N caps THREADS, not comments: every thread carries its root plus EVERY descendant with no per-thread cap, so on an issue with fewer than N root threads this returns the entire history (minus folded resolved threads). Prefer two bounded reads: scan with --roots-only --summary, then open selected threads with --thread <id> --tail N. Use --before/--before-id from the previous response to scroll to older threads.
`--roots-only`	Only return top-level comments (parent_id is null). Each root also carries reply_count + last_activity_at so you can triage which thread to open.
`--since string`	Only return comments created after this timestamp (RFC3339)
`--summary`	Clip each comment's content to a short preview (sets content_truncated) so you can scan a list without pulling full bodies. Composes with any mode.
`--tail int`	Only valid with --thread. Cap reply count to the N most recent replies; the thread root is always included (even with --tail 0). Use --before/--before-id to scroll to older replies.
`--thread string`	Comment UUID — return the thread containing this comment (root + every descendant). May be a root or a reply id.

jiraya issue comment resolve

Resolve a comment thread

Uso

jiraya issue comment resolve <comment-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`json`

jiraya issue comment unresolve

Unresolve a comment thread

Uso

jiraya issue comment unresolve <comment-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`json`

jiraya issue comment update

Update a comment

Update a comment you authored. Workspace owners and admins can update any comment.

Pass the revision returned by `jiraya issue comment list <issue-id> --output json`; the update is rejected if another editor changed the comment first. On that rejection, read the latest body and merge your change into it before retrying. Do not just resend with the newer revision: that overwrites the other edit.

Changing the content is a new trigger, not a silent fix: the server cancels runs this comment triggered that are still in flight and re-enqueues every agent the new body mentions. Attachments are left as they are.

Uso

jiraya issue comment update <comment-id> [flags]

Flags

Flag	Descrição	Padrão
`--allow-external-file`	Allow --content-file to read a path outside the current working directory. Off by default so a stale file from another run/environment can't be picked up (MUL-4252).
`--content string`	New comment content (decodes \n, \r, \t, \\; pipe via --content-stdin for multi-line bodies or to preserve literal backslashes)
`--content-file string`	Read new comment content from a UTF-8 file (preserves multi-line content verbatim; use this on Windows when stdin piping mangles non-ASCII bytes). The path must be inside the current working directory unless --allow-external-file is set.
`--content-stdin`	Read new comment content from stdin (preserves multi-line content verbatim)
`--expected-revision int`	Current positive comment revision from issue comment list --output json (required; prevents overwriting a concurrent edit)
`--output string`	Output format: table or json	`json`

jiraya issue create

Create a new issue

Uso

jiraya issue create [flags]

Flags

Flag	Descrição	Padrão
`--allow-duplicate`	Allow creating an issue even when an active duplicate exists
`--allow-external-file`	Allow --description-file / --attachment to read a path outside the current working directory. Off by default so a stale file from another run/environment can't be picked up (MUL-4252).
`--assignee string`	Assignee name (member, agent, or squad; fuzzy match)
`--assignee-id string`	Assignee UUID — member, agent, or squad (mutually exclusive with --assignee)
`--attachment strings`	File path(s) to attach (can be specified multiple times)
`--attachment-id strings`	Existing attachment UUID(s) to bind to the created issue (can be specified multiple times)
`--description string`	Issue description (decodes \n, \r, \t, \\; pipe via --description-stdin to preserve literal backslashes)
`--description-file string`	Read issue description from a UTF-8 file (preserves multi-line content verbatim; use this on Windows when stdin piping mangles non-ASCII bytes). The path must be inside the current working directory unless --allow-external-file is set.
`--description-stdin`	Read issue description from stdin (preserves multi-line content verbatim)
`--due-date string`	Due date (calendar day, YYYY-MM-DD)
`--output string`	Output format: table or json	`json`
`--parent string`	Parent issue ID
`--priority string`	Issue priority
`--project string`	Project ID
`--reviewer string`	Reviewer name (member or agent; fuzzy match). Omit to apply the default rule: a member creator defaults to themself, an agent creator (CLI/API) gets no default reviewer
`--reviewer-id string`	Reviewer UUID — member or agent (mutually exclusive with --reviewer)
`--stage int`	Stage ordinal (>=1) grouping this sub-issue into an ordered barrier group under its parent; omit for unstaged. The parent assignee is woken only when every sub-issue in a stage finishes.
`--start-date string`	Start date (calendar day, YYYY-MM-DD)
`--status string`	Issue status (default: backlog)
`--title string`	Issue title (required)

jiraya issue draft

Read or update the issue draft of the current conversation

Read or update the issue draft of the conversation you are running for.

In an issue-draft conversation the member reviews a preview of the issue before it exists. You keep that preview current with "jiraya issue draft update"; the member confirms it to create the issue. Never create the issue yourself.

jiraya issue draft get

Show the current issue draft

Show the current issue draft: its revision, fields, and the server's validation verdict (validation.errors lists each invalid field with a code).

Uso

jiraya issue draft get [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`json`

jiraya issue draft update

Write a new revision of the issue draft

Write a new revision of the issue draft.

Flags are merged onto the current draft; fields you do not pass keep their value. --file replaces the whole draft with a JSON object shaped like the "draft" field of "jiraya issue draft get", and flags still apply on top.

The server validates the result. When a field is invalid nothing is saved and the command fails listing each field and code (required, invalid, not_found, archived, forbidden) — fix those fields and run it again. When the member edited the draft since you read it, the command fails with stale_revision: read it again with "jiraya issue draft get" and reapply your change.

Examples:

jiraya issue draft update --title "Fix Safari login" --description-file ./description.md
jiraya issue draft update --priority high --assignee-id <uuid>
jiraya issue draft update --label bug --label frontend
jiraya issue draft update --clear due_date,parent_issue_id

Uso

jiraya issue draft update [flags]

Flags

Flag	Descrição	Padrão
`--allow-external-file`	Allow --file / --description-file to read a path outside the current working directory.
`--assignee string`	Assignee name (member, agent, or squad; fuzzy match)
`--assignee-id string`	Assignee UUID — member, agent, or squad (mutually exclusive with --assignee)
`--attachment-id strings`	Attachment UUID to bind to the issue when it is created; repeat for several. Added to the draft's attachments.
`--clear strings`	Fields to clear: assignee, project_id, parent_issue_id, due_date, label_ids, description
`--description string`	Issue description (decodes \n, \r, \t, \\; prefer --description-file for multi-line text)
`--description-file string`	Read the description from a UTF-8 file. The path must be inside the current working directory unless --allow-external-file is set.
`--description-stdin`	Read the description from stdin
`--due-date string`	Due date (calendar day, YYYY-MM-DD)
`--file string`	Replace the whole draft with this JSON file (the "draft" object). The path must be inside the current working directory unless --allow-external-file is set.
`--label strings`	Label name or ID; repeat to set several. Replaces the draft's labels.
`--output string`	Output format: table or json	`json`
`--parent string`	Parent issue ID or identifier
`--priority string`	Priority: urgent, high, medium, low, or none
`--project string`	Project ID or title
`--status string`	Initial status (defaults to backlog)
`--title string`	Issue title

jiraya issue get

Get issue details

Uso

jiraya issue get <id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`json`
`--resolve-properties issue property list`	JSON output only: replace the properties id map with the rows issue property list prints (property name and type, option and member names beside the stored ids). Omit for the raw map. No effect on --output table.

jiraya issue label

Manage labels on an issue

jiraya issue label add

Attach a label to an issue

Uso

jiraya issue label add <issue-id> <label-id> [flags]

Flags

Flag	Descrição	Padrão
`--full-id`	Show full UUIDs in table output
`--output string`	Output format: table or json	`table`

jiraya issue label list

List labels on an issue

Uso

jiraya issue label list <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--full-id`	Show full UUIDs in table output
`--output string`	Output format: table or json	`table`

jiraya issue label remove

Remove a label from an issue

Uso

jiraya issue label remove <issue-id> <label-id> [flags]

Flags

Flag	Descrição	Padrão
`--full-id`	Show full UUIDs in table output
`--output string`	Output format: table or json	`table`

jiraya issue list

List issues in the workspace

Uso

jiraya issue list [flags]

Flags

Flag	Descrição	Padrão
`--assignee string`	Filter by assignee name (member, agent, or squad; fuzzy match)
`--assignee-id string`	Filter by assignee UUID — member, agent, or squad (mutually exclusive with --assignee)
`--direction string`	Sort direction (asc or desc); requires --sort to be a non-position column or a property sort (position is always ascending)
`--fields string`	JSON output only: comma-separated list of issue fields to include (e.g. id,title,status,priority). Filtering happens client-side after the full response is fetched, so this shrinks CLI output size and agent context cost, not network/server-side cost. Omit for the full issue object (default, unchanged). Valid fields: id, workspace_id, number, identifier, title, description, status, status_category, status_name, priority, assignee_type, assignee_id, creator_type, creator_id, reporter_type, reporter_id, reviewer_type, reviewer_id, parent_issue_id, project_id, position, stage, start_date, due_date, created_at, updated_at, revision, last_activity_at, metadata, properties, labels
`--full-id`	Show full UUIDs in table output
`--limit int`	Page size, 1 to 100 (the server returns at most 100 issues per request; use --offset to page through more)	`50`
`--metadata strings`	Filter by metadata key=value (repeatable; combined with AND). Value is JSON-parsed: 'true'/'false' → bool, numbers → number, otherwise string. Wrap as '"42"' to force a string when the value would otherwise sniff as a number.
`--offset int`	Number of issues to skip (for pagination; while --output json reports has_more, advance it by the number of issues in that same response)
`--output string`	Output format: table or json	`table`
`--priority string`	Filter by priority
`--project string`	Filter by project ID
`--property stringArray`	Filter by custom property, written as "Name=Value" (repeatable, one value per flag). Name is a property name (case-insensitive) or its UUID. Value depends on the type: an option name or id for select and multi_select, true or false for checkbox, a member name, email, or id for actor types, and the value itself for text, url, number, and date (YYYY-MM-DD). Use __none__ to match issues where the property is unset; it works for every type, so an option or member actually named __none__ has to be given by id, as does a property whose name contains "=" or ends in <, > or ! (the >=, <=, and != spellings are reserved for comparison filters). Repeating a property matches ANY of its values; different properties must ALL match.
`--resolve-properties issue property list`	JSON output only: replace the properties id map with the rows issue property list prints (property name and type, option and member names beside the stored ids). Omit for the raw map. No effect on --output table.
`--sort string`	Sort column: position (default, manual board order), title, created_at, start_date, due_date, priority, or property:<name-or-id> to sort by a custom property (select properties sort by option order)
`--status string`	Filter by status

jiraya issue metadata

Manage per-issue metadata (KV)

jiraya issue metadata delete

Delete a single metadata key

Uso

jiraya issue metadata delete <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--key string`	Metadata key (required)
`--output string`	Output format: table or json	`table`

jiraya issue metadata get

Get a single metadata key value

Uso

jiraya issue metadata get <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--key string`	Metadata key (required)
`--output string`	Output format: table or json	`json`

jiraya issue metadata list

List all metadata keys on an issue

Uso

jiraya issue metadata list <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`table`

jiraya issue metadata set

Set a single metadata key value

Set a single metadata key value. The value is JSON-parsed by default:

--value true / --value false  → bool
--value 3 / --value 3.14      → number
--value waiting               → string

Use --type to force a specific type. Quote like '"42"' (JSON-escaped) to force a string when the bare value would otherwise sniff as a number or bool.

Uso

jiraya issue metadata set <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--key string`	Metadata key (required)
`--output string`	Output format: table or json	`table`
`--type string`	Force value type: string, number, or bool (default: auto-infer via JSON parsing)
`--value string`	Metadata value (required)

jiraya issue property

Manage custom property values on an issue

jiraya issue property list

List custom property values set on an issue

Uso

jiraya issue property list <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`table`

jiraya issue property set

Set a custom property value on an issue

Set a custom property value. The property is addressed by --name (case-insensitive) or UUID. Value forms by type:

select        --value Staging            (option name or id)
multi_select  --value "iOS,Android"      (comma-separated option names or ids)
actor         --value Bohan             (member name, email, or id)
multi_actor   --value "Bohan,Jiayuan"   (comma-separated members)
checkbox      --value true|false
number        --value 3.5
date          --value 2026-07-13
text / url    --value "any string"

Uso

jiraya issue property set <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--name string`	Property name or UUID (required)
`--output string`	Output format: table or json	`table`
`--value string`	Property value (required; see --help for per-type forms)

jiraya issue property unset

Remove a custom property value from an issue

Uso

jiraya issue property unset <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--name string`	Property name or UUID (required)
`--output string`	Output format: table or json	`table`

jiraya issue pull-requests

List pull requests linked to an issue

Uso

jiraya issue pull-requests <id> [flags]

Aliases: prs

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`table`

jiraya issue reorder

Move an issue within its status column

Reposition an issue inside its current status column by computing a new ordering position, the same value the board's drag-and-drop sets.

Pick exactly one target:

--before <id>  place it directly above another issue in the same column
--after  <id>  place it directly below another issue in the same column
--top          move it to the top of its column
--bottom       move it to the bottom of its column

Reorder stays inside the issue's current column. To move an issue to a different column, change its status first with `jiraya issue status`, which lands it at the top of the destination column — no follow-up reorder needed.

Uso

jiraya issue reorder <id> [flags]

Flags

Flag	Descrição	Padrão
`--after string`	Place the issue directly below this issue (same column)
`--before string`	Place the issue directly above this issue (same column)
`--bottom`	Move the issue to the bottom of its status column
`--output string`	Output format: table or json	`json`
`--top`	Move the issue to the top of its status column

jiraya issue rerun

Re-enqueue an issue's current agent assignment as a fresh run

Uso

jiraya issue rerun <id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`json`

jiraya issue review

Record your decision on a sub-issue review requested by the platform

Record the reviewer's decision on the pending review round of a sub-issue.

Use it when a platform review request names you as the reviewer. Do not change the sub-issue status yourself — the platform applies the decision:

- --approve moves the sub-issue to done and advances the parent's stage.
- --reject moves it back to todo and wakes the executor with your feedback.
  Feedback is required. The third consecutive rejection blocks the
  sub-issue and escalates to a human instead.

Examples:

jiraya issue review MUL-123 --approve
jiraya issue review MUL-123 --reject --feedback-file ./feedback.md

Uso

jiraya issue review <id> [flags]

Flags

Flag	Descrição	Padrão
`--allow-external-file`	Allow --feedback-file to read a path outside the current working directory.
`--approve`	Approve the delivery (the sub-issue moves to done)
`--feedback string`	Rejection feedback for the executor (inline)
`--feedback-file string`	Read rejection feedback from a UTF-8 file. The path must be inside the current working directory unless --allow-external-file is set.
`--feedback-stdin`	Read rejection feedback from stdin
`--output string`	Output format: table or json	`table`
`--reject`	Reject the delivery (the sub-issue moves back to todo); requires feedback

jiraya issue run-messages

List messages for an execution

Uso

jiraya issue run-messages <run-id> [flags]

Flags

Flag	Descrição	Padrão
`--issue string`	Issue ID/key to scope short run ID prefix resolution
`--output string`	Output format: table or json	`json`
`--since int`	Only return messages after this sequence number

jiraya issue runs

List execution history for an issue

List agent runs for an issue.

Defaults to this issue's full execution history, newest first. Narrow it to work in flight with --active, or widen it across the sub-issue family with --siblings when you need to know whether another agent is already working next to you.

Uso

jiraya issue runs <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--active`	Only in-flight runs (queued, dispatched, running, waiting_local_directory) instead of the full execution history. Answers "is an agent working on this right now" without pulling every past run.
`--full-id`	Show full run UUIDs in table output
`--output string`	Output format: table or json	`table`
`--siblings`	Widen to this issue's sub-issue family — its parent (or itself, when it has no parent) plus every child of that parent — so you can see whether another run is already working alongside you before starting overlapping code or PR work. Implies --active. Returns a compact per-run row (run, issue, agent, status, started) rather than the full execution-log record. Ordered running-first, newest-first within a status, and capped at 20 rows; when the cap truncates the answer the CLI says so on stderr, so a short list is never mistaken for a complete one. Advisory only: it reports work in flight, it does not reserve or serialise anything.

jiraya issue search

Search issues by title, description, or comments

Search issues in the current workspace. The query matches issue titles, descriptions, and comment bodies, so a conclusion that only lives in a comment thread is still findable.

A bare number or an identifier-shaped query ("412", "AGE-412") matches the issue with that number. The prefix is not validated, and number matches rank first, so pasting an identifier from another tracker can put an unrelated local issue at the top of the results.

The MATCH column (match_source in --output json) reports the strongest field that matched — title, description, or comment — and falls back to "comment" for a number-only hit. Treat it as a display hint, not a filter.

Uso

jiraya issue search <query> [flags]

Flags

Flag	Descrição	Padrão
`--include-closed`	Include done and cancelled issues
`--limit int`	Maximum number of results to return	`20`
`--output string`	Output format: table or json	`table`

jiraya issue status

Change issue status

Change an issue's status. The argument is a status KEY, not its display name. Built-in keys: backlog, todo, in_progress, in_review, done, blocked, cancelled. A workspace may define custom statuses on top of these; their keys are shown in Workspace Settings > Issue Statuses, and an unknown value errors with the full list.

Uso

jiraya issue status <id> <status> [flags]

Flags

Flag	Descrição	Padrão
`--no-start`	Change status without starting an agent run
`--output string`	Output format: table or json	`table`

jiraya issue subscriber

Work with issue subscribers

jiraya issue subscriber add

Subscribe a user or agent to an issue (defaults to the caller)

Uso

jiraya issue subscriber add <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`json`
`--user string`	Member or agent name to subscribe (fuzzy match; defaults to the caller)
`--user-id string`	Member or agent UUID to subscribe (mutually exclusive with --user)

jiraya issue subscriber list

List subscribers of an issue

Uso

jiraya issue subscriber list <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`table`

jiraya issue subscriber remove

Unsubscribe a user or agent from an issue (defaults to the caller)

Uso

jiraya issue subscriber remove <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`json`
`--user string`	Member or agent name to unsubscribe (fuzzy match; defaults to the caller)
`--user-id string`	Member or agent UUID to unsubscribe (mutually exclusive with --user)

jiraya issue timeline

Chronological issue history — when status/assignee changed, how long it has been stuck

Chronological history of an issue: the activity log — status / priority / assignee / title / date changes, plus whatever task_completed / task_failed records the server already writes — merged with comments, oldest first.

Use it for the questions the current issue fields cannot answer:

- When did this issue move to in_review?
- How long has it been sitting in its current status?
- What changed on this issue since yesterday?

For "what is the state RIGHT NOW", prefer `issue get` — that is the authoritative current snapshot. This command explains how it got there, which comments alone cannot: a status change writes an activity record, never a comment, so a merge that flipped the issue to done leaves no trace in the comment stream.

Comments are included by default. --activity-only drops comment bodies and keeps every activity record; to isolate the state transitions behind "how long has this been stuck", filter by action instead.

The server caps how far back it will read. When it reports that the response was truncated, a warning naming the affected kinds is printed to stderr — durations and "first entered <status>" cannot be concluded from a truncated read, because the transition you are looking for may be the one that fell off.

Examples:

# How long has MUL-123 been in its current status?
jiraya issue timeline MUL-123 --action status_changed

# Every state change, no comment bodies
jiraya issue timeline MUL-123 --activity-only --output json

# What changed since yesterday?
jiraya issue timeline MUL-123 --since 2026-08-19T00:00:00Z

Uso

jiraya issue timeline <id> [flags]

Aliases: history

Flags

Flag	Descrição	Padrão
`--action strings`	Only return activities with these actions (repeatable or comma-separated). Implies --activity-only, since comments carry no action. Known actions: created, status_changed, priority_changed, assignee_changed, title_changed, description_updated, start_date_changed, due_date_changed, task_completed, task_failed, squad_leader_evaluated.
`--activity-only`	Drop comments and return every activity record — including the task_completed / task_failed entries the server already writes, not just field changes. Much cheaper to read than the full timeline; use --action when you want only state transitions.
`--full-id`	Show full UUIDs in table output
`--output string`	Output format: table or json	`table`
`--since string`	Only return entries created after this timestamp (RFC3339)
`--tail int`	Only return the N most recent entries (applied after every other filter)

jiraya issue update

Update an issue

Uso

jiraya issue update <id> [flags]

Flags

Flag	Descrição	Padrão
`--allow-external-file`	Allow --description-file to read a path outside the current working directory. Off by default so a stale temp file from another run/environment can't be picked up (MUL-4252).
`--assignee string`	New assignee name (member, agent, or squad; fuzzy match)
`--assignee-id string`	New assignee UUID — member, agent, or squad (mutually exclusive with --assignee)
`--description string`	New description (decodes \n, \r, \t, \\; pipe via --description-stdin to preserve literal backslashes)
`--description-file string`	Read new description from a UTF-8 file (preserves multi-line content verbatim; use this on Windows when stdin piping mangles non-ASCII bytes). The path must be inside the current working directory unless --allow-external-file is set.
`--description-stdin`	Read new description from stdin (preserves multi-line content verbatim)
`--due-date string`	New due date (calendar day, YYYY-MM-DD)
`--no-start`	Apply the update without starting an agent run
`--output string`	Output format: table or json	`json`
`--parent string`	Parent issue ID (use --parent "" to clear)
`--position issue reorder`	Ordering position within the board column (lower sorts first); prefer issue reorder for relative moves
`--priority string`	New priority
`--project string`	Project ID
`--reviewer string`	New reviewer name (member or agent; fuzzy match; use --reviewer "" to clear)
`--reviewer-id string`	New reviewer UUID — member or agent (mutually exclusive with --reviewer)
`--stage issue create --stage`	Stage ordinal (>=1) for this sub-issue; see issue create --stage
`--start-date string`	New start date (calendar day, YYYY-MM-DD; pass empty string to clear)
`--status string`	New status
`--title string`	New title

jiraya issue usage

Show aggregated token usage for an issue

Show aggregated token usage for an issue.

In table output, RUNS counts terminal runs. Token totals prefixed with >= are lower bounds because one or more terminal runs did not report usage.

Uso

jiraya issue usage <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format: table or json	`table`

jiraya issue wakeup

Manage event and time wakeups that start ordinary runs

jiraya issue wakeup create

create issue wakeups

Create or replace the complete configuration. Events default to once; every/cron use continuous. Updating explicitly re-enables the configuration. Runs use normal comment delivery. For task events, use --task-id for one run or --filter-agent-id for its agent. For comment/issue/reaction/attachment changes, use --filter-actor-type member|agent with --filter-actor-id. To wait for a person to comment, use --event comment.created --filter-actor-type member --filter-actor-id USER_ID. Actor filters identify who made the change, not the original author of an edited comment. Without a source filter, all matching events on this issue can wake the target.

Uso

jiraya issue wakeup create <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--after string`	Delay for at, e.g. 10m
`--agent-id string`	Agent to wake (defaults to authenticated agent)
`--at string`	Single RFC3339 timestamp
`--cron string`	Five-field cron expression
`--event strings`	Event types (comma-separated); see wakeup events
`--every string`	Fixed interval, e.g. 1h (minimum 1m)
`--filter-actor-id string`	Actor user/agent UUID in this workspace; mutation events only
`--filter-actor-type string`	Event actor: member or agent (requires --filter-actor-id)
`--filter-agent-id string`	Run agent filter; legacy alias of actor=agent for mutation-only events
`--instruction string`	Instruction for the next run
`--instruction-file string`	Read instruction from a UTF-8 file
`--kind string`	event, at, every or cron	`event`
`--mode string`	once or continuous
`--output string`	Output format (json or table)	`json`
`--parent string`	Comment thread for result delivery
`--task-id string`	Match this specific run; terminal state is checked on registration
`--timezone string`	IANA timezone for cron	`UTC`

jiraya issue wakeup disable

disable issue wakeups

Uso

jiraya issue wakeup disable <issue-id> <wakeup-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format (json or table)	`json`

jiraya issue wakeup events

List supported event types and filters

Uso

jiraya issue wakeup events

jiraya issue wakeup get

get issue wakeups

Uso

jiraya issue wakeup get <issue-id> <wakeup-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format (json or table)	`json`

jiraya issue wakeup list

list issue wakeups

Uso

jiraya issue wakeup list <issue-id> [flags]

Flags

Flag	Descrição	Padrão
`--output string`	Output format (json or table)	`json`

jiraya issue wakeup update

update issue wakeups

Uso

jiraya issue wakeup update <issue-id> <wakeup-id> [flags]

Flags

Flag	Descrição	Padrão
`--after string`	Delay for at, e.g. 10m
`--agent-id string`	Agent to wake (defaults to authenticated agent)
`--at string`	Single RFC3339 timestamp
`--cron string`	Five-field cron expression
`--event strings`	Event types (comma-separated); see wakeup events
`--every string`	Fixed interval, e.g. 1h (minimum 1m)
`--filter-actor-id string`	Actor user/agent UUID in this workspace; mutation events only
`--filter-actor-type string`	Event actor: member or agent (requires --filter-actor-id)
`--filter-agent-id string`	Run agent filter; legacy alias of actor=agent for mutation-only events
`--instruction string`	Instruction for the next run
`--instruction-file string`	Read instruction from a UTF-8 file
`--kind string`	event, at, every or cron	`event`
`--mode string`	once or continuous
`--output string`	Output format (json or table)	`json`
`--parent string`	Comment thread for result delivery
`--task-id string`	Match this specific run; terminal state is checked on registration
`--timezone string`	IANA timezone for cron	`UTC`

SubcomandosCopiar link da seção

jiraya issue assignCopiar link da seção

jiraya issue cancel-taskCopiar link da seção

jiraya issue childrenCopiar link da seção

jiraya issue commentCopiar link da seção

jiraya issue comment addCopiar link da seção

jiraya issue comment deleteCopiar link da seção

jiraya issue comment listCopiar link da seção

jiraya issue comment resolveCopiar link da seção

jiraya issue comment unresolveCopiar link da seção

jiraya issue comment updateCopiar link da seção

jiraya issue createCopiar link da seção

jiraya issue draftCopiar link da seção

jiraya issue draft getCopiar link da seção

jiraya issue draft updateCopiar link da seção

jiraya issue getCopiar link da seção

jiraya issue labelCopiar link da seção

jiraya issue label addCopiar link da seção

jiraya issue label listCopiar link da seção

jiraya issue label removeCopiar link da seção

jiraya issue listCopiar link da seção

jiraya issue metadataCopiar link da seção

jiraya issue metadata deleteCopiar link da seção

jiraya issue metadata getCopiar link da seção

jiraya issue metadata listCopiar link da seção

jiraya issue metadata setCopiar link da seção

jiraya issue propertyCopiar link da seção

jiraya issue property listCopiar link da seção

jiraya issue property setCopiar link da seção

jiraya issue property unsetCopiar link da seção

jiraya issue pull-requestsCopiar link da seção

jiraya issue reorderCopiar link da seção

jiraya issue rerunCopiar link da seção

jiraya issue reviewCopiar link da seção

jiraya issue run-messagesCopiar link da seção

jiraya issue runsCopiar link da seção

jiraya issue searchCopiar link da seção

jiraya issue statusCopiar link da seção

jiraya issue subscriberCopiar link da seção

jiraya issue subscriber addCopiar link da seção

jiraya issue subscriber listCopiar link da seção

jiraya issue subscriber removeCopiar link da seção

jiraya issue timelineCopiar link da seção

jiraya issue updateCopiar link da seção

jiraya issue usageCopiar link da seção

jiraya issue wakeupCopiar link da seção

jiraya issue wakeup createCopiar link da seção

jiraya issue wakeup disableCopiar link da seção

jiraya issue wakeup eventsCopiar link da seção

jiraya issue wakeup getCopiar link da seção

jiraya issue wakeup listCopiar link da seção

jiraya issue wakeup updateCopiar link da seção

Nesta página

Subcomandos

jiraya issue assign

jiraya issue cancel-task

jiraya issue children

jiraya issue comment

jiraya issue comment add

jiraya issue comment delete

jiraya issue comment list

jiraya issue comment resolve

jiraya issue comment unresolve

jiraya issue comment update

jiraya issue create

jiraya issue draft

jiraya issue draft get

jiraya issue draft update

jiraya issue get

jiraya issue label

jiraya issue label add

jiraya issue label list

jiraya issue label remove

jiraya issue list

jiraya issue metadata

jiraya issue metadata delete

jiraya issue metadata get

jiraya issue metadata list

jiraya issue metadata set

jiraya issue property

jiraya issue property list

jiraya issue property set

jiraya issue property unset

jiraya issue pull-requests

jiraya issue reorder

jiraya issue rerun

jiraya issue review

jiraya issue run-messages

jiraya issue runs

jiraya issue search

jiraya issue status

jiraya issue subscriber

jiraya issue subscriber add

jiraya issue subscriber list

jiraya issue subscriber remove

jiraya issue timeline

jiraya issue update

jiraya issue usage

jiraya issue wakeup

jiraya issue wakeup create

jiraya issue wakeup disable

jiraya issue wakeup events

jiraya issue wakeup get

jiraya issue wakeup list

jiraya issue wakeup update