From c3cb8710486523c424368ca271a570815666f5ba Mon Sep 17 00:00:00 2001
From: kaitlincart <kaitcart@gmail.com>
Date: Fri, 16 Sep 2022 10:30:11 -0700
Subject: [PATCH 1/4] add new template for eng tasks

---
 .github/ISSUE_TEMPLATE/engineering-task.md | 47 ++++++++++++++++++++++
 1 file changed, 47 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/engineering-task.md

diff --git a/.github/ISSUE_TEMPLATE/engineering-task.md b/.github/ISSUE_TEMPLATE/engineering-task.md
new file mode 100644
index 000000000..daad033ec
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/engineering-task.md
@@ -0,0 +1,47 @@
+---
+name: Vagrant Engineering
+about: For Vagrant Engineers to track tasks. 
+---
+
+<!--
+This template is intended for the Vagrant Engineering team to track tasks. 
+
+Use the Bug Report issue template to request help when Vagrant is not working as expected and the feature request to suggest an enhancement. 
+-->
+
+## Description 
+Should be 2 - 3 sentences that define the solution or changes. 
+
+## Use case (optional) 
+How will this affect the end user? 
+
+## Supporting material 
+Add links to related issues or supporting documentation. 
+
+### Estimated task complexity time-frame (does not guarantee a delivery date)
+[] 1 day
+[] 1 week
+[] 2-3 weeks
+
+If a task takes longer than 3 weeks, either consider if you can break it down into smaller pieces of work or update the issue with a new estimated time-frame with a summary checklist of tasks. 
+
+### Estimated user impact
+Critical: fixes a bug, relieves a common pain point
+Major: addresses a frequent request
+Minor: trivial inconveniences that have robust workarounds 
+
+<!--
+To complete this issue: 
+
+* add labels
+* add a reviewer 
+* select a milestone 
+
+Your milestone selection will be considered a suggestion for the team to review during backlog grooming.
+
+Additional labels to consider: 
+
+Select a task size label based on the estimated completion time and description (task-small, task-medium, task-large).
+
+If the estimated user impact is marked as critical, also add a critical label (list labels here).
+-->

From c8b541f393a9a4c6ae8a8fa470fb6dcfec322546 Mon Sep 17 00:00:00 2001
From: kaitlincart <43049322+kaitlincart@users.noreply.github.com>
Date: Fri, 23 Sep 2022 11:50:48 -0700
Subject: [PATCH 2/4] Update .github/ISSUE_TEMPLATE/engineering-task.md

Co-authored-by: Sophia Castellarin <sophia@hashicorp.com>
---
 .github/ISSUE_TEMPLATE/engineering-task.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/engineering-task.md b/.github/ISSUE_TEMPLATE/engineering-task.md
index daad033ec..ef08f47a3 100644
--- a/.github/ISSUE_TEMPLATE/engineering-task.md
+++ b/.github/ISSUE_TEMPLATE/engineering-task.md
@@ -19,9 +19,9 @@ How will this affect the end user?
 Add links to related issues or supporting documentation. 
 
 ### Estimated task complexity time-frame (does not guarantee a delivery date)
-[] 1 day
-[] 1 week
-[] 2-3 weeks
+- [ ] 1 day
+- [ ] 1 week
+- [ ] 2-3 weeks
 
 If a task takes longer than 3 weeks, either consider if you can break it down into smaller pieces of work or update the issue with a new estimated time-frame with a summary checklist of tasks. 
 

From f9c4b2009ba574ff15bb73d50e538cd36071a987 Mon Sep 17 00:00:00 2001
From: kaitlincart <kaitcart@gmail.com>
Date: Fri, 23 Sep 2022 12:07:31 -0700
Subject: [PATCH 3/4] updates from our backlog session

---
 .github/ISSUE_TEMPLATE/engineering-task.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/engineering-task.md b/.github/ISSUE_TEMPLATE/engineering-task.md
