From 695f75a0ef3d227b367a96ddab9522e6e38c924b Mon Sep 17 00:00:00 2001 From: Eric Date: Fri, 28 Apr 2023 16:03:01 -0500 Subject: [PATCH] Handbook: Fix broken link in Engineering page (#11432) Changes: - Fixed a relative link on the engineering handbook page. --- handbook/engineering/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/handbook/engineering/README.md b/handbook/engineering/README.md index 6a61b5b9a6..29d32421b7 100644 --- a/handbook/engineering/README.md +++ b/handbook/engineering/README.md @@ -764,7 +764,7 @@ To start a preview without starting the simulated hosts, use the `--no-hosts` fl For each bug found, please use the [bug report template](https://github.com/fleetdm/fleet/issues/new?assignees=&labels=bug%2C%3Areproduce&template=bug-report.md&title=) to create a new bug report issue. -For unreleased bugs in an active sprint, no bug report issue is created. Instead, QA moves the associated story (ignoring any technical sub-task issues) back to the "In progress" column in the appropriate project board and assigns the [engineering manager (EM)](../company/development-groups#current-product-groups). QA adds comments about the back or lack of expected functionality that was found. Fixing the bug becomes part of the story. +For unreleased bugs in an active sprint, no bug report issue is created. Instead, QA moves the associated story (ignoring any technical sub-task issues) back to the "In progress" column in the appropriate project board and assigns the [engineering manager (EM)](../company/development-groups.md#current-product-groups). QA adds comments about the back or lack of expected functionality that was found. Fixing the bug becomes part of the story. ### Bug process