commit 241caedcaced700ff52f526ad987ddea5b539446
parent 4c7c32237823f5938c41a20f6d0a9face7687a7c
Author: Marco Castelluccio <mcastelluccio@mozilla.com>
Date: Mon, 1 Dec 2025 14:33:32 +0000
Bug 1759967 - Update 'Triage for Bugzilla' docs. r=firefox-source-docs-reviewers,championshuttler DONTBUILD
Explain that:
- S1 and sec-critical bugs should be assigned within 2 business days;
- QA will set an initial severity when filing bugs;
- A comment explaining the rationale is required for any changes to severity.
Differential Revision: https://phabricator.services.mozilla.com/D274589
Diffstat:
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/docs/bug-mgmt/policies/triage-bugzilla.rst b/docs/bug-mgmt/policies/triage-bugzilla.rst
@@ -47,7 +47,7 @@ an indication that the product is getting worse not better. They should,
best-case, never hit release but be fixed in beta.
- All new S1 and sec-critical bugs should get the full attention of anyone that
- can reasonably help
+ can reasonably help. They should be assigned within 2 business days.
- All new S2 and sec-high bugs should be assigned (with caveats) and monitored
closely (weekly team meeting)
- Tracked bugs should be monitored closely (weekly team meeting)
@@ -161,6 +161,10 @@ are:
- All bugs with reviewed, but unlanded patches in your components
- All bugs with a needinfo request unanswered for more than 10 days
+Note: For bugs filed or reproduced by QA, the QA team will set an initial bug severity.
+
+Changing a bug's severity requires a comment explaining the rationale.
+
There’s a tool with these queries to help you find bugs
https://bugdash.moz.tools/ and the source is at
https://github.com/mozilla/bugdash/.
