From 16d1ba80b7783dd4b7c45f3e6b2f57c09b32c6b3 Mon Sep 17 00:00:00 2001
From: Mo Zhu <mo@fleetdm.com>
Date: Fri, 21 Oct 2022 07:09:54 -0700
Subject: [PATCH] Update new feature work template (#8382)

- Update the issue template
---
 .github/ISSUE_TEMPLATE/new-feature-work.md | 73 +++++++++++++++++-----
 1 file changed, 57 insertions(+), 16 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/new-feature-work.md b/.github/ISSUE_TEMPLATE/new-feature-work.md
index a6b0edc1fc..13c68ab5eb 100644
--- a/.github/ISSUE_TEMPLATE/new-feature-work.md
+++ b/.github/ISSUE_TEMPLATE/new-feature-work.md
@@ -2,38 +2,79 @@
 name: 🎟  New feature work
 about: Specify a planned, new feature in Fleet so that engineering can provide an estimation on the time required for implementation.
 title: ''
-labels: 'needs estimation'
+labels: 'epic'
 assignees: ''
 
 ---
 
-### Goal
+## Problem
 
 TODO
-<!-- Insert the user story or high level business goal. This link is located in the 🧩 Product google document linked here: https://docs.google.com/document/d/10B4eDXHjM9lFob6VcBDFEzYR424QRH3EuTpRLbhWyzM/edit# -->
+<!-- 
+Motivate this feature by describing what is the user's problem. 
+- Who are the affected users? 
+- What is the current situation? Why does the current situation hurt? 
+- What are they doing right now to resolve this issue? Why is this so bad?
+- How many users does this affect? How do you know? Share metrics or links to videos. 
+-->
 
-### Figma
+## Business Case
 
 TODO
-<!-- Insert the link to the feature's page in the Fleet EE (current) Figma file. This link is located in the 🧩 Product google document linked here: https://docs.google.com/document/d/10B4eDXHjM9lFob6VcBDFEzYR424QRH3EuTpRLbhWyzM/edit#. Remove this "Figma" section if there is no link present in the google doc. -->
+<!--
+Why should Fleet work on this problem? How does this contribute to our reaching our strategic goals?
+-->
 
-### API wireframes
+## Analytics
+TODO
+<!--
+- How will we know that the problem has been solved or improved? 
+- What is the current state of the measurement?
+- What measurements do you need to implement? 
+-->
+
+## Requirements
+<!-- Describe the required outcomes -->
+TODO
+1. 
+2. 
+3. 
+
+<!-- Things we tend to forget about -->
+- **Documentation** Do you want a guide written about this?
+- **Analytics** How are we going to measure usage and success?
+- **QA** Any special QA notes?
+
+
+## Design
+### UI
 
 TODO
-<!-- Insert a link to the draft PR that includes the proposed API wireframes to support the feature work. This link is located in the 🧩 Product google document linked here: https://docs.google.com/document/d/10B4eDXHjM9lFob6VcBDFEzYR424QRH3EuTpRLbhWyzM/edit#. Remove this "API wireframes" section if there is no link present in the google doc. -->
+<!-- Insert the link to the relevant Figma file. Remove this section if there are no changes necessary. -->
 
-### How?
-
-#### Frontend
+### API
 
 TODO
-<!-- Describe the required frontend changes to support the feature work. Include screenshot's from the feature's page in Figma when appropriate. Remove the "Frontend" section if the feature work does not require frontend changes. -->
+<!-- Specify what changes to the API are required.Remove this section if there are no changes necessary. -->
 
-- [ ] 
-
-#### Backend
+### CLI
 
 TODO
-<!-- Describe the required backend changes to support the feature work. Include screenshot's from the feature's page in Figma when appropriate. Remove the "Frontend" section if the feature work does not require frontend changes. -->
+<!-- Specify what changes to the CLI are required. Remove this section if there are no changes necessary. -->
 
-- [ ] 
\ No newline at end of file
+## Related
+
+<!-- Insert related items such as child issues -->
+
+### Child issues
+Interface team
+- TODO
+
+Platform team
+- TODO
+
+Agent team
+- TODO
+
+Documentation
+- TODO