index ef08f47a3..0dfb44c46 100644
--- a/.github/ISSUE_TEMPLATE/engineering-task.md
+++ b/.github/ISSUE_TEMPLATE/engineering-task.md
@@ -10,7 +10,7 @@ Use the Bug Report issue template to request help when Vagrant is not working as
 -->
 
 ## Description 
-Should be 2 - 3 sentences that define the solution or changes. 
+2 - 3 sentences that define the solution or changes. 
 
 ## Use case (optional) 
 How will this affect the end user? 
@@ -26,15 +26,15 @@ Add links to related issues or supporting documentation.
 If a task takes longer than 3 weeks, either consider if you can break it down into smaller pieces of work or update the issue with a new estimated time-frame with a summary checklist of tasks. 
 
 ### Estimated user impact
-Critical: fixes a bug, relieves a common pain point
-Major: addresses a frequent request
-Minor: trivial inconveniences that have robust workarounds 
+Most issues should categorized as minor or major. 
+- [ ] Critical: fixes a bug that impacts production deployments
+- [ ] Major: addresses a frequent request, relieves a common pain point
+- [ ] Minor: trivial inconveniences that have robust workarounds 
 
 <!--
 To complete this issue: 
 
 * add labels
-* add a reviewer 
 * select a milestone 
 
 Your milestone selection will be considered a suggestion for the team to review during backlog grooming.
@@ -43,5 +43,5 @@ Additional labels to consider:
 
 Select a task size label based on the estimated completion time and description (task-small, task-medium, task-large).
 
-If the estimated user impact is marked as critical, also add a critical label (list labels here).
+If the estimated user impact is marked as critical, also add a critical label.
 -->

From b53b3874517d617854bd886a5e5a17f578a6068a Mon Sep 17 00:00:00 2001
From: kaitlincart <kaitcart@gmail.com>
Date: Fri, 23 Sep 2022 15:54:43 -0700
Subject: [PATCH 4/4] remove checklists

---
 .github/ISSUE_TEMPLATE/engineering-task.md | 37 +++++++++++-----------
 1 file changed, 18 insertions(+), 19 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/engineering-task.md b/.github/ISSUE_TEMPLATE/engineering-task.md
index 0dfb44c46..603cfc764 100644
--- a/.github/ISSUE_TEMPLATE/engineering-task.md
+++ b/.github/ISSUE_TEMPLATE/engineering-task.md
@@ -18,30 +18,29 @@ How will this affect the end user?
 ## Supporting material 
 Add links to related issues or supporting documentation. 
 
-### Estimated task complexity time-frame (does not guarantee a delivery date)
-- [ ] 1 day
-- [ ] 1 week
-- [ ] 2-3 weeks
+<!--
+To complete this issue, add labels and select a milestone. 
+
+### Labels 
+
+#### Estimated task complexity time-frame (does not guarantee a delivery date)
+* day
+* week
+* multi-week
 
 If a task takes longer than 3 weeks, either consider if you can break it down into smaller pieces of work or update the issue with a new estimated time-frame with a summary checklist of tasks. 
 
-### Estimated user impact
+#### Estimated user impact
 Most issues should categorized as minor or major. 
-- [ ] Critical: fixes a bug that impacts production deployments
-- [ ] Major: addresses a frequent request, relieves a common pain point
-- [ ] Minor: trivial inconveniences that have robust workarounds 
-
-<!--
-To complete this issue: 
-
-* add labels
-* select a milestone 
-
-Your milestone selection will be considered a suggestion for the team to review during backlog grooming.
-
-Additional labels to consider: 
+* Critical: fixes a bug that impacts production deployments
+* Major: addresses a frequent request, relieves a common pain point
+* Minor: trivial inconveniences that have robust workarounds 
+  
+#### Task size
 
 Select a task size label based on the estimated completion time and description (task-small, task-medium, task-large).
 
-If the estimated user impact is marked as critical, also add a critical label.
+### Milestone
+
+Your milestone selection will be considered a suggestion for the team to review during backlog grooming.
 -->