Why does it matter if a crash is new or old?

Because it changes how you treat it. A crash that's new on your latest build is usually a regression, fresh damage that update caused, which deserves fast attention and can often be fixed by examining what changed. An old crash that's persisted for many versions is a known issue you prioritize on impact like any backlog item. Telling them apart keeps you from mistaking a long-standing bug for a new fire, or vice versa.

How do I know if a crash is a regression?

It shows up as a crash that's new specifically on your latest version, absent before, present after the update. Per-version crash tracking surfaces these as new issues on the latest build, flagging them as regressions that release introduced. That points you at what changed in the update, so you can fix the regression fast, often before it spreads to many players.

How Do I Tell If a Crash Is New or Old?

Quick answer: Check when the crash was first seen and on which version. Per-version tracking tells you whether a crash is new on the latest build or a long-standing issue.

Telling whether a crash is new or old changes how you treat it, a brand-new crash on the latest build is likely a regression to fix fast, while a long-standing one is a known quantity. Here's how to tell a crash's age and why it matters.

Check When It Was First Seen

A crash's age comes down to when it first appeared. If you're tracking crashes over time and by version, each grouped issue has a first-seen point, so you can tell whether it just showed up or has been around for many builds. That first-seen data is the key to a crash's age.

Bugnet groups crashes by signature and tracks them over time and per version, so each issue carries its history. Telling if a crash is new or old is reading that history, a crash with a recent first-seen on the latest build is new; one stretching back many versions is old.

New on the Latest Build Means Regression

A crash that's new specifically on your latest version is usually a regression, that update introduced it. These deserve fast attention, because they're fresh damage you caused and can often fix by examining what changed in the release. Identifying them quickly limits how many players they hit.

Bugnet surfaces new issues a release introduces, so regressions stand out as crashes new on the latest build. Telling that a crash is new (a regression) versus old lets you prioritize, fresh regressions often jump the queue because they're both fixable and recently introduced.

Old Crashes Are Known Quantities

A crash that's been around for many versions is an old, known issue, not something your latest update broke. These you can prioritize on impact like any other backlog item, rather than treating them as urgent regressions. Knowing a crash is old prevents you from mistaking it for a new fire.

Bugnet's per-version history shows a crash's lifespan, so you can tell a long-standing issue from a fresh one. Telling if a crash is new or old is checking when it was first seen, treating new-on-latest as a regression, and recognizing old ones as known quantities to prioritize on impact.

Check when the crash was first seen and on which version, new on the latest build means a regression to fix fast, while an old crash spanning many versions is a known quantity. Per-version history tells you.