jira

Jira (Atlassian Cloud)

Direct REST access to Jira Cloud — no MCP server required. Good for triaging backlogs, bulk status updates, sprint/board reporting, creating issues from logs.

Usage

• Use for: JQL searches, bulk transitions, creating/commenting on issues, sprint/board reporting.
• Skip for: Personal TODOs, teams on Linear/GitHub Issues, read-only link sharing, Server/Data Center Jira (Cloud only).

Credentials check

for v in JIRA_EMAIL JIRA_API_TOKEN JIRA_BASE_URL; do
  eval "val=\${$v}"
  [ -n "$val" ] && echo "$v: PRESENT" || echo "$v: MISSING"
done

Never echo the variable values directly (e.g. echo "$JIRA_API_TOKEN") — they would appear in the conversation transcript. Use only the boolean pattern above.

If any required env var is MISSING, respond to the user with EXACTLY this message (do NOT paraphrase, do NOT suggest manual JSON edits):

I need your Jira credentials. Run this in another terminal — it'll guide you through all three values safely (masked input for the secret):

teleport-setup add-key jira

Then restart Claude Code (/exit, then claude) and ask me again.

Do NOT suggest editing ~/.claude/settings.local.json manually. The teleport-setup add-key command handles that safely with backup, validation, and masked input. Stop execution until the user has run the command and restarted.

API

• Base URL: $JIRA_BASE_URL/rest/api/3 — per-workspace (e.g. https://acme.atlassian.net/rest/api/3).
• Auth is Basic, NOT Bearer. AUTH="Basic $(printf '%s' "$JIRA_EMAIL:$JIRA_API_TOKEN" | base64)". Bearer $TOKEN → 401.
• Headers: Accept: application/json always; Content-Type: application/json on writes.
• v3 requires ADF for rich-text fields (description, comment, environment); v2 accepts plain strings — escape hatch.
• Rate limits: cost-based, not req/min (tier-1 pool 65,000 pts/hr). Watch X-RateLimit-NearLimit; on 429 honor Retry-After.

Endpoints

Resource	Method · Path
Issues	GET/POST/PUT/DELETE /rest/api/3/issue[/{idOrKey}]
JQL search	POST /rest/api/3/search/jql (old /search deprecated)
Transitions	GET/POST /rest/api/3/issue/{idOrKey}/transitions
Comments	GET/POST /rest/api/3/issue/{idOrKey}/comment[/{id}] (ADF body)
Projects	GET /rest/api/3/project[/{idOrKey}]
Boards/Sprints	GET /rest/agile/1.0/board[/{id}/sprint]
Users	GET /rest/api/3/myself, /rest/api/3/user?accountId=...
Fields	GET /rest/api/3/field (resolve customfield_* → friendly name)
Attachments	POST /rest/api/3/issue/{idOrKey}/attachments (multipart + XSRF header)