Organize · Bug intake

A bug form that triages itself

Reporters answer a few structured questions. Subo weighs severity against frequency, computes a triage priority on the spot, and shows it back to them, so the important bugs surface the moment they land.

Use this template Build it with the API
Organize GamersBusinesses Calculated fieldAuto-priority scoringSkip logicAnswer piping
What it showcases

Features most survey bots don't have

🧮

It computes priority

Severity and frequency are weighted, and a calculated field derives a HIGH, MEDIUM or LOW triage priority automatically. No human does the first pass.

📨

Reporters see the result

The computed priority is echoed back to the reporter, so they know a bad crash was taken seriously the instant they submit.

🔁

Repro steps only when needed

Skip logic asks for reproduction steps only from reporters who say the bug reproduces, keeping the form short for everyone else.

🗂️

Structured, not a chat blob

Summary, area, severity, frequency, platform and steps come back as fields, so your team reads a triaged queue instead of scrolling a channel.

Worked example This template comes with a a game's #report-a-bug channel example so you can see exactly how it plays. Edit the questions and content to make it your own.

A #bugs channel is a scroll of half-formed reports someone has to triage by hand. This form captures what your team needs to reproduce and prioritize, then does the first pass of triage itself, before a human ever reads it.

Use it as your community’s front door for bugs: a #report-a-bug channel, a QA intake during a beta, or a support form. It asks for a one-line summary, the affected area, severity, frequency, whether it reproduces, and platform, then computes a priority and shows it back to the reporter.

It prioritizes for you

Severity and frequency are weighted, and a calculated field turns them into a HIGH, MEDIUM or LOW priority on the spot. A crash that happens every session outranks a cosmetic glitch nobody hits, with no human doing the sorting. The reporter sees the priority echoed back, so they know a serious bug was heard, and your team starts the day with an already-triaged queue.

The example runs as a game’s #report-a-bug intake. Rename the areas and severity levels and it becomes a support form for any product.

Variants

  • Support ticket intake: rename the areas to product surfaces and route HIGH priority to a dedicated channel.
  • Beta QA form: run it during a playtest to catch and rank issues before launch.
  • Feature request board: repurpose the scoring to rank incoming requests by impact and reach.
  • Crash-only fast lane: trim to severity, platform, and repro steps for a rapid crash report.
How to run it

Live in a few minutes

  1. 1

    Clone and set your areas

    Swap in the parts of your game or product a bug could hit (UI, gameplay, performance, and so on) as the affected-area options.

  2. 2

    Keep or tune the weights

    Severity and frequency carry scoring weights that feed the priority. Leave the defaults for standard triage, or adjust the thresholds to your team's bar.

  3. 3

    Publish as your intake

    Point a #report-a-bug channel, a beta QA form, or a support flow at it. Reporters answer in Discord or on the web.

  4. 4

    Work the triaged queue

    Every report arrives with a priority already computed, so your team starts with the HIGH ones instead of triaging by hand.

FAQ

Common questions

How is the priority calculated?

Severity and frequency each carry a weight. Subo adds them into a score, and a calculated field maps that score to HIGH, MEDIUM or LOW using simple if/then/else rules you can edit.

Can I change the priority thresholds?

Yes. The calculated field is just a formula over the score, so you can move where MEDIUM becomes HIGH or add tiers to match how your team works.

What are calculated fields?

They derive a new value from earlier answers, like turning severity and frequency into a priority label. Almost nobody discovers this feature on their own, which is exactly why this template shows it off.

Does it work for support tickets, not just game bugs?

Yes. It's a self-triaging issue intake for any product or SaaS team. Rename the areas and severity levels and it becomes a support-ticket form.

More templates

Keep exploring

Let demand rank your roadmap

Decide what to build next with data. Members sort every candidate feature into Must, Should, Could or Won't have, cast one 'ship this first' vote, and tell you what's missing.

A community vote people can answer honestly

Put a decision to your community with an anonymous vote, then capture the reasoning behind every For and Against. Decide on more than a tally.

A roadmap vote that asks why, not just what

Let your community vote on what you build next, then ask why. The follow-up adapts to the vote, so you learn not just what people want but the reason behind it.

Use this template

Clone it into your community, swap in your content, and share it. No building from scratch.

Use this template Browse survey recipes