Automated Linear Triage Inbox Routing
Every hour, WebRun opens Linear, reads each issue still sitting in triage, works out the likely team, label and priority from its description, mirrors the queue onto a Trello board, and pings the on-duty engineer in Microsoft Teams so nothing sits unaccepted for a day.
How do I keep the Linear triage inbox from piling up?
WebRun sweeps the Linear triage inbox every hour, reading each unaccepted issue and suggesting the team, label and priority that fit. It mirrors the queue onto a Trello board and posts the on-duty engineer a Microsoft Teams list led by the longest waiting item, so triage never sits idle for a day.
- No triage issue waits a full day unaccepted
- Every incoming issue arrives with a suggested team and label
- The oldest waiting item is always at the top of the queue
Built for engineering teams · on-call engineers · product managers · startups
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
linear.app/loginin a real browser with your saved login - no setup, no API keys. -
1
Linear - read the triage inbox
WebRun opens Linear to read the triage inbox. - Open Linear and go to the triage inbox
- Read each unaccepted issue with its title, description, and reporter
- Suggest the team, label, and priority that fit based on the wording and any linked project
- Note how long each issue has been waiting and skip ones already accepted or assigned
Done when Every issue in triage has a suggested team, label, priority, and an age.
-
2
Trello - mirror the triage queue
WebRun opens Trello to mirror the triage queue. - Create a card per triage issue on your triage board
- Put the suggested team and label on the card and the priority in the title
- Move cards to Accepted when the matching Linear issue leaves triage
- Archive cards for issues that were closed or marked duplicate
Done when The Trello board mirrors the live Linear triage inbox.
-
3
Microsoft Teams - ping the on-duty engineer
WebRun opens Microsoft Teams to ping the on-duty engineer. - Post the current triage queue to your engineering channel
- Lead with anything waiting longer than four hours
- Give each line the suggested team, label, and a one-line summary
- Leave accepting and assigning to the engineer. WebRun suggests but never changes an issue
Done when The on-duty engineer has the hour's triage queue in Teams.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Will it assign or accept issues by itself?
No. WebRun suggests a team, label and priority and leaves the issue exactly as it found it. Accepting, assigning, and editing stay with the engineer on duty.
How does it guess the right team?
It reads the issue title, description, reporter, and any linked project, then matches them against how your existing issues are labelled and routed. You can correct a suggestion any time.
Does it message the person who reported the issue?
No. WebRun posts only to your internal Teams channel and your own Trello board. Nobody outside your workspace is contacted.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.