Linear

Linear is the modern alternative to Jira — same purpose, cleaner API. DevRecall normalizes Linear and Jira into the same activity shape, so standups and brag docs work identically across both.

Connect

devrecall auth linear

Two auth options (chosen interactively during the prompt):

1. OAuth — opens a browser via relay.devrecall.dev.
2. Personal API key — generate at Linear → Settings → API → Personal API keys.

Linear access tokens don’t expire (no refresh-token dance).

What gets collected

Activity	What
Issue transitions	When you moved an issue (e.g., In Progress → Done)
Comments	Comments you wrote
Issues created	Issues you authored
Cycle membership	Which cycle (sprint equivalent)
Project / team	For grouping in summaries

Required scope

Scope	Purpose
read	Read all issues, comments, users

Linear’s scope model is simple: read or write. DevRecall only ever asks for read.

Linking commits to issues

Linear issue identifiers (e.g., ENG-456) are extracted from commit messages the same way as Jira keys. DevRecall asks for your team prefixes during setup so it can disambiguate from Jira when both are connected.

Branches named eng-456-feature-name are also recognized via Linear’s native git integration pattern.

Rate limits

1,500 requests/hour per OAuth app. Typical daily sync is 2–5 requests (GraphQL lets DevRecall fetch everything in one query).

Linear vs Jira

Concept	Jira	Linear
Issue	Issue	Issue
Sprint	Sprint	Cycle
Status	Status	State
Priority	Name	1–4 numeric

Both normalize to the same ticket_update activity in DevRecall.