All posts
Product

How to turn a Linear ticket into a live preview link

To get a preview link from a Linear ticket, connect Linear to Ensemble and pick a trigger: assign the issue to Ensemble, add a label, or move it to a workflow state. Ensemble creates a branch, an AI agent makes the change, and the URL of a running preview is posted back on the issue. Linear stays your tracker.

4 min read

Why a ticket isn't enough

A ticket describes a change. It can't show one.

For most teams, the path from a Linear ticket to something a PM can click looks like this: the ticket waits for an engineer, the engineer builds it on a branch, the branch waits for staging or a screen-share, and only then does the person who wrote the ticket see whether it's what they meant. If it isn't, the loop starts again.

The slow part isn't writing code. It's that the running version of the change only exists on one laptop. Connecting Linear to preview environments moves it off the laptop: every qualifying ticket gets its own running copy of the app, at a URL anyone with access can open.

How to connect Linear to preview environments

Connecting Linear takes one setup step, after which tickets start previews on their own.

1. Connect Linear

In your Ensemble workspace settings, connect Linear and choose the Linear team. Ensemble joins as a Linear user, so it can be assigned issues and comment on them.

2. Pick a trigger

Decide which tickets should get a preview. Use any combination of:

  • Assigned to Ensemble. Assign an issue to the Ensemble user when it's ready.
  • A label. For example, ensemble or preview. Adding the label starts the work.
  • A workflow state. For example, when an issue moves to "Ready."

Most teams start with a label, because it's explicit and easy to undo.

3. Skip big tickets (optional)

Set a complexity gate to skip issues estimated above a certain number of points. Large tickets usually need an engineer's design first; small and medium ones are where this workflow shines.

4. Write or move a ticket

Write the ticket as a clear spec. The five-part format in how to write a spec for an AI coding agent works well: feature, user, change, what must not change, and how you'll check it. Then add the label, assign it, or move it.

Ensemble comments on the issue when the preview is starting and again when it's live, with the URL. Open it, sign in, and try the change.

Ensemble turns the ticket into a branch, runs the change on a full preview of your app, and reports back on the ticket.

Nothing is installed on anyone's laptop. The preview runs the services, databases and seed data your team declared for the project, so the change runs against realistic data from the first load.

From there, you can keep going in Ensemble Studio: open the preview beside a chat, ask for adjustments ("move the toggle above the plan list"), and watch the preview reload. The ticket, the branch and the preview stay linked, so anyone who finds the ticket later can find the running version of the change.

What the reviewer receives

The reviewer gets a link to a running, seeded copy of the app for that ticket, and doesn't need the repo.

Workspace members open the link directly. People outside the workspace, such as a client, a customer success rep or an executive, get an expiring share link that works without an Ensemble account. Reviewers don't need a paid seat. How to review a pull request without running it locally covers access in detail.

Where the pull request goes

The pull request opens into your existing GitHub repo and pipeline, and Ensemble doesn't merge anything.

Your CI runs as usual. An engineer reviews the code, with the preview link in hand, so they can click the change before reading the diff. Branch protection rules decide what merges. When the branch merges, its preview is removed.

Does this replace Linear?

No. Linear stays the tracker for prioritization, cycles and status. Ensemble is the path from a ticket to something people can run.

That split matters. Teams have spent years tuning their Linear workflows, and a tool that asks them to move the backlog somewhere else is a hard sell. Ensemble only asks for a trigger. See Ensemble for Linear for the integration summary.

FAQ

Does every Linear ticket get a preview environment?

Only tickets that match your trigger: assigned to Ensemble, a chosen label, or a chosen workflow state. You decide which tickets qualify, and you can skip tickets above a size estimate.

Do engineers have to use the Ensemble UI?

No. Engineers can keep using their own editor and agent. The preview URL is how everyone sees the work, engineers included: they can click the change before reading the diff.

What if the ticket is vague?

Write the ticket so it says which behavior changes, for whom, and what must stay the same. A five-line spec is enough.

Do reviewers need a paid seat?

No. People who only open the link are free. Builder seats are for people who chat, edit or create previews.

Does Ensemble work with Jira?

Not at launch. Linear is the first tracker integration.


Ensemble turns every change into a running copy of your real app, with its services and data, at a private link anyone on the team can open. What is Ensemble?

Stop shipping the hard way

Agents write the code. Ensemble runs it. Everyone clicks it: product people in the browser, agents in parallel, engineers deciding what merges.

Start free