From 4be1ff6214378541d691cdbca28bec2b6c8a9deb Mon Sep 17 00:00:00 2001
From: Juliya Smith <jules@apeworx.io>
Date: Wed, 11 Sep 2024 13:15:16 -0500
Subject: [PATCH] docs: types fixes

---
 .github/ISSUE_TEMPLATE/feature.yml   |  6 +++---
 .github/ISSUE_TEMPLATE/work-item.yml | 12 ++++++------
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/feature.yml b/.github/ISSUE_TEMPLATE/feature.yml
index d046702186..c8443198c4 100644
--- a/.github/ISSUE_TEMPLATE/feature.yml
+++ b/.github/ISSUE_TEMPLATE/feature.yml
@@ -3,7 +3,7 @@ description: Request a new feature, or an improvement to existing functionality.
 labels: 'category: feature'
 
 body:
-  - type: input
+  - type: textarea
     id: describe
     attributes:
       label: Describe
@@ -13,7 +13,7 @@ body:
         - Why Ape's current functionality is inadequate to address your goal
     validations:
       required: false
-  - type: input
+  - type: textarea
     id: specification
     attributes:
       label: Specification
@@ -22,7 +22,7 @@ body:
         Remember, your feature is much more likely to be included if it does not involve any breaking changes.
     validations:
       required: false
-  - type: input
+  - type: textarea
     id: dependencies
     attributes:
       label: Dependencies
diff --git a/.github/ISSUE_TEMPLATE/work-item.yml b/.github/ISSUE_TEMPLATE/work-item.yml
index 0cc4694d5b..7a8aa1cbdb 100644
--- a/.github/ISSUE_TEMPLATE/work-item.yml
+++ b/.github/ISSUE_TEMPLATE/work-item.yml
@@ -1,7 +1,7 @@
 name: Work Item
 description: New work item for Ape team
 body:
-  - type: input
+  - type: textarea
     id: pitch
     attributes:
       label: Evelator Pitch
@@ -14,30 +14,30 @@ body:
         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: input
+  - type: textarea
     id: dependencies
     attributes:
       label: Dependencies
       placeholder: |
          Call out key people, teams, tech dependencies, or assumptions.
-  - type: input
+  - type: textarea
     id: approach
     attributes:
       label: Design Approach
       placeholder: |
         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: input
+  - type: markdown
     id: tasks
     attributes:
       label: Task List
       description: 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.
       placeholder: \[\] Tasks go here
-  - type: input
+  - type: textarea
     id: date
     attributes:
       label: Estimated Completion Date
-  - type: input
+  - type: markdown
     id: review
     attributes:
       description: 1-2 people needed for signoff