Merge branch issue-templates with refs/heads/master into refs/merge-requests/140/train

.gitlab/issue_templates/Change Request.md

+## 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 !-->
+
+## How does this currently work?
+<!-- the current process, and any associated business rules !-->
+
+## What is the desired way of working?
+<!-- after the change, what should the process be, and what should the business rules be !-->
+
+## Priority/Severity
+<!-- Delete as appropriate. The priority and severity assigned may be different to this !-->
+- [ ] High (This will bring a huge increase in performance/productivity/usability, or is a legislative requirement)
+- [ ] Medium (This will bring a good increase in performance/productivity/usability)
+- [ ] Low (anything else e.g., trivial, minor improvements)

.gitlab/issue_templates/Feature Proposal.md

+## 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
+        - save error prone manual checks
+        - automate labour intensive tasks
+        
+    What risks might this introduce?
+        - May result in more data being shared with staff
+        - requires training materials to be updated
+        - Involves working with a specific vendor for a fixed period.
+!-->
+
+## 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
+<!-- Delete as appropriate. The priority and severity assigned may be different to this !-->
+- [ ] High (This will bring a huge increase in performance/productivity/usability/legislative cover)
+- [ ] Medium (This will bring a good increase in performance/productivity/usability)
+- [ ] Low (anything else e.g., trivial, minor improvements)

.gitlab/issue_templates/Issue Template.md

+<!--- Provide a general summary of the issue in the Title above -->
+
+## Description
+<!--- Provide a more detailed introduction to the issue itself, and why you consider it to be a bug -->
+
+## Expected Behavior
+<!--- Tell us what should happen -->
+
+## Actual Behavior
+<!--- Tell us what happens instead -->
+
+## Possible Fix
+<!--- Not obligatory, but suggest a fix or reason for the bug -->
+
+## Steps to Reproduce
+<!--- Provide a link to a live example, or an unambiguous set of steps to -->
+<!--- reproduce this bug. Include code to reproduce, if relevant -->
+1.
+2.
+3.
+4.
+
+## Context
+<!--- How has this bug affected you? What were you trying to accomplish? -->
+
+## Your Environment
+<!--- Include as many relevant details about the environment you experienced the bug in -->
+* Version used:
+* Environment name and version (e.g. go v1.16.3 on FreeBSD 13.0-current):
+* Server type and version:
+* Operating System and version:
\ No newline at end of file