Jira with orbit CLI

Manage Jira issues, epics, sprints, boards, projects, releases, custom fields, screens, statuses, and issue types using the orbit CLI. Supports both Jira Cloud (REST API v3) and Jira Server/Data Center (REST API v2) with multi-profile support and 1Password secret resolution.

Prerequisites

orbit CLI installed — if which orbit fails, install with:
- macOS/Linux (Homebrew): brew install jorgemuza/tap/orbit
- macOS/Linux (script): curl -sSfL https://raw.githubusercontent.com/jorgemuza/orbit/main/install.sh | sh
- Windows (Scoop): scoop bucket add jorgemuza https://github.com/jorgemuza/scoop-bucket && scoop install orbit
A profile with a jira-cloud or jira-onprem service configured in ~/.config/orbit/config.yaml
Valid credentials — API token for Cloud (basic auth with email + token), PAT for Server
Credentials can be stored as 1Password (op://) or Infisical (infisical://) references for automatic resolution

Quick Reference

All commands follow the pattern: orbit -p <profile> jira <resource> <action> [flags]

The tree stops there - <action> is always a leaf, so there is no <action> list. Reading has its own action name next to writing: issue view --comments reads comments, issue comment only writes them; issue attachments lists attachments, issue attach only uploads. Guessing a subcommand is unsafe rather than merely wrong: write actions take the issue key as their first positional argument, so jira issue comment list PROJ-123 is parsed as issue key list with body PROJ-123 and sent to Jira as a real write. Check references/commands.md instead of guessing.