diff --git a/.github/ISSUE_TEMPLATE/508-accessibility-audit-defect.md b/.github/ISSUE_TEMPLATE/508-accessibility-audit-defect.md new file mode 100644 index 0000000000..30f1063c51 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/508-accessibility-audit-defect.md @@ -0,0 +1,32 @@ +--- +name: 508 Accessibility Audit Defect +about: Capture defects from 508 office audit +title: Defect +labels: 508-audit, accessibility, Needs refining +assignees: '' + +--- + +## Description or Additional Context +Description from 508 office + +## Example +Example and any screenshots + +### Code snippet + + +### Steps to reproduce + + +## Recommended resolution + + +## Defect Criterion +[Defect number and name](urlToGuideline) - Defect description + +### Users affected +- List user types (e.g. keyboard only, screen reader, etc.) + +## Teams that this affects: +- [x] Team name diff --git a/.github/ISSUE_TEMPLATE/508-accessibility-audit-epic.md b/.github/ISSUE_TEMPLATE/508-accessibility-audit-epic.md new file mode 100644 index 0000000000..8e8caa1d18 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/508-accessibility-audit-epic.md @@ -0,0 +1,31 @@ +--- +name: 508 Accessibility Audit Epic +about: Epic for 508 office audit +title: "[Epic} 508 Audit " +labels: 508-audit, accessibility, Epic, Needs refining +assignees: '' + +--- + +## Audit Document + +## Severity Matrix + +- A product with no defects has a score of 100 +- Each open 'Critical' defect lowers the score by 15 +- Each open 'High' defect lowers the score by 5 +- Each open 'Medium' defect lowers the score by 2.5 +- Each open 'Low' defect lowers the score by 1 +- Accessibility defects have no effect on the score. + +| Severity | Number | +|----------|--------| +| Critical | x | +| High | x | +| Medium | x | +| Low | x | +| TOTAL | x | +| Score | x | + +## Timeline +This was completed on and the 508 office is planning on doing an audit of issues every 6 months for all projects. This should try to be addressed by . diff --git a/.github/ISSUE_TEMPLATE/__cms-task.md b/.github/ISSUE_TEMPLATE/__cms-task.md index c108dadc1a..2d91657e5f 100644 --- a/.github/ISSUE_TEMPLATE/__cms-task.md +++ b/.github/ISSUE_TEMPLATE/__cms-task.md @@ -2,7 +2,7 @@ name: Task about: A task for the CMS team. title: "" -labels: Needs refining +labels: Needs refining, UX writing assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/ap-defect.md b/.github/ISSUE_TEMPLATE/ap-defect.md index f9d3c39fa8..1f75fd1a01 100644 --- a/.github/ISSUE_TEMPLATE/ap-defect.md +++ b/.github/ISSUE_TEMPLATE/ap-defect.md @@ -1,8 +1,9 @@ --- -name: (AP) Defect +name: "(AP) Defect" about: Work to fix a problem with existing functionality title: "" labels: Accelerated Publishing, Defect +assignees: '' --- @@ -43,4 +44,3 @@ Log messages here - diff --git a/.github/ISSUE_TEMPLATE/ap-epic.md b/.github/ISSUE_TEMPLATE/ap-epic.md index 28d1e553ab..0290fc4077 100644 --- a/.github/ISSUE_TEMPLATE/ap-epic.md +++ b/.github/ISSUE_TEMPLATE/ap-epic.md @@ -1,8 +1,9 @@ --- -name: (AP) Epic +name: "(AP) Epic" about: A collection of work towards a defined goal title: "[Epic][AP] " -labels: Needs refining, Accelerated Publishing, Epic +labels: Accelerated Publishing, Epic, Needs refining +assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/ap-sprint-overview.md b/.github/ISSUE_TEMPLATE/ap-sprint-overview.md index 01f974d158..511fc6289a 100644 --- a/.github/ISSUE_TEMPLATE/ap-sprint-overview.md +++ b/.github/ISSUE_TEMPLATE/ap-sprint-overview.md @@ -1,8 +1,9 @@ --- -name: (AP) Sprint Overview +name: "(AP) Sprint Overview" about: High priority goals and tickets grouped by focus area title: "[AP] Sprint ##" -labels: Needs refining, Accelerated Publishing +labels: Accelerated Publishing, Needs refining +assignees: '' --- @@ -38,4 +39,3 @@ labels: Needs refining, Accelerated Publishing ## Focus area 5 - [ ] Add issues ``` - diff --git a/.github/ISSUE_TEMPLATE/ap-task.md b/.github/ISSUE_TEMPLATE/ap-task.md index 567dc08385..88399312cc 100644 --- a/.github/ISSUE_TEMPLATE/ap-task.md +++ b/.github/ISSUE_TEMPLATE/ap-task.md @@ -1,10 +1,12 @@ --- -name: (AP) Feature +name: "(AP) Feature" about: New or work or enhancements title: "" -labels: Needs refining, Accelerated Publishing +labels: Accelerated Publishing, Needs refining +assignees: '' --- + ## Requirements @@ -17,4 +19,3 @@ labels: Needs refining, Accelerated Publishing ## Background & implementation details - diff --git a/.github/ISSUE_TEMPLATE/cms-collaboration-cycle-feedback.md b/.github/ISSUE_TEMPLATE/cms-collaboration-cycle-feedback.md index 6b24ec47ce..67d85b1ff4 100644 --- a/.github/ISSUE_TEMPLATE/cms-collaboration-cycle-feedback.md +++ b/.github/ISSUE_TEMPLATE/cms-collaboration-cycle-feedback.md @@ -1,8 +1,10 @@ --- name: CMS Collaboration Cycle Feedback -about: Use this template for CMS Team practice areas to provide feedback to teams going through the CMS Collaboration Cycle. -title: 'Name of Collab Touchpoint - Practice Area Feedback - Name of Project' +about: Use this template for CMS Team practice areas to provide feedback to teams + going through the CMS Collaboration Cycle. +title: Name of Collab Touchpoint - Practice Area Feedback - Name of Project labels: CMS Team, CMS-Collab-Cycle, collab-cycle-feedback +assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/cms-design-system-dev-implementation.md b/.github/ISSUE_TEMPLATE/cms-design-system-dev-implementation.md index d25acc7c6f..7ec1f56f11 100644 --- a/.github/ISSUE_TEMPLATE/cms-design-system-dev-implementation.md +++ b/.github/ISSUE_TEMPLATE/cms-design-system-dev-implementation.md @@ -1,9 +1,9 @@ --- name: CMS Design System Dev Implementation about: Use this template for Developers to implement CMS design system updates. -title: 'Implement from the design system.' +title: Implement from the design system. labels: CMS design system, CMS Team, Drupal engineering, Needs refining -assignees: edmund-dunn, tonytaylor +assignees: edmund-dunn --- diff --git a/.github/ISSUE_TEMPLATE/cms-design-system-documentation.md b/.github/ISSUE_TEMPLATE/cms-design-system-documentation.md index 7a8f5b7834..a47d4c3d0d 100644 --- a/.github/ISSUE_TEMPLATE/cms-design-system-documentation.md +++ b/.github/ISSUE_TEMPLATE/cms-design-system-documentation.md @@ -1,9 +1,9 @@ --- name: CMS Design System Documentation about: Use this template for a designer to update the CMS design system documentation. -title: 'Update/add in the design system documentation.' -labels: CMS design system, CMS design, CMS Team, Needs refining -assignees: BlakeOrgan +title: Update/add in the design system documentation. +labels: CMS design system, CMS Team, Needs refining +assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/cms-design-system-experimental-addition-request.md b/.github/ISSUE_TEMPLATE/cms-design-system-experimental-addition-request.md index 601623c028..a0efd81287 100644 --- a/.github/ISSUE_TEMPLATE/cms-design-system-experimental-addition-request.md +++ b/.github/ISSUE_TEMPLATE/cms-design-system-experimental-addition-request.md @@ -1,9 +1,10 @@ --- name: CMS Design System Experimental Addition Request -about: Use this template for designers outside of the CMS team to request a component or pattern be added to the CMS Design System. -title: 'Experimental Design for [component or pattern name]' -labels: CMS design system, CMS design, CMS Team, Needs refining -assignees: BlakeOrgan +about: Use this template for designers outside of the CMS team to request a component + or pattern be added to the CMS Design System. +title: Experimental Design for [component or pattern name] +labels: CMS design system, CMS Team, Needs refining +assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/cms-design-system-update-or-addition.md b/.github/ISSUE_TEMPLATE/cms-design-system-update-or-addition.md index 99ffd6d681..d0d0bebb39 100644 --- a/.github/ISSUE_TEMPLATE/cms-design-system-update-or-addition.md +++ b/.github/ISSUE_TEMPLATE/cms-design-system-update-or-addition.md @@ -1,9 +1,9 @@ --- name: CMS Design System Update or Addition about: Use this template for a designer to update the CMS design system. -title: 'Update/add in the design system.' -labels: CMS design system, CMS design, CMS Team, Needs refining -assignees: BlakeOrgan +title: Update/add in the design system. +labels: CMS design system, CMS Team, Needs refining +assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/cms-section-request.md b/.github/ISSUE_TEMPLATE/cms-section-request.md index 394b0fd2e0..8784dcc37e 100644 --- a/.github/ISSUE_TEMPLATE/cms-section-request.md +++ b/.github/ISSUE_TEMPLATE/cms-section-request.md @@ -2,7 +2,7 @@ name: CMS section request about: Requests a change to the Sections hierarchy title: '' -labels: Content governance, CMS Team +labels: CMS Team, Content governance assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/content-audit.md b/.github/ISSUE_TEMPLATE/content-audit.md index f4e106cc80..a6e472ab15 100644 --- a/.github/ISSUE_TEMPLATE/content-audit.md +++ b/.github/ISSUE_TEMPLATE/content-audit.md @@ -2,8 +2,8 @@ name: Content Audit about: Submit a request to perform a content audit across VA.gov. title: 'Content Audit: ' -labels: Content audit, CMS Team -assignees: dawnpruitt, EWashb +labels: CMS Team, Content audit +assignees: EWashb --- diff --git a/.github/ISSUE_TEMPLATE/content_model_spec.md b/.github/ISSUE_TEMPLATE/content_model_spec.md index 977ae04a07..94948bc60c 100644 --- a/.github/ISSUE_TEMPLATE/content_model_spec.md +++ b/.github/ISSUE_TEMPLATE/content_model_spec.md @@ -1,8 +1,9 @@ --- name: Content Model Specification -about: Use this template when you are specifying proposed changes to the CMS Content Model -title: "Content model specification for [PRODUCT/FEATURE]" -labels: Content Model +about: Use this template when you are specifying proposed changes to the CMS Content + Model +title: Content model specification for [PRODUCT/FEATURE] +labels: '' assignees: '' --- @@ -22,4 +23,4 @@ SO THAT I can implement it in Drupal ## Acceptance Criteria - [ ] Proposed entities, fields, and field properties are documented using the [content model spec template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/cms/content-model/drupal_content_model_spec_template.xlsx) - [ ] Reviewed with engineering & product -- [ ] Send to CMS Collab Cycle \ No newline at end of file +- [ ] Send to CMS Collab Cycle diff --git a/.github/ISSUE_TEMPLATE/cross-team-intake-request.md b/.github/ISSUE_TEMPLATE/cross-team-intake-request.md index e2cc086a7f..bbe5783d7b 100644 --- a/.github/ISSUE_TEMPLATE/cross-team-intake-request.md +++ b/.github/ISSUE_TEMPLATE/cross-team-intake-request.md @@ -31,4 +31,4 @@ Please provide: ## Acceptance Criteria - [ ] The Product Manager for the recommended intake team is pinged through Slack about the issue - [ ] The Product Manager has discussed with the respective Product Owner to determine prioritization -- [ ] Any decisions made on prioritization or implementation are communicated back to the originating team \ No newline at end of file +- [ ] Any decisions made on prioritization or implementation are communicated back to the originating team diff --git a/.github/ISSUE_TEMPLATE/dark-launch.md b/.github/ISSUE_TEMPLATE/dark-launch.md index e89a437c4b..e0bd30a8db 100644 --- a/.github/ISSUE_TEMPLATE/dark-launch.md +++ b/.github/ISSUE_TEMPLATE/dark-launch.md @@ -1,9 +1,10 @@ --- -name: "Dark launch request" -about: Request to dark launch CMS content that includes React widget, owned by CMS team +name: Dark launch request +about: Request to dark launch CMS content that includes React widget, owned by CMS + team title: 'CMS/React content dark launch request: ' -labels: Drupal engineering, Needs analysis, CMS Team -assignees: BerniXiongA6 +labels: CMS Team, Drupal engineering +assignees: '' --- @@ -39,4 +40,4 @@ Please tick the boxes for completed steps as we go, for cross-team visibility. ## Acceptance Criteria - [ ] Page is verified: Live on Staging - [ ] Page is **not** live on Prod -- [ ] Ticket is cut for production launch planning, e.g. #10627 +- [ ] Ticket is cut for production launch planning, e.g. #10627 diff --git a/.github/ISSUE_TEMPLATE/devops-task.md b/.github/ISSUE_TEMPLATE/devops-task.md index 19be21cac6..22d4762211 100644 --- a/.github/ISSUE_TEMPLATE/devops-task.md +++ b/.github/ISSUE_TEMPLATE/devops-task.md @@ -2,10 +2,10 @@ name: DevOps task about: A task for the CMS DevOps team. title: "" -labels: DevOps, Needs refining, CMS Team +labels: CMS Team, DevOps, Needs refining assignees: '' --- ### Tasks: -- [ ] Task 1... \ No newline at end of file +- [ ] Task 1... diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/enhancement.md index d745c364aa..94f3ba48a5 100644 --- a/.github/ISSUE_TEMPLATE/enhancement.md +++ b/.github/ISSUE_TEMPLATE/enhancement.md @@ -40,4 +40,4 @@ Editor-centered - [ ] `Efficient`: Remove distractions and create clear, straightforward paths to get the job done. - [ ] `Approachable`: Offer friendly guidance over authoritative instruction. - [ ] `Consistent`: Reduce user’s mental load by allowing them to fall back on pattern recognition to complete tasks. -- [ ] `Empowering`: Provide clear information to help editors make decisions about their work. \ No newline at end of file +- [ ] `Empowering`: Provide clear information to help editors make decisions about their work. diff --git a/.github/ISSUE_TEMPLATE/knowledge-base-article.md b/.github/ISSUE_TEMPLATE/knowledge-base-article.md index e2e0a022d0..75c6e336ea 100644 --- a/.github/ISSUE_TEMPLATE/knowledge-base-article.md +++ b/.github/ISSUE_TEMPLATE/knowledge-base-article.md @@ -1,6 +1,7 @@ --- name: Knowledge Base article - Create or update -about: Use this template for new CMS Knowledge Base articles that need to be written or for updates to existing KB articles. +about: Use this template for new CMS Knowledge Base articles that need to be written + or for updates to existing KB articles. title: 'Create new KB article or update existing article : ' labels: Knowledge Base, Needs refining assignees: '' diff --git a/.github/ISSUE_TEMPLATE/linky-update-request.md b/.github/ISSUE_TEMPLATE/linky-update-request.md index 422b40e447..283672ca02 100644 --- a/.github/ISSUE_TEMPLATE/linky-update-request.md +++ b/.github/ISSUE_TEMPLATE/linky-update-request.md @@ -1,8 +1,8 @@ --- name: Linky Reference Update Request about: Submit a request to update a Linky Reference -title: 'Linky Reference Update Request' -labels: "User Support" +title: Linky Reference Update Request +labels: '' assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/octode-project-board-epic.md b/.github/ISSUE_TEMPLATE/octode-project-board-epic.md index adf6ebf126..c2ac5523c4 100644 --- a/.github/ISSUE_TEMPLATE/octode-project-board-epic.md +++ b/.github/ISSUE_TEMPLATE/octode-project-board-epic.md @@ -1,7 +1,8 @@ --- name: Sitewide Epic - Web Governance Board -about: Epic template for Sitewide projects that need to be publicized in the Web Governance Board project view, for Public Websites and Facilities teams. -title: "" +about: Epic template for Sitewide projects that need to be publicized in the Web Governance + Board project view, for Public Websites and Facilities teams. +title: '' labels: Epic, sitewide assignees: '' diff --git a/.github/ISSUE_TEMPLATE/pw-clp-request.md b/.github/ISSUE_TEMPLATE/pw-clp-request.md index 364f3933ec..58760cf7d7 100644 --- a/.github/ISSUE_TEMPLATE/pw-clp-request.md +++ b/.github/ISSUE_TEMPLATE/pw-clp-request.md @@ -1,10 +1,9 @@ --- name: "(Sitewide) Campaign Landing Page request" -about: Request a new Campaign Landing Page, owned by Public - Websites team +about: Request a new Campaign Landing Page, owned by Public Websites team title: 'Campaign Landing Page request: ' -labels: Needs refining, Public Websites, VA.gov frontend, User support, CLP, sitewide -assignees: jilladams, FranECross +labels: Needs refining, Public Websites, sitewide, User support, VA.gov frontend +assignees: FranECross, jilladams --- diff --git a/.github/ISSUE_TEMPLATE/pw-forms-bad-pdf-link-pw.md b/.github/ISSUE_TEMPLATE/pw-forms-bad-pdf-link-pw.md index bc3fe3dcaa..1bffb2d38c 100644 --- a/.github/ISSUE_TEMPLATE/pw-forms-bad-pdf-link-pw.md +++ b/.github/ISSUE_TEMPLATE/pw-forms-bad-pdf-link-pw.md @@ -3,7 +3,7 @@ name: "(PW) Forms/Bad PDF link defect" about: Forms outages / Bad PDF links, owned by Public Websites team title: 'Forms defect:
' labels: Defect, Find a form, Needs refining, Public Websites, sitewide -assignees: jilladams, FranECross +assignees: FranECross, jilladams --- diff --git a/.github/ISSUE_TEMPLATE/pw-injected-header-publish.md b/.github/ISSUE_TEMPLATE/pw-injected-header-publish.md index d71563ff36..bde8a369ee 100644 --- a/.github/ISSUE_TEMPLATE/pw-injected-header-publish.md +++ b/.github/ISSUE_TEMPLATE/pw-injected-header-publish.md @@ -2,7 +2,7 @@ name: "(PW) Injected Header/Footer - publish to prod" about: Submit a request to publish the injected header/footer to prod. title: 'Injected header/footer: Publish to prod: ' -labels: Injected header, Needs refining, Public Websites, VA.gov frontend, sitewide +labels: Injected header, Needs refining, Public Websites, sitewide, VA.gov frontend assignees: jilladams --- @@ -19,4 +19,4 @@ This ticket adds new domain(s) to allowlists that gate the injected header. When ## Acceptance Criteria - [ ] Devops PRs to add www & non-www domain(s) have merged - [ ] Requesting team has signed off that they're ready to publish -- [ ] On requested domain(s) the global header is injected on page load, with no cookie updates required \ No newline at end of file +- [ ] On requested domain(s) the global header is injected on page load, with no cookie updates required diff --git a/.github/ISSUE_TEMPLATE/pw-injected-header.md b/.github/ISSUE_TEMPLATE/pw-injected-header.md index b2d72b516f..dff6abc3ec 100644 --- a/.github/ISSUE_TEMPLATE/pw-injected-header.md +++ b/.github/ISSUE_TEMPLATE/pw-injected-header.md @@ -2,7 +2,7 @@ name: "(PW) Injected Header/Footer - prep for testing" about: Submit a request to add the injected header/footer an existing site. title: 'Injected header/footer: ' -labels: Injected header, Needs refining, Public Websites, VA.gov frontend, sitewide +labels: Injected header, Needs refining, Public Websites, sitewide, VA.gov frontend assignees: jilladams --- diff --git a/.github/ISSUE_TEMPLATE/qa-incidental.md b/.github/ISSUE_TEMPLATE/qa-incidental.md index 2d648c1364..68de1f55a6 100644 --- a/.github/ISSUE_TEMPLATE/qa-incidental.md +++ b/.github/ISSUE_TEMPLATE/qa-incidental.md @@ -20,4 +20,3 @@ _Semi-frequently (at least a few times per sprint), read through the production | Date | Issue(s) | | ---- | -------- | | | | - diff --git a/.github/ISSUE_TEMPLATE/research-collab-cycle.md b/.github/ISSUE_TEMPLATE/research-collab-cycle.md index 6afdf6da88..7b21b7d47d 100644 --- a/.github/ISSUE_TEMPLATE/research-collab-cycle.md +++ b/.github/ISSUE_TEMPLATE/research-collab-cycle.md @@ -3,7 +3,7 @@ name: Collaboration Cycle Research touchpoint(s) for [PRODUCT/INITIATIVE] about: Use this template when you have a research plan & conversation guide ready for review by other teams title: Get through Collaboration Cycle before user research starts -labels: UX, Research +labels: Research, UX assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/research-conversation-guide.md b/.github/ISSUE_TEMPLATE/research-conversation-guide.md index 379a0a4411..01ed29c1e9 100644 --- a/.github/ISSUE_TEMPLATE/research-conversation-guide.md +++ b/.github/ISSUE_TEMPLATE/research-conversation-guide.md @@ -2,7 +2,7 @@ name: Research Conversation Guide about: Use this template when you are drafting a conversation guide title: Draft [PRODUCT/INITIATIVE] conversation guide -labels: UX, Research +labels: Research, UX assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/research-discovery.md b/.github/ISSUE_TEMPLATE/research-discovery.md index 0f591b1754..4b39cd9238 100644 --- a/.github/ISSUE_TEMPLATE/research-discovery.md +++ b/.github/ISSUE_TEMPLATE/research-discovery.md @@ -2,7 +2,7 @@ name: Research Discovery about: Use this template when exploring if research is needed/viable title: Discovery for [PRODUCT/INITIATIVE] research -labels: UX, Research +labels: Research, UX assignees: '' --- @@ -35,4 +35,3 @@ Research Discovery is a time to establish the fundamental approach for a researc - [ ] Findings from research review are documented and shared with Sitewide UX Lead, Product Manager, and Product Owner - [ ] High-level scope of research is drafted and agreed upon - [ ] Subsequent tickets are created - diff --git a/.github/ISSUE_TEMPLATE/research-plan.md b/.github/ISSUE_TEMPLATE/research-plan.md index 36a18dc3e4..a6a04c24e0 100644 --- a/.github/ISSUE_TEMPLATE/research-plan.md +++ b/.github/ISSUE_TEMPLATE/research-plan.md @@ -1,8 +1,8 @@ --- name: Research Plan -about: Use this template when you are drafting a research plan +about: Use this template when you are drafting a research plan title: Draft [PRODUCT/INITIATIVE] research plan -labels: UX, Research +labels: Research, UX assignees: '' --- @@ -35,6 +35,3 @@ Use the appropriate template for the group you're conducting research with: - [ ] Feedback incorporated from PM and/or other team members - [ ] Research plan posted on github in project research folder - [ ] Final approval obtained from Sitewide UX Lead and documented at the bottom of the file in preparation for Research Review cycle - - - diff --git a/.github/ISSUE_TEMPLATE/research-prep.md b/.github/ISSUE_TEMPLATE/research-prep.md index 8f9bbd86d4..3f32c7dca2 100644 --- a/.github/ISSUE_TEMPLATE/research-prep.md +++ b/.github/ISSUE_TEMPLATE/research-prep.md @@ -1,8 +1,9 @@ --- name: Research Prep Tasks -about: Use this template when preparing for a research study after the research plan and conversation guide have been drafted +about: Use this template when preparing for a research study after the research plan + and conversation guide have been drafted title: Prep for [PRODUCT/INITIATIVE] research -labels: UX, Research +labels: Research, UX assignees: '' --- @@ -95,5 +96,3 @@ These types of studies have additional logistical considerations - [ ] The moderator(s), notetaker(s), and observer(s) have been invited to research sessions and daily debriefs - [ ] Pilot session(s) have been conducted - [ ] All preparation done before the first day of research sessions - - diff --git a/.github/ISSUE_TEMPLATE/research-readout-and-post-tasks.md b/.github/ISSUE_TEMPLATE/research-readout-and-post-tasks.md index 701f7479b6..231318d62b 100644 --- a/.github/ISSUE_TEMPLATE/research-readout-and-post-tasks.md +++ b/.github/ISSUE_TEMPLATE/research-readout-and-post-tasks.md @@ -1,6 +1,7 @@ --- name: Research Readout and Post-Research tasks -about: Use this template when sharing your research via readouts and doing final clean-up tasks. +about: Use this template when sharing your research via readouts and doing final clean-up + tasks. title: Conduct [PRODUCT/INITIATIVE] research readout and complete post-research tasks labels: Research, UX assignees: '' diff --git a/.github/ISSUE_TEMPLATE/research-sessions.md b/.github/ISSUE_TEMPLATE/research-sessions.md index 29d437f62a..fb771dad67 100644 --- a/.github/ISSUE_TEMPLATE/research-sessions.md +++ b/.github/ISSUE_TEMPLATE/research-sessions.md @@ -2,7 +2,7 @@ name: Research Sessions about: Use this template when you are conducting research session title: Conduct [PRODUCT/INITIATIVE] research sessions -labels: UX, Research +labels: Research, UX assignees: '' --- @@ -58,4 +58,4 @@ assignees: '' - [ ] Final participant list downloaded from Perigean - [ ] Display name of Perigean Zoom account changed back to what it was - [ ] Recruitment tracker updated with participant demographics - - [ ] For no-show participants, data entered as "N"'s \ No newline at end of file + - [ ] For no-show participants, data entered as "N"'s diff --git a/.github/ISSUE_TEMPLATE/research-synthesis-and-reporting.md b/.github/ISSUE_TEMPLATE/research-synthesis-and-reporting.md index 6e7e1562bd..9e14da24ca 100644 --- a/.github/ISSUE_TEMPLATE/research-synthesis-and-reporting.md +++ b/.github/ISSUE_TEMPLATE/research-synthesis-and-reporting.md @@ -34,4 +34,4 @@ assignees: '' - [ ] Some initial findings and potential recommendations shared (in Mural?) with Sitewide UX Lead and/or team members. What's important and what we might do next have been discussed. - [ ] Research report feedback requested from Sitewide UX Lead and other team members. - [ ] Sitewide UX Lead requested feedback from VA PO and shared with researcher -- [ ] All feedback on research report incorporated +- [ ] All feedback on research report incorporated diff --git a/.github/ISSUE_TEMPLATE/runbook---ux-research.md b/.github/ISSUE_TEMPLATE/runbook---ux-research.md index 0b5ad6ff3f..7be78ffe85 100644 --- a/.github/ISSUE_TEMPLATE/runbook---ux-research.md +++ b/.github/ISSUE_TEMPLATE/runbook---ux-research.md @@ -3,7 +3,7 @@ name: Runbook - UX Research about: Use this template when starting a new UX research process. This will create a high-level checklist to guide you through building tickets for upcoming sprints. title: "[PRODUCT/INITIATIVE] Research Runbook" -labels: UX, Research +labels: Research, UX assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-facility-url-change.md b/.github/ISSUE_TEMPLATE/runbook-facility-url-change.md index d273beb305..6959a440d4 100644 --- a/.github/ISSUE_TEMPLATE/runbook-facility-url-change.md +++ b/.github/ISSUE_TEMPLATE/runbook-facility-url-change.md @@ -2,10 +2,12 @@ name: Runbook - Facility URL Change about: Submit a request to change the URL of a facility title: 'URL Change for: ' -labels: Facilities, Drupal engineering, Flagged Facilities, Redirect request, URL Change, User support +labels: Drupal engineering, Facilities, Flagged Facilities, Redirect request, User + support assignees: '' --- + Parent ticket: #number-of-GH-ticket ### Implementation date @@ -61,4 +63,3 @@ When does this request need to be live: | Facility API ID | Full VA.gov URL | | --- | --- | | vha_691GM | https://www.va.gov/greater-los-angeles-health-care/locations/oxnard-va-clinic | - diff --git a/.github/ISSUE_TEMPLATE/runbook-nca-facility-closed.md b/.github/ISSUE_TEMPLATE/runbook-nca-facility-closed.md index e52edff157..6850f49ad2 100644 --- a/.github/ISSUE_TEMPLATE/runbook-nca-facility-closed.md +++ b/.github/ISSUE_TEMPLATE/runbook-nca-facility-closed.md @@ -2,7 +2,8 @@ name: Runbook - NCA Facility closed about: Steps for archiving a NCA facility in VA.gov CMS. title: 'NCA Facility closed: ' -labels: Change request, Drupal engineering, Facilities, User support, Flagged Facilities, NCA +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, NCA, User + support assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-nca-facility-name-change.md b/.github/ISSUE_TEMPLATE/runbook-nca-facility-name-change.md index 2d527717a0..f09e666d85 100644 --- a/.github/ISSUE_TEMPLATE/runbook-nca-facility-name-change.md +++ b/.github/ISSUE_TEMPLATE/runbook-nca-facility-name-change.md @@ -2,7 +2,8 @@ name: Runbook - NCA Facility name change about: Steps for updating names and URLs title: 'NCA Facility name change: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, NCA +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, NCA, User + support assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-nca-facility-new.md b/.github/ISSUE_TEMPLATE/runbook-nca-facility-new.md index 99d54df0b1..4813cefcf3 100644 --- a/.github/ISSUE_TEMPLATE/runbook-nca-facility-new.md +++ b/.github/ISSUE_TEMPLATE/runbook-nca-facility-new.md @@ -2,7 +2,8 @@ name: Runbook - New NCA Facility about: changing facility information in the CMS for NCA facilities title: 'New NCA Facility: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VBA assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-new-vamc-system.md b/.github/ISSUE_TEMPLATE/runbook-new-vamc-system.md index 3c87668967..59651b7150 100644 --- a/.github/ISSUE_TEMPLATE/runbook-new-vamc-system.md +++ b/.github/ISSUE_TEMPLATE/runbook-new-vamc-system.md @@ -2,7 +2,8 @@ name: Runbook - New VAMC system website about: Creating a new site for a VA healthcare system title: 'New VAMC System: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC, sitewide +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, sitewide, + User support, VAMC assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-closed.md b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-closed.md index c46e422579..fce32ff0ac 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-closed.md +++ b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-closed.md @@ -2,7 +2,8 @@ name: Runbook - VAMC Facility closed about: Steps for archiving a VAMC facility in VA.gov CMS. title: 'VAMC Facility closed: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VAMC assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-duplicate-or-section-change.md b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-duplicate-or-section-change.md index 7ee7e6eca5..6a6d257033 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-duplicate-or-section-change.md +++ b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-duplicate-or-section-change.md @@ -2,7 +2,8 @@ name: Runbook - VAMC facility duplicate record or section change about: How to update the section of a VAMC. title: 'VAMC Facility duplicate record or section change: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VAMC assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-name-change.md b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-name-change.md index 58f1abdec5..3756b99de6 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-name-change.md +++ b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-name-change.md @@ -2,7 +2,8 @@ name: Runbook - VAMC Facility name change about: Steps for updating names and URLs title: 'VAMC Facility name change: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VAMC assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-new.md b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-new.md index 216a0f72b0..5221c0a1ef 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vamc-facility-new.md +++ b/.github/ISSUE_TEMPLATE/runbook-vamc-facility-new.md @@ -2,7 +2,8 @@ name: Runbook - New VAMC Facility about: changing facility information in the CMS for VAMC facilities title: 'New VAMC Facility: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VAMC assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vamc-system-name-change.md b/.github/ISSUE_TEMPLATE/runbook-vamc-system-name-change.md index aad2a5d5e6..27ec9359ca 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vamc-system-name-change.md +++ b/.github/ISSUE_TEMPLATE/runbook-vamc-system-name-change.md @@ -2,7 +2,8 @@ name: Runbook - VAMC system name change about: How to update the name of a VAMC. title: 'VAMC system name change: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VAMC +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VAMC assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vba-facility-closed.md b/.github/ISSUE_TEMPLATE/runbook-vba-facility-closed.md index 4cfba6d07e..74a54869f5 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vba-facility-closed.md +++ b/.github/ISSUE_TEMPLATE/runbook-vba-facility-closed.md @@ -2,7 +2,8 @@ name: Runbook - VBA Facility closed about: Steps for archiving a VBA facility in VA.gov CMS. title: 'VBA Facility closed: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VBA assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vba-facility-launch.md b/.github/ISSUE_TEMPLATE/runbook-vba-facility-launch.md index 8855b512e8..cf28237921 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vba-facility-launch.md +++ b/.github/ISSUE_TEMPLATE/runbook-vba-facility-launch.md @@ -2,7 +2,7 @@ name: Runbook - Launching an approved VBA Facility about: Initial publishing of a VBA Facility title: 'Launching VBA Facility: ' -labels: Drupal engineering, Facilities, sitewide, User support, VBA, Flagged facilties +labels: Drupal engineering, Facilities, sitewide, User support, VBA assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vba-facility-name-change.md b/.github/ISSUE_TEMPLATE/runbook-vba-facility-name-change.md index b61ea5bc6c..55fbb0c115 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vba-facility-name-change.md +++ b/.github/ISSUE_TEMPLATE/runbook-vba-facility-name-change.md @@ -2,7 +2,8 @@ name: Runbook - VBA Facility name change about: Steps for updating names and URLs title: 'VBA Facility name change: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VBA assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vba-facility-new.md b/.github/ISSUE_TEMPLATE/runbook-vba-facility-new.md index 2e4d314944..1c29c185bb 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vba-facility-new.md +++ b/.github/ISSUE_TEMPLATE/runbook-vba-facility-new.md @@ -2,7 +2,8 @@ name: Runbook - New VBA Facility about: changing facility information in the CMS for VBA facilities title: 'New VBA Facility: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, VBA +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + VBA assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vet-center-cap-to-outstation.md b/.github/ISSUE_TEMPLATE/runbook-vet-center-cap-to-outstation.md index 8cd5f00f33..f3998b848d 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vet-center-cap-to-outstation.md +++ b/.github/ISSUE_TEMPLATE/runbook-vet-center-cap-to-outstation.md @@ -2,7 +2,8 @@ name: Runbook - Vet Center CAP becomes an Outstation about: Steps for upgrading a CAP to an Outstation title: 'Vet Center CAP becomes an Outstation: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, Vet Center +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + Vet Center assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vet-center-closed.md b/.github/ISSUE_TEMPLATE/runbook-vet-center-closed.md index 1c5f8ead59..af1f286b02 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vet-center-closed.md +++ b/.github/ISSUE_TEMPLATE/runbook-vet-center-closed.md @@ -2,7 +2,8 @@ name: Runbook - Vet Center, Outstation, Mobile Vet Center Facility closed about: Steps for archiving a Vet Center facility in VA.gov CMS. title: 'Vet Center Facility closed: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, Vet Center +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + Vet Center assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vet-center-name-change.md b/.github/ISSUE_TEMPLATE/runbook-vet-center-name-change.md index 03a6e68fd1..4e6a4ba750 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vet-center-name-change.md +++ b/.github/ISSUE_TEMPLATE/runbook-vet-center-name-change.md @@ -2,10 +2,12 @@ name: Runbook - Vet Center, Outstation, Mobile Vet Center name change about: Steps for updating names and URLs title: 'Vet Center name change: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, Vet Center +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + Vet Center assignees: '' --- + ## Vet Center, Outstation, Mobile Vet Center facility name change - Description Vet Centers, Mobile Vet Centers, and Vet Center Oustations may all be subject to name changes in VAST. Not all steps apply to each type of facility -- please pay attention and make sure you've done the relevant steps based on facility type. diff --git a/.github/ISSUE_TEMPLATE/runbook-vet-center-new.md b/.github/ISSUE_TEMPLATE/runbook-vet-center-new.md index ccf5c93b6b..71e7e0a0f5 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vet-center-new.md +++ b/.github/ISSUE_TEMPLATE/runbook-vet-center-new.md @@ -2,7 +2,8 @@ name: Runbook - New Vet Center Facility about: changing facility information in the CMS for Vet Center facilities title: 'New Vet Center Facility: ' -labels: Change request, Vet Center, Facilities, Flagged Facilities, User support, Drupal engineering +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + Vet Center assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/runbook-vet-center-outstation-to-vet-center.md b/.github/ISSUE_TEMPLATE/runbook-vet-center-outstation-to-vet-center.md index 455cd72d35..5b6c096203 100644 --- a/.github/ISSUE_TEMPLATE/runbook-vet-center-outstation-to-vet-center.md +++ b/.github/ISSUE_TEMPLATE/runbook-vet-center-outstation-to-vet-center.md @@ -2,10 +2,12 @@ name: Runbook - Vet Center Outstation becomes a Vet Center about: Steps for upgrading an outstation to a full Vet Center title: 'Outstation becomes Vet Center: ' -labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, Vet Center +labels: Change request, Drupal engineering, Facilities, Flagged Facilities, User support, + Vet Center assignees: '' --- + # Vet Center Outstation becomes a Vet Center ## Background Outstations have entries in VAST. When an Outstation becomes a full Vet Center, diff --git a/.github/ISSUE_TEMPLATE/sitewide-crew-member-onboarding.md b/.github/ISSUE_TEMPLATE/sitewide-crew-member-onboarding.md index ad5e597781..bbe16171d0 100644 --- a/.github/ISSUE_TEMPLATE/sitewide-crew-member-onboarding.md +++ b/.github/ISSUE_TEMPLATE/sitewide-crew-member-onboarding.md @@ -9,4 +9,4 @@ assignees: '' # Deprecated -Instead, clone the A6 Google [Onboarding Template doc](https://docs.google.com/document/d/1Ea4axA2GTyce0gtyI4mdFhbtBzYxNer9S0x264vw814/edit#heading=h.rcrak4gblqw3). +Instead, clone the A6 Google [Onboarding Template doc](https://docs.google.com/document/d/1Ea4axA2GTyce0gtyI4mdFhbtBzYxNer9S0x264vw814/edit#heading=h.rcrak4gblqw3). diff --git a/.github/ISSUE_TEMPLATE/sitewide-qa-plan.md b/.github/ISSUE_TEMPLATE/sitewide-qa-plan.md index 014ed627ff..95f4df1da2 100644 --- a/.github/ISSUE_TEMPLATE/sitewide-qa-plan.md +++ b/.github/ISSUE_TEMPLATE/sitewide-qa-plan.md @@ -2,7 +2,7 @@ name: Sitewide QA Plan about: QA plan template for test coverage of big-enough features title: 'QA test plan for: ' -labels: sitewide, Facilities, Manual QA, Public Websites +labels: Facilities, Manual QA, Public Websites, sitewide assignees: '' --- diff --git a/.github/ISSUE_TEMPLATE/tier-1-or-2-ongoing-work.md b/.github/ISSUE_TEMPLATE/tier-1-or-2-ongoing-work.md index 81d4f61dcf..cfa18c2066 100644 --- a/.github/ISSUE_TEMPLATE/tier-1-or-2-ongoing-work.md +++ b/.github/ISSUE_TEMPLATE/tier-1-or-2-ongoing-work.md @@ -19,4 +19,4 @@ Tier 2 expectations here: https://docs.google.com/document/d/15oe0wtGI_MdaScYpjJ ### Table to help track issues and approximate time spent | Date | Issue | Resolution | Time Spent | -| -- | -- | -- | -- | \ No newline at end of file +| -- | -- | -- | -- | diff --git a/.github/ISSUE_TEMPLATE/ux-writing.md b/.github/ISSUE_TEMPLATE/ux-writing.md index fb89db5fee..ed2f091479 100644 --- a/.github/ISSUE_TEMPLATE/ux-writing.md +++ b/.github/ISSUE_TEMPLATE/ux-writing.md @@ -37,4 +37,4 @@ E.g. *As a user who may be making changes to content, I'd like a message that wa - [ ] Validate draft with those responsible for the work - [ ] Peer review by a member of the design pod - [ ] Finalize edits to text, and mark as ready to implement in the original issue -- [ ] Document strategy behind language choices that are relevant to [the CMS content style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms/content-style-guide) \ No newline at end of file +- [ ] Document strategy behind language choices that are relevant to [the CMS content style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms/content-style-guide)