TestingOps.ai

Issue trackers, wikis and code · Native connection

Linear and TestingOps: team issues as test context

TestingOps reads the issues of a Linear team into its knowledge base, lets its agents look up and update issues while they test and files defects as Linear issues.

  • Native connection
  • Available
Request a demo Linear API: getting started and personal API keys
Connection
Native connection
Writes back
Within what you allow
Last checked
7 Nov 2026

In short

Linear and TestingOps in short

The Linear connection links one Linear team to a TestingOps project. Its issues, with title, description and workflow state, become requirements that agents search when they write and review test cases.

While they work, agents can open an issue with its comments, search the team's issues and, with the write switch on, comment, change the workflow state or create issues. Defects reported from TestingOps become issues in the team.

Connect with Linear or a personal API key. Linear issues do not start Tester Agent rules.

What it does

What it does for your testing

  1. 1

    Team issues become test context

    Input
    Issues of the linked team: identifier, title, description and state
    TestingOps
    Keeps the 300 most recently updated per sync as requirements in the knowledge base
    Output
    Context agents search when they write and review cases
  2. 2

    Agents check the issue before testing

    Input
    An issue identifier such as ENG-142
    TestingOps
    Reads the current issue with its latest comments and the team's workflow states
    Output
    Cases and runs based on what the issue says now, not on the last sync
  3. 3

    A verified fix moves the issue

    Input
    A passing check of a fix
    TestingOps
    With "Agents may write to this tracker" on, an agent comments the result and changes the workflow state
    Output
    The Linear issue updated by the agent
  4. 4

    Defects land in the team

    Input
    A TestingOps defect
    TestingOps
    Creates an issue in the linked team through Report to…
    Output
    The issue identifier and link stored on the defect

Step by step

How it works

  1. ConnectUnder Integrations → Project tools, open Linear and use Connect with Linear, or paste a personal API key.
  2. Link a teamIn Knowledge Base, add the team under Issue trackers. Each sync reads the team's 300 most recently updated issues, hourly and on Sync now.
  3. Agents read liveAgents use the issues as context and open the live issue when a task needs its current text and comments.
  4. Write backWith the source's write switch on, agents comment, change workflow states and create or update issues; Report to… on a defect creates an issue in the team.

There is no webhook intake or board rule for Linear: agents work with Linear when a task needs it, not when an issue changes.

Connect

Setup

  1. In TestingOps, open Integrations → Project tools, select Linear and choose Connect with Linear, or paste a personal API key and select Connect.
  2. In Knowledge Base, pick the project, select + Add source under Issue trackers, choose the connection, select the team and select Link to RAG.
  3. Turn on Agents may write to this tracker on the source if agents should comment or change workflow states.

Documentation: Linear API: getting started and personal API keys

Where you connect it in TestingOps: Integrations → Project tools → Issue trackers, wikis and code → Linear

Use cases

Use cases

Write cases for the next cycle

Trigger
Issues for the next cycle are written in the team
Uses
Issue titles and descriptions
Agent activity
Agents write draft cases with the issues as context
Result
Cases ready for review before the work is done
Condition
Agents start from a task you give them; Linear events do not start them

Report a regression to the owning team

Trigger
A run fails and a tester confirms the defect
Uses
The defect's steps, its expected and actual result, severity and environment
Agent activity
Report to… opens an issue in the linked team
Result
A Linear issue that names the TestingOps defect
Condition
The connection needs an API key or Linear sign-in

Close the loop after a fix

Trigger
A developer marks a bug fixed and asks for verification
Uses
The issue's comments and the team's workflow states
Agent activity
Runs the related case and, if it passes, comments and moves the issue to the state you name
Result
An updated Linear issue
Condition
Needs Agents may write to this tracker

Capabilities

Capabilities and limits

What is read

  • Issues of one team: identifier, title, description, state and last update; the 300 most recently updated per sync
  • On demand for agents: an issue with comments, search within the team and the team's workflow states

What is produced

Requirements in the project's knowledge base

Where it can write

  • Issues created through Report to… on a defect
  • With "Agents may write to this tracker": comments, workflow state changes, new issues, and title or assignee changes
  • Not written: labels (Linear sets them by id, which is not supported yet) and descriptions of existing issues

How it connects

  • Connect with Linear (read, write and issue creation access) or a personal API key
  • Linear's cloud API

Account and permissions

  • TestingOps reads and writes with the permissions of the key owner or the signed-in user
  • Agent writes need the source's "Agents may write to this tracker" switch

Limits

  • No Tester Agent rules, webhooks or approvals for Linear
  • 300 issues per sync; comments are read live, not stored
  • No code or commit data comes from Linear

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A product team tracks work in a Linear team with the key APP. A tester asks an agent to prepare cases for APP-214, "Export invoices as CSV"; the agent opens the issue, reads the latest comment that adds a 10,000-row limit and drafts cases for an empty export, a normal export and the row limit.

One case fails on staging. The tester reports the defect with Report to…, and a new issue appears in the APP team with the steps, the expected and actual result and the TestingOps defect key.

Frequently asked questions

Can the Tester Agent run on Linear like it does on Jira?

No. Linear has no event intake or board rules in TestingOps. Agents work with Linear when a task needs it: they read issues and, with the write switch on, comment, change states and create issues.

Which Linear data is read?

The issues of the linked team, up to the 300 most recently updated per sync: identifier, title, description and workflow state. Comments are read live by agents, not stored.

What happens when I report a defect to Linear?

Report to… creates an issue in the linked team with the defect's severity, priority, environment, steps, expected and actual result and a line naming the TestingOps defect. The issue link is stored on the defect.

Can agents set labels on Linear issues?

Not yet: Linear sets labels by id, which TestingOps does not support. Title, assignee and workflow state can be changed.

Personal API key or Connect with Linear?

Either. Connect with Linear asks for read, write and issue creation access; a personal API key works with the permissions of its owner.

Next step

Bring a Linear team to a demo and see agents write cases from its issues.

Request a demoMore project tools integrations