acli (Atlassian CLI)

What it is

Atlassian's official CLI (acli) for Jira and Confluence from the terminal: search issues, create/transition tickets, read and edit Confluence pages.

Install

Linux x86_64 — official binary (always the latest stable; see the Atlassian CLI docs for the canonical link):

curl -LO "https://acli.atlassian.com/linux/latest/acli_linux_amd64/acli"
chmod +x acli
sudo mv acli /usr/local/bin/acli

On arm64 use the acli_linux_arm64 variant of the same URL. The CLI self-updates via acli update unless you disable it.

Authenticate

acli jira auth login

Browser-based OAuth 2.0 (3LO) against your Atlassian cloud site; the token is cached under ~/.config/atlassian-cli/. Keep a note of which Atlassian account/org you authorized in Vaultwarden so onboarding a second laptop is a one-minute job.

Configure for this environment

acli jira workitem search --jql "project = PF AND status != Done" --limit 10
acli confluence page view --id <page-id>

Set a default site once so commands don't prompt:

acli jira site list          # pick your site

Self-hosted equivalent

None deployed yet. Self-hosted Jira/Confluence replacements (Plane, OpenProject) were evaluated and deferred — when one lands on the Proxmox cluster it will be announced, and it won't be acli-compatible (Plane and OpenProject have their own REST APIs; closest dev stand-in today is the Plane community Docker compose stack).

Aurélio integration

The cli-atlassian skill drives acli for Jira/Confluence queries and ticket updates. Connector registry id: atlassian (OAuth 2.0 3LO, api.atlassian.com).

Verify

acli --version
# acli version x.y.z
acli jira auth status
# ✓ Authenticated as <name> (<site>.atlassian.net)
acli jira workitem search --jql "assignee = currentUser()" --limit 3
# KEY  SUMMARY  STATUS  ...

Troubleshooting

Browser flow fails on a headless shell — run acli jira auth login from a desktop session, or copy the printed URL to a browser and paste the callback back.
Wrong site — you authorized multiple Atlassian sites; pass --site or re-login with the right tenant.
403 on Jira API — missing OAuth scope; re-run auth login and accept the full scope list.
Corporate proxy breaking OAuth callback — set HTTPS_PROXY before running acli, or use the API-token auth fallback for Jira REST scripts.

2.5 KiB Raw Permalink Blame History