sazabi issues

sazabi issues — Manage issues. Subcommands: create, list, search, get, fix, read, unread, agent-prompt, link-pr, unlink-pr, reject, resolve, ignore, reopen, mute, unmute, update.

`sazabi issues`

Manage issues

sazabi issues <subcommand>

sazabi issues create --from-json issue.json  # Create an issue
sazabi issues list  # List all issues
sazabi issues search checkout  # Search issues
sazabi issues get <issue-id>  # Get one issue
sazabi issues fix <issue-id>  # Ask Sazabi to fix an issue
sazabi issues read <issue-id>  # Mark an issue read for you
sazabi issues unread <issue-id>  # Mark an issue unread for you
sazabi issues agent-prompt <issue-id>  # Print the agent prompt
sazabi issues link-pr <issue-id> <pr-url> --relation caused_by  # Link a suspected cause
sazabi issues unlink-pr <issue-id> <pr-url> --relation caused_by  # Remove a suspected cause
sazabi issues reject <issue-id> --reason not_real  # Reject an issue
sazabi issues resolve <issue-id>  # Resolve an issue
sazabi issues ignore <issue-id>  # Ignore an issue
sazabi issues mute <issue-id>  # Mute an issue
sazabi issues unmute <issue-id>  # Unmute an issue
sazabi issues update <issue-id> --severity high --note "..."  # Change severity

`sazabi issues create`

Create an issue, reusing an existing open issue when one matches

