Directory .gitlab added

.gitlab/issue_templates/bug.md

@@ -0,0 +1,30 @@
+### Summary
+
+(Summarize the bug encountered concisely)
+
+### Steps to reproduce
+
+(How one can reproduce the issue - this is very important)
+
+### What is the current *bug* behavior?
+
+(What actually happens)
+
+### What is the expected *correct* behavior?
+
+(What you should see instead)
+
+### Relevant logs
+
+(Paste any relevant logs - please use code blocks (```) to format console output,
+logs, and code as it's very hard to read otherwise.)
+
+### Screenshots
+
+(If a screenshot is relevant, post it here)
+
+### Possible fixes
+
+(If you can, link to the line of code that might be responsible for the problem)
+
+/label ~Bug

.gitlab/issue_templates/feature-proposal.md

@@ -0,0 +1,14 @@
+### Problem to solve
+
+### Further details
+
+(Include use cases, benefits, and/or goals)
+
+### Proposal
+
+### What does success look like, and how can we measure that?
+
+
+### Links / references
+
+/label ~"Feature Proposal"

.gitlab/issue_templates/improvement.md

@@ -0,0 +1,16 @@
+### What to Improve
+
+(Include a specific module, report, UI)
+
+### Further details
+
+(Include use cases, benefits, and/or goals)
+
+### Proposal
+
+### What does success look like, and how can we measure that?
+
+
+### Links / references
+
+/label ~"improvement"

.gitlab/issue_templates/research.md

@@ -0,0 +1,17 @@
+### Background:
+    
+    (Include problem, use cases, benefits, and/or goals)
+    
+    **What questions are you trying to answer?**
+    
+    **Are you looking to verify an existing hypothesis or uncover new issues you should be exploring?**
+    
+    **What is the backstory of this project and how does it impact the approach?**
+    
+    **What do you already know about the areas you are exploring?**
+    
+    **What does success look like at the end of the project?**
+    
+    ### Links / references:
+    
+    /label ~"Research"

.gitlab/issue_templates/test.md

@@ -0,0 +1,31 @@
+# Test Plan
+    
+    <!-- This issue outlines testing activities related to a particular issue or epic.
+    This and other comments should be removed as you write the plan -->
+    
+    ## Introduction
+    
+    <!-- Briefly outline what is being tested
+    
+    Mention the issue(s) this test plan is related to -->
+    
+    ## Scope
+    
+    <!-- State any limits on aspects of the feature being tested
+    Outline the types of data to be included
+    Outline the types of tests to be performed (functional, security, performance,
+    database, automated, etc) -->
+    
+    
+    ## Test Plan
+    
+    <!-- If the scope is small enough you may not need to write a list of tests to
+    perform. It might be enough to use the Capabilities to guide your testing.
+    
+    If the feature is more complex, especially if it involves multiple Components,
+    briefly outline a set of tests here. When identifying tests to perform be sure
+    to consider risk. 
+    
+    -->
+    
+    /label ~Quality

.gitlab/merge_request_templates/template.md

@@ -0,0 +1,16 @@
+## What does this MR do?
+
+<!-- Briefly describe what this MR is about -->
+
+## Related issues
+
+<!-- Mention the issue(s) this MR closes or is related to -->
+
+Closes 
+
+## Review checklist
+
+- [ ] Your team's review (required)
+- [ ] PM's review (recommended, but not a blocker)
+
+/label ~Documentation