On crash-stats and other WebEng websites we normally file the bug with a link to Sentry, which also gives us how often the crash is happening, a whole lot of metadata, and the ability to replay the request generating the crash. NewRelic has similar functionality. The only bugzilla feature we use to provide metadata about the bug is component. This doesn't tell us much, though, since 5xx's tend to all get filed "webapp". Blocking bugs are filed later if the error originates in another component.
----- Original Message -----
> From: "Maris Fogels" <
ma...@mozilla.com>
> To:
mozilla-d...@lists.mozilla.org
> Sent: Friday, May 30, 2014 9:15:21 AM
> Subject: [webdev] How do you triage website crash bugs?
>
> Hi everyone,
>
> I'm working to standardize the way we report website crash bugs on MDN,
> and I was wondering what other Mozilla web properties do to triage their
> crashes (HTTP 5XX errors). If possible, I'd like to reuse practices
> other Mozilla website projects for MDN.
>
> Here are some specific questions a bug triager might ask that I'd like
> to standardize on our site:
>
> * How do you indicate that a bug involves a server-side error?
> * How do you indicate if a website crash bug is reproducible or not?
> * How do you indicate if a website crash bug has a stacktrace?
> * How do you indicate that a website crash bug is 'complete', ready
> for a developer to investigate?
>
> How do you triage website crash bugs like these in your project?
>
>