sazabi issues create [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--name`	string	No	Stable issue name: at most 80 characters, plain English, "<service or surface>: <customer-visible symptom>", no counts, timestamps, or internal identifiers
`--content-mdx`	string	No	One message for the customer's engineer, posted to Slack as written. No headings. Brief, natural language without emojis or em dashes. State the observed problem, affected scope and material uncertainty. Keep measured populations and time windows. Add a next action only when it adds a concrete lead; omit generic inspect/check handoffs. At most 120 words outside code and 3000 characters after Slack formatting. No line may start with a section label such as Summary:. No Sazabi identifiers.
`--severity`	string	No	Issue severity, by impact. critical: Happening now in production: an outage of the service, of a flow most users depend on, or of a whole feature; or data loss, a security exposure, or failed payments. high: Happening now in production: at least 1% of attempts failing or a region down; or production data loss, exposure, or failed payments that has stopped. medium: A failure limited to a few users or one path, a broad internal failure, a production outage that ended on its own, or serious harm outside production. low: No user or system impact, a transient blip, an internal failure on one item or a rare path, or other work outside production, including eval, training, and canary runs. Omitted, the issue is stored as medium.
`--component`	string	No	Required component ID. List with `sazabi components list` (available once the Components page is enabled for your organization); register one if none fits
`--from-json`	string	No	Read issue fields from a JSON file, or '-' for stdin

sazabi issues create --content-mdx "Checkout is returning 500s due to pool exhaustion." --component "$COMPONENT_ID"  # Create an issue from MDX content
sazabi issues create --from-json issue.json  # Create an issue from a JSON file with contentMdx
cat issue.json | sazabi issues create --from-json - --json  # Create an issue from stdin

`sazabi issues list`

List issues in the active project

sazabi issues list [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--status`	string	No	Filter by status: open, resolved, or ignored
`--severity`	string	No	Filter by severity: low, medium, high, or critical
`--component`	string	No	Filter by component ID
`--caused-by`	string	No	Filter by suspected-cause pull request URL
`--limit`	string	No	Maximum number of issues to return (default: 50, max: 100)
`--cursor`	string	No	Pagination cursor from previous response

sazabi issues list  # List all issues
sazabi issues list --status open  # List open issues only
sazabi issues list --component <component-id>  # List issues for a component

`sazabi issues search`

Search issues by text and filters

sazabi issues search [text...] [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--status`	string	No	Filter by status: open, resolved, or ignored
`--severity`	string	No	Filter by severity: low, medium, high, or critical
`--component`	string	No	Filter by component ID
`--caused-by`	string	No	Filter by suspected-cause pull request URL
`--limit`	string	No	Maximum number of issues to return (default: 50, max: 100)
`--cursor`	string	No	Pagination cursor from previous response
`--include-delivery-metadata`	boolean	No	Include delivery metadata in JSON output

sazabi issues search checkout timeout --status open  # Best matches in open issues' names and descriptions
sazabi issues search --severity critical --json  # No text: newest critical issues

`sazabi issues get`

Get one issue by ID

sazabi issues get <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues get <issue-id>  # Get one issue

`sazabi issues fix`

Ask Sazabi's agent to fix an open issue in its thread

sazabi issues fix <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues fix <issue-id>  # Request a fix; follow it in the issue thread

`sazabi issues read`

Mark an issue read for you, up to its latest activity

sazabi issues read <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues read <issue-id>  # Clear the issue's unread marker for you

`sazabi issues unread`

Mark an issue unread for you

sazabi issues unread <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues unread <issue-id>  # Bring the issue back as unread for you

`sazabi issues agent-prompt`

Print the prompt that hands an issue to your coding agent

sazabi issues agent-prompt <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues agent-prompt <issue-id>  # Print the prompt
sazabi issues agent-prompt <issue-id> | pbcopy  # Copy it on macOS

`sazabi issues link-pr`

Link a pull request to an issue

sazabi issues link-pr <issue-id> <pr-url> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--relation`	string	No	Relationship: fixes (default) or caused_by

sazabi issues link-pr <issue-id> https://github.com/acme/api/pull/42 --relation caused_by

`sazabi issues unlink-pr`

Remove a pull request relationship from an issue

sazabi issues unlink-pr <issue-id> <pr-url> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--relation`	string	No	Required relationship: fixes or caused_by

sazabi issues unlink-pr <issue-id> https://github.com/acme/api/pull/42 --relation caused_by

`sazabi issues reject`

Permanently reject an issue

sazabi issues reject <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--reason`	string	No	Required: not_real, duplicate, incorrect_details, or something_else

sazabi issues reject <issue-id> --reason not_real  # Reject an issue that isn’t real

`sazabi issues resolve`

Resolve an open issue

sazabi issues resolve <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues resolve <issue-id>  # Resolve an issue

`sazabi issues ignore`

Ignore an issue

sazabi issues ignore <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues ignore <issue-id>  # Ignore an issue

`sazabi issues reopen`

Reopen a resolved or ignored issue

sazabi issues reopen <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues reopen <issue-id>  # Reopen a resolved or ignored issue

`sazabi issues mute`

Mute an issue

sazabi issues mute <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues mute <issue-id>  # Mute an issue

`sazabi issues unmute`

Unmute an issue

sazabi issues unmute <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON

sazabi issues unmute <issue-id>  # Unmute an issue

`sazabi issues update`

Change an issue's severity

sazabi issues update <issue-id> [options]

Flag	Type	Required	Description
`--token`	string	No	Override token
`--api-base-url`	string	No	Override API base URL
`--json`	boolean	No	Output as JSON
`--severity`	string	No	Required. Issue severity, by impact. critical: Happening now in production: an outage of the service, of a flow most users depend on, or of a whole feature; or data loss, a security exposure, or failed payments. high: Happening now in production: at least 1% of attempts failing or a region down; or production data loss, exposure, or failed payments that has stopped. medium: A failure limited to a few users or one path, a broad internal failure, a production outage that ended on its own, or serious harm outside production. low: No user or system impact, a transient blip, an internal failure on one item or a rare path, or other work outside production, including eval, training, and canary runs.
`--note`	string	No	Optional context for the severity change, up to 500 characters. Shown in the issue's history.

sazabi issues update <issue-id> --severity high --note "Checkout errors reach 3% of requests"  # Raise an issue's severity

On this page