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 114

2023-10-05 Handbook: add process for inter-team assistance on bugs (#14235)

Browse source 
1. Process to formalize how we prioritize bugs across teams, recognize a
bug's origin, and indicate the team who is currently working on it.
2. Formalize that this coordination will happen at a joint sprint
kick-off review (there are currently separate sprint kick-off reviews
for each team).

---------

Co-authored-by: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
This commit is contained in:
Isabell Reedy 2023-10-07 11:18:00 -04:00 committed by GitHub
parent e9c7d50a2f
commit 1555d09f57
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

11
handbook/engineering/README.md
View file

@ -632,6 +632,17 @@ If the bug does not meet the criteria of a critical bug, the EM will determine i
When fixing the bug, if the proposed solution requires changes that would affect the user experience (UI, API, or CLI), notify the EM and PM to align on the acceptability of the change.
Engineering teams coordinate on bug fixes with the product team during the joint sprint kick-off review. If one team is at capacity and a bug needs attention, another team can step in to assist by following these steps:
For MDM support on CX bugs:
- Remove the `#g-cx` label and add `#g-mdm` label.
- Add `~assisting g-cx` to clarify the bug’s origin.
For CX support on MDM bugs:
- Remove the `#g-mdm` label and add `#g-cx` label.
- Add `~assisting g-mdm` to clarify the bug’s origin.
Fleet [always prioritizes bugs](https://fleetdm.com/handbook/product#prioritizing-improvements) into a release within six weeks. If a bug is not prioritized in the current release, and it is not prioritized in the next release, it is removed from the "Sprint backlog" and placed back in the "Product drafting" column with the `:product` label. Product will determine if the bug should be closed as accepted behavior, or if further drafting is necessary.
#### Awaiting QA