From b7e8af2dd93b60fe1accb5188a7199176508b302 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Mon, 27 Jan 2025 18:17:24 -0500
Subject: [PATCH] Handhook: How to get feature requests, that already have
 issues, into the prioritization flow (#25780)

---
 handbook/company/product-groups.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/handbook/company/product-groups.md b/handbook/company/product-groups.md
index 144e0bd858..65bf403d36 100644
--- a/handbook/company/product-groups.md
+++ b/handbook/company/product-groups.md
@@ -369,7 +369,7 @@ Anyone in the company is invited to submit requests or simply listen in on the 
 
 ### Making a request
 
-To make a feature request or advocate for a feature request from a customer or community member, [create an issue](https://github.com/fleetdm/fleet/issues/new/choose) using the feature request template.
+To make a feature request or advocate for a feature request from a customer or community member, [create an issue](https://github.com/fleetdm/fleet/issues/new/choose) using the feature request template. If you found that an issue already exists, add the `:product` label to it.
 
 New requests are reviewed daily by the Head of Product Design and a former IT admin during the ["Unpacking the why"](https://fleetdm.com/handbook/product-design#unpacking-the-why) call. If the request meets the [criteria for prioritization](#criteria-for-prioritization), the request will be added to the upcoming feature fest (`~feature fest` label). If it doesn't, the request will be put to the side and the requester will be notified.