From ec34f2f9da707699172721802dc215dde529791a Mon Sep 17 00:00:00 2001 From: Mo Zhu Date: Mon, 20 Mar 2023 15:44:08 -0700 Subject: [PATCH] Clarify role of main description vs. comments in github issue (#10613) --- handbook/product/README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/handbook/product/README.md b/handbook/product/README.md index 5654a2006e..3bd8987ef7 100644 --- a/handbook/product/README.md +++ b/handbook/product/README.md @@ -40,6 +40,8 @@ Look here for more information about [Using Figma](https://fleetdm.com/handbook/ * During the product huddle meeting, record and address any feedback on the draft. +> As drafting occurs, inevitably, the requirements will change. The main description of the issue should be the single source of truth for the problem to be solved and the required outcome. The product manager is responsible for keeping the main description of the issue up-to-date. Comments and other items can and should be kept in the issue for historical record-keeping. + ### Deliver * Once your work is complete and all feedback is addressed, make sure that the issue is updated with