- New bugs wait in Triage until someone decides which team owns them. This template makes that first call.
Workflow template · Engineering

Give every new bug an owner
Clear matches move on their own. Unclear ones go to a person.


Issue create
Read Linear routing teams
Choose owning team
Move confidently routed bug
Request routing review
- When an issue labelled bug is created in Triage, OAIZ reads your Linear teams and their descriptions.
- An LLM Call picks the owning team, with a confidence score and a reason. It only chooses from teams Linear returned.
- Above 0.8, the issue moves to that team. Anything else goes to Slack, so a person decides.
A bug lands in Triage
An owner, with a confidence score
Moved, or checked by a person
Issue create
Read Linear routing teams
Choose owning team
Move confidently routed bug
Request routing review
Starts on
Issue create
Issue createState is Triage
Labels include bug
Then Linear · List Teams
Example result
Team: CHK
Confidence: 0.92
Reason: the bug is in discount codes, which the Checkout team owns
Above 0.8: Linear · Save Issue moves the bug
0.8 or below: Slack · Send Message asks for review
#bug-triageRouting review needed for ENG-311: Search returns no results Suggested team: WEB Confidence: 0.6 Search and Storefront both fit.
- Give each Linear team a short description. Without them, bugs go to Slack for review.
- Before you go live, connect Linear and Slack, choose the channel, and match the label and state to your setup.
- Then test it with Run workflow, and choose Go live.
Before you go live
Describe each Linear team
Connect Linear
Connect SlackChoose the Slack channel
Match the label and state
Run workflow
Not liveLiveGo live