Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 01:18:42 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 59

Handbook: Update section about actions taken when a bug is in drafting (#31482)

Browse source
This commit is contained in:
Rachael Shaw 2025-08-05 11:07:55 -05:00 committed by GitHub
parent 893563777b
commit db1dab56eb
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 10 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
handbook/company/product-groups.md
View file

@ -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).