Add Two New Error/Security Logging Service Issue Templates and Update…

… Checklists for Others (#38)

* Add new issue template for StackHawk issues

* Add new issue template for Sentry issues

* Replace AC section with Tasklists for Bug, Redesign, and Task templates

.github/ISSUE_TEMPLATE/bug_report.md

@@ -43,18 +43,16 @@ assignees: ''
 
 <!-- A description of what you expected to happen. -->
 
-## Acceptance Criteria
-
-<!-- A list of one or more requirements that must be met in order for this -->
-<!-- ticket to be considered “done.” Use checkboxes to mark each item as an -->
-<!-- actionable task. -->
-
-- [ ] TK
-
 ## Screenshots
 
 <!-- Would including screenshots help explain the problem? -->
 
 ## Additional context
 
 <!-- Is there any additional context that would be helpful? -->
+
+```[tasklist]
+### Tasks
+```
+<!-- A list of one or more requirements that must be met in order for this -->
+<!-- ticket to be considered “done.” -->

.github/ISSUE_TEMPLATE/redesign-task.md

@@ -24,18 +24,16 @@ assignees: ''
 <!-- case, set this section to “n/a” and any PRs associated with it may be -->
 <!-- merged with only internal review. -->
 
-## Acceptance Criteria
-
-<!-- A list of one or more requirements that must be met in order for this -->
-<!-- ticket to be considered “done.” Use checkboxes to mark each item as an -->
-<!-- actionable task. -->
-
-- [ ] tk…
-
 ## Design Mocks
 
 <!-- Provide the link/links to design mockups? -->
 
 ## Screenshots
 
 <!-- Provide a screenshot of the element you are styling. -->
+
+```[tasklist]
+### Tasks
+```
+<!-- A list of one or more requirements that must be met in order for this -->
+<!-- ticket to be considered “done.” -->

.github/ISSUE_TEMPLATE/sentry_issue.md

@@ -0,0 +1,44 @@
+---
+name: Sentry issue
+about: A Sentry-reported error/bug.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Description
+
+<!-- A clear and concise description of the bug. -->
+<!-- The sections suggested are intended to make it easy to create a -->
+<!-- descriptive bug report. Change as needed! -->
+
+### Sentry Issue
+
+<!-- Link to Sentry dashboard ticket. -->
+
+Resolves 
+
+## Issue Owner
+
+<!-- A list of one or more individuals, responsible for seeing this -->
+<!-- error or bug resolved/patched. -->
+
+
+## Environment
+<!-- The context in which the report was filed. -->
+
+
+## Suggested Solution
+
+<!-- What is the suggestion Sentry has provided? -->
+
+
+## Screenshots
+
+<!-- Would including screenshots help explain the problem? -->
+
+
+```[tasklist]
+### Tasks
+```

.github/ISSUE_TEMPLATE/stackhawk_issue.md

@@ -0,0 +1,44 @@
+---
+name: StackHawk issue
+about: A StackHawk-reported vulnerability.
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+## Description
+
+<!-- A clear and concise description of the bug. -->
+<!-- The sections suggested are intended to make it easy to create a -->
+<!-- descriptive bug report. Change as needed! -->
+
+### StackHawk Issue
+
+<!-- Link to StackHawk dashboard ticket. -->
+
+Resolves 
+
+## Issue Owner
+
+<!-- A list of one or more individuals, responsible for seeing this -->
+<!-- vulnerability resolved/patched. -->
+
+
+## Environment
+<!-- The context in which the report was filed. -->
+
+
+## Suggested Solution
+
+<!-- What is the suggestion StackHawk has provided? -->
+
+
+## Screenshots
+
+<!-- Would including screenshots help explain the problem? -->
+
+
+```[tasklist]
+### Tasks
+```

.github/ISSUE_TEMPLATE/task.md

@@ -24,13 +24,6 @@ assignees: ''
 <!-- case, set this section to “n/a” and any PRs associated with it may be -->
 <!-- merged with only internal review. -->
 
-## Acceptance Criteria
-
-<!-- A list of one or more requirements that must be met in order for this -->
-<!-- ticket to be considered “done.” Use checkboxes to mark each item as an -->
-<!-- actionable task. -->
-
-- [ ] tk…
 
 ## Proposed Solution
 
@@ -43,3 +36,9 @@ assignees: ''
 ## Additional Context
 
 <!-- Is there any additional context that would be helpful? -->
+
+```[tasklist]
+### Tasks
+```
+<!-- A list of one or more requirements that must be met in order for this -->
+<!-- ticket to be considered “done.” -->