From 946982918a7c70991793b4d5cc0528fa40b14009 Mon Sep 17 00:00:00 2001
From: noahtalerman <47070608+noahtalerman@users.noreply.github.com>
Date: Fri, 25 Jun 2021 17:56:31 -0400
Subject: [PATCH] In support process docs, add instruction on adding milestones
 to feature request issues (#1214)

---
 handbook/support-process.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/handbook/support-process.md b/handbook/support-process.md
index fadb4318f2..a7298cbc7e 100644
--- a/handbook/support-process.md
+++ b/handbook/support-process.md
@@ -55,6 +55,11 @@ Typically, the *questions*, *bug reports*, and *feature requests* raised by memb
 - Let's say a community member submits the feature request "I want the ability to do X in Fleet." A follow up question could be "If you were able to do X in Fleet, what's the next action you would take?" or "Why do you want to do X in Fleet?." 
 - Both of these questions provide helpful context on the underlying motivation behind the feature request when it is brought to the Roundup meeting. In addition, the community member receives a response and feels heard.
 
+#### New feature request issues
+
+After [requesting more details](#requesting-more-details), please add the milestone associated with the current time we are along the roadmap timeline. For example, if the current date is June 25, 2021, we would add the H1 2021 milestone to the issue.
+
+Feature request issues automatically include the "idea" label. The "idea" label provides the signal that this issue is an item the Fleet team would like to discuss at a later date. The time of discussion is indicated by the issue's milestones.
 
 #### Closing issues