Skip to main content

CI PyPI version

Jira CLI

Think github-cli but for Jira.

Modular, class-based Jira command-line tool for issue listing, searching, and management.

There's a CLI (jira issue ...) and an interactive TUI (jira tui --project PROJ). Both are self-explanatory via --help / the in-app ? help — see docs/features.md for the full feature overview and TUI keyboard shortcuts.

Installation

# Editable install for local development
uv tool install --editable .
jira --help
# Remote/published, via uvx
uvx --from colenio-jira-cli jira-cli issue list --project PROJ

The PyPI/package name is colenio-jira-cli; the installed commands are jira and jira-cli (both run the same CLI). See docs/distribution.md for other install options (pip, venv).

For screenshots, screencasts, or trying the TUI without Jira credentials, use synthetic demo data:

jira tui --demo

GitHub Issues can be browsed read-only in the TUI. Authentication uses GH_TOKEN or your existing gh auth login session, and -R works like gh -R owner/name:

jira tui --provider github -R colenio/jira-cli

Screenshots

The default issue table is optimized for quick triage: type, key, summary, status, assignee, and priority stay visible while the detail pane follows the current selection.

Jira CLI demo issue table

The board view groups the same issue source by workflow status, with Backlog on the left and done states on the right.

Jira CLI demo board view

Setup

Start with the tracked local.env.example: copy it to local.env or .env, then replace the placeholder values. Never commit the copied file because it contains credentials.

The CLI searches the current directory and up to three parent directories. In each directory it checks local.env before .env and loads the first matching file. Existing process environment variables are used when no file is found.

# Required
JIRA_URL=https://company.atlassian.net
JIRA_EMAIL=user@example.com
JIRA_API_TOKEN=your_api_token_here

# Optional
JIRA_PROJECT=PROJ      # Default project for list/find/tui

Get your API token from Jira Cloud: Account Settings → Security → Create API Token.

For GitHub, set GH_TOKEN, configure GH_REPO or GH_PROJECT as needed, or use an existing gh auth login session. Validate configured contexts before starting the TUI with:

jira validate
jira validate --provider jira --project PROJ
jira validate --provider github --repo owner/repository

For GitLab, set GITLAB_TOKEN to a personal, project, or group access token with the api scope, and set GITLAB_PROJECT to a project path or numeric ID. GITLAB_URL is optional and defaults to https://gitlab.com. Start the TUI with jira tui --provider gitlab --project group/project. The api scope is sufficient; no additional user scope is required.

The TUI can display the authenticated user's email from GitLab's GET /user response. Other project members expose only their public email addresses to regular users; private member emails are not made visible by adding ordinary token scopes. On self-managed instances, an administrator can optionally set GITLAB_ADMIN_TOKEN to a separate admin PAT; the provider then reads private member emails through the admin Users API and falls back to public emails if that lookup is denied. The admin token must belong to an administrator. Current GitLab documentation calls the additional self-managed scope admin_mode (alongside api); some older self-managed versions may expose the legacy admin_api scope instead. Admin Mode must also be enabled where required. See the GitLab access token scopes and Users API documentation.

Use jira tui --demo for a credential-free local run.

Development

uv sync --extra dev --extra local-dev
uv run pytest
uv run black jira_cli
uv run ruff check jira_cli
uv run jira-cli-qa   # runs ruff + radon + pylint

Documentation Site

uv sync --extra docs
uv run jira-cli-docs        # strict MkDocs build
uv run jira-cli-docs-serve  # local preview

The docs are built with MkDocs Material and mkdocstrings. API pages render Python docstrings directly from jira_cli.

Additional Docs

License

MIT

Metadata

Release files for colenio-jira-cli 0.8.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for colenio-jira-cli 0.8.0
File Size Uploaded
colenio_jira_cli-0.8.0.tar.gz 647.5 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for colenio-jira-cli 0.8.0
File Interpreter ABI Platform
colenio_jira_cli-0.8.0-py3-none-any.whl Python 3 none any Details

Total release size: 775.0 kB

Release files / colenio_jira_cli-0.8.0.tar.gz

Download URL colenio_jira_cli-0.8.0.tar.gz
Size 647.5 kB
Tags Source
SHA-256 checksum
How to use checksums
86dfc69b3da4ecd55a3fea8ecdd4f7cdd43ab1586777d97384ffbfa6c64375ce
BLAKE2b-256 checksum
How to use checksums
58a3f0262ef490ee60f0483a9e6d3409f9647a2f24d7a424ca0ca6b50355db20
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release files / colenio_jira_cli-0.8.0-py3-none-any.whl

Download URL colenio_jira_cli-0.8.0-py3-none-any.whl
Size 127.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
2f274234ebfe5ce3cdf0a3f2040410a96497b88c5f12d0b606f1b24f6518344d
BLAKE2b-256 checksum
How to use checksums
b4523523b536ca406b3a61f1973e6524f42ae948f630d939f7244e74a2fd65e2
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 2, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.8.0 This release

2 release files

0.7.2

2 release files

0.7.1

2 release files

0.7.0

2 release files

0.6.0

2 release files

0.5.0

2 release files

0.2.2

2 release files

0.2.1

2 release files

0.2.0

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page