From a62cf135bde143ae1315bb40bc3351a12bce7fc7 Mon Sep 17 00:00:00 2001 From: Tim Lee Date: Thu, 28 Aug 2025 13:39:39 -0600 Subject: [PATCH] Clarify bug triage process for website bugs (#32424) --- handbook/company/product-groups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index 79fcef043c..12287738a4 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -534,7 +534,7 @@ You can read our guide to diagnosing issues in Fleet on the [debugging page](htt #### Inbox -Quickly reproducing bug reports is a [priority for Fleet](https://fleetdm.com/handbook/company/why-this-way#why-make-it-obvious-when-stuff-breaks). When a new bug is created using the [bug report form](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=bug%2C%3Areproduce&template=bug-report.md&title=), it is in the "inbox" state. +Quickly reproducing bug reports is a [priority for Fleet](https://fleetdm.com/handbook/company/why-this-way#why-make-it-obvious-when-stuff-breaks). When a new bug is created using the [bug report form](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=bug%2C%3Areproduce&template=bug-report.md&title=), it is in the "inbox" state. Website bugs (label: `#g-website`) are triaged by the [website group](https://fleetdm.com/handbook/company/product-groups#website-group). At this state, the bug review DRI (QA) is responsible for going through the inbox and documenting reproduction steps, asking for more reproduction details from the reporter, or asking the product team for more guidance. QA has **1 business day** to move the bug to the next step (reproduced) or request more information.