Linear Integration

The Linear integration pulls issue data, project and cycle tracking, and team structure into Koalr. Linear cycle time data feeds into DORA lead time calculations alongside GitHub PR review time.

Connecting Linear

Koalr connects to Linear via Linear's OAuth 2.0 flow.

Prerequisites

• You must have access to the Linear workspace you want to connect.
• Admin access is not required for connecting Linear, but only issues and projects visible to the connected user account will be synced.

OAuth connection steps

1. Go to Settings → Integrations in Koalr.
2. Click Connect Linear.
3. You are redirected to Linear's authorization page.
4. Click Authorize Koalr to grant read access.
5. You are redirected back to Koalr. An initial sync starts immediately.

Koalr requests read-only access to your Linear workspace. We do not create, update, or delete issues or projects.

What Koalr syncs from Linear

Issues

Koalr imports all issues visible to the connected account across all teams in the workspace. For each issue, Koalr tracks:

• State transitions — timestamps for each state change, used to calculate cycle time
• Assignee — mapped to Koalr users by email address
• Labels and priority — available as filters in the pull requests and cycle time dashboards
• Completion date — used as the lead time endpoint in DORA calculations

Cycle time from Linear state transitions

Cycle time is calculated from Linear issue state transitions. Koalr identifies the first transition into a state of type started as the start time, and the first transition into a state of type completed as the end time.

Linear state types map as follows:

Linear state type	Koalr interpretation
triage, backlog, unstarted	Not started
started	In progress (cycle time starts)
completed, cancelled	Done (cycle time ends)

Cycle time data appears in the Lead Time and DORA dashboards.

Projects

Linear projects are synced and displayed in the Service Catalog and project-level analytics views. For each project, Koalr tracks:

• Project name, lead, and target date
• Issue completion rate (completed issues / total issues)
• Rolling 30-day velocity (issues completed per week)

Cycles (sprints)

Linear's Cycles feature is the equivalent of Jira sprints. Koalr syncs all cycles from all teams, including:

• Cycle start and end dates
• Issues included in each cycle and their completion status
• Scope changes (issues added or removed after cycle start)

Cycle data appears in the Team Velocity dashboard.

Teams

Linear teams are imported and can be linked to Koalr teams in Settings → Teams. When a Linear team is linked to a Koalr team, issue and cycle data is scoped to that team in the dashboards.

Real-time updates

After the initial sync, Linear events are picked up on a polling interval (approximately every 2 minutes). Linear does not provide webhook push for all event types, so a small delay is expected between changes in Linear and their appearance in Koalr.

Initial sync time

The initial Linear sync imports 90 days of issue and cycle history. For most workspaces, this completes in under 5 minutes.

Differences from Jira

If you use both Linear and Jira (common in organizations with both engineering and product teams on different tools), Koalr can connect to both simultaneously. Cycle time is tracked separately per issue source — Linear issues show Linear cycle time, Jira issues show Jira cycle time — and the DORA lead time metric aggregates across both.

Disconnecting Linear

To disconnect Linear, go to Settings → Integrations → Linear and click Disconnect. Historical data is retained for 30 days, then deleted.