diff --git a/.github/ISSUE_TEMPLATE/bug.yml b/.github/ISSUE_TEMPLATE/bug.yml
index 89b3c5103f..2286545450 100644
--- a/.github/ISSUE_TEMPLATE/bug.yml
+++ b/.github/ISSUE_TEMPLATE/bug.yml
@@ -32,6 +32,7 @@ body:
         - macOS (Intel)
         - macOS (Apple Silicon)
         - Linux
+      required: true
   - type: textarea
     attributes:
       label: ape-config.yaml file
diff --git a/.github/ISSUE_TEMPLATE/work-item.yml b/.github/ISSUE_TEMPLATE/work-item.yml
deleted file mode 100644
index ec271460d6..0000000000
--- a/.github/ISSUE_TEMPLATE/work-item.yml
+++ /dev/null
@@ -1,53 +0,0 @@
-name: Work Item
-description: New work item for Ape team
-body:
-  - type: textarea
-    attributes:
-      label: Evelator Pitch
-      description: 1-2 line summary of the scope of this work item
-  - type: textarea
-    attributes:
-      label: Value
-      description: |
-        Who is this for?
-        Persona or group of people whom will derive value from the scenario.
-        What benefits will be achieved or business metrics improved?
-  - type: textarea
-    id: dependencies
-    attributes:
-      label: Dependencies
-      description: |
-         Call out key people, teams, tech dependencies, or assumptions.
-  - type: textarea
-    attributes:
-      label: Design Approach
-      description: |
-        Free text / diagram / whiteboard picture / etc. that clearly shows your approach and considerations to build the task list.
-        Existing code patterns in production code base that you will base your work off of.
-  - type: markdown
-    attributes:
-      value: |
-        ### Task List
-
-        Bulleted list describing the exit criteria, desired end state and any documentation, monitors, work for DRI, etc. that will need to be added to make sure someone else can support once it's live.
-
-        [ ] Tasks go here
-
-  - type: input
-    id: date
-    attributes:
-      label: Estimated Completion Date
-  - type: markdown
-    attributes:
-      value: |
-        ### Sign-off
-
-        1-2 people needed for signoff
-
-        Do not signoff unless:
-
-        1. agreed the tasks and design approach will achieve acceptance, and
-        2. the work can be completed by one person within the SLA.
-             Design reviewers should consider simpler approaches to achieve goals.
-
-        (Please leave a comment to sign off)