Create doc & flowchart for Nightly crash triage criteria
Categories
(Firefox for Android :: Crash Reporting, task, P3)
Tracking
()
People
(Reporter: jmahon, Assigned: boek)
Details
We receive crash reports in Nightly that our crash monitors are responsible for triaging, but different people have different standards for what is worth escalating or deferring.
We should come up with agreed-upon documentation that outlines general criteria to help guide people monitoring crash reports to help triage crashes more consistently and effectively. In addition to the triage criteria, this documentation should help monitors understand what to do with crashes that do need escalation (e.g., add them to a board? Assign them to an owner directly? Raise in an incident? etc)
Might be helpful to include a flowchart-like visualization in this document to help guide peoples' decisions.
|
||
Comment 1•2 years ago
|
||
We have some existing rules about high-volume nightly crashes (see here), but we haven't reviewed them in a while. For other types of crashes, such as security-sensitive ones or low-volume-but-high-impact ones, we've been relying on the triagers' personal experience. Putting that experience in written form and agreeing on a policy would be a very nice improvement.
Description
•