Most teams triage in a weekly meeting. Someone shares a screen, the inbox scrolls by, and eight people watch one person drag reports into columns. By the time a bug is sorted it is a week old, and the customer who reported it has stopped waiting.
Keel 4.12, out since Tuesday, moves that work to the moment a report arrives. Every new issue in the triage inbox comes with a suggested label, priority and owner. Nothing changes until someone accepts it. Press 1 to take the suggestion, 2 to change it first, or 3 to decline the report.
What Assist looks at
Assist reads the report, the last 90 days of your workspace and nothing else. It does not train on your issues, and no other workspace's data is involved in a suggestion. Three signals carry most of the weight:
- Who touched the code last. If a report mentions checkout and Ana changed
checkout.tsnine times this month, she is the likely owner. - How many people asked. Forty-one reports about the same coupon bug make it urgent; one report about a typo does not.
- What it repeats. A report that reads like a closed issue is linked to it instead of filed again.
Triage · 3 new1 accept
- Coupon field keeps the pay button disabledBug!AM
- Allow PDF invoices per teamFeatureRD
- Typo in the welcome emailPolishJK
Why it never acts alone
In the first beta, Assist applied its suggestions directly and let you undo them. Acceptance looked great on paper: 84% of suggestions were never undone. Then we watched people use it. They were not agreeing with Assist; they were not noticing it. Priorities drifted, and two teams found an urgent bug sitting in Low a week later.
“The moment the tool decides for you, you stop reading the report. We wanted people to read the report.”
So suggestions stay suggestions. A dashed outline shows what Assist proposes, one key accepts it, and the issue history records who accepted what. In the final beta, people accepted 71% of suggestions and changed 23%, and the changed ones were exactly the cases where a human knew something the report did not say.
Habits that make it work
- Triage little and often. Teams that clear the inbox daily spend 6 minutes on it; teams that batch it weekly spend 50.
- Rotate the owner. One person per cycle owns the inbox. The others do not look at it.
- Close with a reason. “Won’t fix” with one sentence saves the next person from filing it again.
We still have a triage meeting at Keel. It lasts ten minutes, happens on Monday, and covers only the reports someone flagged as “needs a conversation”. Everything else was handled the day it arrived.