From 1555d09f57def72d2dfe72dced363ecae010b045 Mon Sep 17 00:00:00 2001 From: Isabell Reedy <113355639+ireedy@users.noreply.github.com> Date: Sat, 7 Oct 2023 11:18:00 -0400 Subject: [PATCH] 2023-10-05 Handbook: add process for inter-team assistance on bugs (#14235) 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> --- handbook/engineering/README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index df35137430..975185961c 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -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