try a new github issue template

diff --git a/.github/ISSUE_TEMPLATE/custom-issue-report.md b/.github/ISSUE_TEMPLATE/custom-issue-report.md
deleted file mode 100644 (file)
index dbc63e6..0000000
--- a/.github/ISSUE_TEMPLATE/custom-issue-report.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-name: custom-issue-report
-about: A brief template for bug/issue reports
-title: ''
-labels: ''
-assignees: ''
-
----
-
-#This tracker is for pcsx-rearmed-libretro issues *only*.
-
-If the issue also occurs in standalone PCSX-ReARMed, the upstream repo is probably a better place for it.
-
-That said, we would suggest that you also try it on other PCSX-based forks such as PCSX Reloaded, PCSX Redux and the upstream version
-as well because these share a similar codebase (or derive from it) and are helpful for regression testing, thus making it more 
-likely for the bug to be fixed if it is indeed specific to the libretro core only.
-
-## Description
-
-Please describe the issue. If this is a feature request, please add [feature request] to the title of the issue report.
-
-## Steps to reproduce
-
-How can we reproduce this issue? Please include all relevant steps, as well as any settings that you have changed from their default values, particularly including whether you are using the dynarec or interpreter CPU emulation.
-
-## When did the behavior start?
-
-If you can bisect the issue (that is, pinpoint the exact commit that caused the problem), please do. Someone has to do it, and having this already done greatly increases the likelihood that a developer will investigate and/or fix the problem. Barring that, please state the last time it worked properly (if ever).
-
-## Your device/OS/platform/architecture
-
-Such as Android, iOS, Windows 10, Linux, x86_64, a smart toaster, etc.
-
-## Logs (enable file logging and set log levels to DEBUG for core and frontend)
-
-## Screenshots (if needed for visual confirmation)
-
-## Others (save states and/or save files nearest to the affected area, compressed)

diff --git a/.github/ISSUE_TEMPLATE/report.yml b/.github/ISSUE_TEMPLATE/report.yml
new file mode 100644 (file)
index 0000000..f68f236
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/report.yml
@@ -0,0 +1,57 @@
+name: Bug report
+description: Report a PCSX-ReARMed issue
+body:
+  - type: input
+    id: pcsx_version
+    attributes:
+      label: PCSX-ReARMed Version
+      description: Version number of the emulator as shown in the menus and printed in logs.
+      placeholder: r23l a4e249a1
+    validations:
+      required: true
+  - type: input
+    id: device
+    attributes:
+      label: Your device
+      description: "Examples: Raspberry Pi4, PC, PS Vita, PS Classic, etc."
+      placeholder: PC
+    validations:
+      required: true
+  - type: dropdown
+    id: os
+    attributes:
+      label: Operating System of your device
+      description: What OS are you using?
+      options:
+        - Android
+        - Apple (iOS, tvOS, macOS etc.)
+        - Linux (or Linux-based like RetroPie etc.)
+        - Windows
+        - Other (consoles, etc.)
+  - type: dropdown
+    id: arch
+    attributes:
+      label: CPU architecture
+      description: Select the type of the CPU in your device. In case you're using 32bit software on a 64bit device, please select 32bit.
+      options:
+        - ARM 64bit (AArch64)
+        - ARM 32bit
+        - x86-64 (64bit Intel, AMD, etc.)
+        - x86 (32bit Intel, AMD, etc.)
+        - Other
+  - type: textarea
+    id: issue_description
+    attributes:
+      label: Issue description
+      description: What issue are you having?
+      placeholder: Crash Bandicoot crashes after pressing start.
+    validations:
+      required: true
+  - type: textarea
+    id: step_by_step
+    attributes:
+      label: Step-by-step reproduction and logs
+      description: Type here how your issue can be reproduced and attach any logs.
+      placeholder: Wait for the game's title screen to appear and then press start.
+    validations:
+      required: false