All posts

Engineering2 min read

How Triage reads an inbox

Triage turns bug reports into tasks without guessing. It reads, groups, files and asks.

One question first

Triage reads each new item in the inbox and asks one question before anything else: is this about something we already track? It searches open tasks by title, error text and the page the report came from before it files anything.

Group, then file

Reports that share an error and a route become one task with every report linked. The task gets a short title, the steps to reproduce when the report has them, and the deploy that was live when it started.

It asks before it guesses

When two tasks could match, Triage asks in the thread instead of picking one. Anything that changes your app waits for a person, and the owner's "Ask before" policy decides what else it checks first.

Every edit can be undone

Every edit Triage makes shows up in Activity with Undo next to it, so a wrong guess takes one click to reverse.

Get the changelog by email

One email a week, only when something ships.

RSSscaffold.llc/changelog.rss