Projects, agile resources, releases, and automation

Discovery

Use project list/get/issue-types/priorities/components, board list, and board config list to resolve names into keys or IDs. Use sprint list and sprint issues only after resolving the board and sprint.

Search users with user list --query. Use server info for deployment and API diagnostics. Generate completions only when the user requests shell setup.

Releases

Use release list --fields to identify the version ID. Mutations support dry-run:

jrc release create --project PROJ --name v1.2.0 --start 2026-07-01 \
  --release 2026-08-01 --description-file ./notes.md --dry-run
jrc release update VERSION_ID --release 2026-08-08 --dry-run
jrc release release VERSION_ID --date 2026-08-08 --dry-run
jrc release archive VERSION_ID --dry-run
jrc release delete VERSION_ID --move-fix-to OTHER_ID --confirm --dry-run

Deleting a version can clear references. Supply replacement version IDs when the user asks to retain fix- or affects-version associations.

Automation

Use automation list/get/runs to inspect rules before enabling, disabling, or triggering them. Rule mutations can affect many issues; show the selected rule ID and dry-run payload, then act only when the request names or unambiguously identifies that rule.