Skip to main content
Turn Linear ticket assignment into code shipment. When a ticket gets labeled devin (or assigned to Devin), this automation reads the full ticket — title, description, acceptance criteria, comments — then implements the feature or fix with tests, and opens a pull request that references the ticket.

Use this template

Open Linear Ticket Implementation in Devin and create the automation with the default configuration. You can customize it before saving.

​
What this automation does

This template closes the loop between project management and code delivery. You keep using Linear the way you already do — the only difference is some tickets get picked up by Devin instead of a human engineer. Devin handles the same workflow: reading the spec, coding the change, writing tests, running the suite, and opening a PR ready for review.

​
How it works

Trigger: Linear event — label.added
  • Event: linear:label_added
    • Conditions:
      • addedLabel.name eq devin
What Devin does: Starts a session with full event context, executes the prompt below, and (optionally) notifies you on failure.

​
Prerequisites

​
Example prompt

The template ships with this prompt. You can edit it after clicking Use template, or leave it as-is.

​
Setting it up

  1. Open Automations → Templates in Devin.
  2. Click Linear Ticket Implementation. The create page opens with this template pre-filled.
  3. Connect any required integrations and install MCP servers if you haven’t already.
  4. Replace any placeholder values in the trigger conditions (for example, swap your-org/your-repo for your actual repo).
  5. Review the prompt and adjust it for your team’s language, conventions, and guardrails.
  6. Click Create automation.
Most automation templates include suggested ACU and invocation limits to bound cost during early rollout. Keep them as-is until you’re confident in the automation’s behavior, then raise them to fit your workload.

​
When to use this template

  • Backlogs full of small, well-defined tickets that never make it to a sprint
  • Scoping experiments: ship five variations in parallel and pick the best
  • Freeing senior engineers from ticket-shaving work
  • Asynchronous implementation for distributed teams in different time zones

​
Customization ideas

  • Use a different label (ready-for-devin, implementation-ready)
  • Route to a specific playbook that encodes implementation conventions (tests, linting, docs)
  • Scope to a specific Linear team or project
  • Chain after Bug Report Triage so triaged bugs with Clear Fix auto-implement

​
See also