Updating Sitewide issue templates (#19403)

* Updating Sitewide issue templates

* Rename Sitewide issue template to appear higher in the list sorry not sorry

* syntax fixes

* Formatting adjustments

* jebus

* jebus2

.github/ISSUE_TEMPLATE/__cms-task.md

@@ -1,5 +1,5 @@
 ---
-name: Task
+name: CMS Task
 about: A task for the CMS team.
 title: "<Insert summary of task>"
 labels: Needs refining, UX writing

.github/ISSUE_TEMPLATE/_cms-epic.md

@@ -1,5 +1,5 @@
 ---
-name: Epic
+name: CMS Epic
 about: Epic template
 title: "<Insert summary of epic>"
 labels: Epic, Needs refining

.github/ISSUE_TEMPLATE/_sitewide-issue.md

@@ -0,0 +1,53 @@
+---
+name: "(Sitewide) Issue template"
+about: Issue template for Sitewide team
+title: ''
+labels: Needs refining, sitewide
+assignees: ''
+
+---
+
+## Description
+
+### User story
+> _Describe the audience/user, enhancement or fix, and value / outcome desired._
+
+**AS A**
+**I WANT**
+**SO THAT**
+
+
+### Engineering notes / background
+
+
+### Analytics considerations
+
+
+## Testing & QA
+
+### Scope / Impact analysis
+_What, if anything, could break as a result of this change?_
+_Engineer should assess this when approaching PR._
+
+
+### Roles / assignments
+_After functional testing, code review, accessibility review, and design review can happen in parallel._
+* **Functional testing:** 
+* **Code review:** 
+* **Design review:** 
+* **Accessibility review:** 
+* **Product acceptance:** 
+
+
+
+## Acceptance criteria
+_ACs should capture expected behavior, to inform test plans. Consider devices, documentation updates including KBs, change management, and [content model](https://prod.cms.va.gov/admin/structure/cm_document) when applicable._
+
+
+- [ ] 
+- [ ] Impact analysis is filled out and QA test plan is updated accordingly
+- [ ] Does this product have an existing regression test plan?
+	- [ ] Yes, link: 
+	- [ ] No, regression test plan will be created as part of the work / points in this ticket
+- [ ] Design review? 
+- [ ] Accessibility review? 

.github/ISSUE_TEMPLATE/enhancement.md

@@ -1,5 +1,5 @@
 ---
-name: Enhancement (user story or feature request)
+name: CMS Enhancement (user story or feature request)
 about: Suggest an idea for the CMS
 title: "<Summary of enhancement>"
 labels: Enhancement, Needs refining