Jira

Jira adds task-level context: what tickets you worked on, status transitions (“moved to In Review”), and sprint membership.

Connect

devrecall auth jira

You’ll be prompted for three things:

1. Base URL — e.g. https://mycompany.atlassian.net
2. Email — your Atlassian account email
3. API token — generate one at id.atlassian.com → Security → API tokens

The token is validated against /rest/api/3/myself and stored at ~/.devrecall/tokens/jira.json (0600).

Both Cloud and Server / Data Center are supported. DevRecall detects which based on your base URL.

No relay involved

Jira auth is pure API-token: nothing touches relay.devrecall.dev and no DevRecall-owned OAuth app sees your account. The token you paste goes straight from your machine to Atlassian.

What gets collected

Activity	What
Issue transitions	When you moved a ticket between statuses
Comments	Comments you wrote
Issues created	Issues you reported
Sprint membership	Which sprint, velocity contribution
Worklogs	Time logged (if your team uses worklogs)

Read-only. DevRecall never creates or modifies issues.

Token scopes

Atlassian API tokens inherit your user permissions — there are no separate scopes to configure. DevRecall only ever issues GET requests, so even if your account has write access, nothing is modified.

How standups link Jira → Git

When a commit message contains a Jira issue key (e.g., PROJ-123: fix retry logic), DevRecall groups commits under their tickets in generated standups:

- PROJ-123 (Fix payment retry): 3 commits — backoff, max retries, tests
- PROJ-123: moved to In Review

This is automatic — no extra setup.

Rate limits

Atlassian recommends ≤100 requests/minute per user. DevRecall uses JQL to fetch all relevant issues in a single query — a typical daily sync is 5–10 requests.

Confluence

Pages, blogposts, and comments you authored in Confluence are collected too — they share this same Atlassian token. See Confluence for setup and details.