Jira CLI Pro

Jira Cli Pro brings ticket management to the terminal so you never have to context-switch into a browser to triage, comment, or close issues. It is built for engineers and team leads who live in JQL and want to run bulk operations, generate sprint artifacts, and script Jira into their existing workflows. If you already drive Git, CI, and deploys from a shell, this fills the last gap.

When to use it

• A sprint just ended and you need to close out 40 "Done" tickets that never got transitioned.
• Inbound bugs keep landing in the backlog unlabeled and you want to auto-route them by component or keyword.
• Your manager wants a sprint summary by Friday and you'd rather generate it than assemble it by hand.
• You're cleaning a backlog and want to find-and-comment on everything untouched for 90+ days before bulk-closing.

What it does

The skill wraps the Jira Cloud REST API v3 and authenticates with an API token (email + token, Basic auth). Core verbs map to familiar operations:

• jira issue list "<JQL>" runs any JQL query and prints results as a table, JSON, or CSV.
• jira issue transition KEY-123 "Done" moves tickets through workflow states (validated against the project's available transitions).
• jira issue assign, jira issue comment, and jira issue label cover the day-to-day edits.
• jira bulk applies any of the above across a JQL result set, with a --dry-run flag that previews affected keys before mutating.
• jira sprint report and jira epic summary aggregate issues into Markdown, grouping by status, assignee, and story points.

Triage rules live in a .jira-cli.yml file (keyword → label/component/assignee mappings) so auto-triage is reproducible across the team.

Example

curl -fsSL --create-dirs -o ~/.claude/skills/jira-cli-pro/SKILL.md https://claudeskil.com/skills/jira-cli-pro/SKILL.md

# Preview, then bulk-close stale tickets
jira issue list 'project = PAY AND status = "In Review" AND updated < -30d'
jira bulk transition --jql 'project = PAY AND status = "In Review" AND updated < -30d' \
  --to "Closed" --comment "Auto-closed: stale >30d" --dry-run

# Generate a sprint report
jira sprint report --board 12 --sprint active --format md > sprint.md

Tips & gotchas

• Always run bulk with --dry-run first; it prints the exact keys and counts so you can sanity-check the JQL before anything mutates.
• Transition names are project-specific. "Done" in one workflow may be "Resolved" in another — list transitions for a sample issue if a bulk run fails partway.
• The REST v3 API paginates at 50–100 issues; large queries are auto-paged, but rate limits apply, so very large bulk runs are throttled rather than parallelized.
• Store your token in JIRA_API_TOKEN (env), not the config file, so it stays out of version control.

FAQ

Does it work with Jira Data Center / Server? It targets Jira Cloud REST v3. Self-hosted instances expose a slightly different auth and endpoint set, so behavior on Server is not guaranteed.

Can I undo a bulk close? There's no single undo, but every bulk run logs the affected keys; re-run bulk transition on that key list to move them back.

How are story points read for reports? From the configured story-points custom field (set its field id in .jira-cli.yml, since it varies per instance).