Merge branch 'dev' into 'master'

Add Repository Templates

See merge request crafty-controller/crafty-4!326

.gitlab/issue_templates/Bug.md

@@ -0,0 +1,20 @@
+## Quick Information
+- **Operating System:** Windows / Linux / MacOS / UnRAID
+- **Install Type:** Git Cloned(Manual) / Installer / WinPackage / Docker
+
+## What Happened?
+*A brief description of what happened when you tried to perform an action*
+
+## Expected result
+*What should have happened when you performed the actions*
+
+## Steps to reproduce
+*List the steps required to produce the error. These should be as few as possible*
+
+## Screenshots
+Any relevant screenshots which show the issue* !-->*
+
+## Priority/Severity
+- [ ] High (anything that impacts the normal user flow or blocks app usage)
+- [ ] Medium (anything that negatively affects the user experience)
+- [ ] Low (anything else e.g., typos, missing icons/translations, layout/formatting issues, etc.)

.gitlab/issue_templates/Change Request.md

@@ -0,0 +1,15 @@
+## Summary
+*Outline the issue being faced, and why this needs to change*
+
+## Area of the system
+*This might only be one part, but may involve multiple sections, Login/Dashboad/Terminal/Config*
+
+## How does this currently work?
+
+## What is the desired way of working?
+*After the change, what should the process/operation be?*
+
+## Priority/Severity
+- [ ] High (This will bring a huge increase in performance/productivity/usability)
+- [ ] Medium (This will bring a good increase in performance/productivity/usability)
+- [ ] Low (anything else e.g., trivial, minor improvements)

.gitlab/issue_templates/Feature Request.md

@@ -0,0 +1,27 @@
+## Problem Statement
+*What is the issue being faced and needs addressing?*
+
+## Who will benefit?
+*Will this fix a problem that only one user has, or will it benefit a lot of people*
+
+## Benefits and risks
+    What benefits does this bring?
+        - reduced support issues
+        - extend functionality
+
+    What risks might this introduce?
+        - May result in security issues
+        - May break current application flow
+        - Licence issues
+
+
+## Proposed solution
+*How would you like to see this issue resolved?*
+
+## Examples
+*Are there any examples of this which exist in other software?*
+
+## Priority/Severity
+- [ ] High (This will bring a huge increase in performance/productivity/usability)
+- [ ] Medium (This will bring a good increase in performance/productivity/usability)
+- [ ] Low (anything else e.g., trivial, minor improvements)

.gitlab/merge_request_templates/Default.md

@@ -0,0 +1,29 @@
+## What does this MR do and why?
+
+___Describe in detail what your merge request does and why.___<br>
+> *Please keep this description updated with any discussion that takes place so*<br>
+*that reviewers can understand your intent. Keeping the description updated is*<br>
+*especially important if they didn't participate in the discussion.*<br>
+
+
+## Screenshots or screen recordings
+
+___These are strongly recommended to assist reviewers and reduce the time to merge your change.___<br>
+> *Please include any relevant screenshots or screen recordings that will assist*<br>
+*reviewers and future readers. If you need help visually verifying the change,*<br>
+*please leave a comment and ping a GitLab reviewer, maintainer, or MR coach.*<br>
+
+
+## How to set up and validate locally
+
+___Numbered steps to set up and validate the change are strongly suggested.___
+
+
+## MR acceptance checklist
+
+This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
+* [ ] Have you checked this doesn't interfere/conflict/duplicate someone elses work?
+* [ ] Have you fully tested your changes?
+* [ ] Have you resolved any lint issues?
+* [ ] Have you assigned a reviewer?
+* [ ] Have you applied correct labels?