Chore(docs): update issue templates (#1256)

* Update bug_report.md

add more descriptive needs for solving bugs

* Update bug_report.md

fix typos

* Update bug_report.md

* Update bug_report.md

edit requirements documentation to make them more clear

.github/ISSUE_TEMPLATE/bug_report.md

@@ -7,6 +7,7 @@ assignees: ''
 
 ---
 
+
 <!--
 MIND YOUR TITLE:
 - "App in a deploying state" is NOT the title/description of your actual bug.
@@ -14,6 +15,40 @@ MIND YOUR TITLE:
 - Don't refer to a version, bugs are always for latest version
 -->
 
+
+***SCALE version***
+<!--
+- the version of truenas scale you are currently running.
+- FOUND IN: System settings > general > os version
+-->
+
+***App Version***
+<!--
+- the version of the app having the issue and versions of any apps being used in conjunction
+- FOUND IN: apps > installed applications
+-->
+
+***Application Events***
+<!--
+- debug information from the app(s) specifically
+- FOUND IN: apps > installed applications > (click on the app name) > click the carrot next to application events and include a screenshot here
+-->
+
+***Application Logs***
+<!--
+- log output from the containers involved in the app
+- FOUND IN: apps > installed applications > (click the 3 dots on the top right of the app box) > logs > open the logs for each pod used for the app and take a screenshot
+- it can take a moment for the logs to show on the logs screen
+-->
+
+***Application Configuration***
+<!--
+- the configuration settings for the app (make sure to include what you have changed and what you didnt change
+- if possible use the edit features in your screenshot tool to highlight the portions you cnaged intentionally
+- FOUND IN: apps > installed applications > (click the 3 dots on the top right of the app box) edit
+-->
+
+
 **Describe the bug**
 <!--
 A clear and concise description of what the bug is.
@@ -21,6 +56,7 @@ A clear and concise description of what the bug is.
 
 **To Reproduce**
 <!--
+- make sure that if you follow these steps again yourself the bug happens again. if it doesnt its probbly a configuration error and should be handled with a support thread on the discord
 Steps to reproduce the behavior:
 1. Go to '...'
 2. Click on '....'