From 0e794f2a35571692bd5e13904319a4b1f058cd81 Mon Sep 17 00:00:00 2001
From: Artur Michalek <artur.michalek@swmansion.com>
Date: Fri, 20 Dec 2024 17:53:52 +0100
Subject: [PATCH] Update work item template

---
 .github/ISSUE_TEMPLATE/work_item.yml | 32 +++++++++++++++++-----------
 1 file changed, 19 insertions(+), 13 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/work_item.yml b/.github/ISSUE_TEMPLATE/work_item.yml
index 5de8d547dd..2236f8c8fc 100644
--- a/.github/ISSUE_TEMPLATE/work_item.yml
+++ b/.github/ISSUE_TEMPLATE/work_item.yml
@@ -1,23 +1,29 @@
 name: Work item
 description: Submit an actionable task
 body:
-  - type: dropdown
-    id: tool-name
+  - type: textarea
+    id: current-state
     attributes:
-      label: Which components does the task require to be changed? (think hard pls)
-      multiple: true
-      options:
-        - snforge
-        - sncast
-        - cairo-profiler
-        - other (describe below)
+      label: Current State
+      description: Describe the current state and state the problem
+      placeholder: Currently, the `print_a` cheatcode prints `"a"` to stdout. This is problematic because user might want it to be printed on their actual printer.
     validations:
       required: true
 
-  - type: textarea
-    id: description
+  - type: input
+    id: correct-state
     attributes:
-      label: Description
-      description: Describe the issue here.
+      label: Correct State
+      description: Briefly describe the correct state
+      placeholder: `print_a` should magically detect if user wants to print to stdout or a printer.
     validations:
       required: true
+
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional Context
+      description: Provide additional context on the desired state.
+      placeholder: E.g. if we can detect any printers in local network it might indicate that user wants to print to it.
+    validations:
+      required: false