-
Notifications
You must be signed in to change notification settings - Fork 69
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
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
- Loading branch information
1 parent
a18fa10
commit 30742d8
Showing
6 changed files
with
56 additions
and
58 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -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? |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file was deleted.
Oops, something went wrong.