Subcommands
| Subcommand | Description |
|---|---|
get | Get full detail for a single issue |
list | List issues for the current organisation |
update | Update an issue’s status, resolution, or severity |
versori issues get
-h,--help: help for get--project: Project ID; defaults from .versori when inside a synced project directory.
versori issues list
List issues raised in the organisation (via ctx.createIssue(), unhandled workflow errors, or
platform events such as an out-of-memory kill).
Filters (all optional) narrow server-side by status, project, environment, and severity. Inside a
synced project directory the project filter defaults from .versori. An OOM-killed project surfaces
here as an issue titled “OOM Killed” — inspect it with ‘issues get <id>’.
-
--after: Pagination cursor: pass a prior response’s last issue ID to fetch the next page -
--before: Pagination cursor for the previous page -
--environment: Filter by environment ID -
--first: Max issues to return (0 lets the server default apply) -
-h,--help: help for list -
--project: Project ID; defaults from .versori when inside a synced project directory. -
--severity: Filter by severity (critical, high, low, medium) -
--status: Filter by status (open, closed, acked, resolved)
versori issues update
Update the editable fields of an issue. Common uses:
issues update <id> —status acked # acknowledge
issues update <id> —status resolved —resolution-status resolved
Only the flags you pass are changed; everything else is left as-is. This is a mutation — run it only
when explicitly asked.
-h,--help: help for update--resolution-status: Resolution status (resolved, negated, ignored)--severity: New severity (critical, high, low, medium)--status: New status (open, closed, acked, resolved)