Adds docker install for testing

.devcontainer/python_development/devcontainer.json

@@ -1,11 +1,11 @@
 {
   "name": "Python Development",
   "dockerComposeFile": [
-    "../../testing/development/docker-compose.yml"
+    "../../testing/v2/development/docker-compose.yml"
   ],
   "service": "ubuntu",
   "shutdownAction": "none",
-  "workspaceFolder": "/lme",
+  "workspaceFolder": "/root/LME",
   "customizations": {
     "vscode": {
       "extensions": [
@@ -15,5 +15,5 @@
       ]
     }
   },
-  "remoteUser": "admin.ackbar"
+  "remoteUser": "root"
 }

.github/ISSUE_TEMPLATE/bug-or-error-report.md

@@ -10,38 +10,24 @@ assignees: ''
 ## **BEFORE CREATING THE ISSUE, CHECK THE FOLLOWING GUIDES**: 
  - [ ] [FAQ](https://github.com/cisagov/LME/blob/main/docs/markdown/reference/faq.md)
  - [ ] [Troubleshooting](https://github.com/cisagov/LME/blob/main/docs/markdown/reference/troubleshooting.md)
- - [ ] Search current/closed issues for similar questions and utilize github/google search to see if an answer exists for the error you are encountering.
+ - [ ] Search current/closed issues for similar questions, and utilize github/google search to see if an answer exists for the error I'm encountering.  
 
 If the above did not answer your question, proceed with creating an issue below: 
 
 ## Describe the bug
-<!-- A clear and concise description of what the software flaw you are experiencing looks like, or what the behavior is. -->
-
-## Expected behavior
-A clear and concise description of what you expected to happen.
+<!-- A clear and concise description of what the bug is. -->
 
 ## To Reproduce
 <!-- Steps to reproduce the behavior. These should be clear enough that our team can understand your running environment, software/operating system versions, and anything else we might need to debug the issue.  -->  
 <!-- Good examples can be found here: [Issue 1](https://github.com/cisagov/LME/issues/15) [Issue 2](https://github.com/cisagov/LME/issues/19).  --> 
 
 ### Please complete the following information
-
-#### **Setup**
-- Are you running the LME machines in a virtual environment (i.e. Docker) or are you running natively on the machines?
-- Which version of LME are you installing?
-- Is this a first-time installation or are you upgrading?  If upgrading, what was your previous version?
-
-#### **Desktop:** (Client Machines)
-- OS: [e.g. Windows 10]
-- Browser: [e.g. Firefox Version 104.0.1]
-- Software version: [e.g. Sysmon v15.0]
-
-#### **Domain Controller:** 
-- OS: [e.g. Windows Server]
-- Browser: [e.g. Firefox Version 104.0.1]
-- Software version: [e.g. Winlogbeat 8.11.1]
+#### **Desktop:**
+ - OS: [e.g. Windows 10]
+ - Browser: [e.g. Firefox Version 104.0.1]
+ - Software version: [e.g. Sysmon v15.0, Winlogbeat 8.11.1]
 
-#### **ElasticSearch/Kibana Server:**
+#### **Server:**
 - OS: [e.g. Ubuntu 22.04]
 - Software Versions:
   - ELK: [e.g. 8.7.1]
@@ -65,7 +51,7 @@ Increase the number of lines if your issue is not present, or include a relevant
 ## Expected behavior
 A clear and concise description of what you expected to happen.
 
-## Screenshots
+## Screenshots **OPTIONAL**
 If applicable, add screenshots to help explain your problem.
 
 ## Additional context

.github/PULL_REQUEST_TEMPLATE.md

@@ -18,13 +18,11 @@
 ## 🧪 Testing 
 
 <!-- How did you test your changes? How could someone else test this PR? -->
-<!-- Include details of your testing environment, and the tests you ran to. -->
+<!-- Include details of your testing environment, and the tests you ran to -->
 <!-- see how your change affects other areas of the code, etc. -->
 
 ## ✅ Pre-approval checklist ##
-- [ ] There is a [gitIssue](https://github.com/cisagov/LME/issues) that this PR resolves
-- [ ] Git Issue that this PR solves has been selected in the Development section
-- [ ] The PR's base branch has been modified to be the proper branch. 
+
 - [ ] Changes are limited to a single goal **AND** 
       the title reflects this in a clear human readable format
 - [ ] Issue that this PR solves has been selected in the Development section
@@ -35,12 +33,11 @@
 
 ## ✅ Pre-merge Checklist
 
-- [ ] All tests pass.
-- [ ] PR has been tested and the documentation for testing is above.
-- [ ] Squash and merge all commits into one PR level commit. 
+- [ ] All tests pass
+- [ ] PR has been tested and the documentation for testing is above
+- [ ] Squash and merge all commits into one PR level commit 
 
 ## ✅ Post-merge Checklist
 
-- [ ] Delete the branch to keep down number of branches.
-- [ ] The PR is labeled with `feat` for an added new feature, `update` for an update, **OR** `fix` for a fix.
-- [ ] The PR contains `Resolves #<issue #>` so that merging it closes out the corresponding issue.  For example `Resolves #132`.
+- [ ] Delete the branch to keep down number of branches
+