LinuxCommandLibrary

jira-issue

Manage Jira issues from the command line

TLDR

List recent issues

$ jira issue [[ls|list]]
copy

List issues assigned to a specific user
$ jira issue [[ls|list]] [[-a|--assignee]] "[email_or_display_name]"
copy

List high priority issues assigned to me
$ jira issue [[ls|list]] [[-a|--assignee]] $(jira me) [[-y|--priority]] High
copy

Create an issue using an interactive prompt
$ jira issue create
copy

Edit an issue using an interactive prompt
$ jira issue edit
copy

Assign user to an issue using an interactive prompt
$ jira issue [[asg|assign]]
copy

Move an issue to a certain state
$ jira issue [[mv|move]] [issue_id] "[In Progress]"
copy

Open an issue in the terminal using less
$ jira issue view [issue_id]
copy

SYNOPSIS

jira-issue <action> [options] [<issue-key> | <jql-query>]

PARAMETERS

-h, --help
    Show help and usage

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

--user EMAIL
    Jira username or email

--token TOKEN
    API token for authentication

-o, --output FORMAT
    Output format: text, json, yaml (default: text)

-p, --project PROJECT
    Filter by project key

--fields FIELDS
    Comma-separated fields to fetch (e.g., summary,assignee,status)

--no-color
    Disable colored output

-v, --verbose
    Enable verbose logging

DESCRIPTION

The jira-issue command is a third-party Linux utility designed to interact with Atlassian's Jira issue tracking system from the command line. It allows users to view, create, update, transition, and list Jira issues without needing a web browser. Typically installed via package managers like npm, pip, or as a standalone binary from repositories such as go-jira or Atlassian's CLI tools, it authenticates via API tokens or OAuth.

Key features include fetching issue details in JSON or formatted text, attaching files, commenting, and performing workflows like resolving or reopening issues. It's invaluable for developers integrating Jira into CI/CD pipelines, scripting automation, or remote ticket management. Configuration is stored in ~/.jira/config.yml for server URL, credentials, and preferences. Supports filters, JQL queries for listing issues, and custom fields handling.

Usage requires a Jira Cloud or Server instance with API access enabled. Output can be piped to tools like jq for parsing.

CAVEATS

Requires valid Jira API token; rate-limited by Jira; not officially supported by Atlassian; configuration file permissions must be secure.

ACTIONS

Supported actions: view <key> - display issue; create - new issue; edit <key> - update fields; list [<jql>] - search issues; transition <key> <transition> - workflow change.

CONFIGURATION

Run jira-issue configure interactively to set server, user, and token; stores in ~/.jira/config.yml.

HISTORY

Originated from community tools like go-jira (2015), evolved with Atlassian's jira-cli beta (2022); widely used in DevOps for automation.

SEE ALSO

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

Copied to clipboard