Removing Bug Hunter-set Severity

We've removed a feature today: bug hunters no longer set a Severity.

If a program has AI triage enabled, Bugbot now assigns severity automatically based on the program's scope and historical reports.

Why the change?

In every discovery call we've done, program runners said the same thing: take hunter-assigned severities with a grain of salt. Some bugs need a "drop everything" response, others can wait until Monday. But that call is never based on what the hunter chose. And why would it be? Bug hunters are incentivised to go high.

Bugbot isn't perfect, but it's already more consistent. It's more aligned with the program's expectations than hunter-submitted severities.

We only added the field originally because "that's how reports are usually done." But in the age of AI, collecting inputs we can reliably infer just creates friction. So we're cutting it.

In the age of AI, collecting inputs we can reliably infer just creates friction. So we're cutting it.

How do you handle severity in your program?

We'd love to hear how other programs approach severity classification. Are you relying on hunter submissions, internal triage, or something else entirely?