diff --git a/.github/ISSUE_TEMPLATE/bug-report.md b/.github/ISSUE_TEMPLATE/bug-report.md index e621a9680f..aee03bb3d9 100644 --- a/.github/ISSUE_TEMPLATE/bug-report.md +++ b/.github/ISSUE_TEMPLATE/bug-report.md @@ -19,8 +19,8 @@ assignees: '' TODO -### 🛠️ To fix - +### 🛠️ Expected behavior + TODO ### 🧑‍💻  Steps to reproduce diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md index aed97eb386..82043568b3 100644 --- a/handbook/company/product-groups.md +++ b/handbook/company/product-groups.md @@ -675,7 +675,7 @@ Quickly confirming and reproducing bug reports is a [priority for Fleet](https:/ At this state, the Head of Product Design is responsible for going through the inbox and adding the correct product group label (e.g. `#g-mdm`, `#g-orchestration`, `#g-software`, `#g-security-compliance`). -Then, it's the product group Product Designer's responsibility to decide if it's a bug, make sure reproduction steps are documented, and update the bug's title to focus on the expected behavior instead of what's broken. +Then, it's the product group Product Designer's responsibility to decide if it's a bug, specify the expected behavior, and make sure reproduction steps are documented. If the expected behavior is unclear, ask the product group's Tech Lead for help. If reproduction steps are missing, add them, ask for more reproduction details from the reporter, or ask the QA team for help with reproduction. The Product Designer has **1 business day** to move the bug to the next step ([needs reproduction](#needs-reproduction) or [reproduced](#reproduced)) or request more information.