Don't set severity automatically on crash bugs to prevent them skipping triage
Categories
(bugzilla.mozilla.org :: Bug Creation/Editing, enhancement)
Tracking
()
People
(Reporter: bryce, Assigned: suhaib)
References
(Regression)
Details
Attachments
(1 file)
Bug 1690202 means that we automatically set S2 on bugs with the crash
keyword. This makes sense from the perspective of us treating crashes seriously. However, it can result in such bugs not appearing in triage queues. This is because triage tools such as Triage Center and some triage queries will treat any bug with a severity or priority as triaged.
This can result in the opposite to intended outcome where teams fail to action higher severity issues because they slip the net.
We could also consider alternatives, like more aggressive nagging on such bugs.
Thanks for the heads-up; I agree this is problematic!
This change was part of a set of changes implemented to help triage.
As the driver for these changes is on extended leave I'll see if I can find someone else to make the call here.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Even if we are going to change the triage center to consider the "triaged" keyword instead of the severity being set or not, I still think it would be valuable not to set severity by default for crashes, as the severity depends on the volume of the crash.
Comment 3•2 years ago
|
||
Another option could be to add support in Socorro to file bugs with a pre-filled severity based on the crash volume.
Comment 4•2 years ago
|
||
Given the last few months focus on S2 bugs, we have noticed that this is necessary to avoid increasing S2 numbers in the wrong way (even small volume crashes staying at S2 severity).
Assignee | ||
Comment 5•2 years ago
|
||
Comment 6•2 years ago
|
||
Updated•2 years ago
|
Description
•