Why shouldn't I mark a bug fixed when I ship the fix?

Because fixes fail, they can address the wrong cause, miss an edge case, or get undone by another change, so a shipped fix is a hope, not a fact, until confirmed. Marking it fixed prematurely leaves a potentially-still-broken bug in a false 'fixed' state. Verifying with per-version data that the issue actually stopped is what lets you close it with confidence.

How do I know if my fix worked?

Check whether the issue still occurs on the version that fixed it. If you track issues per version, you can see occurrences drop to zero on the fixed build, confirming the fix, or continue, revealing it failed. This field verification with real player data is far more reliable than assuming the fix worked because the change shipped or because it worked once on your machine.

How Do I Verify a Bug Is Actually Fixed?

Quick answer: Watch whether the issue stops occurring in reports from the version that fixed it onward. Track crashes per version so you can confirm the fix landed.

Shipping a fix isn't the same as fixing the bug, plenty of fixes don't work, or only fix part of the problem. Verifying with real data is what lets you close a bug with confidence instead of hoping. Here's how to confirm a bug is actually fixed.

Don't Assume a Shipped Fix Worked

A common trap is marking a bug fixed the moment you ship the change. But fixes fail, they address the wrong cause, miss an edge case, or get undone by another change. Until you've confirmed the bug stopped happening for real players, 'fixed' is a hope, not a fact.

Bugnet shows whether an issue continues after the fixing version, so you don't have to assume. Treating a shipped fix as unverified until the data confirms it is what keeps bugs from lingering in a false 'fixed' state.

Watch Occurrences on the Fixed Version

The way to verify is per-version: after the fix ships in, say, v1.5, watch whether the issue still occurs in reports from v1.5 and later. If occurrences drop to zero on the fixed build, the fix worked. If they continue, it didn't, and you know to reopen it.

Bugnet tracks issues per version, so you can see whether a bug keeps happening on the build that was supposed to fix it. Watching occurrences on the fixed version is the concrete test, real data from real players, rather than your assumption that the change worked.

Reopen If It's Still Happening

Verification cuts both ways: if the issue is still occurring on the fixed version, the fix failed, and catching that early, rather than assuming success, lets you address it before it lingers. A bug isn't closed until the data shows it's gone.

Bugnet surfaces continued occurrences after a fix, so a failed fix is visible rather than silently ineffective. Verifying a bug is fixed is not assuming, watching occurrences on the fixed version, and reopening if it persists, the loop that lets you close bugs with proof instead of hope.

Don't assume a shipped fix worked, watch whether the issue stops occurring on the version that fixed it. If occurrences continue, the fix failed and you reopen. Close with proof, not hope.