/
Tools Connect: Linear (Beta)

Tools Connect: Linear (Beta)

 

Connect Linear to Allstacks with a personal API key, enable Detailed issue history per Linear team, then enable the workspace and teams you want ingested in Allstacks. Most customers see usable data within 24 hours after the next sync run. {info}

Prerequisites

Complete these steps before connecting Allstacks. Skipping them does not block the connection, but activity-level data may be incomplete.

Requirement

Details

Requirement

Details

Linear access

Account with permission to create personal API keys and manage team settings

Allstacks access

Permission to manage Tools at the organization level

Teams identified

Know which Linear teams you want in Allstacks (Allstacks does not ingest every team by default)

Connection steps

Step 1 — Enable detailed issue history

Without it, sync still works, but granular activity data (status changes, assignee changes, label changes, etc.) may be incomplete compared with Jira-style history.

  1. In Linear, hover the team name in the left sidebar.

  2. Click the ··· menu → Team settings.

  1. Open the General tab.

  1. Enable Detailed issue history.

Step 2 — Create a Linear API key

  1. In Linear, open Settings (workspace menu, upper left).

  2. Go to Account → Security & access.

  3. Under Personal API keys, click New API key.

  1. Name the key (e.g. Allstacks).

  2. Set Permissions:

    • Default: Full Access

  3. Set Team access:

    • All teams you have access to — recommended if Allstacks should mirror your full Linear footprint.

    • Or restrict intentionally to specific teams.

  4. Click Create.

  1. Copy the key immediately and store it securely. Linear shows it only once.

Step 3 — Connect Linear in Allstacks

  1. From the organization dropdown, go to Tools.

image-20251021-181540.png

  1. Click Add Tools.

image-20251021-181617.png

  1. Search for Linear.

  2. Paste your API key.

  3. Click Add Tool.

image-20251021-181658.png

Functionality Overview

Current Functionality

  • Available now / working in production today:

    • Metrics and WIT function as expected.

    • Several special Linear parent types are enabled:

      • Team parent

      • Label

      • Label group parent

    • Advanced filters and chart settings/axis groupings are also functional.

    • Label groups are a new concept unique to Linear:

      • A label group aggregates multiple labels (e.g., a “color” label group might contain “red,” “yellow,” “green”).

      • Selecting the group in reports shows all items tagged with any of those labels (not grouped visually by label).

    • Teams are also unique in Linear

      • They behave similar to a “project” in Jira

Remaining / Upcoming Work

  • UI updates are the final step needed for complete functionality (the backend is ready).

    • This enables the user to select the Linear-specific concepts such as Label Groups and Teams

  • Projects and Cycles are not yet covered:

    • Cycles are Linear’s version of sprints.

    • Projects act as a middle layer between issues and initiatives — similar to Jira epics, but can pull issues from multiple teams.

    • Initiatives group multiple projects (similar conceptually to Jira initiatives).

  • Team nesting

    • While we have teams working today as parent objects, there may be some nuances to how the data needs to be presented when teams are nested. It sounds like this is similar to ADO’s concepts of teams and area paths.