Generate test cases from a Linear issue

01Why generate from Linear

Linear is where a lot of teams define the work. Re-typing that work into test cases by hand is slow and drifts out of sync. Generating cases straight from a Linear issue gives you a structured first draft mapped to your test template, with a link back to the issue so coverage is traceable.

Linear is TestOrchestrator's deepest integration — beyond generation, it adds one-click OAuth, live issue search when linking, an AI insight on each linked issue, and two-way traceability. See the Linear integration page for the full picture.

02Connect Linear (one time)

A workspace admin connects Linear in Admin → External References using one-click OAuth — no API token to copy. Optionally set a default project for cases generated from the Linear sidebar. Full steps are in the Linear integration docs.

03Generate the cases

Open the Linear issue you want coverage for.
Use the Generate tests action in the issue's sidebar (or generate from inside TestOrchestrator against a linked Linear issue).
AI drafts test cases mapped to your project's template — titles, steps, expected results.
Review the drafts, edit as needed, and save the ones you want. They land in your chosen project and link back to the issue.

04What you get back

Template-aware drafts, not a generic shape.
A link back to the Linear issue, so the case's origin is always clear.
An AI insight on the linked issue — a plain-language summary of what it is about — shown next to the link.

Generation produces drafts for a human to review; nothing is created silently. See AI test case generation for the general flow.

05Beyond generation: results flow back

The same Linear integration also includes the QA Agent, which closes the loop in the other direction. After a test run is closed, it looks at results tied to a linked Linear issue and can send the outcome back to Linear — so the issue reflects how its coverage actually did.

It posts an AI-written summary of the linked issue's results and can move a regression back to In Progress — but only when you opt in to automatic actions.
High-risk actions, like closing an issue or filing a "Bug:" sub-issue, are always approval-gated: an admin approves them before anything changes in Linear.
It is off by default, opt-in per tenant, and needs a plan that includes AI capabilities.

See the Linear integration page and the QA Agent section of the Linear docs for the full picture.

06Related

07Frequently asked questions

Do I need to connect Linear first?

Yes. A workspace admin connects Linear once with one-click OAuth (no API token to paste). After that the integration is available across your projects.

Where do the generated test cases go?

Into the project you choose. For generation triggered from the Linear sidebar, cases land in the default project set on the Linear connection. The generated cases are drafts you review like any other test case.

Does it link the cases back to the Linear issue?

Yes. Cases generated from an issue reference that issue, so coverage traces back to the work item — and you can see an AI insight summarising how the linked issue relates.

Is this an AI feature?

Yes — test-case generation and the AI insight on a linked issue are AI-assisted and available on plans that include AI capabilities.

Does it update Linear automatically?

Only if you opt in. The QA Agent is off by default. After a run closes it can post a results summary and reopen regressions on linked issues, but those automatic actions require a separate auto-actions opt-in, and high-risk actions like closing an issue or filing a bug are always approval-gated — an admin approves them before anything reaches Linear. It needs a plan that includes AI capabilities.