Skip to main content

​
Overview

Linear is a one-click connector that gives Rootly AI read access to your Linear workspace during investigations. When an incident correlates with recent engineering work, Rootly AI can pull related issues, project context, and roadmap items automatically — useful for surfacing “was this already flagged?” or “who owns this area?” Every query is read-only. Rootly AI can search and read issues, projects, and roadmaps but cannot create, comment on, or edit anything on the Linear side.

​
Before You Start

  • A Linear workspace with permission to authorize third-party OAuth apps.
  • Read access to the teams and projects you want Rootly AI to be able to see.

​
Setup

Open Configuration → AI → Connectors and click Connect on the Linear card. Sign in to Linear and authorize Rootly AI for the workspace you want to connect. When the flow completes, the card flips to Connected.

​
What Rootly AI Can Read

  • Issues — active and completed issues, filterable by team, project, assignee, or label.
  • Projects — project titles, descriptions, status, and the issues within them.
  • Roadmaps — the higher-level roadmap items that group projects together.
  • Comments and history — the discussion thread on an issue.
Rootly AI reaches for Linear when a question is about “who owns this?” or “was this already flagged?” — pair it with an observability connector (Sentry, Datadog) to link the incident’s symptom to the tracked work.

​
During an Incident

“There’s an active project tracking the migration involved here. Current status and owner attached.” Rootly AI searches Linear for related issues and roadmap items when the incident touches ongoing work. If a migration, refactor, or planned change is already tracked, responders see the project link, current status, and owner in the investigation output — useful for figuring out whether the current incident is a symptom of known in-progress work.

​
Best Practices

  • Authorize at the workspace level. Restricting the connector to one team means Rootly AI can’t see cross-team incidents, which is exactly the case where knowing about related work matters most.
  • Keep issue titles descriptive. Linear’s search ranks by title. Clear titles help Rootly AI surface the right related issue, not just any related one.
  • Pick one work tracker per team. Rootly AI supports both Linear and Atlassian (Jira). Connecting both when your team only uses one adds a source that never fires and clutters investigation output.

​
Troubleshooting

The authorizing Linear user doesn’t have access to those teams. Confirm the account has the right team memberships, then disconnect and reconnect to refresh the OAuth grant.
Linear search returns both open and closed issues. If a closed issue is being cited over the current work, ensure the current issue has stronger title/label signal or update the closed one so it stops being the top match.
If a Linear admin revokes the Rootly AI OAuth grant from Linear’s side, Rootly’s card still shows Connected but every query fails. Reconnect from Rootly to reauthorize.

​
Frequently Asked Questions

Whichever your team actually uses. Rootly AI can query both, but connecting both when only one is used in practice adds a source that never returns useful signal.
No. Connectors are read-only. To create Linear issues from an incident, use the existing Linear integration — that’s a separate configuration.
Rootly does not maintain a persistent copy of Linear data — queries run at investigation time and the response is used in reasoning only. Query results do appear in the LLM traces Rootly logs for quality monitoring, as with every tool call Rootly AI makes. See Data Privacy for Rootly AI for the retention boundary.

Connectors Overview

All connectors and how they fit together.

Atlassian

The alternative work-tracking connector — covers Jira and Confluence.

Data Privacy for Rootly AI

What Rootly AI sees, retention, and model training controls.