From db1dab56eb00d8801444d199baf0454a931a12b7 Mon Sep 17 00:00:00 2001 From: Rachael Shaw Date: Tue, 5 Aug 2025 11:07:55 -0500 Subject: [PATCH] Handbook: Update section about actions taken when a bug is in drafting (#31482) --- handbook/company/product-groups.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index 6cce9309a4..ff8120e7b3 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -514,9 +514,17 @@ Remove the “:reproduce” label, add the following labels: #### In product drafting -After reproduction, all released bugs go through drafting to validate that it is not expected behavior, it requires a code change to fix, and the bug report is fully populated. +After reproduction, all released bugs go through drafting to validate that it is not expected behavior, it requires a code change to fix, and the bug report is fully populated. During drafting, product design will take one of the following actions: -It will stay in this state until product design closes the bug, updates it to a feature request by removing all bug labels and leaving the issue in the "New requests" column, assigns it to a non-engineering team, or moves it to the "Ready to estimate" column of the drafting board for engineering review and estimation. ++ Prepare for engineering review and estimation + - Specify a fix or a timebox + - Update the issue title, if it no longer matches our understanding of the issue + - Move it to the "Ready to estimate" column of the drafting board ++ Convert to a feature request + - Remove all bug labels + - Leave the issue in the "New requests" column ++ Assign to a non-engineering team ++ Close, if determined to be expected behavior If a bug meets the criteria for a [critical bug](https://fleetdm.com/handbook/company/product-groups#release-testing), the `~critical bug` label is added, and product design follows the [critical bug notification process](https://fleetdm.com/handbook/company/product-groups#notify-the-community-about-a-critical-bug).