Product feedback triage
Each weekday, turn raw Discord feedback into a deduped, triaged list of issues worth filing in Linear.
Every weekday at 10am, triage product feedback and bug reports from Discord into a short list of what's genuinely new and worth filing in Linear. 1. Read Discord. Using the Discord connection, pull messages from the last 24 hours (since the previous run) from these channels: #feedback, #bug-reports, #help. List the channels first if you're unsure of the exact names. Pick out anything that's a real bug report or product request — ignore chit-chat, thank-yous, and questions already answered in-thread. 2. Group and summarize. Cluster messages that describe the same underlying issue into one item. For each, write a one-line title, a one-sentence summary in plain language, the reporter's handle, a rough severity (blocker / bug / papercut / request), and how many separate people raised it. 3. Dedupe against Linear. For each item, search existing Linear issues (use the Linear connection — search by the key symptom and a couple of keywords, across open and recently-closed issues). If a matching issue already exists, mark it "Already tracked" with the issue ID (e.g. ENG-482) and skip it from the "new" list. Only surface items with no clear Linear match as new. Do NOT create or modify any Linear issues — this is a read-only triage. Just tell me what to file. Output, kept skimmable and under a screen: - "New — worth filing (N)": each as `severity · title — summary (xN reporters, @handle)`. Most severe first. - "Already tracked (N)": one line each, `title — ENG-123`. - "Noise": a single count of messages you skipped. If there's nothing new, say "No new feedback to file" in one line.
Feedback triage — 30 Jun 2026 New — worth filing (3) • blocker · Export to CSV times out — large workspaces (5k+ rows) get a 504 on "Export", 4 reports since Friday (x4, @dana_k) • bug · OAuth popup blank on Safari 18 — login popup loads white, must retry 2–3× (x2, @miguel.r) • request · Bulk-edit issue labels — multiple users want to relabel a filtered set in one action (x3, @priya) Already tracked (2) • Dark-mode contrast on the sidebar — ENG-482 • Slack notifications duplicated — ENG-510 Noise: 21 messages skipped (questions, thanks, off-topic).
How it works
- Attach your Discord and Linear connections — the routine reads the last day of messages from your feedback channels through Discord, and searches your existing issues through Linear.
- It clusters duplicate reports into one item, then checks each against Linear so you only see what isn't already filed — no re-triaging the same bug every morning.
- It's read-only: it never creates or edits Linear issues. You get a triaged shortlist and decide what to file. Keep "Email me the result" on to get it at 10am.
Make it yours
- Point it at the exact channels you watch (#feedback, #bug-reports, a specific support category) and adjust the lookback window.
- Tune the severity buckets or ask it to tag each item with the Linear team it belongs to.
- Want it to file the new ones for you? Tell it to create a Linear issue for anything marked "New" — it'll use the same connection, with a label so you can review.
Run “Product feedback triage” on autopilot
Copy it to your account, tweak the details, and it runs weekdays at 10:00 am.
Use this routine →More Engineering templates
Every Monday, an active-cycle progress digest from Linear grouped by status, with at-risk and carried-over issues called out and linked back.
Every Friday, scan Cloudflare's developer docs for the Workers, Pages, and security features that matter to your setup — plus recent changelog posts — emailed as a prioritized digest.
Every Monday, check Context7 for the current documented version, API, and migration notes of the libraries your project depends on — emailed as a short upgrade to-do list.
Every Thursday, ask DeepWiki what's new in the public GitHub repos you depend on — releases, breaking changes, and migration notes — emailed as a prioritized summary.