What's the difference between upvotes and impact data for prioritization?

Upvotes reflect what your vocal, engaged community wants prioritized, a sentiment signal capturing desire. Impact data reflects how many players each issue actually affects, including the silent majority who never vote, capturing objective reach. Upvotes tell you how much players want a fix; impact data tells you how many are affected. Each has a blind spot, so you combine them rather than prioritizing on votes alone.

Should I prioritize bugs by player upvotes?

Use upvotes as one signal, not the only one. Upvotes reflect your vocal, engaged players, not your whole base, so a crash silently hitting thousands of casual players who never vote can get fewer upvotes than a minor issue a vocal group fixates on. Combine upvotes (desire) with impact data (how many players are actually affected) so you don't miss silent, widespread problems that voting alone would under-prioritize.

Why isn't player voting enough to prioritize bugs?

Because voting is biased toward the vocal minority, the players engaged enough to visit your tracker and vote, while missing the silent majority who just churn without voting. A widespread crash hitting thousands of casual players might get zero upvotes because those players never engage with your tracker, even though it's your biggest problem. Impact data captures that silent reach, so combining it with upvotes gives a complete picture that votes alone can't.

Upvotes vs Impact Data for Prioritization

Quick answer: Upvotes reflect what vocal players want; impact data reflects how many players are actually affected, including the silent majority. Combine both, don't prioritize on votes alone.

When prioritizing what to fix, you can lean on player upvotes or on impact data, and they tell you different things. Relying on either alone leads to blind spots. Here's how they compare and why you want both.

What Upvotes Tell You

Upvotes (players voting on issues) tell you what your vocal, engaged community wants prioritized. They're a useful sentiment signal: a heavily-upvoted issue is something your active players care about, and voting reduces duplicate reports. Upvotes capture desire and community demand directly from players.

But upvotes are biased toward the vocal. They reflect the players engaged enough to visit your tracker and vote, not your whole base. Bugnet supports upvotes for this community signal, but they're one input, not the full picture, because they systematically miss the silent majority.

What Impact Data Tells You

Impact data, how many players each issue actually affects, tells you reach from your whole player base, including the silent majority who never vote. A crash silently hitting thousands of casual players shows up in impact data even though it got zero upvotes, because those players never visited your tracker.

Bugnet's crash capture and occurrence counts reveal this silent impact that votes can't see. Impact data captures objective reach, but not desire, it tells you how many are affected, not how much players want a fix, which is where upvotes add something impact data lacks.

Why You Combine Both

They capture different things, desire (upvotes) and reach (impact data), and each has a blind spot. Upvotes miss silent widespread problems; impact data misses how much players want a particular change. Combining them gives the full picture: where they agree, you have a clear priority; where they diverge, you decide with both signals.

Bugnet gives you both the upvotes and the real occurrence data, so you weigh community voice against measured reach. So don't prioritize on upvotes alone, they over-weight the vocal and miss silent problems, combine them with impact data so your priorities reflect both what players want and what actually affects the most players.

Upvotes reflect what vocal players want (desire); impact data reflects how many are actually affected, including the silent majority (reach). Each has a blind spot, combine both rather than prioritizing on votes alone.