Support

Every bug report becomes a well-labeled Linear issue with reproduction steps in under 5 minutes

A bug-intake pipeline that turns unstructured bug reports (from email, Slack, or a web form) into properly filed Linear issues with reproduction steps, severity, and affected component labels. An agent reads the report, extracts the key details, checks for duplicates, and enriches the issue with environment context and any relevant logs. The issue is created in the right Linear team and project with consistent labels, and the reporter gets a confirmation with a link to track progress. For critical bugs, it also alerts the on-call channel.

How it works

TriggerRuns when a new bug report is submitted
  1. 01
    Agent

    Extract and structure the bug report

    Read the incoming bug report and extract:
- **Title**: a concise one-line summary
- **Severity**: P0 (outage), P1 (blocking), P2 (degraded), P3 (cosmetic)
- **Reproduction steps**: what the user did, what they expected, what happened
- **Environment**: browser, OS, app version if mentioned
- **Affected component**: which part of the product (infer from the description)

Check the issue tracker for duplicates before filing.
  2. 02
    Agent

    Enrich with context and logs

    Pull any relevant context: the reporter's account tier, recent activity, error logs matching the timestamp, and related issues. Add this as supporting detail to the issue body.

    delegates to Log Investigator

    Search error logs and monitoring tools for entries matching the reported issue's timestamp, user ID, and affected component. Attach the most relevant log excerpts.

  3. 03
    Tool

    Create the Linear issue with labels

    File the issue in Linear with: structured title, severity label, component label, reproduction steps, environment details, and log excerpts. Set the appropriate team and project. If P0 or P1, set priority to Urgent.
  4. 04
    Tool

    Confirm to reporter and alert on critical bugs

    Send a confirmation reply to the reporter with the issue link. For P0 or P1 bugs, also post an alert to #oncall on Slack with the issue summary and link.
ResultEvery bug report becomes a labeled, enriched Linear issue with a confirmation back to the reporter