Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 08:58:41 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 111

Added bug prioritization section to handbook (#38476)

Browse source
This commit is contained in:
Victor Lyuboslavsky 2026-01-19 14:17:06 -05:00 committed by GitHub
parent c5c901a063
commit d63288588b
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -986,6 +986,15 @@ At sprint kickoff, the EM or TL may assign planned issues to specific contributo
- Help complete sub-issues for active user stories.
4. **Look ahead when sprint work is done.** If all sprint work is complete or blocked, check the team's drafting board for issues in the "Estimated" column. Prioritize unreleased bugs over released bugs.
#### Bug prioritization
When selecting which bug to work on next, prioritize in the following order:
1. **P0, P1, P2 bugs**: High-priority bugs take precedence over all other bugs.
2. **Customer bugs**: Bugs with a `customer-` label are prioritized because they directly impact customers.
3. **Flaky tests**: Flaky tests impact engineering velocity and should be addressed promptly.
4. **Dogfood issues**: Bugs with the `~dogfood` label are prioritized because we have the best context for reproducing and fixing them.
5. **Oldest bugs**: Among remaining bugs, work on the oldest first.
## Outside contributions