Skip to main content
Apply a Bug label in Linear and an engineer shows up to investigate — except the engineer is Devin. This template listens for Linear’s label-added events, fires a triage session that pulls the ticket context, searches your repos for relevant code paths, correlates recent git history, and comments the findings directly back on the ticket.

Use this template

Open Bug Report Triage in Devin and create the automation with the default configuration. You can customize it before saving.
Looking for a hands-on walkthrough? See the step-by-step tutorial for Bug Report Triage.

​
What this automation does

The Bug Report Triage automation turns your Linear workflow into a fully-automated triage pipeline. You don’t change how you file bugs — you just keep adding labels the same way. Devin handles the investigation work that used to eat up a senior engineer’s morning: reading the description, searching the codebase for validateEmail, checking git log for recent changes, and summarizing the likely root cause.

​
How it works

Trigger: Linear event — label.added
  • Event: linear:label_added
    • Conditions:
      • addedLabel.name eq bug
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 Bug Report Triage. 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

  • Engineering teams drowning in bug reports during rollouts or launches
  • Support-originated tickets that need codebase context before a human can act
  • Reducing triage load on senior engineers and tech leads
  • Building baseline investigation reports before assigning to a specific owner

​
Customization ideas

  • Match a different label (Needs Triage, Customer Reported, etc.)
  • Scope to a specific Linear team or project
  • Attach a triage playbook that codifies your team’s investigation steps
  • Chain with Linear Ticket Implementation for Clear Fix tickets

​
See also