Add bug templates for bugs and features

.gitlab/issue_templates/Bug.md

@@ -0,0 +1,45 @@
+<!---
+Please read this!
+
+Before opening a new issue, make sure to search for keywords in the issues
+filtered by the "Regression" or "Bug" label:
+
+https://gitlab.com/aimber/ScreenPlay/issues?label_name%5B%5D=Bug
+https://gitlab.com/aimber/ScreenPlay/issues?label_name%5B%5D=Regression
+
+
+Verify the issue you're about to submit isn't a duplicate.
+--->
+
+### Summary
+
+(Summarize the bug encountered concisely)
+
+### Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+### Example Project
+
+(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, and link to it here in the bug report)
+
+(If you are using an older version of ScreenPlay, this will also determine whether the bug has been fixed in a more recent version)
+
+### What is the current *bug* behavior?
+
+(What actually happens)
+
+### What is the expected *correct* behavior?
+
+(What you should see instead)
+
+### Relevant logs and/or screenshots
+
+(Paste any relevant logs - please use code blocks (```) to format console output,
+logs, and code as it's very hard to read otherwise.)
+
+### Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/label ~Bug

.gitlab/issue_templates/Feature.md

@@ -0,0 +1,34 @@
+<!---
+Please read this!
+
+Before opening a new issue, make sure to search for keywords in the feature
+filtered by the "Feature"  label:
+
+https://gitlab.com/aimber/ScreenPlay/issues?label_name%5B%5D=Feature
+
+
+Verify the feature you're about to submit isn't a duplicate.
+--->
+
+
+### Problem to solve
+
+<!-- What problem do we solve? Keep it short like a TL:DR-->
+
+### Further details
+
+<!-- Include use cases, benefits, and/or goals (contributes to our vision?) -->
+
+### Proposal
+
+<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey -->
+
+
+### What does success look like, and how can we measure that?
+
+<!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. -->
+
+
+### Links / references
+
+/label ~Feature