jira-issues

View documentation for the original command

$ tldr jira issue

jira-issues [options] [JQL-query]

-s, --server URL
    Jira server base URL (e.g., https://your-domain.atlassian.net)
Required unless configured

-u, --user USERNAME
    Jira username or email for authentication

-p, --password PASSWORD
    Password or API token (use JIRA_TOKEN env var for security)

-t, --token TOKEN
    API token for passwordless auth (preferred)

-b, --board ID
    Fetch issues from specific Agile board

-l, --limit NUM
    Maximum number of issues to return (default: 50)

-o, --output FORMAT
    Output format: table|json|csv (default: table)

-f, --fields FIELDS
    Comma-separated fields to display (e.g., key,summary,status)

-c, --config FILE
    Path to config file (default: ~/.jira.cfg)

-v, --verbose
    Enable verbose logging for debugging

-h, --help
    Show usage help

The jira-issues command is a lightweight Linux utility designed to interact with Atlassian Jira instances from the command line. It allows users to search, list, and filter issues using Jira Query Language (JQL) directly in the terminal, making it ideal for developers, DevOps engineers, and administrators who need quick access to issue data without opening a web browser.

Key features include support for authentication via username/password, API tokens, or OAuth; customizable output formats such as table, JSON, or CSV; pagination for large result sets; and integration with shell scripting for automation workflows. It fetches issue details like summary, status, assignee, priority, and custom fields, enabling efficient triage and reporting.

Built on top of Jira's REST API, jira-issues handles rate limiting, retries, and error reporting gracefully. It's particularly useful in CI/CD pipelines, cron jobs for monitoring, or bash scripts for generating reports. Configuration is stored in ~/.jira.cfg for reuse across sessions, reducing repetitive flag usage.

Requires network access to Jira API; API tokens recommended over passwords for security.
Rate limits apply (typically 100/min); use --limit wisely. Cloud vs Server/DC may differ in auth.

jira-issues -s https://example.atlassian.net -u user@example.com -t token 'project = PROJ AND status = Open'
jira-issues --board 123 --output json | jq '.issues[] | .key'
jira-issues assignee = currentUser --fields key,summary

Edit ~/.jira.cfg with:
[default]
server = https://your-domain.atlassian.net
user = your@email.com

Developed as part of the open-source go-jira project around 2015 by community contributors. Evolved from early Jira CLI wrappers; major updates in 2020 for Jira Cloud support and token auth. Maintained on GitHub with active releases.

jira(1), curl(1), jq(1), gh(1)