---
name: "Atlassian"
description: Work with Jira issues, sprints, and boards plus Confluence pages through the official `acli`.
version: 1
situations: jira, confluence, tickets, sprints, atlassian
requires-secrets:
requires-packages:
requires-connector: atlassian
---

# Atlassian (`acli`)

Runs through Atlassian's official CLI in your **bash** tool. The operator connected a site from 00's
skill store.

## First, know which site

```
acli jira auth status
```

Not authenticated? **Skill store → Atlassian → Connect**. Confluence is a separate, identical login
the operator runs once: `acli confluence auth login --web`. If Confluence commands fail while Jira
works, that's why — say so rather than retrying.

## Jira — read

```
acli jira workitem search --jql "project = ENG AND status != Done ORDER BY updated DESC" --limit 30 --json
acli jira workitem view ENG-123 --json
acli jira project list --json
acli jira board list --json
acli jira sprint list --board-id 42 --json
```

JQL is the real interface here. Prefer one precise JQL query over listing everything and filtering
locally — it's faster and it doesn't page through a thousand issues.

## Jira — write

```
acli jira workitem create --project ENG --type Task --summary "…" --description "…"
acli jira workitem comment ENG-123 --body "…"
acli jira workitem transition ENG-123 --status "In Progress"
acli jira workitem assign ENG-123 --assignee "user@example.com"
```

Say which issue and which project before you write. Transitioning someone else's ticket, or
reassigning it, is a social act — ask.

## Confluence

```
acli confluence page list --space ENG --json
acli confluence page view --id 12345 --json
acli confluence page create --space ENG --title "…" --file body.md
```

## Never without being asked in this turn

Deleting issues or pages, bulk transitions across a JQL result, closing sprints, and editing a page
someone else owns. A bulk edit that touches fifty tickets cannot be undone with one command.