co issue — issues
Issue CRUD and parent/child (sub-issue) trees
co issue operates on issues — create, list, view, edit, delete, and the sub-issue (parent/child) tree.
co issue create
Creates a new issue. If -t / -b / --type / --priority are omitted you'll get an interactive prompt.
co issue create -t "Bug X" --type bug --priority high
co issue create -t "Refactor" --type task --project web
co issue create --assignee none # leave unassigned| Flag | Description |
|---|---|
| -t, --title <title> | Issue title |
| -b, --body <body> | Description (markdown) |
| --type <type> | bug |
| --priority <p> | low |
| --status <status> | Initial status (default: backlog) |
| --project <name | key> |
| --assignee <user> | username/email/numeric ID. Default: yourself. "none" to leave unassigned |
| --workspace <slug> | Override workspace |
co issue list
Lists your issues, or every issue in the workspace, as a compact table.
co issue list
co issue list --scope workspace
co issue list -s in_progress,review
co issue list -l 50| Flag | Description |
|---|---|
| --scope <scope> | me |
| -s, --status <status> | Status filter, comma-separated for multiple |
| -l, --limit <n> | Page size |
co issue view <key>
Shows the full issue — status / priority badges, metadata (project, assignee, reviewer, due date, milestone, sprint), parent/sub-issue progress, and the description.
co issue view 123
co issue view 123 --comments # also print the comment threadco issue edit <key>
Updates issue properties. At least one flag is required.
co issue edit 123 --status in_progress
co issue edit 123 --due 2026-05-20
co issue edit 123 --assignee bob --reviewer alice
co issue edit 123 --project web --milestone 17
co issue edit 123 --due none| Flag | Description |
|---|---|
| -t/-b | Title / body |
| --type / --priority / --status | Issue metadata |
| --assignee <user> | username/email/numeric ID, or none |
| --reviewer <user> | username/email/numeric ID, or none |
| --due <YYYY-MM-DD> | Due date, none clears |
| --project <name | key> |
| --milestone <key> | Milestone, none clears |
| --sprint <key> | Sprint key, none clears |
| --sprint-group <key> | Required when assigning a sprint |
co issue comment <key>
Add, edit, or delete a comment on an issue. Same options as co cr comment — -b/-F/$EDITOR/--edit/--delete and automatic @-mention resolution.
co issue comment 2084 -b "Triaged: next sprint"
co issue comment 2084 -F notes.md
git log -1 --pretty=%B | co issue comment 2084 -F -
co issue comment 2084 # opens $EDITOR
co issue comment 2084 --edit 91 -b "updated body"
co issue comment 2084 --delete 91| Option | Description |
|---|---|
| -b, --body <text> | Comment body (omit to open $EDITOR) |
| -F, --body-file <path> | File or stdin('-') |
| --edit <id> | Edit existing comment (PUT) |
| --delete <id> | Delete an existing comment |
| --workspace <slug> | Override workspace |
To see the thread inline, use co issue view <key> --comments. Mention format and resolution rules match co cr comment.
co issue close / co issue reopen
co issue close 123 # status=done
co issue reopen 123 # status=todo (default)
co issue reopen 123 --status in_progressco issue delete <key>
Permanent delete. The server returns 409 if the issue has sub-issues, so you must opt in with --cascade.
co issue delete 123
co issue delete 123 --cascade -yco issue sub
Manages parent/child (sub-issue) links. The child issue itself remains a normal issue — only the link is added or removed.
co issue sub list 123 # direct children
co issue sub tree 123 # full tree
co issue sub add 123 456 # link existing Issue-456 under 123
co issue sub create 123 -t "Sub-task"
co issue sub remove 123 456 -y # unlink (child stays alive)co issue sub remove only severs the link. Call co issue delete <key> separately to remove the child issue itself.