Update issue templates

.github/ISSUE_TEMPLATE/bug-repor.md

@@ -0,0 +1,27 @@
+---
+name: Bug repor
+about: 'Create a detailed report to help reproduce the error '
+title: ''
+labels: bug
+assignees: ''
+
+---
+
+**1. Title**
+TEXT HERE 
+<!--- Your title should serve as a concise summary of what the bug is.Pro Tip: We recommend you review the title again after completing the report to ensure it is concise and reflects the problem.-->
+
+[]: # (This is a comment)
+<!--- This is an HTML comment in Markdown -->
+- Text here 
+
+
+2.	Environment
+The environment for every application can vary widely, but be as specific as you can. Testers should always follow the given bug report template unless otherwise specified — it helps cut down on unnecessary information.
+
+Device: What type of hardware are you using? Which specific model?
+OS: Which version number of the OS has displayed the issue?
+Account Used: This matters if testers are given test accounts by the client. it’s best to then include email + password in the issue report. When the developers get the bug they understand which account was used to discover the issue.
+Testing App Version: Which version number of the application are you testing? Simply writing “latest version” or “App Store Version” won’t cut it, since some bugs are version-specific and it’s hard to know the app store version when searching the store at a later date – make sure your testers include this specific information.
+Connection type (if applicable): If the application you’re testing is reliant on Internet connectivity, are you on WiFi, Ethernet, or cellular data? What is the speed of the connection?
+Reproducibility Rate: How many times have you been able to reproduce the error, using the exact steps you’ve taken to activate the bug? It’s also useful to report how many times the bug has been reproduced vs. the number of attempts it’s taken to reproduce the issue, in case it’s an intermittent occurrence.

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,39 @@
+---
+name: Bug Report
+about: 'Create a detailed report to help reproduce the error '
+title: "[bug]"
+labels: bug
+assignees: ampersand38
+
+---
+
+<!---NOTE: Replace any "ENTER TEXT HERE" with your input  .-->
+
+<!--- Your title should serve as a concise summary of what the bug is.Pro Tip: We recommend you review the title again after completing the report to ensure it is concise and reflects the problem.-->
+
+# Prerequisites
+
+Please answer the following questions for yourself before submitting an issue. **YOU MAY DELETE THE PREREQUISITES SECTION.**
+
+- [ ] I checked the documentation and found no answer
+- [ ] I checked to make sure that this issue has not already been filed
+- [ ] I checked the FAQ and known bugs on the discord 
+
+**1. Title**
+USER TEXT HERE
+<!--- Your title should serve as a concise summary of what the bug is.Pro Tip: We recommend you review the title again after completing the report to ensure it is concise and reflects the problem.-->
+
+
+<!--- This is an HTML comment in Markdown -->
+- Text here 
+
+
+2.	Environment
+The environment for every application can vary widely, but be as specific as you can. Testers should always follow the given bug report template unless otherwise specified — it helps cut down on unnecessary information.
+
+Device: What type of hardware are you using? Which specific model?
+OS: Which version number of the OS has displayed the issue?
+Account Used: This matters if testers are given test accounts by the client. it’s best to then include email + password in the issue report. When the developers get the bug they understand which account was used to discover the issue.
+Testing App Version: Which version number of the application are you testing? Simply writing “latest version” or “App Store Version” won’t cut it, since some bugs are version-specific and it’s hard to know the app store version when searching the store at a later date – make sure your testers include this specific information.
+Connection type (if applicable): If the application you’re testing is reliant on Internet connectivity, are you on WiFi, Ethernet, or cellular data? What is the speed of the connection?
+Reproducibility Rate: How many times have you been able to reproduce the error, using the exact steps you’ve taken to activate the bug? It’s also useful to report how many times the bug has been reproduced vs. the number of attempts it’s taken to reproduce the issue, in case it’s an intermittent occurrence.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/devops.md

@@ -0,0 +1,10 @@
+---
+name: DevOps
+about: Automate workflow
+title: "[DevObs]"
+labels: DevOps
+assignees: ''
+
+---
+
+Make better

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: Feature request
+assignees: YannikH
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.