Unnamed: 0,id,type,created_at,repo,repo_url,action,title,labels,body,index,text_combine,label,text,binary_label 95512,11996325718.0,IssuesEvent,2020-04-08 16:34:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Take Ch 36 to Design Intent,design vsa vsa-ebenefits,"Complete designs Align with team schedule design intent meeting (Jason)",1.0,"Take Ch 36 to Design Intent - Complete designs Align with team schedule design intent meeting (Jason)",1,take ch to design intent complete designs align with team schedule design intent meeting jason ,1 24604,17466546622.0,IssuesEvent,2021-08-06 17:44:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Documentation - EKS ,operations infrastructure eks,"## Description Make sure developers understand how we use Kubernetes in our environment. - How to onboard a new project - Application Manifest documentation (How to make a simple application manifest, etc) - CI documentation (what CI needs to output to manifest) - ArgoCD documentation (logging in, interacting with applications) - How to use Kubernetes secrets in your application repo (external-secrets, parameter store) ## Background/context/resources _Any additional context for the reader to know, if applicable_ ## Technical notes _Notes around work that is happening, if applicable_ --- ## Tasks - [ ] _Write documentation_ - [ ] Peer review / Edits ## Definition of Done - [ ] _Developer documentation for EKS is written and available to developers_ --- ### Reminders - [ ] Please attach your team label and any other appropriate label(s) - [ ] Please attach the needs grooming tag if needed - [ ] Please connect to an epic ",1.0,"Documentation - EKS - ## Description Make sure developers understand how we use Kubernetes in our environment. - How to onboard a new project - Application Manifest documentation (How to make a simple application manifest, etc) - CI documentation (what CI needs to output to manifest) - ArgoCD documentation (logging in, interacting with applications) - How to use Kubernetes secrets in your application repo (external-secrets, parameter store) ## Background/context/resources _Any additional context for the reader to know, if applicable_ ## Technical notes _Notes around work that is happening, if applicable_ --- ## Tasks - [ ] _Write documentation_ - [ ] Peer review / Edits ## Definition of Done - [ ] _Developer documentation for EKS is written and available to developers_ --- ### Reminders - [ ] Please attach your team label and any other appropriate label(s) - [ ] Please attach the needs grooming tag if needed - [ ] Please connect to an epic ",0,documentation eks description make sure developers understand how we use kubernetes in our environment how to onboard a new project application manifest documentation how to make a simple application manifest etc ci documentation what ci needs to output to manifest argocd documentation logging in interacting with applications how to use kubernetes secrets in your application repo external secrets parameter store background context resources any additional context for the reader to know if applicable technical notes notes around work that is happening if applicable tasks write documentation peer review edits definition of done developer documentation for eks is written and available to developers reminders please attach your team label and any other appropriate label s please attach the needs grooming tag if needed please connect to an epic ,0 178434,29811444362.0,IssuesEvent,2023-06-16 15:21:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design VAOS' documentation space,design ux appointments-product-design,"## Task description Work with VAOS dev and product to redesign the structure of our GitHub documentation space. ## References - [VAOS documentation notes](https://docs.google.com/document/d/1tHihdzLKTD333DYKPjaoxE0skaaWRaTPqLASvmJfruE/edit#) - [Optimal sort workshop results](https://app.optimalworkshop.com/a/dj540s05/optimalsort/results/1a920c40-accf-4693-a836-d22f82e8e4c6#/t/results/overview) ## Acceptance criteria - [x] Team has reviewed synthesis from card sort exercise - [x] Team has workshopped new structure - [x] Team has identified final new structure",2.0,"Design VAOS' documentation space - ## Task description Work with VAOS dev and product to redesign the structure of our GitHub documentation space. ## References - [VAOS documentation notes](https://docs.google.com/document/d/1tHihdzLKTD333DYKPjaoxE0skaaWRaTPqLASvmJfruE/edit#) - [Optimal sort workshop results](https://app.optimalworkshop.com/a/dj540s05/optimalsort/results/1a920c40-accf-4693-a836-d22f82e8e4c6#/t/results/overview) ## Acceptance criteria - [x] Team has reviewed synthesis from card sort exercise - [x] Team has workshopped new structure - [x] Team has identified final new structure",1,design vaos documentation space task description work with vaos dev and product to redesign the structure of our github documentation space references acceptance criteria team has reviewed synthesis from card sort exercise team has workshopped new structure team has identified final new structure,1 160773,25229755881.0,IssuesEvent,2022-11-14 18:46:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Design | Profile | Nametag | Update Documentation,design vsa authenticated-experience needs-grooming profile sprint-planning,"## Background After completing #48306 we want to ensure all Sketch files are updated to reflect the Nametag states and that we have these new designs and states documented in our Git repository. ## Tasks - [ ] Update sketch files - [ ] Update/create Git documentation ## Acceptance Criteria - [ ] Documentation is complete for the Nametag section ## Associated Tickets - #48306 ",1.0,"Design | Profile | Nametag | Update Documentation - ## Background After completing #48306 we want to ensure all Sketch files are updated to reflect the Nametag states and that we have these new designs and states documented in our Git repository. ## Tasks - [ ] Update sketch files - [ ] Update/create Git documentation ## Acceptance Criteria - [ ] Documentation is complete for the Nametag section ## Associated Tickets - #48306 ",1,design profile nametag update documentation background after completing we want to ensure all sketch files are updated to reflect the nametag states and that we have these new designs and states documented in our git repository tasks update sketch files update create git documentation acceptance criteria documentation is complete for the nametag section associated tickets ,1 137625,20178739881.0,IssuesEvent,2022-02-10 16:30:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Discovery: How could we leverage other open source design systems to help improve our CSS class library,vsp-design-system-team,"## Description We are a relatively small team responsible for building and maintaining a design system for use in pages and applications across VA.gov. We need to make sure that the components, utility classes, design resources, and guidance we create are high quality and well-tested. One option for helping us to do this is to leverage other open source design system resources that are supported by larger teams and are well-used and tested. For this ticket, we'd like to explore what resources are available to us to help improve our CSS class library and evaluate how we might take advantage of them. ## Acceptance Criteria - [ ] Generate list of resources available - [ ] Evaluate how we could leverage those resources to help in building and maintaining our CSS class library - [ ] Add list and evaluations as comment(s) on this ticket.",1.0,"Discovery: How could we leverage other open source design systems to help improve our CSS class library - ## Description We are a relatively small team responsible for building and maintaining a design system for use in pages and applications across VA.gov. We need to make sure that the components, utility classes, design resources, and guidance we create are high quality and well-tested. One option for helping us to do this is to leverage other open source design system resources that are supported by larger teams and are well-used and tested. For this ticket, we'd like to explore what resources are available to us to help improve our CSS class library and evaluate how we might take advantage of them. ## Acceptance Criteria - [ ] Generate list of resources available - [ ] Evaluate how we could leverage those resources to help in building and maintaining our CSS class library - [ ] Add list and evaluations as comment(s) on this ticket.",1,discovery how could we leverage other open source design systems to help improve our css class library description we are a relatively small team responsible for building and maintaining a design system for use in pages and applications across va gov we need to make sure that the components utility classes design resources and guidance we create are high quality and well tested one option for helping us to do this is to leverage other open source design system resources that are supported by larger teams and are well used and tested for this ticket we d like to explore what resources are available to us to help improve our css class library and evaluate how we might take advantage of them acceptance criteria generate list of resources available evaluate how we could leverage those resources to help in building and maintaining our css class library add list and evaluations as comment s on this ticket ,1 132495,18727012865.0,IssuesEvent,2021-11-03 17:16:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Scaffold out the SAHG Mockup,design vsa vsa-ebenefits,"wire frame is fine use cases some IA suggestions kick off (Jason) this is really to prep for design intent",1.0,"Scaffold out the SAHG Mockup - wire frame is fine use cases some IA suggestions kick off (Jason) this is really to prep for design intent",1,scaffold out the sahg mockup wire frame is fine use cases some ia suggestions kick off jason this is really to prep for design intent,1 123653,16521494440.0,IssuesEvent,2021-05-26 14:59:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"VSA Accessibility Feedback for ""Submit 686""",508/Accessibility design vsa vsa-ebenefits,"Definitely a complex undertaking! **Should** 1. For individual’s info — “Your first name”, and the rest — consider repeating whose info pattern throughout, i.e. “**Veteran’s first name**” for cognitive ease, including for the Veteran. **Consider** 1. Thinking of the cognitive/emotional load of the former spouse info questions, I wonder about the possibility of allowing this to be completed in an unauthenticated state. This use case may need the save in progress functionality, or at least ability to save in an encrypted local storage session. 2. If the country/city/county is a free text field, is it possible to clean the data b4 it goes into the db? Ensure not ALL CAPS, for example, to future-proof data. 3. What does the workflow / screen look like if someone starts filling out the form, saves, and comes back? [I think I just saw this in the forms systems demo.] 4. Have concerns about the cognitive load of this strung-together approach. Possibility of individual links to separate workflows, collect each of them, and provide review at the end to collect into a single submission, to ease cognitive impact. **Note:** I am trying a new framework for providing input (Feedback on this is welcome!): - **❗️ Must** for if the feedback must be applied - **⚠️Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ```diff - ""Must"" for if the feedback must be applied ! ""Should"" if the feedback is best practice + ""Consider"" for suggestions/enhancements ```",1.0,"VSA Accessibility Feedback for ""Submit 686"" - Definitely a complex undertaking! **Should** 1. For individual’s info — “Your first name”, and the rest — consider repeating whose info pattern throughout, i.e. “**Veteran’s first name**” for cognitive ease, including for the Veteran. **Consider** 1. Thinking of the cognitive/emotional load of the former spouse info questions, I wonder about the possibility of allowing this to be completed in an unauthenticated state. This use case may need the save in progress functionality, or at least ability to save in an encrypted local storage session. 2. If the country/city/county is a free text field, is it possible to clean the data b4 it goes into the db? Ensure not ALL CAPS, for example, to future-proof data. 3. What does the workflow / screen look like if someone starts filling out the form, saves, and comes back? [I think I just saw this in the forms systems demo.] 4. Have concerns about the cognitive load of this strung-together approach. Possibility of individual links to separate workflows, collect each of them, and provide review at the end to collect into a single submission, to ease cognitive impact. **Note:** I am trying a new framework for providing input (Feedback on this is welcome!): - **❗️ Must** for if the feedback must be applied - **⚠️Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ```diff - ""Must"" for if the feedback must be applied ! ""Should"" if the feedback is best practice + ""Consider"" for suggestions/enhancements ```",1,vsa accessibility feedback for submit definitely a complex undertaking should for individual’s info — “your first name” and the rest — consider repeating whose info pattern throughout i e “ veteran’s first name ” for cognitive ease including for the veteran consider thinking of the cognitive emotional load of the former spouse info questions i wonder about the possibility of allowing this to be completed in an unauthenticated state this use case may need the save in progress functionality or at least ability to save in an encrypted local storage session if the country city county is a free text field is it possible to clean the data it goes into the db ensure not all caps for example to future proof data what does the workflow screen look like if someone starts filling out the form saves and comes back have concerns about the cognitive load of this strung together approach possibility of individual links to separate workflows collect each of them and provide review at the end to collect into a single submission to ease cognitive impact note i am trying a new framework for providing input feedback on this is welcome ❗️ must for if the feedback must be applied ⚠️should if the feedback is best practice ✔️ consider for suggestions enhancements diff must for if the feedback must be applied should if the feedback is best practice consider for suggestions enhancements ,1 108552,13639491694.0,IssuesEvent,2020-09-25 11:07:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] - update documentation for learning center About template responsive tables,design documentation mobile planned-work vsa-public-websites,"Per[ feedback from the design intent review](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13825#issuecomment-697014817), create documentation for: - document at what viewport width we plan to collapse columns 2–12, so that we have all the info and are in agreement. - document focus management for when the collapsed row is expanded/collapsed. It is expected it would behave the way the additionalinfo component does (where focus remains on the button that expands/collapses). **acceptance criteria** - [ ] documentation created and shared with PW FE developers",1.0,"[Design] - update documentation for learning center About template responsive tables - Per[ feedback from the design intent review](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13825#issuecomment-697014817), create documentation for: - document at what viewport width we plan to collapse columns 2–12, so that we have all the info and are in agreement. - document focus management for when the collapsed row is expanded/collapsed. It is expected it would behave the way the additionalinfo component does (where focus remains on the button that expands/collapses). **acceptance criteria** - [ ] documentation created and shared with PW FE developers",1, update documentation for learning center about template responsive tables per create documentation for document at what viewport width we plan to collapse columns – so that we have all the info and are in agreement document focus management for when the collapsed row is expanded collapsed it is expected it would behave the way the additionalinfo component does where focus remains on the button that expands collapses acceptance criteria documentation created and shared with pw fe developers,1 95077,11952816960.0,IssuesEvent,2020-04-03 19:37:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reopened,Documentation - Implement Recommendations from ROE Research,Epic content-ia-team service-design super-epic,"**Problem:** - User research on ROE documentation found VFS teams are building their own link aggregator pages in order to access the relevant documentation from our repository. We also found people don’t know which documents to trust as the source of truth and don’t have confidence that they are looking at the most up-to-date version. - A related pain point for VFS teams is they missing having a high-level view of the tasks they will be asked to do through the product development lifecycle showing why and where they fit in to the big picture **Solution:** 1. Update the ReadMe’s for each practice area using this proposed template as applicable: https://docs.google.com/document/d/10kREoy1dMFS2zUg2z5CJ0OIAIQBJa2JoNootVkjx5yw/edit?usp=sharing 2. Pin updated ReadMe's to the vfs-platform-support slack channel. 3. Lend a feeling of authority to documentation by adding “Date last updated” and “Team Responsible” as a default part of va.gov-team repo content which also serves to instill a level of responsibility for our teams to maintain the documentation. **Objectives:** O1: Any volume of simultaneous customers have a delightful, self-service, end-to-end experience using the Platform to build on VA.gov. **KPIs:** - Reduction in average volume of documentation support requests per week - Increase in customer NPS - Reduction in volume of “non-human-needed” support requests month over month **Next Steps:** - Does the template work for each practice area? - As a way to keep the ReadMe as the main message when landing in a practice area folder (it displays below other files in the folder), consider gathering loose internal documents into a folder labeled for internal use (or something like that) to make it clear what VFS members should look at. **Definition of Done:** [Practice area](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform) READMEs have been updated in accordance with recommendations: - [x] accessibility - [ ] analytics - [ ] call-center - [x] content - [x] design - [ ] engineering - [x] information architecture - [ ] operations - [ ] product management - [ ] quality assurance - [ ] research - [ ] security - [ ] tools - [ ] triage - [ ] working-with-vsp Additional /platform READMEs have been updated _or_ next steps identified and captured as backlog ZH items - [ ] about-vsp - [ ] cms - [ ] service-design",1.0,"Documentation - Implement Recommendations from ROE Research - **Problem:** - User research on ROE documentation found VFS teams are building their own link aggregator pages in order to access the relevant documentation from our repository. We also found people don’t know which documents to trust as the source of truth and don’t have confidence that they are looking at the most up-to-date version. - A related pain point for VFS teams is they missing having a high-level view of the tasks they will be asked to do through the product development lifecycle showing why and where they fit in to the big picture **Solution:** 1. Update the ReadMe’s for each practice area using this proposed template as applicable: https://docs.google.com/document/d/10kREoy1dMFS2zUg2z5CJ0OIAIQBJa2JoNootVkjx5yw/edit?usp=sharing 2. Pin updated ReadMe's to the vfs-platform-support slack channel. 3. Lend a feeling of authority to documentation by adding “Date last updated” and “Team Responsible” as a default part of va.gov-team repo content which also serves to instill a level of responsibility for our teams to maintain the documentation. **Objectives:** O1: Any volume of simultaneous customers have a delightful, self-service, end-to-end experience using the Platform to build on VA.gov. **KPIs:** - Reduction in average volume of documentation support requests per week - Increase in customer NPS - Reduction in volume of “non-human-needed” support requests month over month **Next Steps:** - Does the template work for each practice area? - As a way to keep the ReadMe as the main message when landing in a practice area folder (it displays below other files in the folder), consider gathering loose internal documents into a folder labeled for internal use (or something like that) to make it clear what VFS members should look at. **Definition of Done:** [Practice area](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform) READMEs have been updated in accordance with recommendations: - [x] accessibility - [ ] analytics - [ ] call-center - [x] content - [x] design - [ ] engineering - [x] information architecture - [ ] operations - [ ] product management - [ ] quality assurance - [ ] research - [ ] security - [ ] tools - [ ] triage - [ ] working-with-vsp Additional /platform READMEs have been updated _or_ next steps identified and captured as backlog ZH items - [ ] about-vsp - [ ] cms - [ ] service-design",1,documentation implement recommendations from roe research problem user research on roe documentation found vfs teams are building their own link aggregator pages in order to access the relevant documentation from our repository we also found people don’t know which documents to trust as the source of truth and don’t have confidence that they are looking at the most up to date version a related pain point for vfs teams is they missing having a high level view of the tasks they will be asked to do through the product development lifecycle showing why and where they fit in to the big picture solution update the readme’s for each practice area using this proposed template as applicable pin updated readme s to the vfs platform support slack channel lend a feeling of authority to documentation by adding “date last updated” and “team responsible” as a default part of va gov team repo content which also serves to instill a level of responsibility for our teams to maintain the documentation objectives any volume of simultaneous customers have a delightful self service end to end experience using the platform to build on va gov kpis reduction in average volume of documentation support requests per week increase in customer nps reduction in volume of “non human needed” support requests month over month next steps does the template work for each practice area as a way to keep the readme as the main message when landing in a practice area folder it displays below other files in the folder consider gathering loose internal documents into a folder labeled for internal use or something like that to make it clear what vfs members should look at definition of done readmes have been updated in accordance with recommendations accessibility analytics call center content design engineering information architecture operations product management quality assurance research security tools triage working with vsp additional platform readmes have been updated or next steps identified and captured as backlog zh items about vsp cms service design,1 149803,23533331098.0,IssuesEvent,2022-08-19 17:38:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyHealth - Design Folders desktop page,design my-health my-health-SM-CORE mhv-to-va.gov-SM,"## Issue Description As a secure messaging user, I need a folder page so that I can see all the folders I have created in my secure messages --- ## Tasks - [x] Design folder page for desktop - [x] Design folder page for mobile - [x] Drop link to mockups into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Folder and desktop mockups will be complete and ready for review by PO. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] MyHealth - Design Folders desktop page - ## Issue Description As a secure messaging user, I need a folder page so that I can see all the folders I have created in my secure messages --- ## Tasks - [x] Design folder page for desktop - [x] Design folder page for mobile - [x] Drop link to mockups into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Folder and desktop mockups will be complete and ready for review by PO. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, myhealth design folders desktop page issue description as a secure messaging user i need a folder page so that i can see all the folders i have created in my secure messages tasks design folder page for desktop design folder page for mobile drop link to mockups into a comment on this ticket drop a note into mhv on vagov in slack when you are ready for tracey to review acceptance criteria folder and desktop mockups will be complete and ready for review by po how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 152155,23923843198.0,IssuesEvent,2022-09-09 19:53:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Links] [508] Create a download & video link component,508/Accessibility 508-issue-semantic-markup 508-experiment vsp-design-system-team DST-audited,"## Description Build a download & video link React component based on the [markup examples comment](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/152#issuecomment-553127340) from @jenstrickland . Consider building two separate components: one for download & a second for video links
Markup Examples
Note: This content was copy/pasted from the comment linked above, it may not exactly match if edited after July 28, 2020 ----- Collaborating with @1copenut, we reviewed the icon implementations to ensure accessibility. - Added `aria-hidden=""true""` to `` to suppress the injected text content (that renders the icon) from screen readers - To comply with WCAG, we edited link text to be clear about what the link does without the surrounding content. _(2.4.4, 2.4.9 - ""**The link text MUST make sense in context, and should make sense when taken out of context** (problematic phrases include: “click here,” “learn more,” “more,” “read more,” etc.).)""_ **Download PDF Link Example** ```HTML Download the Voices of Veterans PDF (4.9MB) ``` **View Video Example** ```HTML View video about VA disability compensation on Youtube ``` **Download Graphic Link Example** ```HTML Download VA benefits to people who've served JPG (0.11MB) ``` **Download Word Document Example** ```HTML Download Learn how to apply for VA benefits DOCX (0.49MB) ``` Related: https://github.com/department-of-veterans-affairs/va.gov-team/issues/12184 ### Guidance * [Proposal for a more accessible Download Link](https://accessabilly.com/proposal-for-a-more-accessible-download-link/) * [CSS Tricks - Building a Good Download ""button""](https://css-tricks.com/building-good-download-button/) * [I thought title text improved accessibility. I was wrong.](https://silktide.com/blog/i-thought-title-text-improved-accessibility-i-was-wrong/)
## Acceptance Criteria - [ ] Download link follows example patterns - [ ] Video link follows example patterns ",1.0,"[Links] [508] Create a download & video link component - ## Description Build a download & video link React component based on the [markup examples comment](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/152#issuecomment-553127340) from @jenstrickland . Consider building two separate components: one for download & a second for video links
Markup Examples
Note: This content was copy/pasted from the comment linked above, it may not exactly match if edited after July 28, 2020 ----- Collaborating with @1copenut, we reviewed the icon implementations to ensure accessibility. - Added `aria-hidden=""true""` to `` to suppress the injected text content (that renders the icon) from screen readers - To comply with WCAG, we edited link text to be clear about what the link does without the surrounding content. _(2.4.4, 2.4.9 - ""**The link text MUST make sense in context, and should make sense when taken out of context** (problematic phrases include: “click here,” “learn more,” “more,” “read more,” etc.).)""_ **Download PDF Link Example** ```HTML Download the Voices of Veterans PDF (4.9MB) ``` **View Video Example** ```HTML View video about VA disability compensation on Youtube ``` **Download Graphic Link Example** ```HTML Download VA benefits to people who've served JPG (0.11MB) ``` **Download Word Document Example** ```HTML Download Learn how to apply for VA benefits DOCX (0.49MB) ``` Related: https://github.com/department-of-veterans-affairs/va.gov-team/issues/12184 ### Guidance * [Proposal for a more accessible Download Link](https://accessabilly.com/proposal-for-a-more-accessible-download-link/) * [CSS Tricks - Building a Good Download ""button""](https://css-tricks.com/building-good-download-button/) * [I thought title text improved accessibility. I was wrong.](https://silktide.com/blog/i-thought-title-text-improved-accessibility-i-was-wrong/)
## Acceptance Criteria - [ ] Download link follows example patterns - [ ] Video link follows example patterns ",1, create a download video link component description build a download video link react component based on the from jenstrickland consider building two separate components one for download a second for video links markup examples note this content was copy pasted from the comment linked above it may not exactly match if edited after july collaborating with we reviewed the icon implementations to ensure accessibility added aria hidden true to to suppress the injected text content that renders the icon from screen readers to comply with wcag we edited link text to be clear about what the link does without the surrounding content the link text must make sense in context and should make sense when taken out of context problematic phrases include “click here ” “learn more ” “more ” “read more ” etc download pdf link example html a href download voices of veterans pdf type application pdf download the voices of veterans pdf mb view video example html a class video link href target blank rel noopener view video about va disability compensation on youtube download graphic link example html a class file download with icon href img va web badges al jpg download img va web badges al jpg download va benefits to people who ve served jpg mb download word document example html a class file download with icon href files chooseva marketing flyer docx download files chooseva marketing flyer docx download learn how to apply for va benefits docx mb related guidance acceptance criteria download link follows example patterns video link follows example patterns ,1 118503,15302930392.0,IssuesEvent,2021-02-24 15:15:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Yellow Ribbon: Schools near me,design dt-yellow-ribbon-schools-search frontend needs-grooming vsa vsa-decision-tools,"## User Story As a Veteran, I want to be able to find participating Yellow Ribbon schools near me by entering a location and being presented with a map showing schools, as well as a text-based list. ## Expected Behavior This feature would behave in the same manner as Google maps and similar map-based tools wherein one enters city, state, zip and searches for specific types of facilities (ex gas stations) within a selected radius (ex 10, 25, 50, 100 miles). The facilities within the selected radius are displayed on a map and may also be displayed in a list and sorted distance, initially from closest to farthest away. ## Acceptance Criteria - [ ] Story is groomed and clearly defined - [ ] Story is estimated, & broken into sprint-sized pieces of work - [ ] Collab cycle-related tasks are created - [ ] All work to implement, including collab cycle tasks are completed & tested - [ ] Update is peer-reviewed and reviewed on Staging by PO, PM - [ ] Feature flags are removed - [ ] Change is live on Production ",1.0,"Yellow Ribbon: Schools near me - ## User Story As a Veteran, I want to be able to find participating Yellow Ribbon schools near me by entering a location and being presented with a map showing schools, as well as a text-based list. ## Expected Behavior This feature would behave in the same manner as Google maps and similar map-based tools wherein one enters city, state, zip and searches for specific types of facilities (ex gas stations) within a selected radius (ex 10, 25, 50, 100 miles). The facilities within the selected radius are displayed on a map and may also be displayed in a list and sorted distance, initially from closest to farthest away. ## Acceptance Criteria - [ ] Story is groomed and clearly defined - [ ] Story is estimated, & broken into sprint-sized pieces of work - [ ] Collab cycle-related tasks are created - [ ] All work to implement, including collab cycle tasks are completed & tested - [ ] Update is peer-reviewed and reviewed on Staging by PO, PM - [ ] Feature flags are removed - [ ] Change is live on Production ",1,yellow ribbon schools near me user story as a veteran i want to be able to find participating yellow ribbon schools near me by entering a location and being presented with a map showing schools as well as a text based list expected behavior this feature would behave in the same manner as google maps and similar map based tools wherein one enters city state zip and searches for specific types of facilities ex gas stations within a selected radius ex miles the facilities within the selected radius are displayed on a map and may also be displayed in a list and sorted distance initially from closest to farthest away acceptance criteria story is groomed and clearly defined story is estimated broken into sprint sized pieces of work collab cycle related tasks are created all work to implement including collab cycle tasks are completed tested update is peer reviewed and reviewed on staging by po pm feature flags are removed change is live on production ,1 144262,22309745846.0,IssuesEvent,2022-06-13 15:53:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Research] My VA - Payment info: Create prototype for testing,design research my-va-dashboard vsa-authenticated-exp planned-work,"## Background As part of the next iteration of the Benefit Payments and Debt feature on My VA we need to do another round of research. We need to create the prototype for the research, incorporating the feedback from our [design intent](https://github.com/department-of-veterans-affairs/va.gov-team/issues/40551). Feedback from design intent documented by practice area below: - #40721 - #40757 - #40699 ## Tasks - [x] Create prototype - [ ] Review with PMs + PO ",1.0,"[Research] My VA - Payment info: Create prototype for testing - ## Background As part of the next iteration of the Benefit Payments and Debt feature on My VA we need to do another round of research. We need to create the prototype for the research, incorporating the feedback from our [design intent](https://github.com/department-of-veterans-affairs/va.gov-team/issues/40551). Feedback from design intent documented by practice area below: - #40721 - #40757 - #40699 ## Tasks - [x] Create prototype - [ ] Review with PMs + PO ",1, my va payment info create prototype for testing background as part of the next iteration of the benefit payments and debt feature on my va we need to do another round of research we need to create the prototype for the research incorporating the feedback from our feedback from design intent documented by practice area below tasks create prototype review with pms po ,1 125736,16829264279.0,IssuesEvent,2021-06-18 00:19:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Convert the Text input react component to a web component,vsp-design-system-team,"Convert the Text input REACT component to a web component as background prep work for the new forms library prototype. ",1.0,"Convert the Text input react component to a web component - Convert the Text input REACT component to a web component as background prep work for the new forms library prototype. ",1,convert the text input react component to a web component convert the text input react component to a web component as background prep work for the new forms library prototype ,1 161718,25385619970.0,IssuesEvent,2022-11-21 21:34:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Test appointments list with screenreader users,discovery ux vaos-product-design,"## Task Description * Test the appointments list proof of concept with Veterans who use screen readers ## Resources ## Acceptance Criteria - [ ] Devs have completed proof of concept. Includes dummy data and working detail pages - [ ] Proof of concept can be accessed via a test user on staging - [ ] Research plan and conversation guide are complete - [ ] Test is complete ",1.0,"Test appointments list with screenreader users - ## Task Description * Test the appointments list proof of concept with Veterans who use screen readers ## Resources ## Acceptance Criteria - [ ] Devs have completed proof of concept. Includes dummy data and working detail pages - [ ] Proof of concept can be accessed via a test user on staging - [ ] Research plan and conversation guide are complete - [ ] Test is complete ",1,test appointments list with screenreader users task description test the appointments list proof of concept with veterans who use screen readers resources acceptance criteria devs have completed proof of concept includes dummy data and working detail pages proof of concept can be accessed via a test user on staging research plan and conversation guide are complete test is complete ,1 174696,27710648817.0,IssuesEvent,2023-03-14 14:03:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Migrate unified experience wireframes to 375 width,design ux HCE-Checkin,"## Description Migrate all unified experience wireframes to 375 artboard in sketch. I.e., to reduce risk of issues when viewing wireframes on small screens. This is design debt, but would make sense to do pretty soon as we're just about completing the core set of unified experience wireframes. Ideally, these can be converted to 375, and then we make changes moving forward in this new artboard. ## Tasks - [x] Convert wireframes to 375 ## AC - [x] New sketch page is available at 375 width ## Deliverable The artboards are now converted to 375 widths for the [Unified Experience - Pre-Check-in and Check-in UXUI](https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec#Version) page of the sketch cloud.",1.0,"[Design] Migrate unified experience wireframes to 375 width - ## Description Migrate all unified experience wireframes to 375 artboard in sketch. I.e., to reduce risk of issues when viewing wireframes on small screens. This is design debt, but would make sense to do pretty soon as we're just about completing the core set of unified experience wireframes. Ideally, these can be converted to 375, and then we make changes moving forward in this new artboard. ## Tasks - [x] Convert wireframes to 375 ## AC - [x] New sketch page is available at 375 width ## Deliverable The artboards are now converted to 375 widths for the [Unified Experience - Pre-Check-in and Check-in UXUI](https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec#Version) page of the sketch cloud.",1, migrate unified experience wireframes to width description migrate all unified experience wireframes to artboard in sketch i e to reduce risk of issues when viewing wireframes on small screens this is design debt but would make sense to do pretty soon as we re just about completing the core set of unified experience wireframes ideally these can be converted to and then we make changes moving forward in this new artboard tasks convert wireframes to ac new sketch page is available at width deliverable the artboards are now converted to widths for the page of the sketch cloud ,1 155309,24443505717.0,IssuesEvent,2022-10-06 16:04:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,DDL: Revise Decision Letter designs,design research Claim Status Tool benefits-team-1 squad-1 download-decision-letter,Revise Decision Letter designs based on feedback from testing ,1.0,DDL: Revise Decision Letter designs - Revise Decision Letter designs based on feedback from testing ,1,ddl revise decision letter designs revise decision letter designs based on feedback from testing ,1 138375,20423731342.0,IssuesEvent,2022-02-24 00:04:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Editing Edge Cases: Time expired (after midnight)with valid link,design ux vsa-healthcare-exp HCE-Checkin,"# Description A Veteran attempts to pre-check-in after 12:00am on the day before their appointment. We need a messaging to let user know that they can no longer complete pre-check-in prior to their appointment. - Engineering isn’t track this currently, but they can (per Adrian). If they can, there should be a specific message related to the use case. # Tasks - [ ] Create new content and designs in Sketch - [ ] Review with content # Acceptance Criteria - [ ] Review final designs with product and UX - [ ] Create FE ticket",1.0,"[Design] Editing Edge Cases: Time expired (after midnight)with valid link - # Description A Veteran attempts to pre-check-in after 12:00am on the day before their appointment. We need a messaging to let user know that they can no longer complete pre-check-in prior to their appointment. - Engineering isn’t track this currently, but they can (per Adrian). If they can, there should be a specific message related to the use case. # Tasks - [ ] Create new content and designs in Sketch - [ ] Review with content # Acceptance Criteria - [ ] Review final designs with product and UX - [ ] Create FE ticket",1, editing edge cases time expired after midnight with valid link description a veteran attempts to pre check in after on the day before their appointment we need a messaging to let user know that they can no longer complete pre check in prior to their appointment engineering isn’t track this currently but they can per adrian if they can there should be a specific message related to the use case tasks create new content and designs in sketch review with content acceptance criteria review final designs with product and ux create fe ticket,1 139152,20782927552.0,IssuesEvent,2022-03-16 16:14:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Implement text changes to ""Check the status of your VA home loan COE"" landing page in COE prototype",content design vsa vsa-ebenefits LGY,"## Background The ""Check the status of your VA home loan COE"" page is the entry point to a user's COE status. It's essentially a public landing page with general info about the process and status. There were wholesale revisions to the page's copy to bring the content in line with other VA.gov tool landing pages. ### Considerations The COE prototype has been in design and development for more than one year. Recent revisions will bring the old page layout into agreement with the latest landing page screen designs. - [Link to the UXPin prototype](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030) ### Tasks - [x] Implement changes to UXPin screen - [x] Connect new screen/content to prototype functionality ### Acceptance criteria - [x] New prototype screen with text and layout revisions in place - [x] New screen connected to prototype functionality ",1.0,"Implement text changes to ""Check the status of your VA home loan COE"" landing page in COE prototype - ## Background The ""Check the status of your VA home loan COE"" page is the entry point to a user's COE status. It's essentially a public landing page with general info about the process and status. There were wholesale revisions to the page's copy to bring the content in line with other VA.gov tool landing pages. ### Considerations The COE prototype has been in design and development for more than one year. Recent revisions will bring the old page layout into agreement with the latest landing page screen designs. - [Link to the UXPin prototype](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030) ### Tasks - [x] Implement changes to UXPin screen - [x] Connect new screen/content to prototype functionality ### Acceptance criteria - [x] New prototype screen with text and layout revisions in place - [x] New screen connected to prototype functionality ",1,implement text changes to check the status of your va home loan coe landing page in coe prototype background the check the status of your va home loan coe page is the entry point to a user s coe status it s essentially a public landing page with general info about the process and status there were wholesale revisions to the page s copy to bring the content in line with other va gov tool landing pages considerations the coe prototype has been in design and development for more than one year recent revisions will bring the old page layout into agreement with the latest landing page screen designs tasks implement changes to uxpin screen connect new screen content to prototype functionality acceptance criteria new prototype screen with text and layout revisions in place new screen connected to prototype functionality ,1 119049,15394798775.0,IssuesEvent,2021-03-03 18:22:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"[UI] Refine Immunizations, Allergies, and Medications Wireframes",design vsa-healthcare-exp,"## User Story - As a Veteran, I want to be able to notify my VA provider of changes to my medication, allergies, and immunization history. ## Related Documentation - [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md) - [Medications Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/medications.md) - [Allergies Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/allergies.md) - [Immunizations Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/immunizations.md) ## Description Continued refinement of wireframe set on immunizations, allergies, and medications within a questionnaire will be delivered, so it can be utilized: - as a discussion guide with internal stakeholders, accessibility, and content - within a usability test - further work will probably be needed to make the wireframes interactive for the actual test. - within collab cycle meetings (design intent) _ This is a continuation of ticket #20095. ## Tasks - [ ] Create a draft set of [wireframes](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product and team for feature capabilities",1.0,"[UI] Refine Immunizations, Allergies, and Medications Wireframes - ## User Story - As a Veteran, I want to be able to notify my VA provider of changes to my medication, allergies, and immunization history. ## Related Documentation - [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md) - [Medications Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/medications.md) - [Allergies Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/allergies.md) - [Immunizations Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/immunizations.md) ## Description Continued refinement of wireframe set on immunizations, allergies, and medications within a questionnaire will be delivered, so it can be utilized: - as a discussion guide with internal stakeholders, accessibility, and content - within a usability test - further work will probably be needed to make the wireframes interactive for the actual test. - within collab cycle meetings (design intent) _ This is a continuation of ticket #20095. ## Tasks - [ ] Create a draft set of [wireframes](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product and team for feature capabilities",1, refine immunizations allergies and medications wireframes user story as a veteran i want to be able to notify my va provider of changes to my medication allergies and immunization history related documentation description continued refinement of wireframe set on immunizations allergies and medications within a questionnaire will be delivered so it can be utilized as a discussion guide with internal stakeholders accessibility and content within a usability test further work will probably be needed to make the wireframes interactive for the actual test within collab cycle meetings design intent this is a continuation of ticket tasks create a draft set of link to prototype acceptance criteria ui review meeting with product and team for feature capabilities,1 120114,15704612977.0,IssuesEvent,2021-03-26 15:11:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My VA: Claims error message,design my-va-dashboard planned-work vsa-authenticated-exp,"## Background Original discussion in #21177. We need an error message for the claims section if we can't load it. - If either endpoint fails, then we won't show anything. We will need a message here to say why. - If the section is loading for a long time there is a spinner - this can take up to 30 seconds. Maybe we need to think about how to handle this situation better. ## Tasks - [ ] Mock up design for claims error - [ ] Review with team - [ ] Work with copy - [ ] Handoff to FE",1.0,"[Design] My VA: Claims error message - ## Background Original discussion in #21177. We need an error message for the claims section if we can't load it. - If either endpoint fails, then we won't show anything. We will need a message here to say why. - If the section is loading for a long time there is a spinner - this can take up to 30 seconds. Maybe we need to think about how to handle this situation better. ## Tasks - [ ] Mock up design for claims error - [ ] Review with team - [ ] Work with copy - [ ] Handoff to FE",1, my va claims error message background original discussion in we need an error message for the claims section if we can t load it if either endpoint fails then we won t show anything we will need a message here to say why if the section is loading for a long time there is a spinner this can take up to seconds maybe we need to think about how to handle this situation better tasks mock up design for claims error review with team work with copy handoff to fe,1 159066,24941606564.0,IssuesEvent,2022-10-31 19:27:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My VA audit UX improvements: Update designs/docs to use new notification design system component in health care section on My VA,design my-va-dashboard authenticated-experience unplanned-work my-va-audit,"## Background Per feedback from Midpoint review, we learned we can use the notification component that Angela designed and submitted to the design system (it was approved!). This ticket is to update designs and documentation to indicate use of new notification component instead of ""warning alert component"" on My VA in the Health care section. (_I believe the health care section is the only ""in-line"" location where the ""warning alert component"" is currently used._) Feedback on this topic can be found in these tickets: * #48655 -- Should section ## Tasks - [x] Update designs/sketch files to show new design system notification component (instead of ""warning alert component"") for in-line notifications - [x] Update FE documentation to show and explain use of new design system notification component (instead of ""warning alert component"")for in-line notifications - [x] PM's to make sure corresponding FE tickets not already in flight/complete are updated as needed to reflect updated notification component ## Acceptance Criteria - [x] Sketch files and documentation are updated to indicate use of new notification component (instead of ""warning alert component"") for in-line notifications ## Validation - **_Who can validate this ticket? (FE, BE, Design, PM)?_** any team member - **_How can this work be validated?_** check documentation see that it's updated ",1.0,"[Design] My VA audit UX improvements: Update designs/docs to use new notification design system component in health care section on My VA - ## Background Per feedback from Midpoint review, we learned we can use the notification component that Angela designed and submitted to the design system (it was approved!). This ticket is to update designs and documentation to indicate use of new notification component instead of ""warning alert component"" on My VA in the Health care section. (_I believe the health care section is the only ""in-line"" location where the ""warning alert component"" is currently used._) Feedback on this topic can be found in these tickets: * #48655 -- Should section ## Tasks - [x] Update designs/sketch files to show new design system notification component (instead of ""warning alert component"") for in-line notifications - [x] Update FE documentation to show and explain use of new design system notification component (instead of ""warning alert component"")for in-line notifications - [x] PM's to make sure corresponding FE tickets not already in flight/complete are updated as needed to reflect updated notification component ## Acceptance Criteria - [x] Sketch files and documentation are updated to indicate use of new notification component (instead of ""warning alert component"") for in-line notifications ## Validation - **_Who can validate this ticket? (FE, BE, Design, PM)?_** any team member - **_How can this work be validated?_** check documentation see that it's updated ",1, my va audit ux improvements update designs docs to use new notification design system component in health care section on my va background per feedback from midpoint review we learned we can use the notification component that angela designed and submitted to the design system it was approved this ticket is to update designs and documentation to indicate use of new notification component instead of warning alert component on my va in the health care section i believe the health care section is the only in line location where the warning alert component is currently used feedback on this topic can be found in these tickets should section tasks update designs sketch files to show new design system notification component instead of warning alert component for in line notifications update fe documentation to show and explain use of new design system notification component instead of warning alert component for in line notifications pm s to make sure corresponding fe tickets not already in flight complete are updated as needed to reflect updated notification component acceptance criteria sketch files and documentation are updated to indicate use of new notification component instead of warning alert component for in line notifications validation who can validate this ticket fe be design pm any team member how can this work be validated check documentation see that it s updated ,1 181675,30723901843.0,IssuesEvent,2023-07-27 18:01:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Copy of Certificate of Eligibility | Display uploaded documents,design Umbrella,"## Value Statement **_As a_** Veteran applying for a home loan **_I want to_** see the documents that I shared when applying for my CoE **_So that_** I can quickly reference them when corresponding with a loan assistant. --- ## Background Context LGY requested this functionality for us cases when a Veteran needs to quickly see what they shared with a loan assistant, so they can identify missing documents easily. ## Acceptance Criteria - [ ] When a Veteran uploads a document, it appears in the appropriate section of the page. - [ ] When a Veteran clicks on an uploaded document, they can view the contents of the document. ## Designs and Build Notes - [Link to previous UX Pin designs](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030/simulate/sitemap) ## Tasks - [ ] Refine internally (Gary and Eugene to review in staging together) - [ ] Discuss use cases with LGY ## Definition of Ready - [ ] Clear value description - [ ] Testable acceptance criteria - [ ] Accessibility added to acceptance criteria - [ ] Approved designs attached - [ ] Sample data provided where appropriate - [ ] Estimated to fit within the sprint - [ ] Dependencies and blockers linked ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Copy of Certificate of Eligibility | Display uploaded documents - ## Value Statement **_As a_** Veteran applying for a home loan **_I want to_** see the documents that I shared when applying for my CoE **_So that_** I can quickly reference them when corresponding with a loan assistant. --- ## Background Context LGY requested this functionality for us cases when a Veteran needs to quickly see what they shared with a loan assistant, so they can identify missing documents easily. ## Acceptance Criteria - [ ] When a Veteran uploads a document, it appears in the appropriate section of the page. - [ ] When a Veteran clicks on an uploaded document, they can view the contents of the document. ## Designs and Build Notes - [Link to previous UX Pin designs](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030/simulate/sitemap) ## Tasks - [ ] Refine internally (Gary and Eugene to review in staging together) - [ ] Discuss use cases with LGY ## Definition of Ready - [ ] Clear value description - [ ] Testable acceptance criteria - [ ] Accessibility added to acceptance criteria - [ ] Approved designs attached - [ ] Sample data provided where appropriate - [ ] Estimated to fit within the sprint - [ ] Dependencies and blockers linked ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,copy of certificate of eligibility display uploaded documents value statement as a veteran applying for a home loan i want to see the documents that i shared when applying for my coe so that i can quickly reference them when corresponding with a loan assistant background context lgy requested this functionality for us cases when a veteran needs to quickly see what they shared with a loan assistant so they can identify missing documents easily acceptance criteria when a veteran uploads a document it appears in the appropriate section of the page when a veteran clicks on an uploaded document they can view the contents of the document designs and build notes tasks refine internally gary and eugene to review in staging together discuss use cases with lgy definition of ready clear value description testable acceptance criteria accessibility added to acceptance criteria approved designs attached sample data provided where appropriate estimated to fit within the sprint dependencies and blockers linked definition of done meets acceptance criteria passed testing coverage passed unit testing coverage passed integration testing if applicable code reviewed internal submitted to staging reviewed and approved by product and or design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 110534,13912624752.0,IssuesEvent,2020-10-20 19:09:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create standardized approach for printer-friendly confirmation page ,design-system-team needs-grooming triage,"### User story(ies) _As a VFS developer, I need to be able to find the standard approach for implementing a printer-friendly confirmation page, so that I can implement a consistent experience. _Example: As a VFS developer, I need to be able to create a custom error message for the XYZ form, so that I can implement the unique error message content that has been approved via the VSP Collaboration Cycle._ ### Additional details/notes/links Printer-friendly confirmation pages have been implemented in various ways. DST should review and create a standard for this feature. ### Acceptance criteria Create and document standard printer-friendly confirmation page component. ### Point(s) of contact - [ ] @cvalarida - [ ] @caw310 ### What type of issue is this? - [ ] Bug - [X] Request new feature - [X] Request update to existing feature - [ ] Documentation change - [ ] Other (please describe) ### How to configure this issue - [ ] When ticket is opened, assign to Epic [#12765 Forms library user feedback and requests to be triaged](https://app.zenhub.com/workspaces/vsp-5cedc9cce6e3335dc5a49fc4/issues/department-of-veterans-affairs/va.gov-team/12765) - [ ] FE Tools team will triage and add to [Design System Governance Process Project Board](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/projects/3) as applicable ",1.0,"Create standardized approach for printer-friendly confirmation page - ### User story(ies) _As a VFS developer, I need to be able to find the standard approach for implementing a printer-friendly confirmation page, so that I can implement a consistent experience. _Example: As a VFS developer, I need to be able to create a custom error message for the XYZ form, so that I can implement the unique error message content that has been approved via the VSP Collaboration Cycle._ ### Additional details/notes/links Printer-friendly confirmation pages have been implemented in various ways. DST should review and create a standard for this feature. ### Acceptance criteria Create and document standard printer-friendly confirmation page component. ### Point(s) of contact - [ ] @cvalarida - [ ] @caw310 ### What type of issue is this? - [ ] Bug - [X] Request new feature - [X] Request update to existing feature - [ ] Documentation change - [ ] Other (please describe) ### How to configure this issue - [ ] When ticket is opened, assign to Epic [#12765 Forms library user feedback and requests to be triaged](https://app.zenhub.com/workspaces/vsp-5cedc9cce6e3335dc5a49fc4/issues/department-of-veterans-affairs/va.gov-team/12765) - [ ] FE Tools team will triage and add to [Design System Governance Process Project Board](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/projects/3) as applicable ",1,create standardized approach for printer friendly confirmation page user story ies as a vfs developer i need to be able to find the standard approach for implementing a printer friendly confirmation page so that i can implement a consistent experience example as a vfs developer i need to be able to create a custom error message for the xyz form so that i can implement the unique error message content that has been approved via the vsp collaboration cycle additional details notes links printer friendly confirmation pages have been implemented in various ways dst should review and create a standard for this feature acceptance criteria create and document standard printer friendly confirmation page component point s of contact cvalarida what type of issue is this bug request new feature request update to existing feature documentation change other please describe how to configure this issue when ticket is opened assign to epic fe tools team will triage and add to as applicable ,1 137624,20178685827.0,IssuesEvent,2022-02-10 16:27:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Discovery: How could we leverage other open source design systems to help improve our component library?,vsp-design-system-team,"## Description We are a relatively small team responsible for building and maintaining a design system for use in pages and applications across VA.gov. We need to make sure that the components, utility classes, design resources, and guidance we create are high quality and well-tested. One option for helping us to do this is to leverage other open source design system resources that are supported by larger teams and are well-used and tested. For this ticket, we'd like to explore what resources are available to us to help improve our component library and evaluate how we might take advantage of them. ## Acceptance Criteria - [ ] Generate list of resources available - [ ] Evaluate how we could leverage those resources to help in building and maintaining our component library - [ ] Add list and evaluations as comment(s) on this ticket.",1.0,"Discovery: How could we leverage other open source design systems to help improve our component library? - ## Description We are a relatively small team responsible for building and maintaining a design system for use in pages and applications across VA.gov. We need to make sure that the components, utility classes, design resources, and guidance we create are high quality and well-tested. One option for helping us to do this is to leverage other open source design system resources that are supported by larger teams and are well-used and tested. For this ticket, we'd like to explore what resources are available to us to help improve our component library and evaluate how we might take advantage of them. ## Acceptance Criteria - [ ] Generate list of resources available - [ ] Evaluate how we could leverage those resources to help in building and maintaining our component library - [ ] Add list and evaluations as comment(s) on this ticket.",1,discovery how could we leverage other open source design systems to help improve our component library description we are a relatively small team responsible for building and maintaining a design system for use in pages and applications across va gov we need to make sure that the components utility classes design resources and guidance we create are high quality and well tested one option for helping us to do this is to leverage other open source design system resources that are supported by larger teams and are well used and tested for this ticket we d like to explore what resources are available to us to help improve our component library and evaluate how we might take advantage of them acceptance criteria generate list of resources available evaluate how we could leverage those resources to help in building and maintaining our component library add list and evaluations as comment s on this ticket ,1 182676,30883647185.0,IssuesEvent,2023-08-03 19:43:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Design | 686c Foreign Address Indicator,686 needs-design stakeholder-request Tree,"## Issue Description There are usually b/w 1-20 dependent claims per day where the system is taking addresses in VBMS and flipping them to be foreign addresses, which then routes the claim to the Pittsburgh claim center (the only center that handles these foreign claims). Research in #66193 uncovered that user error is causing the ""foreign address"" indicator to be added to the claim. Users are selecting that they live on a foreign military base but then entering a domestic address. (See comment from Zack that outlines the situation and suggested approach.) ## Tasks - [ ] Redesign foreign address question in the ""Veteran's Information"" section of the 686c form - [ ] Obtain CAIA approval of change - [ ] Assign to PM who will draft engineering ticket ## Acceptance Criteria - [ ] Wireframe of question redesign ## Current Design ![image.png](https://images.zenhubusercontent.com/64820e3ee0808dee239ecb52/c7312cd4-9925-4de6-bdf9-5e79883e853e) ",1.0,"Design | 686c Foreign Address Indicator - ## Issue Description There are usually b/w 1-20 dependent claims per day where the system is taking addresses in VBMS and flipping them to be foreign addresses, which then routes the claim to the Pittsburgh claim center (the only center that handles these foreign claims). Research in #66193 uncovered that user error is causing the ""foreign address"" indicator to be added to the claim. Users are selecting that they live on a foreign military base but then entering a domestic address. (See comment from Zack that outlines the situation and suggested approach.) ## Tasks - [ ] Redesign foreign address question in the ""Veteran's Information"" section of the 686c form - [ ] Obtain CAIA approval of change - [ ] Assign to PM who will draft engineering ticket ## Acceptance Criteria - [ ] Wireframe of question redesign ## Current Design ![image.png](https://images.zenhubusercontent.com/64820e3ee0808dee239ecb52/c7312cd4-9925-4de6-bdf9-5e79883e853e) ",1,design foreign address indicator issue description there are usually b w dependent claims per day where the system is taking addresses in vbms and flipping them to be foreign addresses which then routes the claim to the pittsburgh claim center the only center that handles these foreign claims research in uncovered that user error is causing the foreign address indicator to be added to the claim users are selecting that they live on a foreign military base but then entering a domestic address see comment from zack that outlines the situation and suggested approach tasks redesign foreign address question in the veteran s information section of the form obtain caia approval of change assign to pm who will draft engineering ticket acceptance criteria wireframe of question redesign current design ,1 103661,12960688269.0,IssuesEvent,2020-07-20 14:41:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,VAOSR Express Care v1.1 - Handle multiple site registrations,VAMF design discovery frontend roadmapOCC vaos,"# Stakeholder input: As a Veteran with multiple site registrations, I need to understand when I am directed to a site that I do not normally use (because they have Express Care enabled) and/or select from multiple sites because Express Care is enabled at 2+ sites that I am registered. ## Goals / Outcomes - Ensure Veterans that are registered at multiple sites and Express Care enabled understand where and why they are request Express Care through that site --- ## Hypothesis or Bet We believe that Veterans who have Express Care enabled at a site they no longer go to will be confused when they receive a call from that site instead of the site they currently seek care from. ## Definition of done ### We handle the use case where a Veteran is registered at multiple sites but only one of those sites has Express Care enabled (even if it's not their preferred site to use) ### We handle the use case where a Veteran is registered at multiple sites and those multiple sites have Express Care enabled ## Issues to create within this Epic - Design mockups for handling flows for these two scenarios - need to account for this on the homepage where we display the date/time window - both active and inactive states - User story - If veteran is registered at one or more VAMC facilities, and only one facility has EC enabled and availability today --- do what? - User story - If veteran is registered at one or more facilities, and more than one facility has EC enabled and available today --- do what? Prompt to select? ",1.0,"VAOSR Express Care v1.1 - Handle multiple site registrations - # Stakeholder input: As a Veteran with multiple site registrations, I need to understand when I am directed to a site that I do not normally use (because they have Express Care enabled) and/or select from multiple sites because Express Care is enabled at 2+ sites that I am registered. ## Goals / Outcomes - Ensure Veterans that are registered at multiple sites and Express Care enabled understand where and why they are request Express Care through that site --- ## Hypothesis or Bet We believe that Veterans who have Express Care enabled at a site they no longer go to will be confused when they receive a call from that site instead of the site they currently seek care from. ## Definition of done ### We handle the use case where a Veteran is registered at multiple sites but only one of those sites has Express Care enabled (even if it's not their preferred site to use) ### We handle the use case where a Veteran is registered at multiple sites and those multiple sites have Express Care enabled ## Issues to create within this Epic - Design mockups for handling flows for these two scenarios - need to account for this on the homepage where we display the date/time window - both active and inactive states - User story - If veteran is registered at one or more VAMC facilities, and only one facility has EC enabled and availability today --- do what? - User story - If veteran is registered at one or more facilities, and more than one facility has EC enabled and available today --- do what? Prompt to select? ",1,vaosr express care handle multiple site registrations stakeholder input as a veteran with multiple site registrations i need to understand when i am directed to a site that i do not normally use because they have express care enabled and or select from multiple sites because express care is enabled at sites that i am registered goals outcomes ensure veterans that are registered at multiple sites and express care enabled understand where and why they are request express care through that site hypothesis or bet we believe that veterans who have express care enabled at a site they no longer go to will be confused when they receive a call from that site instead of the site they currently seek care from definition of done we handle the use case where a veteran is registered at multiple sites but only one of those sites has express care enabled even if it s not their preferred site to use we handle the use case where a veteran is registered at multiple sites and those multiple sites have express care enabled issues to create within this epic design mockups for handling flows for these two scenarios need to account for this on the homepage where we display the date time window both active and inactive states user story if veteran is registered at one or more vamc facilities and only one facility has ec enabled and availability today do what user story if veteran is registered at one or more facilities and more than one facility has ec enabled and available today do what prompt to select ,1 170581,26985133871.0,IssuesEvent,2023-02-09 15:39:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Share grandfathering flow with content teams for feedback,content design login.gov-adoption,"### Problem statement Veterans need to make migrate their DS Logon accounts to Login.gov through grandfathering, which allows them to defer identity proofing. ## Initiative _Let's discuss this when we meet on Friday._ ",1.0,"Share grandfathering flow with content teams for feedback - ### Problem statement Veterans need to make migrate their DS Logon accounts to Login.gov through grandfathering, which allows them to defer identity proofing. ## Initiative _Let's discuss this when we meet on Friday._ ",1,share grandfathering flow with content teams for feedback problem statement veterans need to make migrate their ds logon accounts to login gov through grandfathering which allows them to defer identity proofing initiative let s discuss this when we meet on friday ,1 141167,21419357669.0,IssuesEvent,2022-04-22 14:09:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Determine what form these guidelines should ultimately take: audience, scope, what we hope they take away",service-design,"## Issue Description Determine what form these guidelines should ultimately take: audience, scope, what we hope they take away --- ## Tasks - [ ] Workshop to determine optimal form of guidelines ## Acceptance Criteria - [ ] Alignment on audience and format",1.0,"Determine what form these guidelines should ultimately take: audience, scope, what we hope they take away - ## Issue Description Determine what form these guidelines should ultimately take: audience, scope, what we hope they take away --- ## Tasks - [ ] Workshop to determine optimal form of guidelines ## Acceptance Criteria - [ ] Alignment on audience and format",1,determine what form these guidelines should ultimately take audience scope what we hope they take away issue description determine what form these guidelines should ultimately take audience scope what we hope they take away tasks workshop to determine optimal form of guidelines acceptance criteria alignment on audience and format,1 131515,18295190129.0,IssuesEvent,2021-10-05 19:45:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Profile: Discovery around functionality that allows users to edit contact information without abandoning their task (Part 1),design discovery vsa-authenticated-exp profile planned-work,"## Background We have an existing modal solution, but don’t think that offers the most intuitive or accessible UX. Let's explore how we might allow Veterans to edit contact information without leaving their current task, while considering other uses cases on VA.gov that could help make this a reusable component. [Note from Kevin Hoffman on our slack thread about next steps](https://dsva.slack.com/archives/C909ZG2BB/p1625233376036200?thread_ts=1625082968.005300&cid=C909ZG2BB): > I leave it to the team to determine whether or not to address this pre- or post-launch, IMO, your findings demonstrate that the behavior this is intended to support (modifying data for a contact channel) is a secondary one to the main goal of this tool (modifying notification preferences). Therefore, post-launch makes more sense to me. ## Tasks - [x] Identify where, if at all, we have edit-in-place functionality on VA.gov and learn what we can about how that is working for Veterans - [x] Learn about other profile info edit-in-place use cases (check with Kristen and Kevin RE their needs) ",1.0,"[Design] Profile: Discovery around functionality that allows users to edit contact information without abandoning their task (Part 1) - ## Background We have an existing modal solution, but don’t think that offers the most intuitive or accessible UX. Let's explore how we might allow Veterans to edit contact information without leaving their current task, while considering other uses cases on VA.gov that could help make this a reusable component. [Note from Kevin Hoffman on our slack thread about next steps](https://dsva.slack.com/archives/C909ZG2BB/p1625233376036200?thread_ts=1625082968.005300&cid=C909ZG2BB): > I leave it to the team to determine whether or not to address this pre- or post-launch, IMO, your findings demonstrate that the behavior this is intended to support (modifying data for a contact channel) is a secondary one to the main goal of this tool (modifying notification preferences). Therefore, post-launch makes more sense to me. ## Tasks - [x] Identify where, if at all, we have edit-in-place functionality on VA.gov and learn what we can about how that is working for Veterans - [x] Learn about other profile info edit-in-place use cases (check with Kristen and Kevin RE their needs) ",1, profile discovery around functionality that allows users to edit contact information without abandoning their task part background we have an existing modal solution but don’t think that offers the most intuitive or accessible ux let s explore how we might allow veterans to edit contact information without leaving their current task while considering other uses cases on va gov that could help make this a reusable component i leave it to the team to determine whether or not to address this pre or post launch imo your findings demonstrate that the behavior this is intended to support modifying data for a contact channel is a secondary one to the main goal of this tool modifying notification preferences therefore post launch makes more sense to me tasks identify where if at all we have edit in place functionality on va gov and learn what we can about how that is working for veterans learn about other profile info edit in place use cases check with kristen and kevin re their needs ,1 91109,11463408314.0,IssuesEvent,2020-02-07 15:57:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"MDT- Introduction page- Form introduction page - default state, v1",design vsa vsa-benefits-2,"## User story: As a Veteran interested in reordering medical device resupply items, I need an introduction about the ordering process so I know what to expect before placing my order. ## Tasks: - Create a high fidelity mockup of the order flow introduction page - Upload mockup to Invision and indicate initial focus point as a comment ## Acceptance criteria: - [x] Mockup aligns with VA.gov’s design system - [x] There is an alert notifying the Veteran that they are logged in - [x] The subway map contains all of the steps the Veteran can expect during the order flow - [x] (Optional) Any additional helpful content for the Veteran is included - [x] The screen’s initial focus point is incorporated - [x] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps - content review - design review ## Dependencies: No currently known dependencies ",1.0,"MDT- Introduction page- Form introduction page - default state, v1 - ## User story: As a Veteran interested in reordering medical device resupply items, I need an introduction about the ordering process so I know what to expect before placing my order. ## Tasks: - Create a high fidelity mockup of the order flow introduction page - Upload mockup to Invision and indicate initial focus point as a comment ## Acceptance criteria: - [x] Mockup aligns with VA.gov’s design system - [x] There is an alert notifying the Veteran that they are logged in - [x] The subway map contains all of the steps the Veteran can expect during the order flow - [x] (Optional) Any additional helpful content for the Veteran is included - [x] The screen’s initial focus point is incorporated - [x] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps - content review - design review ## Dependencies: No currently known dependencies ",1,mdt introduction page form introduction page default state user story as a veteran interested in reordering medical device resupply items i need an introduction about the ordering process so i know what to expect before placing my order tasks create a high fidelity mockup of the order flow introduction page upload mockup to invision and indicate initial focus point as a comment acceptance criteria mockup aligns with va gov’s design system there is an alert notifying the veteran that they are logged in the subway map contains all of the steps the veteran can expect during the order flow optional any additional helpful content for the veteran is included the screen’s initial focus point is incorporated sketch artboards are uploaded to invision and linked in this ticket as a comment next steps content review design review dependencies no currently known dependencies ,1 175183,27805679108.0,IssuesEvent,2023-03-17 19:39:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Fix mobile view ""Feedback"" button layout location.",medium-priority team-platform-design-system platform-cop-frontend platform-cop," ### Description At 320 X 520 resolution the Last Updated: div is pushing the feedback button outside of visibility. looks like that div lives in content-build/src/site/includes/last-update.html. Who would I reach out to try and get this fixed? it is occurring here [https://www.va.gov/burials-memorials/pre-need-eligibility/](https://www.va.gov/burials-memorials/pre-need-eligibility/). ### Definition of Done - [ ] button does not overflow - [ ] follows proper style guide ### Original Support Request: https://dsva.slack.com/archives/CBU0KDSB1/p1678733140735639",1.0,"Fix mobile view ""Feedback"" button layout location. - ### Description At 320 X 520 resolution the Last Updated: div is pushing the feedback button outside of visibility. looks like that div lives in content-build/src/site/includes/last-update.html. Who would I reach out to try and get this fixed? it is occurring here [https://www.va.gov/burials-memorials/pre-need-eligibility/](https://www.va.gov/burials-memorials/pre-need-eligibility/). ### Definition of Done - [ ] button does not overflow - [ ] follows proper style guide ### Original Support Request: https://dsva.slack.com/archives/CBU0KDSB1/p1678733140735639",1,fix mobile view feedback button layout location description at x resolution the last updated div is pushing the feedback button outside of visibility looks like that div lives in content build src site includes last update html who would i reach out to try and get this fixed it is occurring here definition of done button does not overflow follows proper style guide original support request ,1 90837,11437632701.0,IssuesEvent,2020-02-05 00:35:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create plan to research user search expectations ,design research vsa vsa-facilities,"## User Story or Problem Statement * As a Veteran, I want Facility Locator search results to be relevant to my location so that I can identify a location close to me which can meet my needs. ## Objectives or Key Results this is meant to further - Improve the Veteran Search Experience (Veterans have the information they need to be prepared for an urgent care visit. ) ## Goals of research Understand Veterans expectations for search results, including the following: - how many results they expect to be returned for a healthcare related search - how that number of search results is impacted by geographic setting (urban/rural) - what geographic area they would expect the map to show by default - how they would expect to interact with the map to change their search results - how facility type impacts expectations - if device (mobile vs desktop) impacts user expectations ## Acceptance Criteria - Expected output is research plan, including a request for recruitment of 10+ participants representing rural **and** urban settings, preferably with a mix of mobile **and** desktop experience. ## Acceptance Criteria [ ] Approved research plan [ ] Approved conversation guide Conduct research [#3897] Synthesis follows in [#4004]",1.0,"Create plan to research user search expectations - ## User Story or Problem Statement * As a Veteran, I want Facility Locator search results to be relevant to my location so that I can identify a location close to me which can meet my needs. ## Objectives or Key Results this is meant to further - Improve the Veteran Search Experience (Veterans have the information they need to be prepared for an urgent care visit. ) ## Goals of research Understand Veterans expectations for search results, including the following: - how many results they expect to be returned for a healthcare related search - how that number of search results is impacted by geographic setting (urban/rural) - what geographic area they would expect the map to show by default - how they would expect to interact with the map to change their search results - how facility type impacts expectations - if device (mobile vs desktop) impacts user expectations ## Acceptance Criteria - Expected output is research plan, including a request for recruitment of 10+ participants representing rural **and** urban settings, preferably with a mix of mobile **and** desktop experience. ## Acceptance Criteria [ ] Approved research plan [ ] Approved conversation guide Conduct research [#3897] Synthesis follows in [#4004]",1,create plan to research user search expectations user story or problem statement as a veteran i want facility locator search results to be relevant to my location so that i can identify a location close to me which can meet my needs objectives or key results this is meant to further improve the veteran search experience veterans have the information they need to be prepared for an urgent care visit goals of research understand veterans expectations for search results including the following how many results they expect to be returned for a healthcare related search how that number of search results is impacted by geographic setting urban rural what geographic area they would expect the map to show by default how they would expect to interact with the map to change their search results how facility type impacts expectations if device mobile vs desktop impacts user expectations acceptance criteria expected output is research plan including a request for recruitment of participants representing rural and urban settings preferably with a mix of mobile and desktop experience acceptance criteria approved research plan approved conversation guide conduct research synthesis follows in ,1 323997,23978163432.0,IssuesEvent,2022-09-13 13:14:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Certificate of Eligibility Ops Template,operations documentation-support pw-footer-feedback other-platform-teams-triage-pct,"### Description I received a request to fill out an OPs template for the **Certificate of Eligibility** service, see here: https://github.com/department-of-veterans-affairs/va.gov-team/issues/34077 I'll comment below with what I was able to put together. Hopefully this is the correct location to share this document, and if now, perhaps you could let me the correct location for it!",1.0,"Certificate of Eligibility Ops Template - ### Description I received a request to fill out an OPs template for the **Certificate of Eligibility** service, see here: https://github.com/department-of-veterans-affairs/va.gov-team/issues/34077 I'll comment below with what I was able to put together. Hopefully this is the correct location to share this document, and if now, perhaps you could let me the correct location for it!",0,certificate of eligibility ops template description i received a request to fill out an ops template for the certificate of eligibility service see here i ll comment below with what i was able to put together hopefully this is the correct location to share this document and if now perhaps you could let me the correct location for it ,0 160133,25108512075.0,IssuesEvent,2022-11-08 18:28:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Publicize the Q4 Platform Satisfaction Survey,service-design,"## Issue Description Share survey's availability in Slack, ToT, and relevant group discussions every few days as needed to ensure participation. # Make sure Content has updated Platform before linking to page ## Tasks - [x] Share Survey in Slack - [x] Add Survey announcement to ToT slide (and share) ## Acceptance Criteria - [x] Survey posted in Slack - [x] Survey posted in ToT slides for active period - [x] Survey reminders are posted in Slack (all-teams, and practice channels) - [x] Survey reminders are sent via DM to small groups",1.0,"Publicize the Q4 Platform Satisfaction Survey - ## Issue Description Share survey's availability in Slack, ToT, and relevant group discussions every few days as needed to ensure participation. # Make sure Content has updated Platform before linking to page ## Tasks - [x] Share Survey in Slack - [x] Add Survey announcement to ToT slide (and share) ## Acceptance Criteria - [x] Survey posted in Slack - [x] Survey posted in ToT slides for active period - [x] Survey reminders are posted in Slack (all-teams, and practice channels) - [x] Survey reminders are sent via DM to small groups",1,publicize the platform satisfaction survey issue description share survey s availability in slack tot and relevant group discussions every few days as needed to ensure participation make sure content has updated platform before linking to page tasks share survey in slack add survey announcement to tot slide and share acceptance criteria survey posted in slack survey posted in tot slides for active period survey reminders are posted in slack all teams and practice channels survey reminders are sent via dm to small groups,1 142335,21717292060.0,IssuesEvent,2022-05-10 19:16:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Tech Debt: Remove SideNav example from Storybook,vsp-design-system-team,"## Description SideNav in Storybook is currently not functional and should be removed until we can create an appropriate web component based off of productions SideNav ie: https://www.va.gov/health-care/eligibility/ ## Related Ticket https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/745#issuecomment-1122584608 ## Acceptance Criteria - [ ] Remove SideNav Storybook story from Component Library",1.0,"Tech Debt: Remove SideNav example from Storybook - ## Description SideNav in Storybook is currently not functional and should be removed until we can create an appropriate web component based off of productions SideNav ie: https://www.va.gov/health-care/eligibility/ ## Related Ticket https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/745#issuecomment-1122584608 ## Acceptance Criteria - [ ] Remove SideNav Storybook story from Component Library",1,tech debt remove sidenav example from storybook description sidenav in storybook is currently not functional and should be removed until we can create an appropriate web component based off of productions sidenav ie related ticket acceptance criteria remove sidenav storybook story from component library,1 116300,14941117228.0,IssuesEvent,2021-01-25 19:16:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Health Record Discovery,design vsa-healthcare-exp,"## Description Beginning to plan and explore the Health Record initiative, including medications, immunizations, and allergies features. ## Tasks - [ ] Think through questions that we have - [ ] Think through knowns - [ ] Think about what internal VA groups we need/want to talk to - [ ] Begin thinking about what questions we want to ask Veterans about ## Acceptance Criteria - [ ] Add any documentation/ideas to https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md ",1.0,"Health Record Discovery - ## Description Beginning to plan and explore the Health Record initiative, including medications, immunizations, and allergies features. ## Tasks - [ ] Think through questions that we have - [ ] Think through knowns - [ ] Think about what internal VA groups we need/want to talk to - [ ] Begin thinking about what questions we want to ask Veterans about ## Acceptance Criteria - [ ] Add any documentation/ideas to https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md ",1,health record discovery description beginning to plan and explore the health record initiative including medications immunizations and allergies features tasks think through questions that we have think through knowns think about what internal va groups we need want to talk to begin thinking about what questions we want to ask veterans about acceptance criteria add any documentation ideas to ,1 118018,15215384702.0,IssuesEvent,2021-02-17 14:21:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] 526: Add a New Disability screen - UX Enhancements,526 design research vsa-benefits,"## User Story or Problem Statement As a designer, I need to ensure that the 'add a new disability' screen is consistent among va.gov patterns and provides the best user experience possible. ![Screen Shot 2021-02-16 at 4.37.42 PM.png](https://images.zenhubusercontent.com/5d65638e0845ad5f24bada4a/3d388810-dc75-44d4-ad5f-9e279d88831b) ### Why we're asking this question Recently, our backend devs [collected some data on drop-off points for the 526 form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/15689#issuecomment-769944735). Among them was a fair amount of drop-offs on the fully developed claim page. After assessing whether or not this was tech or experience design-related, we determined it was likely to be a design question that requires some research and UI edits. Some specific questions to consider: - What patterns should be leveraged for the 'list loop' component we are using to add disabilities? - How can we change language and wording to be easier to understand for the user? - How might we create a better 'autocomplete' functionality for disabilities? - Can we make the list of disabilities easier to use (i.e. better terms)? ## Tasks - [ ] Chat with VBA to understand the business needs around the dropdown list - [ ] Consider other patterns for the addition of new conditions",1.0,"[Design] 526: Add a New Disability screen - UX Enhancements - ## User Story or Problem Statement As a designer, I need to ensure that the 'add a new disability' screen is consistent among va.gov patterns and provides the best user experience possible. ![Screen Shot 2021-02-16 at 4.37.42 PM.png](https://images.zenhubusercontent.com/5d65638e0845ad5f24bada4a/3d388810-dc75-44d4-ad5f-9e279d88831b) ### Why we're asking this question Recently, our backend devs [collected some data on drop-off points for the 526 form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/15689#issuecomment-769944735). Among them was a fair amount of drop-offs on the fully developed claim page. After assessing whether or not this was tech or experience design-related, we determined it was likely to be a design question that requires some research and UI edits. Some specific questions to consider: - What patterns should be leveraged for the 'list loop' component we are using to add disabilities? - How can we change language and wording to be easier to understand for the user? - How might we create a better 'autocomplete' functionality for disabilities? - Can we make the list of disabilities easier to use (i.e. better terms)? ## Tasks - [ ] Chat with VBA to understand the business needs around the dropdown list - [ ] Consider other patterns for the addition of new conditions",1, add a new disability screen ux enhancements user story or problem statement as a designer i need to ensure that the add a new disability screen is consistent among va gov patterns and provides the best user experience possible why we re asking this question recently our backend devs among them was a fair amount of drop offs on the fully developed claim page after assessing whether or not this was tech or experience design related we determined it was likely to be a design question that requires some research and ui edits some specific questions to consider what patterns should be leveraged for the list loop component we are using to add disabilities how can we change language and wording to be easier to understand for the user how might we create a better autocomplete functionality for disabilities can we make the list of disabilities easier to use i e better terms tasks chat with vba to understand the business needs around the dropdown list consider other patterns for the addition of new conditions,1 99018,12393432850.0,IssuesEvent,2020-05-20 15:24:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Mobile navigation documentation,design profile vsa-authenticated-exp,"## Background [Mobile Navigation Markdown Document](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Research/mobile-navigation-research.md) This ticket is related to #8233 Specifically in mobile, participants had a difficult time finding the 'profile menu', and in general were confused about the mobile navigation. Mobile subnavigation should be clearer for the entire logged in experience - this is two-tier solution. First, there should be a short term fix specific to the profile (#8233) followed by a more involved long term solution based on previous research and more comprehensive mobile navigation needs. This is based on [Combine Profile and Account Research Findings](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Research/cpaa-research-findings.md) ##Research Document [Mobile Navigation Research](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Research/mobile-navigation-research.md) ## Tasks - [x] Research other mobile navigation methods across VA.gov - [x] Compile all research into a markdown document - [x] Share with appropriate parties (if applicable) ## Acceptance Criteria - [x] Markdown document has been created ",1.0,"[Design] Mobile navigation documentation - ## Background [Mobile Navigation Markdown Document](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Research/mobile-navigation-research.md) This ticket is related to #8233 Specifically in mobile, participants had a difficult time finding the 'profile menu', and in general were confused about the mobile navigation. Mobile subnavigation should be clearer for the entire logged in experience - this is two-tier solution. First, there should be a short term fix specific to the profile (#8233) followed by a more involved long term solution based on previous research and more comprehensive mobile navigation needs. This is based on [Combine Profile and Account Research Findings](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Research/cpaa-research-findings.md) ##Research Document [Mobile Navigation Research](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Research/mobile-navigation-research.md) ## Tasks - [x] Research other mobile navigation methods across VA.gov - [x] Compile all research into a markdown document - [x] Share with appropriate parties (if applicable) ## Acceptance Criteria - [x] Markdown document has been created ",1, mobile navigation documentation background this ticket is related to specifically in mobile participants had a difficult time finding the profile menu and in general were confused about the mobile navigation mobile subnavigation should be clearer for the entire logged in experience this is two tier solution first there should be a short term fix specific to the profile followed by a more involved long term solution based on previous research and more comprehensive mobile navigation needs this is based on img width alt screen shot at am src research document tasks research other mobile navigation methods across va gov compile all research into a markdown document share with appropriate parties if applicable acceptance criteria markdown document has been created ,1 108309,13613699550.0,IssuesEvent,2020-09-23 12:16:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Healthcare: View your lab and test results ,auth-homepage design needs-grooming vsa-authenticated-exp,"## Background See [Design plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/logged-in-homepage/2.0-redesign/product/LIH-outline-and-timeline.md) Note: link shown conditionally if someone has health care in general ## Tasks - [ ] Visual design exploration - [ ] High fidelity mockups - [ ] Appropriate stakeholder reviews and approvals have been completed ",1.0,"[Design] Healthcare: View your lab and test results - ## Background See [Design plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/logged-in-homepage/2.0-redesign/product/LIH-outline-and-timeline.md) Note: link shown conditionally if someone has health care in general ## Tasks - [ ] Visual design exploration - [ ] High fidelity mockups - [ ] Appropriate stakeholder reviews and approvals have been completed ",1, healthcare view your lab and test results background see note link shown conditionally if someone has health care in general tasks visual design exploration high fidelity mockups appropriate stakeholder reviews and approvals have been completed ,1 171101,27062464313.0,IssuesEvent,2023-02-13 20:58:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Collaboration Cycle for [Modernized Check-in, eCheck-in & Pre-Check-in, Simplified VA Header/Footer]",Epic collaboration-cycle staging-review collab-cycle-review HCE-Checkin design-intent CC-Request," ## VFS product information ### VFS team name Modernized Check-in ### Product name eCheck-in & Pre-Check-in ### Feature name Simplified VA Header/Footer ### GitHub label for product HCE-Checkin ### GitHub label for feature _No response_ ## Kickoff questions
Toggle kickoff questions ### When did/will you start working on this product/feature? December 2022 ### Will your work result in visible changes to the user experience? Yes ### Are you doing research with VA.gov users? Yes ### Will your work involve changes to... Static pages ### Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo? Yes ### Do you need to capture any additional analytics or metrics? No ### Product outline https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/product/README.md ### Notify the Collaboration Cycle team of this ticket in the vfs-platform-support Slack channel. - [X] I acknowledge that I must notify \#vfs-platform-support after submitting this issue. -
## Recommended Collaboration Cycle touchpoints ### Design Intent
Toggle Design Intent #### Before meeting ##### VFS actions - Navigate to reference link: [Design Intent Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent) - [x] Schedule your Design Intent when ready: - Open the [Calendly design intent calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click ""Schedule Event"" - [x] Notify the Collaboration Cycle team of this event with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)) - [x] Link all artifacts **ONLY** in the Design Intent artifacts section below at least two days before the scheduled Design Intent. **Do NOT add artifacts to Comments section** **Design Intent artifacts** - [x] [Wireframe with simplified header/footer and progress bar - segmented (Sketch)](https://www.sketch.com/s/a720996f-5ebb-4092-8e5d-8e3dcff50dc7/prototype/a/E50121F2-F405-46C7-9FE6-8505525F7010) - [x] [Wireframe to show no progress bar because it's fewer than 3 steps (Sketch)](https://www.sketch.com/s/a720996f-5ebb-4092-8e5d-8e3dcff50dc7/prototype/a/29396E62-4DCD-4779-9065-3C69021F930C) - [x] [Wireframe for desktop simplified header/footer (Sketch)](https://www.sketch.com/s/a720996f-5ebb-4092-8e5d-8e3dcff50dc7/a/L0LVoDQ) - [x] [User flow (Mural)](https://app.mural.co/t/vfscie8528/m/vfscie8528/1668453754472/d0ee71372e957dae8b3051726d29e74921e1b417?sender=u83bc52d7fa73658f84f27755) - [ ] Research plan - [x] [Problem Statements.docx](https://app.zenhub.com/files/133843125/ce0fcd91-9cc8-4e39-9881-6bc47ac47360/download) - [x] [Experimental Design Simplified VA Header and Footer request ticket](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1339) - [x] [Experimental Design Progress Bar - Segmented request ticket](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1333) - [x] [Header and footer GA events for patient check in.xlsx](https://app.zenhub.com/files/133843125/f8125ff7-dba9-4842-9421-6c8648593dbd/download) - [x] [Page 10 - Eliminating Veteran Confusion at Check In.pdf](https://app.zenhub.com/files/133843125/d95d096d-afa2-4309-98cf-bb394e2f4802/download) - [x] [Existing prototype without progress bar (for comparison) (Sketch)](https://www.sketch.com/s/e79a827e-42cf-4a82-b554-874c75b5c70e/prototype/a/9F9F9F9F-E205-4F5E-9177-DD4AD750828C) ##### Platform actions - [x] Follow Moderator Responsibilities guidance for Design Intent - [x] Meeting date/time: Monday, Nov 21 @ 330pm ET #### After meeting ##### Platform actions - [ ] If you have feedback, create feedback tickets and link to this epic. Once you have completed you review, check the box next to your practice area - [x] Accessibility has completed the review - [x] Design has completed the review - [ ] IA has completed the review - [x] Update this ticket with the Zoom recording - Recording URL: [Zoom link](https://oddball-io.zoom.us/rec/share/UY1j5Y6wu7VuJAdomkVt00QJh_PU1_V-D0FWcvNcGyjKytktWw77Mm124pf-CFtK.OdGdJy5Gn58QlPZY) - Password: U1SJ?By! ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concerns
### Sitewide Content and IA Intake Request
Toggle Sitewide Content and IA Intake Request ##### VFS actions - [ ] Complete the [sitewide content and IA intake request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Sitewide-Content-and-IA-intake-request.2124906551.html) - [ ] Link to the Sitewide Content and IA Intake Request ticket below
### Research Review
Toggle Research Review #### VFS actions - [x] Complete the [research review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Research-plan-review.1781891143.html) - NOTE: we presented the research at DSC
### Midpoint Review
Toggle Midpoint Review #### Before meeting ##### VFS actions **NOTE: midpoint and design intent were consolidated into one meeting** Navigate to reference link: [Midpoint Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review) - [ ] Schedule your Midpoint Review when ready: - Open the [Calendly midpoint review calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click ""Schedule Event"" - [ ] Check this box if you'd like this review to be asynchronous (Please refer to the [Midpoint Review guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Midpoint-review.1781039167.html) for the difference between a synchronous meeting and an asynchronous review) - [ ] Notify the Collaboration Cycle team of this event with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)) - [ ] Link all artifacts **ONLY** in the Midpoint Review artifacts section below at least two days before the scheduled Midpoint Review. **Do NOT add artifacts to Comments section** **Midpoint Review artifacts** Provide links or documents for the following: - [ ] Finalized design prototype or mockup - [ ] Specify which pages are included in the review - [ ] Research plan - [ ] Conversation guide **Content artifacts** - [ ] Your product’s content source of truth: - [ ] Github ticket for any relevant static content page and entry point updates for tool or feature (if applicable): **IA artifacts** - [ ] Please include a link to any [Sitewide Content & IA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including an IA review document or intake form. **QA artifacts** [Learn more about QA artifacts](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/qa-artifacts.md#test-plan) - [x] Regression test plans (if there isn't already a regression test plan for this feature in TestRailProduct): - [x] Link to test cases/test plan in TestRail (draft OK): - [Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4437) - [Regression Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4440) ##### Platform actions - [ ] Follow Moderator Responsibilities guidance for Midpoint Review - [ ] Meeting date/time: #### After meeting ##### Platform actions - [ ] If you have midpoint review feedback, create feedback ticket and link to this epic. Once you have completed your review, check the box next to your practice area - [ ] Design has completed the review - [ ] Accessibility has completed the review - [ ] IA has completed the review - [ ] Content has completed the review - [ ] QA has completed the review - [ ] Update this ticket with the Zoom recording - Recording URL: - Password: ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concerns
### Analytics Request
Toggle Analytics Request #### VFS actions - [ ] Complete the [analytics request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Analytics-request.1782120453.html) - [ ] Link to the Analytics Implementation and QA Request ticket below
### Contact Center Review
Toggle Contact Center Review #### VFS actions - [ ] Complete the [Contact Center review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Contact-center-review.1782317061.html) - [ ] Link to the Contact Center review request ticket below
### Staging Review
Toggle Staging Review #### Before meeting ##### VFS actions - Navigate to reference link: [Staging Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-review) - [x] Schedule your Staging Review when ready: 02/07/2023 11:30 am - 12:00 pm ET - Open the [Calendly staging review calendar](https://calendly.com/collaboration-cycle/staging-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click ""Schedule Event"" - [x] Notify the Collaboration Cycle team of this event with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)) - [x] If this product contains any [experimental design](https://design.va.gov/experimental-design/), add the `experimental-design` label and schedule a meeting with DSC to present the research findings. [Experimental design ticket ](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1339) - Reviewed on 1/13 at DSC [Pull request for simplified header ](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/pull/1425/commits/50494600ba0829e7305de6d38bc504957223bc74) - Reviewed on 1/20 at DSC [Pull request for simplified footer ](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/pull/1431/commits/22f7b5c090a4138d9eb8af40615105531c5ddac0) - Reviewed on 1/20 at DSC [Test and evaluation plan with Veterans](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/gh/department-of-veterans-affairs/va.gov-team/49895#issuecomment-1398558060) - [x] Link all artifacts **ONLY** in the Staging Review artifacts section below at least four days before the scheduled Staging Review. **Do NOT add artifacts to Comments section** - [x] I confirm the environment is available and test users have been provided. - [x] Please verify your product information in the [Product Directory](https://depo-platform-documentation.scrollhelp.site/getting-started/vfs-product-directory). **Staging Review artifacts** Platform guidance on [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts) **Product artifacts** - [x] Review env URL [The VA simplified header and footer can be reviewed in the review environment](http://d13daffe92166e2dd824118270cf37e4.review.vetsgov-internal/health-care/appointment-check-in/error?error=no-token). Because the VA header and footer code sits outside of our applications, we cannot feature flag or create a staging environment with it enabled for our application. In addition, appointments can not be scheduled to view in the review environment. Therefore, accessing the review environment will show an error message because a unique URL wasn't used to access the application. SOCKS must be enabled to access the [review environment](http://d13daffe92166e2dd824118270cf37e4.review.vetsgov-internal/health-care/appointment-check-in/error?error=no-token). Also, there is an [issue with the review environment ](https://dsva.slack.com/archives/CBU0KDSB1/p1674832178377869) that causes it to get wiped in 1-2 days. If the review environment is not available, please [request a new link in Slack via #check-in-experience](https://dsva.slack.com/archives/C022AC2STBM/p1675437090216129?thread_ts=1675375113.205119&cid=C022AC2STBM), and then we'll update the review environment link in this ticket. This feature is a new version of the VA.gov header and footer. Therefore, this feature can be seen in the wrapper that's present on all pages of our pre-check-in and check-in apps. There have been no user flow, design or content changes to our application as part of this feature. [View video of the simplified header and footer running along with our application in the review environment.]( https://images.zenhubusercontent.com/133843125/552591fc-10c6-40a0-9497-0fe44fec4527/screen_recording_2023_01_31_at_16_36_37.mov) - [x] Staging test user information Staging test users have not been provided because this code is not part of our application. **Note:** Please double-check that you've provided staging access information appropriate for testing the tool or feature. Don't put staging credentials in your va.gov-team ticket; store [test user information, passwords, and tasks](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md) in a .md file in the va.gov-team-sensitive repository. **Content artifacts** - [x] None at this time for this feature **IA artifacts** - [x] Please include a link to any [Sitewide Content & IA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including an IA review document or intake form. No content & IA changes to the PCI app with this feature. **QA artifacts** An artifact that corresponds to each standard in the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards). - [x] [Regression Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4440) - [x] [Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4437) - [x] [Coverage for References](https://dsvavsp.testrail.io/index.php?/reports/view/394) - [x] [Summary(Defects) reports](https://dsvavsp.testrail.io/index.php?/reports/view/393) - [x] E2E tests - day-of: https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in/day-of/tests/e2e - pre-check-in: https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in/pre-check-in/tests/e2e - shared: https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in/tests/e2e/pages - [x] Code coverage | Application | Lines | Functions | Statements | Branches | Link | | - | - | - | - | - | - | | Day-of | 92% | 90% | 92% | 66% | [application folder](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in) ( unit tests are co-located with components, pages) | | Pre-check-in | 67% | 63% | 67% | 56% | [application folder](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in) ( unit tests are co-located with components, pages) | **Accessibility artifacts** - [x] [Completed accessibility testing artifact](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/gh/department-of-veterans-affairs/va.gov-team/52512) ##### Platform actions - [x] Follow Moderator Responsibilities guidance for Staging Review - [ ] Meeting date/time: ~~**Tuesday, January 31 at 11:30AM Eastern**~~ - [ ] Create feedback tickets and link to this epic - [ ] Design feedback provided - [ ] Accessibility feedback provided - [ ] IA feedback provided - [ ] Content feedback provided - [ ] QA feedback provided #### After meeting ##### Platform actions - [ ] Update this ticket with the Zoom recording - Recording URL: - Password: ##### VFS actions - [x] Review feedback tickets and comment on the ticket if there are any questions or concerns - [x] Close individual feedback tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket. - [ ] After launch, [request an accessibility audit from the VA 508 Office](https://depo-platform-documentation.scrollhelp.site/developer-docs/request-support-from-the-va-508-office#RequestsupportfromtheVA508office-AuditRequest). This is required even if no accessibility issues were found during the Staging Review. - [ ] Share ServiceNow ticket number here: ______ - [ ] Close ticket once Privacy, Security, Infrastructure Readiness Review has been completed, VA 508 Office audit is requested, and all other post-Staging actions are complete
### Privacy, Security, Infrastructure Readiness Review
Toggle Privacy, Security, Infrastructure Readiness Review #### VFS actions No changes were made to our application as part of this collab cycle. Therefore, we did not initiate this step. - [ ] Complete the [Privacy, security, infrastructure readiness review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Privacy-and-security-review.1782317101.html) necessary - [ ] Link to the Readiness Review ticket below #### Platform actions - [ ] Privacy, security, infrastructure readiness review is complete
",1.0,"Collaboration Cycle for [Modernized Check-in, eCheck-in & Pre-Check-in, Simplified VA Header/Footer] - ## VFS product information ### VFS team name Modernized Check-in ### Product name eCheck-in & Pre-Check-in ### Feature name Simplified VA Header/Footer ### GitHub label for product HCE-Checkin ### GitHub label for feature _No response_ ## Kickoff questions
Toggle kickoff questions ### When did/will you start working on this product/feature? December 2022 ### Will your work result in visible changes to the user experience? Yes ### Are you doing research with VA.gov users? Yes ### Will your work involve changes to... Static pages ### Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo? Yes ### Do you need to capture any additional analytics or metrics? No ### Product outline https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/product/README.md ### Notify the Collaboration Cycle team of this ticket in the vfs-platform-support Slack channel. - [X] I acknowledge that I must notify \#vfs-platform-support after submitting this issue. -
## Recommended Collaboration Cycle touchpoints ### Design Intent
Toggle Design Intent #### Before meeting ##### VFS actions - Navigate to reference link: [Design Intent Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/design-intent) - [x] Schedule your Design Intent when ready: - Open the [Calendly design intent calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click ""Schedule Event"" - [x] Notify the Collaboration Cycle team of this event with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)) - [x] Link all artifacts **ONLY** in the Design Intent artifacts section below at least two days before the scheduled Design Intent. **Do NOT add artifacts to Comments section** **Design Intent artifacts** - [x] [Wireframe with simplified header/footer and progress bar - segmented (Sketch)](https://www.sketch.com/s/a720996f-5ebb-4092-8e5d-8e3dcff50dc7/prototype/a/E50121F2-F405-46C7-9FE6-8505525F7010) - [x] [Wireframe to show no progress bar because it's fewer than 3 steps (Sketch)](https://www.sketch.com/s/a720996f-5ebb-4092-8e5d-8e3dcff50dc7/prototype/a/29396E62-4DCD-4779-9065-3C69021F930C) - [x] [Wireframe for desktop simplified header/footer (Sketch)](https://www.sketch.com/s/a720996f-5ebb-4092-8e5d-8e3dcff50dc7/a/L0LVoDQ) - [x] [User flow (Mural)](https://app.mural.co/t/vfscie8528/m/vfscie8528/1668453754472/d0ee71372e957dae8b3051726d29e74921e1b417?sender=u83bc52d7fa73658f84f27755) - [ ] Research plan - [x] [Problem Statements.docx](https://app.zenhub.com/files/133843125/ce0fcd91-9cc8-4e39-9881-6bc47ac47360/download) - [x] [Experimental Design Simplified VA Header and Footer request ticket](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1339) - [x] [Experimental Design Progress Bar - Segmented request ticket](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1333) - [x] [Header and footer GA events for patient check in.xlsx](https://app.zenhub.com/files/133843125/f8125ff7-dba9-4842-9421-6c8648593dbd/download) - [x] [Page 10 - Eliminating Veteran Confusion at Check In.pdf](https://app.zenhub.com/files/133843125/d95d096d-afa2-4309-98cf-bb394e2f4802/download) - [x] [Existing prototype without progress bar (for comparison) (Sketch)](https://www.sketch.com/s/e79a827e-42cf-4a82-b554-874c75b5c70e/prototype/a/9F9F9F9F-E205-4F5E-9177-DD4AD750828C) ##### Platform actions - [x] Follow Moderator Responsibilities guidance for Design Intent - [x] Meeting date/time: Monday, Nov 21 @ 330pm ET #### After meeting ##### Platform actions - [ ] If you have feedback, create feedback tickets and link to this epic. Once you have completed you review, check the box next to your practice area - [x] Accessibility has completed the review - [x] Design has completed the review - [ ] IA has completed the review - [x] Update this ticket with the Zoom recording - Recording URL: [Zoom link](https://oddball-io.zoom.us/rec/share/UY1j5Y6wu7VuJAdomkVt00QJh_PU1_V-D0FWcvNcGyjKytktWw77Mm124pf-CFtK.OdGdJy5Gn58QlPZY) - Password: U1SJ?By! ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concerns
### Sitewide Content and IA Intake Request
Toggle Sitewide Content and IA Intake Request ##### VFS actions - [ ] Complete the [sitewide content and IA intake request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Sitewide-Content-and-IA-intake-request.2124906551.html) - [ ] Link to the Sitewide Content and IA Intake Request ticket below
### Research Review
Toggle Research Review #### VFS actions - [x] Complete the [research review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Research-plan-review.1781891143.html) - NOTE: we presented the research at DSC
### Midpoint Review
Toggle Midpoint Review #### Before meeting ##### VFS actions **NOTE: midpoint and design intent were consolidated into one meeting** Navigate to reference link: [Midpoint Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/midpoint-review) - [ ] Schedule your Midpoint Review when ready: - Open the [Calendly midpoint review calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click ""Schedule Event"" - [ ] Check this box if you'd like this review to be asynchronous (Please refer to the [Midpoint Review guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Midpoint-review.1781039167.html) for the difference between a synchronous meeting and an asynchronous review) - [ ] Notify the Collaboration Cycle team of this event with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)) - [ ] Link all artifacts **ONLY** in the Midpoint Review artifacts section below at least two days before the scheduled Midpoint Review. **Do NOT add artifacts to Comments section** **Midpoint Review artifacts** Provide links or documents for the following: - [ ] Finalized design prototype or mockup - [ ] Specify which pages are included in the review - [ ] Research plan - [ ] Conversation guide **Content artifacts** - [ ] Your product’s content source of truth: - [ ] Github ticket for any relevant static content page and entry point updates for tool or feature (if applicable): **IA artifacts** - [ ] Please include a link to any [Sitewide Content & IA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including an IA review document or intake form. **QA artifacts** [Learn more about QA artifacts](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/qa-artifacts.md#test-plan) - [x] Regression test plans (if there isn't already a regression test plan for this feature in TestRailProduct): - [x] Link to test cases/test plan in TestRail (draft OK): - [Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4437) - [Regression Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4440) ##### Platform actions - [ ] Follow Moderator Responsibilities guidance for Midpoint Review - [ ] Meeting date/time: #### After meeting ##### Platform actions - [ ] If you have midpoint review feedback, create feedback ticket and link to this epic. Once you have completed your review, check the box next to your practice area - [ ] Design has completed the review - [ ] Accessibility has completed the review - [ ] IA has completed the review - [ ] Content has completed the review - [ ] QA has completed the review - [ ] Update this ticket with the Zoom recording - Recording URL: - Password: ##### VFS actions - [ ] Review feedback tickets and comment on the ticket if there are any questions or concerns
### Analytics Request
Toggle Analytics Request #### VFS actions - [ ] Complete the [analytics request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Analytics-request.1782120453.html) - [ ] Link to the Analytics Implementation and QA Request ticket below
### Contact Center Review
Toggle Contact Center Review #### VFS actions - [ ] Complete the [Contact Center review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Contact-center-review.1782317061.html) - [ ] Link to the Contact Center review request ticket below
### Staging Review
Toggle Staging Review #### Before meeting ##### VFS actions - Navigate to reference link: [Staging Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-review) - [x] Schedule your Staging Review when ready: 02/07/2023 11:30 am - 12:00 pm ET - Open the [Calendly staging review calendar](https://calendly.com/collaboration-cycle/staging-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click ""Schedule Event"" - [x] Notify the Collaboration Cycle team of this event with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)) - [x] If this product contains any [experimental design](https://design.va.gov/experimental-design/), add the `experimental-design` label and schedule a meeting with DSC to present the research findings. [Experimental design ticket ](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1339) - Reviewed on 1/13 at DSC [Pull request for simplified header ](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/pull/1425/commits/50494600ba0829e7305de6d38bc504957223bc74) - Reviewed on 1/20 at DSC [Pull request for simplified footer ](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/pull/1431/commits/22f7b5c090a4138d9eb8af40615105531c5ddac0) - Reviewed on 1/20 at DSC [Test and evaluation plan with Veterans](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/gh/department-of-veterans-affairs/va.gov-team/49895#issuecomment-1398558060) - [x] Link all artifacts **ONLY** in the Staging Review artifacts section below at least four days before the scheduled Staging Review. **Do NOT add artifacts to Comments section** - [x] I confirm the environment is available and test users have been provided. - [x] Please verify your product information in the [Product Directory](https://depo-platform-documentation.scrollhelp.site/getting-started/vfs-product-directory). **Staging Review artifacts** Platform guidance on [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts) **Product artifacts** - [x] Review env URL [The VA simplified header and footer can be reviewed in the review environment](http://d13daffe92166e2dd824118270cf37e4.review.vetsgov-internal/health-care/appointment-check-in/error?error=no-token). Because the VA header and footer code sits outside of our applications, we cannot feature flag or create a staging environment with it enabled for our application. In addition, appointments can not be scheduled to view in the review environment. Therefore, accessing the review environment will show an error message because a unique URL wasn't used to access the application. SOCKS must be enabled to access the [review environment](http://d13daffe92166e2dd824118270cf37e4.review.vetsgov-internal/health-care/appointment-check-in/error?error=no-token). Also, there is an [issue with the review environment ](https://dsva.slack.com/archives/CBU0KDSB1/p1674832178377869) that causes it to get wiped in 1-2 days. If the review environment is not available, please [request a new link in Slack via #check-in-experience](https://dsva.slack.com/archives/C022AC2STBM/p1675437090216129?thread_ts=1675375113.205119&cid=C022AC2STBM), and then we'll update the review environment link in this ticket. This feature is a new version of the VA.gov header and footer. Therefore, this feature can be seen in the wrapper that's present on all pages of our pre-check-in and check-in apps. There have been no user flow, design or content changes to our application as part of this feature. [View video of the simplified header and footer running along with our application in the review environment.]( https://images.zenhubusercontent.com/133843125/552591fc-10c6-40a0-9497-0fe44fec4527/screen_recording_2023_01_31_at_16_36_37.mov) - [x] Staging test user information Staging test users have not been provided because this code is not part of our application. **Note:** Please double-check that you've provided staging access information appropriate for testing the tool or feature. Don't put staging credentials in your va.gov-team ticket; store [test user information, passwords, and tasks](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md) in a .md file in the va.gov-team-sensitive repository. **Content artifacts** - [x] None at this time for this feature **IA artifacts** - [x] Please include a link to any [Sitewide Content & IA](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/sitewide-content-and-ia-intake-request) feedback you received, including an IA review document or intake form. No content & IA changes to the PCI app with this feature. **QA artifacts** An artifact that corresponds to each standard in the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards). - [x] [Regression Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4440) - [x] [Test Plan](https://dsvavsp.testrail.io/index.php?/plans/view/4437) - [x] [Coverage for References](https://dsvavsp.testrail.io/index.php?/reports/view/394) - [x] [Summary(Defects) reports](https://dsvavsp.testrail.io/index.php?/reports/view/393) - [x] E2E tests - day-of: https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in/day-of/tests/e2e - pre-check-in: https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in/pre-check-in/tests/e2e - shared: https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in/tests/e2e/pages - [x] Code coverage | Application | Lines | Functions | Statements | Branches | Link | | - | - | - | - | - | - | | Day-of | 92% | 90% | 92% | 66% | [application folder](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in) ( unit tests are co-located with components, pages) | | Pre-check-in | 67% | 63% | 67% | 56% | [application folder](https://github.com/department-of-veterans-affairs/vets-website/tree/main/src/applications/check-in) ( unit tests are co-located with components, pages) | **Accessibility artifacts** - [x] [Completed accessibility testing artifact](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/gh/department-of-veterans-affairs/va.gov-team/52512) ##### Platform actions - [x] Follow Moderator Responsibilities guidance for Staging Review - [ ] Meeting date/time: ~~**Tuesday, January 31 at 11:30AM Eastern**~~ - [ ] Create feedback tickets and link to this epic - [ ] Design feedback provided - [ ] Accessibility feedback provided - [ ] IA feedback provided - [ ] Content feedback provided - [ ] QA feedback provided #### After meeting ##### Platform actions - [ ] Update this ticket with the Zoom recording - Recording URL: - Password: ##### VFS actions - [x] Review feedback tickets and comment on the ticket if there are any questions or concerns - [x] Close individual feedback tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket. - [ ] After launch, [request an accessibility audit from the VA 508 Office](https://depo-platform-documentation.scrollhelp.site/developer-docs/request-support-from-the-va-508-office#RequestsupportfromtheVA508office-AuditRequest). This is required even if no accessibility issues were found during the Staging Review. - [ ] Share ServiceNow ticket number here: ______ - [ ] Close ticket once Privacy, Security, Infrastructure Readiness Review has been completed, VA 508 Office audit is requested, and all other post-Staging actions are complete
### Privacy, Security, Infrastructure Readiness Review
Toggle Privacy, Security, Infrastructure Readiness Review #### VFS actions No changes were made to our application as part of this collab cycle. Therefore, we did not initiate this step. - [ ] Complete the [Privacy, security, infrastructure readiness review process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Privacy-and-security-review.1782317101.html) necessary - [ ] Link to the Readiness Review ticket below #### Platform actions - [ ] Privacy, security, infrastructure readiness review is complete
",1,collaboration cycle for if your product is already on va gov please verify your product information in the product directory the product information in the product directory is accurate vfs product information vfs team name modernized check in product name echeck in pre check in feature name simplified va header footer github label for product hce checkin github label for feature no response kickoff questions toggle kickoff questions when did will you start working on this product feature december will your work result in visible changes to the user experience yes are you doing research with va gov users yes will your work involve changes to static pages does your product feature have google analytics tracking and a kpi dashboard in domo yes do you need to capture any additional analytics or metrics no product outline notify the collaboration cycle team of this ticket in the vfs platform support slack channel i acknowledge that i must notify vfs platform support after submitting this issue recommended collaboration cycle touchpoints design intent toggle design intent before meeting vfs actions navigate to reference link schedule your design intent when ready open the select a date and time and click “confirm” add your name and email click add guests and enter the vfs meeting attendees email addresses invite all relevant vfs team members including accessibility support product owners and other va stakeholders click schedule event notify the collaboration cycle team of this event with scheduled date time in vfs platform support link all artifacts only in the design intent artifacts section below at least two days before the scheduled design intent do not add artifacts to comments section design intent artifacts research plan platform actions follow moderator responsibilities guidance for design intent meeting date time monday nov et after meeting platform actions if you have feedback create feedback tickets and link to this epic once you have completed you review check the box next to your practice area accessibility has completed the review design has completed the review ia has completed the review update this ticket with the zoom recording recording url password by vfs actions review feedback tickets and comment on the ticket if there are any questions or concerns sitewide content and ia intake request toggle sitewide content and ia intake request vfs actions complete the link to the sitewide content and ia intake request ticket below research review toggle research review vfs actions complete the note we presented the research at dsc midpoint review toggle midpoint review before meeting vfs actions note midpoint and design intent were consolidated into one meeting navigate to reference link schedule your midpoint review when ready open the select a date and time and click “confirm” add your name and email click add guests and enter the vfs meeting attendees email addresses invite all relevant vfs team members including accessibility support product owners and other va stakeholders click schedule event check this box if you d like this review to be asynchronous please refer to the for the difference between a synchronous meeting and an asynchronous review notify the collaboration cycle team of this event with scheduled date time in vfs platform support link all artifacts only in the midpoint review artifacts section below at least two days before the scheduled midpoint review do not add artifacts to comments section midpoint review artifacts provide links or documents for the following finalized design prototype or mockup specify which pages are included in the review research plan conversation guide content artifacts your product’s content source of truth github ticket for any relevant static content page and entry point updates for tool or feature if applicable ia artifacts please include a link to any feedback you received including an ia review document or intake form qa artifacts regression test plans if there isn t already a regression test plan for this feature in testrailproduct link to test cases test plan in testrail draft ok platform actions follow moderator responsibilities guidance for midpoint review meeting date time after meeting platform actions if you have midpoint review feedback create feedback ticket and link to this epic once you have completed your review check the box next to your practice area design has completed the review accessibility has completed the review ia has completed the review content has completed the review qa has completed the review update this ticket with the zoom recording recording url password vfs actions review feedback tickets and comment on the ticket if there are any questions or concerns analytics request toggle analytics request vfs actions complete the link to the analytics implementation and qa request ticket below contact center review toggle contact center review vfs actions complete the link to the contact center review request ticket below staging review toggle staging review before meeting vfs actions navigate to reference link schedule your staging review when ready am pm et open the select a date and time and click “confirm” add your name and email click add guests and enter the vfs meeting attendees email addresses invite all relevant vfs team members including accessibility support product owners and other va stakeholders click schedule event notify the collaboration cycle team of this event with scheduled date time in vfs platform support if this product contains any add the experimental design label and schedule a meeting with dsc to present the research findings experimental design ticket reviewed on at dsc pull request for simplified header reviewed on at dsc pull request for simplified footer reviewed on at dsc link all artifacts only in the staging review artifacts section below at least four days before the scheduled staging review do not add artifacts to comments section i confirm the environment is available and test users have been provided please verify your product information in the staging review artifacts platform guidance on product artifacts review env url because the va header and footer code sits outside of our applications we cannot feature flag or create a staging environment with it enabled for our application in addition appointments can not be scheduled to view in the review environment therefore accessing the review environment will show an error message because a unique url wasn t used to access the application socks must be enabled to access the also there is an that causes it to get wiped in days if the review environment is not available please and then we ll update the review environment link in this ticket this feature is a new version of the va gov header and footer therefore this feature can be seen in the wrapper that s present on all pages of our pre check in and check in apps there have been no user flow design or content changes to our application as part of this feature staging test user information staging test users have not been provided because this code is not part of our application note please double check that you ve provided staging access information appropriate for testing the tool or feature don t put staging credentials in your va gov team ticket store  in a md file in the va gov team sensitive repository content artifacts none at this time for this feature ia artifacts please include a link to any feedback you received including an ia review document or intake form no content ia changes to the pci app with this feature qa artifacts an artifact that corresponds to each standard in the tests day of pre check in shared code coverage application lines functions statements branches link day of unit tests are co located with components pages pre check in unit tests are co located with components pages accessibility artifacts platform actions follow moderator responsibilities guidance for staging review meeting date time tuesday january at eastern create feedback tickets and link to this epic design feedback provided accessibility feedback provided ia feedback provided content feedback provided qa feedback provided after meeting platform actions update this ticket with the zoom recording recording url password vfs actions review feedback tickets and comment on the ticket if there are any questions or concerns close individual feedback tickets when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment on the issue ticket after launch this is required even if no accessibility issues were found during the staging review share servicenow ticket number here close ticket once privacy security infrastructure readiness review has been completed va office audit is requested and all other post staging actions are complete privacy security infrastructure readiness review toggle privacy security infrastructure readiness review vfs actions no changes were made to our application as part of this collab cycle therefore we did not initiate this step complete the necessary link to the readiness review ticket below platform actions privacy security infrastructure readiness review is complete ,1 85169,10593895681.0,IssuesEvent,2019-10-09 15:40:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Discovery] Claim Status Tool - Research Synthesis - Affinity Mapping Session,design discovery vsa-benefits,"## Goal Take key quotes and observations and move them into general categories (and subcategories). ## Acceptance Criteria - [ ] Create Mural board to start Affinity Mapping - [ ] Add all quotes and observations to synthesis - affinity mapping - spreadsheet - [ ] Group/categorize key quotes and observations",1.0,"[Discovery] Claim Status Tool - Research Synthesis - Affinity Mapping Session - ## Goal Take key quotes and observations and move them into general categories (and subcategories). ## Acceptance Criteria - [ ] Create Mural board to start Affinity Mapping - [ ] Add all quotes and observations to synthesis - affinity mapping - spreadsheet - [ ] Group/categorize key quotes and observations",1, claim status tool research synthesis affinity mapping session goal take key quotes and observations and move them into general categories and subcategories acceptance criteria create mural board to start affinity mapping add all quotes and observations to synthesis affinity mapping spreadsheet group categorize key quotes and observations,1 136109,19705200821.0,IssuesEvent,2022-01-12 21:05:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Modal web component: development,vsp-design-system-team,"## Description Build a web-component version of our [Modal React component](https://github.com/department-of-veterans-affairs/component-library/tree/master/packages/react-components/src/components/Modal). ## Details Styles: https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/blob/8ce0431d342a5be24170d9329e19257eb6e678db/packages/formation/sass/modules/_m-modal.scss This component makes use of the `react-focus-on` library to manage focus states. See #33489 for notes on how to implement this without React. ## Acceptance Criteria - [ ] `va-modal` is written - [ ] E2E tests are written - [ ] component is checked for accessibility issues - [ ] Alert Carol that component is ready for staging review - [ ] Address any staging review comments - [ ] Merge component",1.0,"Modal web component: development - ## Description Build a web-component version of our [Modal React component](https://github.com/department-of-veterans-affairs/component-library/tree/master/packages/react-components/src/components/Modal). ## Details Styles: https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/blob/8ce0431d342a5be24170d9329e19257eb6e678db/packages/formation/sass/modules/_m-modal.scss This component makes use of the `react-focus-on` library to manage focus states. See #33489 for notes on how to implement this without React. ## Acceptance Criteria - [ ] `va-modal` is written - [ ] E2E tests are written - [ ] component is checked for accessibility issues - [ ] Alert Carol that component is ready for staging review - [ ] Address any staging review comments - [ ] Merge component",1,modal web component development description build a web component version of our details styles this component makes use of the react focus on library to manage focus states see for notes on how to implement this without react acceptance criteria va modal is written tests are written component is checked for accessibility issues alert carol that component is ready for staging review address any staging review comments merge component,1 118938,15380429180.0,IssuesEvent,2021-03-02 21:05:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,508-enhancement [MOBILE DESIGN]: Consider conducting mobile screen reader research with iOS users,508-enhancement 508-issue-mobile-design 508-issue-screenreader 508/Accessibility needs research,"## Feedback framework - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix. ## Point of Contact **VFS Point of Contact:** _Josh, Angela, Trevor_ ## User Story or Problem Statement As a researcher, I want to better understand how mobile screen reader users interact with typeahead searches. ## Details Our typeahead implementation requires users to touch the input and re-establish focus (away from the keypad) before they can swipe right to listen to options. I think it's worth setting up research sessions to determine if users understand this paradigm and iterate as necessary. ## Acceptance Criteria - [ ] Research participants are [selected from an inclusive audience](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/accessibility/research/inclusive-research-recommendations.md#guidelines-for-inclusive-research-recruiting) - [ ] 5-7 user research sessions are conducted - [ ] Research is documented and synthesized with other a11y specialists ",1.0,"508-enhancement [MOBILE DESIGN]: Consider conducting mobile screen reader research with iOS users - ## Feedback framework - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix. ## Point of Contact **VFS Point of Contact:** _Josh, Angela, Trevor_ ## User Story or Problem Statement As a researcher, I want to better understand how mobile screen reader users interact with typeahead searches. ## Details Our typeahead implementation requires users to touch the input and re-establish focus (away from the keypad) before they can swipe right to listen to options. I think it's worth setting up research sessions to determine if users understand this paradigm and iterate as necessary. ## Acceptance Criteria - [ ] Research participants are [selected from an inclusive audience](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/accessibility/research/inclusive-research-recommendations.md#guidelines-for-inclusive-research-recruiting) - [ ] 5-7 user research sessions are conducted - [ ] Research is documented and synthesized with other a11y specialists ",1, enhancement consider conducting mobile screen reader research with ios users feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact josh angela trevor user story or problem statement as a researcher i want to better understand how mobile screen reader users interact with typeahead searches details our typeahead implementation requires users to touch the input and re establish focus away from the keypad before they can swipe right to listen to options i think it s worth setting up research sessions to determine if users understand this paradigm and iterate as necessary acceptance criteria research participants are user research sessions are conducted research is documented and synthesized with other specialists ,1 141930,21641245402.0,IssuesEvent,2022-05-05 19:01:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Consider moving breadcrumbs and adding a My VA button in profile,design vsa-authenticated-exp,"Since we are updating the nametag in profile to match the nametag in MyVA, we need to consider if we need to update the rest of the elements to be consistent with MyVA. Specifically this includes: - moving where the breadcrumbs to be below the nametag - And adding a My VA button All changes are shown in the screenshot below. ![Screen Shot 2021-01-21 at 10.13.07 AM.png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/60bcf007-dbe5-4563-8f10-a7726fc53214)",1.0,"Consider moving breadcrumbs and adding a My VA button in profile - Since we are updating the nametag in profile to match the nametag in MyVA, we need to consider if we need to update the rest of the elements to be consistent with MyVA. Specifically this includes: - moving where the breadcrumbs to be below the nametag - And adding a My VA button All changes are shown in the screenshot below. ![Screen Shot 2021-01-21 at 10.13.07 AM.png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/60bcf007-dbe5-4563-8f10-a7726fc53214)",1,consider moving breadcrumbs and adding a my va button in profile since we are updating the nametag in profile to match the nametag in myva we need to consider if we need to update the rest of the elements to be consistent with myva specifically this includes moving where the breadcrumbs to be below the nametag and adding a my va button all changes are shown in the screenshot below ,1 144790,22550428463.0,IssuesEvent,2022-06-27 04:34:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,QA Feedback - Staging Review - Design System Team - Text area web component,collaboration-cycle staging-review vsp-design-system-team governance-team collab-cycle-feedback Staging,"## VFS acceptance criteria - [ ] Let Platform know when the **Must** feedback has been incorporated - [ ] Leave any comments for feedback you decide _not_ to take - [ ] VFS team closes the ticket Feedback for https://github.com/department-of-veterans-affairs/va.gov-team/issues/42520 **Comments:** None ## Feedback - **Must** = the feedback must be applied - **Should** = the feedback is best practice - **Consider** = suggestions/enhancements **Must:** None **Should:** None **Consider:** - Zero and negative values can be entered for the `maxlength` property. Consider limiting this to only positive values.",1.0,"QA Feedback - Staging Review - Design System Team - Text area web component - ## VFS acceptance criteria - [ ] Let Platform know when the **Must** feedback has been incorporated - [ ] Leave any comments for feedback you decide _not_ to take - [ ] VFS team closes the ticket Feedback for https://github.com/department-of-veterans-affairs/va.gov-team/issues/42520 **Comments:** None ## Feedback - **Must** = the feedback must be applied - **Should** = the feedback is best practice - **Consider** = suggestions/enhancements **Must:** None **Should:** None **Consider:** - Zero and negative values can be entered for the `maxlength` property. Consider limiting this to only positive values.",1,qa feedback staging review design system team text area web component vfs acceptance criteria let platform know when the must feedback has been incorporated leave any comments for feedback you decide not to take vfs team closes the ticket feedback for comments none feedback must the feedback must be applied should the feedback is best practice consider suggestions enhancements must none should none consider zero and negative values can be entered for the maxlength property consider limiting this to only positive values ,1 160762,25228413423.0,IssuesEvent,2022-11-14 17:41:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] MyHealth: Medical Records: Surfacing requirements,design my-health my-health-MR-CORE,"## :star2: User Story - As a designer, I want to create a centralized place (i.e. Mural) where all the valuable information gathered from discovery research (interviews, technical discovery, accessibility audit) so it can be used to inform the strategic design brief and Medical Records design work. ## :star2: Related Documentation - Link documents here; remember to update if they change. ## :star2: Description Create a centralized place (i.e. Mural) where all the valuable information gathered from discovery research (interviews, technical discovery, accessibility audit) ## :star2: Tasks - [x] Create Mural (with discovery interviews, technical conversations sections) - [x] Use Mural to inform the first draft of the strategic brief ## :star2: Acceptance Criteria - [ ]
## 🌟 How to configure this issue - [x] Confirm this issue is being added to the correct team (ex. Core or MHV) and Product (ex. Secure Messaging) board - [x] Add App Name (ex. Secure Messaging) and Task Name to Issue Title ⬆️ - [x] Fill in User Story ⬆️ - [x] Link to any Related Documentation if appropriate, and remember to update if they change ⬆️ - [x] Fill in Description ⬆️ - [x] Add/remove Tasks as needed ⬆️ - [x] Add/remove Acceptance Criteria as needed ⬆️ - [x] Attach any Dependency stories, indiating whether this is a blocker, or is being blocked - [x] If work is in progress, change Pipeline to In Progress :arrow_right: - [x] Add any necessary labels not automatically included. If this is unplanned work, add the `unplanned work` label :arrow_right: - [x] If work is in progress, add Assignee(s) in addition to PM :arrow_right: - [x] If Sprint is known, select it at the right :arrow_right: - [ ] If work has been sized, add story points :arrow_right: - [x] Attach to an Epic (what body of work is this a part of?) :arrow_right: ",1.0,"[DESIGN] MyHealth: Medical Records: Surfacing requirements - ## :star2: User Story - As a designer, I want to create a centralized place (i.e. Mural) where all the valuable information gathered from discovery research (interviews, technical discovery, accessibility audit) so it can be used to inform the strategic design brief and Medical Records design work. ## :star2: Related Documentation - Link documents here; remember to update if they change. ## :star2: Description Create a centralized place (i.e. Mural) where all the valuable information gathered from discovery research (interviews, technical discovery, accessibility audit) ## :star2: Tasks - [x] Create Mural (with discovery interviews, technical conversations sections) - [x] Use Mural to inform the first draft of the strategic brief ## :star2: Acceptance Criteria - [ ]
## 🌟 How to configure this issue - [x] Confirm this issue is being added to the correct team (ex. Core or MHV) and Product (ex. Secure Messaging) board - [x] Add App Name (ex. Secure Messaging) and Task Name to Issue Title ⬆️ - [x] Fill in User Story ⬆️ - [x] Link to any Related Documentation if appropriate, and remember to update if they change ⬆️ - [x] Fill in Description ⬆️ - [x] Add/remove Tasks as needed ⬆️ - [x] Add/remove Acceptance Criteria as needed ⬆️ - [x] Attach any Dependency stories, indiating whether this is a blocker, or is being blocked - [x] If work is in progress, change Pipeline to In Progress :arrow_right: - [x] Add any necessary labels not automatically included. If this is unplanned work, add the `unplanned work` label :arrow_right: - [x] If work is in progress, add Assignee(s) in addition to PM :arrow_right: - [x] If Sprint is known, select it at the right :arrow_right: - [ ] If work has been sized, add story points :arrow_right: - [x] Attach to an Epic (what body of work is this a part of?) :arrow_right: ",1, myhealth medical records surfacing requirements user story as a designer i want to create a centralized place i e mural where all the valuable information gathered from discovery research interviews technical discovery accessibility audit so it can be used to inform the strategic design brief and medical records design work related documentation link documents here remember to update if they change description create a centralized place i e mural where all the valuable information gathered from discovery research interviews technical discovery accessibility audit tasks create mural with discovery interviews technical conversations sections use mural to inform the first draft of the strategic brief acceptance criteria 🌟 how to configure this issue confirm this issue is being added to the correct team ex core or mhv and product ex secure messaging board add app name ex secure messaging and task name to issue title ⬆️ fill in user story ⬆️ link to any related documentation if appropriate and remember to update if they change ⬆️ fill in description ⬆️ add remove tasks as needed ⬆️ add remove acceptance criteria as needed ⬆️ attach any dependency stories indiating whether this is a blocker or is being blocked if work is in progress change pipeline to in progress arrow right add any necessary labels not automatically included if this is unplanned work add the unplanned work label arrow right if work is in progress add assignee s in addition to pm arrow right if sprint is known select it at the right arrow right if work has been sized add story points arrow right attach to an epic what body of work is this a part of arrow right ,1 130288,18062068299.0,IssuesEvent,2021-09-20 14:56:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Gather initial set of Platform Orientation content,service-design Orientation vsp-product-support,"## Issue Description The information shared at Platform Orientation is vast. However, it may not be the full scope of information VFS teams need, and sometimes information may be duplicated across parties (ex: design orientation overlaps with general orientation). The goal of this ticket is to ​define all of the content that should be included in Platform Orientation. --- ## Tasks - [ ] Collect content from existing sources (parentheses indicates owner): - [General Orientation slide deck ](https://docs.google.com/presentation/d/1xZMmHtsa65fJ1nMMfFC2PWFBDhBmBWmx1EqQQlPdsVc/edit?usp=sharing) - [Design Orientation slide deck] (https://docs.google.com/presentation/d/1gSeffl2STubvPDH9EoB-wUE2Al73wAwsG9QPQQU6eqw/edit#slide=id.p1) - [BE Tools Orientation slide deck](https://docs.google.com/presentation/d/1SvXyF3Y2khQQlKpqJFI8g62HfOdx93ckPA0xiwYyjwc/edit?usp=sharing) - FE Tools Orientation - [Onboarding for VFS teams] (https://docs.google.com/document/d/1JUp0Nm6NEJfZOt822U7lV2xJdGyLgqF2OIbkX79gFZA/edit) - [FE Tools, Technical Onboarding] (https://docs.google.com/document/d/19C8T0C0pPRgkv_O3RyELVC-qXX8JdXC_XDrXMNtGczk/edit) - [FE Tools, Organizational Onboarding] (https://docs.google.com/document/d/1JUp0Nm6NEJfZOt822U7lV2xJdGyLgqF2OIbkX79gFZA/edit) - [Accessibility orientation slide deck] (https://docs.google.com/presentation/d/1rJLur5iIB0H47JVoTTUKd39U6TbvP12KbxICXgXNu0w/edit#slide=id.p4) - [QA orientation slide deck] (https://docs.google.com/presentation/d/1D6QFNd5NsPhbc7JHD7zvFkJ_y1irvJ6yP9WSQkiyLnY/edit) - [Analytics Orientation slide deck](https://docs.google.com/presentation/d/1TKYK88pHqNAJ0HrGtXIjnDYPQT-ccBQcOTy64kd0cd4/edit#slide=id.g5f29ec5fc2_4_71) - [Analytics Getting Started page](https://vfs.atlassian.net/wiki/spaces/AT/pages/1771864128/WIP+-+Getting+started+with+Platform+Analytics+Insights) - CMS Orientation - [Non-Technical Repo] (https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms) - [Technical Repo] (https://github.com/department-of-veterans-affairs/va.gov-cms) - [New Team VSP Orientation Epic Template](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=&labels=&template=orientation-epic.md&title=New+Team+VSP+Orientation) - [Platform Orientation Research](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1717403694/Platform+Orientation+Research) (@rebekahickey ) - [Platform Orientation Improvements 2021 Q3](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1626224014681/c8d9fc08366d488190a7fcfba099a2f885dc5b93?sender=u0574179b1d97118ccc0e3591) (@rebekahickey) - Slack Workflow Support data analysis (@jchasia-adhoc ) - [Requests from new VFS team members in June/July](https://docs.google.com/spreadsheets/d/1rfOXfOwP4rLXF49eKRb9kOWBpHn0fe1b0sh-FoTOov8/edit?usp=sharing) ( @rebekahickey ) - [VSA team orientation] (https://app.zenhub.com/files/133843125/9934acd7-a4b0-474b-aba4-109c493908ad/download) - [ ] add all subjects/topics to MURAL board - [ ] group like items ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1.0,"Gather initial set of Platform Orientation content - ## Issue Description The information shared at Platform Orientation is vast. However, it may not be the full scope of information VFS teams need, and sometimes information may be duplicated across parties (ex: design orientation overlaps with general orientation). The goal of this ticket is to ​define all of the content that should be included in Platform Orientation. --- ## Tasks - [ ] Collect content from existing sources (parentheses indicates owner): - [General Orientation slide deck ](https://docs.google.com/presentation/d/1xZMmHtsa65fJ1nMMfFC2PWFBDhBmBWmx1EqQQlPdsVc/edit?usp=sharing) - [Design Orientation slide deck] (https://docs.google.com/presentation/d/1gSeffl2STubvPDH9EoB-wUE2Al73wAwsG9QPQQU6eqw/edit#slide=id.p1) - [BE Tools Orientation slide deck](https://docs.google.com/presentation/d/1SvXyF3Y2khQQlKpqJFI8g62HfOdx93ckPA0xiwYyjwc/edit?usp=sharing) - FE Tools Orientation - [Onboarding for VFS teams] (https://docs.google.com/document/d/1JUp0Nm6NEJfZOt822U7lV2xJdGyLgqF2OIbkX79gFZA/edit) - [FE Tools, Technical Onboarding] (https://docs.google.com/document/d/19C8T0C0pPRgkv_O3RyELVC-qXX8JdXC_XDrXMNtGczk/edit) - [FE Tools, Organizational Onboarding] (https://docs.google.com/document/d/1JUp0Nm6NEJfZOt822U7lV2xJdGyLgqF2OIbkX79gFZA/edit) - [Accessibility orientation slide deck] (https://docs.google.com/presentation/d/1rJLur5iIB0H47JVoTTUKd39U6TbvP12KbxICXgXNu0w/edit#slide=id.p4) - [QA orientation slide deck] (https://docs.google.com/presentation/d/1D6QFNd5NsPhbc7JHD7zvFkJ_y1irvJ6yP9WSQkiyLnY/edit) - [Analytics Orientation slide deck](https://docs.google.com/presentation/d/1TKYK88pHqNAJ0HrGtXIjnDYPQT-ccBQcOTy64kd0cd4/edit#slide=id.g5f29ec5fc2_4_71) - [Analytics Getting Started page](https://vfs.atlassian.net/wiki/spaces/AT/pages/1771864128/WIP+-+Getting+started+with+Platform+Analytics+Insights) - CMS Orientation - [Non-Technical Repo] (https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/cms) - [Technical Repo] (https://github.com/department-of-veterans-affairs/va.gov-cms) - [New Team VSP Orientation Epic Template](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=&labels=&template=orientation-epic.md&title=New+Team+VSP+Orientation) - [Platform Orientation Research](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1717403694/Platform+Orientation+Research) (@rebekahickey ) - [Platform Orientation Improvements 2021 Q3](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1626224014681/c8d9fc08366d488190a7fcfba099a2f885dc5b93?sender=u0574179b1d97118ccc0e3591) (@rebekahickey) - Slack Workflow Support data analysis (@jchasia-adhoc ) - [Requests from new VFS team members in June/July](https://docs.google.com/spreadsheets/d/1rfOXfOwP4rLXF49eKRb9kOWBpHn0fe1b0sh-FoTOov8/edit?usp=sharing) ( @rebekahickey ) - [VSA team orientation] (https://app.zenhub.com/files/133843125/9934acd7-a4b0-474b-aba4-109c493908ad/download) - [ ] add all subjects/topics to MURAL board - [ ] group like items ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1,gather initial set of platform orientation content issue description the information shared at platform orientation is vast however it may not be the full scope of information vfs teams need and sometimes information may be duplicated across parties ex design orientation overlaps with general orientation the goal of this ticket is to ​define all of the content that should be included in platform orientation tasks collect content from existing sources parentheses indicates owner fe tools orientation cms orientation rebekahickey rebekahickey slack workflow support data analysis jchasia adhoc rebekahickey add all subjects topics to mural board group like items acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 131165,18244448785.0,IssuesEvent,2021-10-01 16:28:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] Update check-in poster based upon Phase 2 usability and Martinsburg visit findings,design vsa-healthcare-exp HCE-Checkin HealthExp - Planned,"Based upon the research findings from the Martinsburg visit ([draft research report](https://dsva.slack.com/archives/C022AC2STBM/p1631824953375300)) and Phase 2 Usability study ([Synthesis document - report coming soon](https://app.mural.co/t/vsa8243/m/vsa8243/1629923298341/3f6e350a2b322a4c77a92b30ae0dac25e42439d5?sender=uc940f53ad96ac0203d6d3631)), the following UX/UI updates are recommended to be made to the poster: ## Tasks - [ ] Explore new visuals to highlight starting with a text and that a link will be coming through. - [ ] Create new wording to highlight that Veterans should wait for a link to appear to complete check-in. - Review with Danielle Thierry (site-wide content). - [ ] Create final version in Illustrator for the following size posters: 8.5X11, 11X17, 24X36 - [ ] Determine need to usability test this new version. ## Acceptance Criteria - [ ] Post to [GitHub](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/health-care/checkin/design/visual-collateral). Don't override the original designs until we usability test this version.",1.0,"[DESIGN] Update check-in poster based upon Phase 2 usability and Martinsburg visit findings - Based upon the research findings from the Martinsburg visit ([draft research report](https://dsva.slack.com/archives/C022AC2STBM/p1631824953375300)) and Phase 2 Usability study ([Synthesis document - report coming soon](https://app.mural.co/t/vsa8243/m/vsa8243/1629923298341/3f6e350a2b322a4c77a92b30ae0dac25e42439d5?sender=uc940f53ad96ac0203d6d3631)), the following UX/UI updates are recommended to be made to the poster: ## Tasks - [ ] Explore new visuals to highlight starting with a text and that a link will be coming through. - [ ] Create new wording to highlight that Veterans should wait for a link to appear to complete check-in. - Review with Danielle Thierry (site-wide content). - [ ] Create final version in Illustrator for the following size posters: 8.5X11, 11X17, 24X36 - [ ] Determine need to usability test this new version. ## Acceptance Criteria - [ ] Post to [GitHub](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/health-care/checkin/design/visual-collateral). Don't override the original designs until we usability test this version.",1, update check in poster based upon phase usability and martinsburg visit findings based upon the research findings from the martinsburg visit and phase usability study the following ux ui updates are recommended to be made to the poster tasks explore new visuals to highlight starting with a text and that a link will be coming through create new wording to highlight that veterans should wait for a link to appear to complete check in review with danielle thierry site wide content create final version in illustrator for the following size posters determine need to usability test this new version acceptance criteria post to don t override the original designs until we usability test this version ,1 108650,13645072664.0,IssuesEvent,2020-09-25 20:04:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Show different error alert text when we cannot connect to MPI,content design profile ux vsa-authenticated-exp,"Currently if we are unable to connect to MPI/MVI, when we show the Profile we treat the user as though they aren't even in MPI, when the reality is we can't even tell if they are or not. If we cannot even connect to MPI, I think we should: - still block users from most Profile sections, as though they are not in MPI - show an error alert, like we do if they aren't in MPI, but modify the text to make it clear that the issue is we couldn't connect to MPI, _not_ that we couldn't find them in MPI For reference, this is the error we are showing in either case: ![image](https://user-images.githubusercontent.com/20728956/91222904-b1e12900-e6d4-11ea-9f84-89340769e138.png) More background in [this ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/12727) ## Tasks - [ ] Change error alert content to be more accurate",1.0,"[Design] Show different error alert text when we cannot connect to MPI - Currently if we are unable to connect to MPI/MVI, when we show the Profile we treat the user as though they aren't even in MPI, when the reality is we can't even tell if they are or not. If we cannot even connect to MPI, I think we should: - still block users from most Profile sections, as though they are not in MPI - show an error alert, like we do if they aren't in MPI, but modify the text to make it clear that the issue is we couldn't connect to MPI, _not_ that we couldn't find them in MPI For reference, this is the error we are showing in either case: ![image](https://user-images.githubusercontent.com/20728956/91222904-b1e12900-e6d4-11ea-9f84-89340769e138.png) More background in [this ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/12727) ## Tasks - [ ] Change error alert content to be more accurate",1, show different error alert text when we cannot connect to mpi currently if we are unable to connect to mpi mvi when we show the profile we treat the user as though they aren t even in mpi when the reality is we can t even tell if they are or not if we cannot even connect to mpi i think we should still block users from most profile sections as though they are not in mpi show an error alert like we do if they aren t in mpi but modify the text to make it clear that the issue is we couldn t connect to mpi not that we couldn t find them in mpi for reference this is the error we are showing in either case more background in tasks change error alert content to be more accurate,1 54947,14078444758.0,IssuesEvent,2020-11-04 13:34:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[MOBILE DESIGN]: GIBCT EYB - Responsive tables SHOULD have HTML updated for better mobile presentation,508-defect-3 508-issue-semantic-markup 508/Accessibility Awaiting Feedback BAH-EYB bug,"# [508-defect-3](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-3) **Feedback framework** - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Point of Contact **VFS Point of Contact:** _Trevor_ ## User Story or Problem Statement As a mobile user, I want to see a header for the responsive table rows, so I understand what each data point means. ## Details The responsive table that's deployed on the GIBCT needs a couple of modifications to be fully inline with the recommended version that will become a design system component. Specifically: 1. The `tbody > tr > th` needs a `role=""rowheader""` attribute 1. The `tbody > tr > th` needs a `` added that is hidden at desktop size, and shown at mobile size ## Acceptance Criteria - [ ] Code is updated to match the HTML snippet and [comment on 13825](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13825#issuecomment-700810625) from VSA specialist - [ ] DFN labels are appearing at mobile sizes - [ ] HTML validates in the W3C validator - [ ] Zero axe-core violations are shown ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix. ## Environment * https://staging.va.gov/gi-bill-comparison-tool/profile/11006124 or any other profile view that has the responsive table ## Solution (if known) ```diff - ... + + SMC letter designation + SMC-K Monthly payment (in U.S. $)110.31 How this payment variation worksIf you qualify for SMC-K, we add this rate to your basic disability compensation rate for any disability rating from 0% to 100%. We also add this rate to all SMC basic rates except SMC-O, SMC-Q, and SMC-R. You may receive 1 to 3 SMC-K awards in addition to basic and SMC rates. ``` ## Screenshots or Trace Logs ![Screen Shot 2020-10-05 at 3 54 30 PM](https://user-images.githubusercontent.com/934879/95131939-91b97680-0724-11eb-8bbd-29ec6c5ad24e.png) ",1.0,"[MOBILE DESIGN]: GIBCT EYB - Responsive tables SHOULD have HTML updated for better mobile presentation - # [508-defect-3](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-3) **Feedback framework** - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Point of Contact **VFS Point of Contact:** _Trevor_ ## User Story or Problem Statement As a mobile user, I want to see a header for the responsive table rows, so I understand what each data point means. ## Details The responsive table that's deployed on the GIBCT needs a couple of modifications to be fully inline with the recommended version that will become a design system component. Specifically: 1. The `tbody > tr > th` needs a `role=""rowheader""` attribute 1. The `tbody > tr > th` needs a `` added that is hidden at desktop size, and shown at mobile size ## Acceptance Criteria - [ ] Code is updated to match the HTML snippet and [comment on 13825](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13825#issuecomment-700810625) from VSA specialist - [ ] DFN labels are appearing at mobile sizes - [ ] HTML validates in the W3C validator - [ ] Zero axe-core violations are shown ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix. ## Environment * https://staging.va.gov/gi-bill-comparison-tool/profile/11006124 or any other profile view that has the responsive table ## Solution (if known) ```diff - ... + + SMC letter designation + SMC-K Monthly payment (in U.S. $)110.31 How this payment variation worksIf you qualify for SMC-K, we add this rate to your basic disability compensation rate for any disability rating from 0% to 100%. We also add this rate to all SMC basic rates except SMC-O, SMC-Q, and SMC-R. You may receive 1 to 3 SMC-K awards in addition to basic and SMC rates. ``` ## Screenshots or Trace Logs ![Screen Shot 2020-10-05 at 3 54 30 PM](https://user-images.githubusercontent.com/934879/95131939-91b97680-0724-11eb-8bbd-29ec6c5ad24e.png) ",0, gibct eyb responsive tables should have html updated for better mobile presentation enter an issue title using the format brief description of the problem edit buttons need aria label for context add another user link will not receive keyboard focus heading levels should increase by one error messages should be more specific blue button on blue background does not have sufficient contrast ratio feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements point of contact vfs point of contact trevor user story or problem statement as a mobile user i want to see a header for the responsive table rows so i understand what each data point means details the responsive table that s deployed on the gibct needs a couple of modifications to be fully inline with the recommended version that will become a design system component specifically the tbody tr th needs a role rowheader attribute the tbody tr th needs a added that is hidden at desktop size and shown at mobile size acceptance criteria code is updated to match the html snippet and from vsa specialist dfn labels are appearing at mobile sizes html validates in the validator zero axe core violations are shown definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix environment or any other profile view that has the responsive table solution if known diff smc letter designation smc k monthly payment in nbsp u s nbsp how this payment variation works if you qualify for smc k we add this rate to your basic disability compensation rate for any disability rating from to we also add this rate to all smc basic rates except smc o smc q and smc r you may receive to smc k awards in addition to basic and smc rates screenshots or trace logs ,0 126658,17092382920.0,IssuesEvent,2021-07-08 19:22:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Style va-alert so it doesn't rely on formation.css,vsp-design-system-team,"## Issue Description Currently, the styles implicitly rely on formation.css to show up properly, but that shouldn't be a peer dependency. Specifically, the font-awesome icon for the close button doesn't show up without the formation stylesheet.",1.0,"Style va-alert so it doesn't rely on formation.css - ## Issue Description Currently, the styles implicitly rely on formation.css to show up properly, but that shouldn't be a peer dependency. Specifically, the font-awesome icon for the close button doesn't show up without the formation stylesheet.",1,style va alert so it doesn t rely on formation css issue description currently the styles implicitly rely on formation css to show up properly but that shouldn t be a peer dependency specifically the font awesome icon for the close button doesn t show up without the formation stylesheet ,1 91259,11489889274.0,IssuesEvent,2020-02-11 16:12:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Caregiver Usability Research Synthesis ,design research vsa-caregiver,"## User Story As the Caregiver team, we need to understand how to build the Caregiver application in the way most helpful to our uses. ## Tasks Synthesize information gleaned from Caregiver usability research sessions ## Acceptance Criteria [ ] Research readout summary which includes findings, recommendations, additional questions",1.0,"Caregiver Usability Research Synthesis - ## User Story As the Caregiver team, we need to understand how to build the Caregiver application in the way most helpful to our uses. ## Tasks Synthesize information gleaned from Caregiver usability research sessions ## Acceptance Criteria [ ] Research readout summary which includes findings, recommendations, additional questions",1,caregiver usability research synthesis user story as the caregiver team we need to understand how to build the caregiver application in the way most helpful to our uses tasks synthesize information gleaned from caregiver usability research sessions acceptance criteria research readout summary which includes findings recommendations additional questions,1 120465,15768981285.0,IssuesEvent,2021-03-31 17:49:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Migrate sketch templates to starter page in Sketch cloud,vsp-design-system-team,"Templates to bring over - [ ] Blank templates - [ ] Sign in templates - [ ] Modal templates - [ ] Blank form templates - [ ] Benefit templates - eligibility - [ ] Benefit templates - how to apply - [ ] Benefit templates - apply now - [ ] Benefit templates - after you apply ",1.0,"Migrate sketch templates to starter page in Sketch cloud - Templates to bring over - [ ] Blank templates - [ ] Sign in templates - [ ] Modal templates - [ ] Blank form templates - [ ] Benefit templates - eligibility - [ ] Benefit templates - how to apply - [ ] Benefit templates - apply now - [ ] Benefit templates - after you apply ",1,migrate sketch templates to starter page in sketch cloud templates to bring over blank templates sign in templates modal templates blank form templates benefit templates eligibility benefit templates how to apply benefit templates apply now benefit templates after you apply ,1 115220,14704950939.0,IssuesEvent,2021-01-04 17:17:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Create LOA1 Design (MyVA Dashboard),design my-va-dashboard needs-grooming vsa-authenticated-exp,"## Background We need to create the design for LOA1 users. ## Tasks - [ ] Create LOA1 design - [ ] Review with Matt/Samara",1.0,"[Design] Create LOA1 Design (MyVA Dashboard) - ## Background We need to create the design for LOA1 users. ## Tasks - [ ] Create LOA1 design - [ ] Review with Matt/Samara",1, create design myva dashboard background we need to create the design for users tasks create design review with matt samara,1 171196,27082172823.0,IssuesEvent,2023-02-14 14:43:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Update internal instructions for running the Survey each quarter.,service-design,"## Purpose Because we are changing the survey, we need to update our own guide on running it. ## Tasks - [ ] archive previous page. - [ ] update [existing page](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1445724309/How-to+Launch+the+Platform+Satisfaction+Survey#Conduct-Synthesis) w/ new instructions regarding synthesis of results. ## Acceptance Criteria - [ ] Site reflects updated process ",1.0,"Update internal instructions for running the Survey each quarter. - ## Purpose Because we are changing the survey, we need to update our own guide on running it. ## Tasks - [ ] archive previous page. - [ ] update [existing page](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1445724309/How-to+Launch+the+Platform+Satisfaction+Survey#Conduct-Synthesis) w/ new instructions regarding synthesis of results. ## Acceptance Criteria - [ ] Site reflects updated process ",1,update internal instructions for running the survey each quarter purpose because we are changing the survey we need to update our own guide on running it tasks archive previous page update w new instructions regarding synthesis of results acceptance criteria site reflects updated process ,1 237078,19592294694.0,IssuesEvent,2022-01-05 14:15:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Google Analytics: Create GA Derived User Activity Visualization,VSP-testing-team 2021-Q4,"## User Story _As a VFS product stakeholder, I would like to have a dashboard card that will display the number of events triggered over a period of time by my application. This would give a good indication of how easily interactable our applications are and if users are finding their way around it easy enough. It also could indicate struggles to use an application if a simple application has more events than anticipated._ ## Tasks - [ ] Create a Domo Dashboard Card that reflects the number of events triggered, broken down by application, over a selected time period * This data requires the prior Google Analytics data task to be completed first. The data source for this should already exist in Domo. * This card should support filtering by application. * If possible, it'd be ideal to allow the filtering to be applied via clicking any of the bars to show a single application view, in addition to top-of-page filtering. ## Acceptance Criteria - [ ] _A dashboard card exists reflecting the number of events triggered, over a period of time, broken down by application on va.gov_",1.0,"Google Analytics: Create GA Derived User Activity Visualization - ## User Story _As a VFS product stakeholder, I would like to have a dashboard card that will display the number of events triggered over a period of time by my application. This would give a good indication of how easily interactable our applications are and if users are finding their way around it easy enough. It also could indicate struggles to use an application if a simple application has more events than anticipated._ ## Tasks - [ ] Create a Domo Dashboard Card that reflects the number of events triggered, broken down by application, over a selected time period * This data requires the prior Google Analytics data task to be completed first. The data source for this should already exist in Domo. * This card should support filtering by application. * If possible, it'd be ideal to allow the filtering to be applied via clicking any of the bars to show a single application view, in addition to top-of-page filtering. ## Acceptance Criteria - [ ] _A dashboard card exists reflecting the number of events triggered, over a period of time, broken down by application on va.gov_",0,google analytics create ga derived user activity visualization user story as a vfs product stakeholder i would like to have a dashboard card that will display the number of events triggered over a period of time by my application this would give a good indication of how easily interactable our applications are and if users are finding their way around it easy enough it also could indicate struggles to use an application if a simple application has more events than anticipated tasks create a domo dashboard card that reflects the number of events triggered broken down by application over a selected time period this data requires the prior google analytics data task to be completed first the data source for this should already exist in domo this card should support filtering by application if possible it d be ideal to allow the filtering to be applied via clicking any of the bars to show a single application view in addition to top of page filtering acceptance criteria a dashboard card exists reflecting the number of events triggered over a period of time broken down by application on va gov ,0 132789,18763500153.0,IssuesEvent,2021-11-05 19:35:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Resize poster,design ux vsa-healthcare-exp HCE-Checkin,"## Description We need to resize the poster for 24 X 36 and letter. The resizing should incorporate the changes from #32438. # Tasks - [ ] Create PDF # Acceptance Criteria - [ ] Post to GitHub page ",1.0,"[Design] Resize poster - ## Description We need to resize the poster for 24 X 36 and letter. The resizing should incorporate the changes from #32438. # Tasks - [ ] Create PDF # Acceptance Criteria - [ ] Post to GitHub page ",1, resize poster description we need to resize the poster for x and letter the resizing should incorporate the changes from tasks create pdf acceptance criteria post to github page ,1 96673,12149478160.0,IssuesEvent,2020-04-24 16:13:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Logged-in homepage: Notifications audit,auth-homepage design notifications personalization-2.0 vsa-authenticated-exp,"## Backgrounds We need to figure out what kind of status updates/alerts that we could show on a new logged-in homepage. We should first focus on the data we already have access to, but we could also include updates we'd like to show if we decide that's a good use of time. ## Tasks - [ ] Create audit of notification/status updates/alerts we could show on VA.gov today. - [ ] If time, note additional alerts we'd like to show. ## Acceptance criteria - [ ] Audit is complete.",1.0,"[Design] Logged-in homepage: Notifications audit - ## Backgrounds We need to figure out what kind of status updates/alerts that we could show on a new logged-in homepage. We should first focus on the data we already have access to, but we could also include updates we'd like to show if we decide that's a good use of time. ## Tasks - [ ] Create audit of notification/status updates/alerts we could show on VA.gov today. - [ ] If time, note additional alerts we'd like to show. ## Acceptance criteria - [ ] Audit is complete.",1, logged in homepage notifications audit backgrounds we need to figure out what kind of status updates alerts that we could show on a new logged in homepage we should first focus on the data we already have access to but we could also include updates we d like to show if we decide that s a good use of time tasks create audit of notification status updates alerts we could show on va gov today if time note additional alerts we d like to show acceptance criteria audit is complete ,1 87932,11012261947.0,IssuesEvent,2019-12-04 17:53:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Design Intent,NOD design vsa-benefits,"## User Story: As a designer on the BaM team, I need clearly define the design intent for Notice of Disagreement so that I can drill down further in design of individual steps of the form. ## Tasks - [ ] Create a design intent ## Acceptance Criteria: - [ ] Design intent created",1.0,"[Design] Design Intent - ## User Story: As a designer on the BaM team, I need clearly define the design intent for Notice of Disagreement so that I can drill down further in design of individual steps of the form. ## Tasks - [ ] Create a design intent ## Acceptance Criteria: - [ ] Design intent created",1, design intent user story as a designer on the bam team i need clearly define the design intent for notice of disagreement so that i can drill down further in design of individual steps of the form tasks create a design intent acceptance criteria design intent created,1 93066,11737872293.0,IssuesEvent,2020-03-11 15:15:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Refine 686 Mockup Content,design vsa vsa-ebenefits,"## Goal Now that we have received feedback from various places, we need to insert those recommendations in to the mockups. ## Tasks - Implement the recommendations from the usability sessions - Refine and revise the content for the intro screen, the form workflows, inline guidance and confirmation page. - Have the changes reviewed by Peggy ## Acceptance Criteria - [ ] Mockups have been updated - [ ] Peggy has been updated for review - [ ] A list of the changes are noted in a .MD file in GH",1.0,"Refine 686 Mockup Content - ## Goal Now that we have received feedback from various places, we need to insert those recommendations in to the mockups. ## Tasks - Implement the recommendations from the usability sessions - Refine and revise the content for the intro screen, the form workflows, inline guidance and confirmation page. - Have the changes reviewed by Peggy ## Acceptance Criteria - [ ] Mockups have been updated - [ ] Peggy has been updated for review - [ ] A list of the changes are noted in a .MD file in GH",1,refine mockup content goal now that we have received feedback from various places we need to insert those recommendations in to the mockups tasks implement the recommendations from the usability sessions refine and revise the content for the intro screen the form workflows inline guidance and confirmation page have the changes reviewed by peggy acceptance criteria mockups have been updated peggy has been updated for review a list of the changes are noted in a md file in gh,1 116882,15024813657.0,IssuesEvent,2021-02-01 20:10:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[UI]: Completed Tabs Defaults to Past Three Months,design vsa-healthcare-exp,"## User Story - As a Veteran, I want to know that I'm only seeing the past 3 months of completed questionnaires to start. (Default on the completed tab) ## Related Documentation - [MVP: Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) ## Description > What will the team get at the end of this ticket? A wireframes set of the completed tab showing the default is set to three months as well as how to change the time period will be delivered with the technical specifications needed for engineering to implement said feature. ## Tasks - [ ] Review this functionality in VAOS - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product/team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Published mockup link exists and it is added/updated within the product feature outline",1.0,"[UI]: Completed Tabs Defaults to Past Three Months - ## User Story - As a Veteran, I want to know that I'm only seeing the past 3 months of completed questionnaires to start. (Default on the completed tab) ## Related Documentation - [MVP: Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) ## Description > What will the team get at the end of this ticket? A wireframes set of the completed tab showing the default is set to three months as well as how to change the time period will be delivered with the technical specifications needed for engineering to implement said feature. ## Tasks - [ ] Review this functionality in VAOS - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product/team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Published mockup link exists and it is added/updated within the product feature outline",1, completed tabs defaults to past three months user story as a veteran i want to know that i m only seeing the past months of completed questionnaires to start default on the completed tab related documentation description what will the team get at the end of this ticket a wireframes set of the completed tab showing the default is set to three months as well as how to change the time period will be delivered with the technical specifications needed for engineering to implement said feature tasks review this functionality in vaos finalize detailed mockup and callouts of link to prototype acceptance criteria ui review meeting with product team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above published mockup link exists and it is added updated within the product feature outline,1 182256,30822642420.0,IssuesEvent,2023-08-01 17:29:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[AFTER RESEARCH] SPIKE - Do we want to Allow Check in Text when No Appointments/Tasks,design ux HCE-Checkin,"## Questions When the Veterans texts ""check in"" but has no appointments for which to check in, do we want to still allow them to get to the unified experience and see their appointments and see that they have no tasks to complete right now. ## Description It's possible that at launch of the MVP that we're still supporting Veteran's texting ""check in"" to 53079. So, knowing that that's a possibility and, for the moment, let's assume a UUID is returned, what are the wireframes that are needed? Think through the different scenarios: - What if there are appts for today? - What if there are no appts for today? Likely, we need to create another version of our expired alert. ## Tasks - [ ] Think through this scenario and decide if we want to pursue it - [ ] Create f/u tickets if needed ",1.0,"[AFTER RESEARCH] SPIKE - Do we want to Allow Check in Text when No Appointments/Tasks - ## Questions When the Veterans texts ""check in"" but has no appointments for which to check in, do we want to still allow them to get to the unified experience and see their appointments and see that they have no tasks to complete right now. ## Description It's possible that at launch of the MVP that we're still supporting Veteran's texting ""check in"" to 53079. So, knowing that that's a possibility and, for the moment, let's assume a UUID is returned, what are the wireframes that are needed? Think through the different scenarios: - What if there are appts for today? - What if there are no appts for today? Likely, we need to create another version of our expired alert. ## Tasks - [ ] Think through this scenario and decide if we want to pursue it - [ ] Create f/u tickets if needed ",1, spike do we want to allow check in text when no appointments tasks questions when the veterans texts check in but has no appointments for which to check in do we want to still allow them to get to the unified experience and see their appointments and see that they have no tasks to complete right now description it s possible that at launch of the mvp that we re still supporting veteran s texting check in to so knowing that that s a possibility and for the moment let s assume a uuid is returned what are the wireframes that are needed think through the different scenarios what if there are appts for today what if there are no appts for today likely we need to create another version of our expired alert tasks think through this scenario and decide if we want to pursue it create f u tickets if needed ,1 168330,26631661927.0,IssuesEvent,2023-01-24 18:20:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Research Likert scale use for updated Survey,service-design,"## Issue Description Given the discussions and learnings of previous tickets, perform a quick desk research effort on the Likert scale's utility for our Survey purposes. Research [notes](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2491383911/Quant+Measure+Options+Likert+Scales+and+Others#How-does-the-above-inform-what-we-are-trying-to-measure%3F) ## Tasks - [x] Review usefulness - [x] If useful, provide guidance on how to implement ## Acceptance Criteria - [x] [Guidance](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2491383911/Quant+Measure+Options+Likert+Scales+and+Others#Recommendation) provided ",1.0,"Research Likert scale use for updated Survey - ## Issue Description Given the discussions and learnings of previous tickets, perform a quick desk research effort on the Likert scale's utility for our Survey purposes. Research [notes](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2491383911/Quant+Measure+Options+Likert+Scales+and+Others#How-does-the-above-inform-what-we-are-trying-to-measure%3F) ## Tasks - [x] Review usefulness - [x] If useful, provide guidance on how to implement ## Acceptance Criteria - [x] [Guidance](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2491383911/Quant+Measure+Options+Likert+Scales+and+Others#Recommendation) provided ",1,research likert scale use for updated survey issue description given the discussions and learnings of previous tickets perform a quick desk research effort on the likert scale s utility for our survey purposes research tasks review usefulness if useful provide guidance on how to implement acceptance criteria provided ,1 123356,16485694415.0,IssuesEvent,2021-05-24 17:36:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Convert the Radio buttons react component to a web component,vsp-design-system-team,Convert the Radio buttons react component to a web component as background prep work for the new forms library prototype. ,1.0,Convert the Radio buttons react component to a web component - Convert the Radio buttons react component to a web component as background prep work for the new forms library prototype. ,1,convert the radio buttons react component to a web component convert the radio buttons react component to a web component as background prep work for the new forms library prototype ,1 53093,22613321953.0,IssuesEvent,2022-06-29 19:16:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,console-api Argo SuperUser Integration,console-services Console-API,"## Description As a workaround until the live Keycloak + Argo (without Dex) Integration is completed, we need a way to make Argo API calls. In order to get a valid access token, we will need to use a username/password as the authentication method. Ideally, once the Keycloak + Argo, we will use the access_token from keycloak to authenticate to Argo, but until then we need a working implementation. ## API docs https://cd.apps.argoproj.io/swagger-ui#operation/SessionService_Create https://argo-cd.readthedocs.io/en/stable/developer-guide/api-docs/ [Related ticket](https://github.com/orgs/department-of-veterans-affairs/projects/547/views/1?filterQuery=argo) ## Acceptance Criteria - [ ] Super user integration is used as Argo authentication method to make API calls",1.0,"console-api Argo SuperUser Integration - ## Description As a workaround until the live Keycloak + Argo (without Dex) Integration is completed, we need a way to make Argo API calls. In order to get a valid access token, we will need to use a username/password as the authentication method. Ideally, once the Keycloak + Argo, we will use the access_token from keycloak to authenticate to Argo, but until then we need a working implementation. ## API docs https://cd.apps.argoproj.io/swagger-ui#operation/SessionService_Create https://argo-cd.readthedocs.io/en/stable/developer-guide/api-docs/ [Related ticket](https://github.com/orgs/department-of-veterans-affairs/projects/547/views/1?filterQuery=argo) ## Acceptance Criteria - [ ] Super user integration is used as Argo authentication method to make API calls",0,console api argo superuser integration description as a workaround until the live keycloak argo without dex integration is completed we need a way to make argo api calls in order to get a valid access token we will need to use a username password as the authentication method ideally once the keycloak argo we will use the access token from keycloak to authenticate to argo but until then we need a working implementation api docs acceptance criteria super user integration is used as argo authentication method to make api calls,0 121674,16014324055.0,IssuesEvent,2021-04-20 14:22:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Make updated contribution templates for contributing to the design system,vsp-design-system-team,"- [x] Create a template for adding a new or updated component or pattern to the design system - [x] Create a documentation template ",1.0,"Make updated contribution templates for contributing to the design system - - [x] Create a template for adding a new or updated component or pattern to the design system - [x] Create a documentation template ",1,make updated contribution templates for contributing to the design system create a template for adding a new or updated component or pattern to the design system create a documentation template ,1 160141,25109334973.0,IssuesEvent,2022-11-08 19:08:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create detailed draft of Guide for the mapping process,service-design,"## Issue Description Document the mapping process, expanding upon the major phases developed in Issue [45606](https://app.zenhub.com/workspace/o/department-of-veterans-affairs/va.gov-team/issues/45606). Should result in an internal guide that a SDT member can follow. ## Tasks - [ ] Workshop Phases-to-specifics details - [ ] Spell out specific steps within each phase to accomplish a completed map - [ ] Refine w/ team input - [ ] Shape raw steps into a crude guide in [Confluence](https://vfs.atlassian.net/l/cp/szWWFLku) ## Acceptance Criteria - [ ] Process is documented in an internal guide format.",1.0,"Create detailed draft of Guide for the mapping process - ## Issue Description Document the mapping process, expanding upon the major phases developed in Issue [45606](https://app.zenhub.com/workspace/o/department-of-veterans-affairs/va.gov-team/issues/45606). Should result in an internal guide that a SDT member can follow. ## Tasks - [ ] Workshop Phases-to-specifics details - [ ] Spell out specific steps within each phase to accomplish a completed map - [ ] Refine w/ team input - [ ] Shape raw steps into a crude guide in [Confluence](https://vfs.atlassian.net/l/cp/szWWFLku) ## Acceptance Criteria - [ ] Process is documented in an internal guide format.",1,create detailed draft of guide for the mapping process issue description document the mapping process expanding upon the major phases developed in issue should result in an internal guide that a sdt member can follow tasks workshop phases to specifics details spell out specific steps within each phase to accomplish a completed map refine w team input shape raw steps into a crude guide in acceptance criteria process is documented in an internal guide format ,1 116757,14998581341.0,IssuesEvent,2021-01-29 18:39:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Reschedule Appointments,Epic roadmapVAOSR vaos-product-design,"## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/product-outline-template.md) ## High Level User Story/ies As a _____, I need _____ so I can _____. ## Hypothesis or Bet **If** _we make this change_ **then** _we expect this to happen_. ## OKR _Which Objective / Key Result does this epic push forward?_ ## Definition of Done ### What must be true in order for you to consider this epic complete? *Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.* ## Dependencies - Homepage Refresh MVP",1.0,"Reschedule Appointments - ## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/product-outline-template.md) ## High Level User Story/ies As a _____, I need _____ so I can _____. ## Hypothesis or Bet **If** _we make this change_ **then** _we expect this to happen_. ## OKR _Which Objective / Key Result does this epic push forward?_ ## Definition of Done ### What must be true in order for you to consider this epic complete? *Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.* ## Dependencies - Homepage Refresh MVP",1,reschedule appointments product outline high level user story ies as a i need so i can hypothesis or bet if we make this change then we expect this to happen okr which objective key result does this epic push forward definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements dependencies homepage refresh mvp,1 86272,10730978232.0,IssuesEvent,2019-10-28 18:32:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Integrate Icons into background-only alerts,design design system vsa-benefits-2,"## High Level User Story As a designer working on veteran facing tools, I need icons integrated into the design system's background-only alerts so I can indicate the tone and meaning of the alert with another attribute other than color. ## Hypothesis/(es) **If** we were to add icons to the background-only alerts **then** we expect that those with colorblindness (and those without!) will be able to determine the tone and meaning of the alert more simply. ## Goals We would like to see the inclusion of icons into the following component: https://design.va.gov/components/alertboxes#background-color-only ## Objectives Which VSP Objectives does this body of work push forward? Capacity-building ## How to configure this issue - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) ",2.0,"Integrate Icons into background-only alerts - ## High Level User Story As a designer working on veteran facing tools, I need icons integrated into the design system's background-only alerts so I can indicate the tone and meaning of the alert with another attribute other than color. ## Hypothesis/(es) **If** we were to add icons to the background-only alerts **then** we expect that those with colorblindness (and those without!) will be able to determine the tone and meaning of the alert more simply. ## Goals We would like to see the inclusion of icons into the following component: https://design.va.gov/components/alertboxes#background-color-only ## Objectives Which VSP Objectives does this body of work push forward? Capacity-building ## How to configure this issue - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) ",1,integrate icons into background only alerts high level user story as a designer working on veteran facing tools i need icons integrated into the design system s background only alerts so i can indicate the tone and meaning of the alert with another attribute other than color hypothesis es if we were to add icons to the background only alerts then we expect that those with colorblindness and those without will be able to determine the tone and meaning of the alert more simply goals we would like to see the inclusion of icons into the following component objectives which vsp objectives does this body of work push forward capacity building how to configure this issue labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content ,1 116618,14984667887.0,IssuesEvent,2021-01-28 18:56:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] HLR: Higher-Level Decision Review Requests,Epic HLR design research vsa-benefits vsa-decision-reviews,"## High Level User Story/ies As a researcher/designer on the Benefits and Memorials team, I need to conduct user research of the Higher-Level Review digital form so I can identify any design updates that are recommended by the users. ## Full project epic #1053 - [x] Create research plan & kickoff recruiting #3965 - [x] Create conversation guide #3968 - [x] Conduct sessions #3971 - [x] Create report #3972 - [x] Work with PM to create tickets ",1.0,"[Design] HLR: Higher-Level Decision Review Requests - ## High Level User Story/ies As a researcher/designer on the Benefits and Memorials team, I need to conduct user research of the Higher-Level Review digital form so I can identify any design updates that are recommended by the users. ## Full project epic #1053 - [x] Create research plan & kickoff recruiting #3965 - [x] Create conversation guide #3968 - [x] Conduct sessions #3971 - [x] Create report #3972 - [x] Work with PM to create tickets ",1, hlr higher level decision review requests high level user story ies as a researcher designer on the benefits and memorials team i need to conduct user research of the higher level review digital form so i can identify any design updates that are recommended by the users full project epic create research plan kickoff recruiting create conversation guide conduct sessions create report work with pm to create tickets ,1 154712,24330029031.0,IssuesEvent,2022-09-30 18:28:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design System Governance: Work identified by Design Council - Q3 2022,Epic vsp-design-system-team PO Endorsed platform-okrs,"## Product Outline https://vfs.atlassian.net/l/c/Ah0VFf0A ## High Level User Story/ies - As a VFS team, I want my suggested changes to the design system to be published so that I can use them in my work on VA.gov
. - As the design council, I want approved changes to the design system to be implemented so that VFS teams can use the new designs. ## Hypothesis or Bet If we improve the Design System by providing design templates, reusable components, patterns and guidelines, then VFS teams will be able to rapidly build and improve the Veteran facing digital applications provided by VA. ## OKR _Which Objective / Key Result does this epic push forward?_ Quarterly Operations and Maintenance ## Definition of done ### What must be true in order for you to consider this epic complete? We have done the following: - Completed 4 of the top priorities identified by the Design System Council - Improve and increase contributions to Design System - - 3-4 shared Sketch libraries - Work on at least one ticket related to the 5 high priority DSC requests per sprint There are the items from the DSC project board that we have identified that we will work on in Q3: - 1 -[Promo banner is inaccessible to keyboard and screen reader users, poor usability on mobile](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/725) - 2 - [Reconcile Full-width Alert vs. Banner](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/816) - 6 - [New Components: Download, Video Link, and Accessibility Links](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/281) - 10 - [Text date inputs](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/481) - 12 - [Breadcrumb line break on mobile](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/469) - 26 - [508-defect-3 [COGNITION]: ""Finish this request later"" button should be styled as a button and positioned higher in the page](https://github.com/department-of-veterans-affairs/va.gov-team/issues/25111) ",1.0,"Design System Governance: Work identified by Design Council - Q3 2022 - ## Product Outline https://vfs.atlassian.net/l/c/Ah0VFf0A ## High Level User Story/ies - As a VFS team, I want my suggested changes to the design system to be published so that I can use them in my work on VA.gov
. - As the design council, I want approved changes to the design system to be implemented so that VFS teams can use the new designs. ## Hypothesis or Bet If we improve the Design System by providing design templates, reusable components, patterns and guidelines, then VFS teams will be able to rapidly build and improve the Veteran facing digital applications provided by VA. ## OKR _Which Objective / Key Result does this epic push forward?_ Quarterly Operations and Maintenance ## Definition of done ### What must be true in order for you to consider this epic complete? We have done the following: - Completed 4 of the top priorities identified by the Design System Council - Improve and increase contributions to Design System - - 3-4 shared Sketch libraries - Work on at least one ticket related to the 5 high priority DSC requests per sprint There are the items from the DSC project board that we have identified that we will work on in Q3: - 1 -[Promo banner is inaccessible to keyboard and screen reader users, poor usability on mobile](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/725) - 2 - [Reconcile Full-width Alert vs. Banner](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/816) - 6 - [New Components: Download, Video Link, and Accessibility Links](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/281) - 10 - [Text date inputs](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/481) - 12 - [Breadcrumb line break on mobile](https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/469) - 26 - [508-defect-3 [COGNITION]: ""Finish this request later"" button should be styled as a button and positioned higher in the page](https://github.com/department-of-veterans-affairs/va.gov-team/issues/25111) ",1,design system governance work identified by design council product outline high level user story ies as a vfs team i want my suggested changes to the design system to be published so that i can use them in my work on va gov
 as the design council i want approved changes to the design system to be implemented so that vfs teams can use the new designs hypothesis or bet if we improve the design system by providing design templates reusable components patterns and guidelines then vfs teams will be able to rapidly build and improve the veteran facing digital applications provided by va okr which objective key result does this epic push forward quarterly operations and maintenance definition of done what must be true in order for you to consider this epic complete we have done the following completed of the top priorities identified by the design system council improve and increase contributions to design system shared sketch libraries work on at least one ticket related to the high priority dsc requests per sprint there are the items from the dsc project board that we have identified that we will work on in finish this request later button should be styled as a button and positioned higher in the page ,1 162302,25517638147.0,IssuesEvent,2022-11-28 17:35:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design | Profile | Nametag | Update Documentation,design vsa authenticated-experience needs-grooming profile sprint-planning,"## Background We need to update any existing or create new documentation for the Nametag feature. Currently, this [documentation](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/frontend/documentation/nametag.md) exists so we can review/edit this as needed. The need for documentation stemmed from [this question](https://dsva.slack.com/archives/C018V2JCWRJ/p1668018835059419) in slack. Currently we are updating sketch files and use cases so this would include any documentation outside of that. ## Tasks - [ ] Update documentation for Nametag - [ ] Determine where this documentation should live (as its a shared feature of Profile and My VA) ",1.0,"Design | Profile | Nametag | Update Documentation - ## Background We need to update any existing or create new documentation for the Nametag feature. Currently, this [documentation](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/frontend/documentation/nametag.md) exists so we can review/edit this as needed. The need for documentation stemmed from [this question](https://dsva.slack.com/archives/C018V2JCWRJ/p1668018835059419) in slack. Currently we are updating sketch files and use cases so this would include any documentation outside of that. ## Tasks - [ ] Update documentation for Nametag - [ ] Determine where this documentation should live (as its a shared feature of Profile and My VA) ",1,design profile nametag update documentation background we need to update any existing or create new documentation for the nametag feature currently this exists so we can review edit this as needed the need for documentation stemmed from in slack currently we are updating sketch files and use cases so this would include any documentation outside of that tasks update documentation for nametag determine where this documentation should live as its a shared feature of profile and my va ,1 100229,12509996418.0,IssuesEvent,2020-06-02 17:51:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Development] BDD Military Service History Wording,BDD design development frontend vsa-benefits,"## Issue Description The Military Service History page in BDD should be adjusted so its language more accurately describes users who do not have previous military history. This is necessary because users filing BDD frequently have no past military history imported. ![image](https://user-images.githubusercontent.com/53942725/82586181-28fea280-9b65-11ea-8494-ce4953477073.png) ## Tasks - [ ] Work with design to adjust Military Service History page language to explain the situation better ## Acceptance Criteria - [ ] Military Service History page text makes sense in all contexts of previous history",1.0,"[Development] BDD Military Service History Wording - ## Issue Description The Military Service History page in BDD should be adjusted so its language more accurately describes users who do not have previous military history. This is necessary because users filing BDD frequently have no past military history imported. ![image](https://user-images.githubusercontent.com/53942725/82586181-28fea280-9b65-11ea-8494-ce4953477073.png) ## Tasks - [ ] Work with design to adjust Military Service History page language to explain the situation better ## Acceptance Criteria - [ ] Military Service History page text makes sense in all contexts of previous history",1, bdd military service history wording issue description the military service history page in bdd should be adjusted so its language more accurately describes users who do not have previous military history this is necessary because users filing bdd frequently have no past military history imported tasks work with design to adjust military service history page language to explain the situation better acceptance criteria military service history page text makes sense in all contexts of previous history,1 147056,23159950419.0,IssuesEvent,2022-07-29 16:34:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[design] draft supplemental claims design,design benefits-team-1 squad-2,"## User Story As a user I would like to be able to complete a Supplemental Claim form on VA.gov ## Expected Behavior Happy path design layout for completing a Supplemental Claim on VA.gov ## Acceptance Criteria - [x] Sketch files with initial happy path layout for Supplemental Claims - [x] Identified opportunities for optimization - [x] Identified use cases ",1.0,"[design] draft supplemental claims design - ## User Story As a user I would like to be able to complete a Supplemental Claim form on VA.gov ## Expected Behavior Happy path design layout for completing a Supplemental Claim on VA.gov ## Acceptance Criteria - [x] Sketch files with initial happy path layout for Supplemental Claims - [x] Identified opportunities for optimization - [x] Identified use cases ",1, draft supplemental claims design user story as a user i would like to be able to complete a supplemental claim form on va gov expected behavior happy path design layout for completing a supplemental claim on va gov acceptance criteria sketch files with initial happy path layout for supplemental claims identified opportunities for optimization identified use cases ,1 86929,10854174741.0,IssuesEvent,2019-11-13 15:58:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Time Periods rule ,design research vsa-benefits vsa-decision-reviews,"## User Story or Problem Statement As a claimant, I need to identify the best day and times that work for me to have an informal review so I can communicate this in my form without any chance of error. ## Goal _Create a user friendly way to select day/time for informal review_ ## Acceptance Criteria Scenario: System user wants to select time-frames of availability for informal review - GIVEN the system user has confirmed their contact information - WHEN the user moves forward in the HLR process to the Request an Informal Conference - THEN the system will prompt the user to select if they want to request an informal conference *and* select if they want VA to contact their representative *and* select up to 2 time periods when they are available to schedule their informal review *and* confirm the number of attempts the VA will make to reach the user *and* user can click the Continue button - THEN the system moves the user to the next page of the HLR process ## Definition of Done - [x] Identify current design issue - [x] Identify design of proposed solution for displaying time periods - [x] Request content review from VSP (Yana create a ticket and assign Peggy Gannon) - [x] _*This relates to epic ticket #1053 *Check the box below when this has been completed and comment ""done""._ ## Screen Shots see below for latest ",1.0,"[Design] Time Periods rule - ## User Story or Problem Statement As a claimant, I need to identify the best day and times that work for me to have an informal review so I can communicate this in my form without any chance of error. ## Goal _Create a user friendly way to select day/time for informal review_ ## Acceptance Criteria Scenario: System user wants to select time-frames of availability for informal review - GIVEN the system user has confirmed their contact information - WHEN the user moves forward in the HLR process to the Request an Informal Conference - THEN the system will prompt the user to select if they want to request an informal conference *and* select if they want VA to contact their representative *and* select up to 2 time periods when they are available to schedule their informal review *and* confirm the number of attempts the VA will make to reach the user *and* user can click the Continue button - THEN the system moves the user to the next page of the HLR process ## Definition of Done - [x] Identify current design issue - [x] Identify design of proposed solution for displaying time periods - [x] Request content review from VSP (Yana create a ticket and assign Peggy Gannon) - [x] _*This relates to epic ticket #1053 *Check the box below when this has been completed and comment ""done""._ ## Screen Shots see below for latest ",1, time periods rule user story or problem statement as a claimant i need to identify the best day and times that work for me to have an informal review so i can communicate this in my form without any chance of error goal create a user friendly way to select day time for informal review acceptance criteria scenario system user wants to select time frames of availability for informal review given the system user has confirmed their contact information when the user moves forward in the hlr process to the request an informal conference then the system will prompt the user to select if they want to request an informal conference and select if they want va to contact their representative and select up to time periods when they are available to schedule their informal review and confirm the number of attempts the va will make to reach the user and user can click the continue button then the system moves the user to the next page of the hlr process definition of done identify current design issue identify design of proposed solution for displaying time periods request content review from vsp yana create a ticket and assign peggy gannon this relates to epic ticket check the box below when this has been completed and comment done screen shots see below for latest ,1 165648,26204569512.0,IssuesEvent,2023-01-03 21:03:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] [Content] Create wireframes for unified experience,content design ux HCE-Checkin,"## Tasks - [ ] Review outcome of [user flow decisions](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/department-of-veterans-affairs/va.gov-team/50608) - [ ] Draft content for most complex path + simple path (e.g., checking in for telephone appt) - [ ] Draft wireframes for most complex path + simple path (e.g., checking in for telephone appt) - [ ] Set meeting to present to team ## AC - [ ] Wireframes drafted and collection created in abstract - [ ] Meeting set up to present to team ",1.0,"[Design] [Content] Create wireframes for unified experience - ## Tasks - [ ] Review outcome of [user flow decisions](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/department-of-veterans-affairs/va.gov-team/50608) - [ ] Draft content for most complex path + simple path (e.g., checking in for telephone appt) - [ ] Draft wireframes for most complex path + simple path (e.g., checking in for telephone appt) - [ ] Set meeting to present to team ## AC - [ ] Wireframes drafted and collection created in abstract - [ ] Meeting set up to present to team ",1, create wireframes for unified experience tasks review outcome of draft content for most complex path simple path e g checking in for telephone appt draft wireframes for most complex path simple path e g checking in for telephone appt set meeting to present to team ac wireframes drafted and collection created in abstract meeting set up to present to team ,1 107266,13447871324.0,IssuesEvent,2020-09-08 14:46:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Questionnaire Title/Appointment Details,design vsa-healthcare-exp,"Finalize the questionnaire title and appt details locations, layout and content",1.0,"Questionnaire Title/Appointment Details - Finalize the questionnaire title and appt details locations, layout and content",1,questionnaire title appointment details finalize the questionnaire title and appt details locations layout and content,1 134170,19096147950.0,IssuesEvent,2021-11-29 16:52:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Update documentation on check-in text messages,design ux vsa-healthcare-exp HCE-Checkin,Need to move the current Mural over to Sketch that documents all the current text messages sent related to check-in. Need to coordinate with CHIP to update to wording currently coded and mark any scenario where there is a difference. CHIP might need a ticket to help us with this.,1.0,[Design] Update documentation on check-in text messages - Need to move the current Mural over to Sketch that documents all the current text messages sent related to check-in. Need to coordinate with CHIP to update to wording currently coded and mark any scenario where there is a difference. CHIP might need a ticket to help us with this.,1, update documentation on check in text messages need to move the current mural over to sketch that documents all the current text messages sent related to check in need to coordinate with chip to update to wording currently coded and mark any scenario where there is a difference chip might need a ticket to help us with this ,1 88471,11099177936.0,IssuesEvent,2019-12-16 16:31:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[FE] Candidate Address Modal - Confirmation Screen,design frontend vsa-authenticated-exp,"## User Story: As a designer i need to upload the final UX steps of getting through the states of validation all the way to the confirmation stage. ## Tasks _The steps that must be done by the team to complete the acceptance criteria_ - [x] Upload all the states to be accounted for in the user flow - [ ] Make sure confirmation page is added and validated - [ ] Validate on staging that confirmation page is added and all states are accounted. ## Acceptance Criteria: _The requirements that must be met in order to mark this user story as completed_ - [ ] This is validated on staging ## UX Final Mock Up ## Final Copy for each state ## Confirmation UX Mock UP ",1.0,"[FE] Candidate Address Modal - Confirmation Screen - ## User Story: As a designer i need to upload the final UX steps of getting through the states of validation all the way to the confirmation stage. ## Tasks _The steps that must be done by the team to complete the acceptance criteria_ - [x] Upload all the states to be accounted for in the user flow - [ ] Make sure confirmation page is added and validated - [ ] Validate on staging that confirmation page is added and all states are accounted. ## Acceptance Criteria: _The requirements that must be met in order to mark this user story as completed_ - [ ] This is validated on staging ## UX Final Mock Up ## Final Copy for each state ## Confirmation UX Mock UP ",1, candidate address modal confirmation screen user story as a designer i need to upload the final ux steps of getting through the states of validation all the way to the confirmation stage tasks the steps that must be done by the team to complete the acceptance criteria upload all the states to be accounted for in the user flow make sure confirmation page is added and validated validate on staging that confirmation page is added and all states are accounted acceptance criteria the requirements that must be met in order to mark this user story as completed this is validated on staging ux final mock up final copy for each state confirmation ux mock up ,1 58508,24468550719.0,IssuesEvent,2022-10-07 17:19:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Document Strategy to Iterate API V0 to V1 for vets-api,Epic super-epic console-services,"# Problem There is currently no official strategy or guidelines around creating new (V1) endpoints. Without a defined strategy we will certainly run into issues with existing apps utilizing deprecated end points. There needs to be clear guidelines to when and how a new (V1) endpoint is created, when and how existing apps switch where they point, and when that old end point is deprecated. ## VSP Q1 + Q2 2020 OKRs O3: Stability and resiliency of the Platform's systems and teams continue to improve. ## Measuring Success # Details and Notes ### Hypothesis ### Areas for Discovery",1.0,"Document Strategy to Iterate API V0 to V1 for vets-api - # Problem There is currently no official strategy or guidelines around creating new (V1) endpoints. Without a defined strategy we will certainly run into issues with existing apps utilizing deprecated end points. There needs to be clear guidelines to when and how a new (V1) endpoint is created, when and how existing apps switch where they point, and when that old end point is deprecated. ## VSP Q1 + Q2 2020 OKRs O3: Stability and resiliency of the Platform's systems and teams continue to improve. ## Measuring Success # Details and Notes ### Hypothesis ### Areas for Discovery",0,document strategy to iterate api to for vets api problem there is currently no official strategy or guidelines around creating new endpoints without a defined strategy we will certainly run into issues with existing apps utilizing deprecated end points there needs to be clear guidelines to when and how a new endpoint is created when and how existing apps switch where they point and when that old end point is deprecated vsp okrs stability and resiliency of the platform s systems and teams continue to improve measuring success details and notes hypothesis areas for discovery,0 142328,21716593081.0,IssuesEvent,2022-05-10 18:33:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Documentation] Add `editModeOnReviewPage` to forms library,forms vsp-design-system-team,"### What is your documentation request, question, comment, or issue? The `editModeOnReviewPage` form config page option is not documented on this page - https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/forms/config-options - or any others. ",1.0,"[Documentation] Add `editModeOnReviewPage` to forms library - ### What is your documentation request, question, comment, or issue? The `editModeOnReviewPage` form config page option is not documented on this page - https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/forms/config-options - or any others. ",1, add editmodeonreviewpage to forms library what is your documentation request question comment or issue the editmodeonreviewpage form config page option is not documented on this page or any others ,1 105063,13159989239.0,IssuesEvent,2020-08-10 16:46:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[UI] This Visit Questions ,design vsa-healthcare-exp,"## Product Documentation [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) - [Feature - This Visit ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/this-visit.md) ## User Story/ies * **Use Case:** --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ - [ ] See This Visit feature outline for fields and valuation - [ ] Create detailed mockups and callouts of landing page [link] ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ - [ ] UI review meeting with product for feature capabilities - [ ] UI review meeting and callouts with engineering for layout and callouts - [ ] published to ABC environment. link ",1.0,"[UI] This Visit Questions - ## Product Documentation [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) - [Feature - This Visit ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/this-visit.md) ## User Story/ies * **Use Case:** --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ - [ ] See This Visit feature outline for fields and valuation - [ ] Create detailed mockups and callouts of landing page [link] ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ - [ ] UI review meeting with product for feature capabilities - [ ] UI review meeting and callouts with engineering for layout and callouts - [ ] published to ABC environment. link ",1, this visit questions product documentation user story ies use case tasks what work is necessary for this story to be completed see this visit feature outline for fields and valuation create detailed mockups and callouts of landing page acceptance criteria what will be created or happen as a result of this story ui review meeting with product for feature capabilities ui review meeting and callouts with engineering for layout and callouts published to abc environment link ,1 147626,23243959720.0,IssuesEvent,2022-08-03 18:11:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Communication Plan template optimization,service-design,"### Primary assignee: Dan Turner ## Issue Description Reconsider structure and content of Plan template ## Tasks - [x] Dr ## Acceptance Criteria - [x] dem ",1.0,"Communication Plan template optimization - ### Primary assignee: Dan Turner ## Issue Description Reconsider structure and content of Plan template ## Tasks - [x] Dr ## Acceptance Criteria - [x] dem ",1,communication plan template optimization primary assignee dan turner issue description reconsider structure and content of plan template tasks dr acceptance criteria dem ,1 79560,28374225938.0,IssuesEvent,2023-04-12 19:26:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.4),content design 508/Accessibility ia vaos 508-defect-2 collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard appointment-list,"### General Information #### VFS team name VA Online Scheduling (VAOS) #### VFS product name VA Online Scheduling #### VFS feature name Appointment List #### Point of Contact/Reviewers Brian DeConinck - @briandeconinck - Accessibility *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details The Pending and Past navigation items are visually styled to be links and are navigational so they should be links, but they're coded as buttons. Buttons and links are treated differently by some assistive technologies, including screen readers and voice command software. When the code semantics of the element don't match up with the visual presentation or the interaction pattern for the element, you can introduce unexpected accessibility barriers. Example: a voice command user may speak the command ""Click link,"" which will then highlight all the links on the page with a number, and then allow them to specify which link they want to follow, eg. ""Click fifteen."" Since Pending and Past are visually styled to look like links, a sighted voice command user would expect them to be highlighted when they say ""Click link."" But since they're not coded as links, they won't be highlighted --- leaving the user to try to guess what might be going wrong and what the magic words might be to be able to click those not-links. ### Link, screenshot or steps to recreate The Pending and Past items are currently coded as: ``` ``` ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Maintain material honesty whenever possible. Since it looks like a link and acts like a link, it should just be a link. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.4) - ### General Information #### VFS team name VA Online Scheduling (VAOS) #### VFS product name VA Online Scheduling #### VFS feature name Appointment List #### Point of Contact/Reviewers Brian DeConinck - @briandeconinck - Accessibility *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details The Pending and Past navigation items are visually styled to be links and are navigational so they should be links, but they're coded as buttons. Buttons and links are treated differently by some assistive technologies, including screen readers and voice command software. When the code semantics of the element don't match up with the visual presentation or the interaction pattern for the element, you can introduce unexpected accessibility barriers. Example: a voice command user may speak the command ""Click link,"" which will then highlight all the links on the page with a number, and then allow them to specify which link they want to follow, eg. ""Click fifteen."" Since Pending and Past are visually styled to look like links, a sighted voice command user would expect them to be highlighted when they say ""Click link."" But since they're not coded as links, they won't be highlighted --- leaving the user to try to guess what might be going wrong and what the magic words might be to be able to click those not-links. ### Link, screenshot or steps to recreate The Pending and Past items are currently coded as: ``` ``` ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Maintain material honesty whenever possible. Since it looks like a link and acts like a link, it should just be a link. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",0, design components or patterns don t align with design system guidelines general information vfs team name va online scheduling vaos vfs product name va online scheduling vfs feature name appointment list point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details the pending and past navigation items are visually styled to be links and are navigational so they should be links but they re coded as buttons buttons and links are treated differently by some assistive technologies including screen readers and voice command software when the code semantics of the element don t match up with the visual presentation or the interaction pattern for the element you can introduce unexpected accessibility barriers example a voice command user may speak the command click link which will then highlight all the links on the page with a number and then allow them to specify which link they want to follow eg click fifteen since pending and past are visually styled to look like links a sighted voice command user would expect them to be highlighted when they say click link but since they re not coded as links they won t be highlighted leaving the user to try to guess what might be going wrong and what the magic words might be to be able to click those not links link screenshot or steps to recreate the pending and past items are currently coded as pending past va gov experience standard other references wcag sc aa platform recommendation maintain material honesty whenever possible since it looks like a link and acts like a link it should just be a link vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,0 111920,14172495081.0,IssuesEvent,2020-11-12 17:01:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Write stories for LoadingIndicator,design-system-team frontend,"## Issue Description Using the documentation found in [the markdown file for `LoadingIndicator`](https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/tree/master/packages/formation-react/src/components/LoadingIndicator/LoadingIndicator.mdx), write Storybook stories for the component. ## Acceptance Criteria - [ ] All the ""stories"" found in `LoadingIndicator.mdx` are written as Storybook stories - [ ] These stories are found in `packages/formation-react/src/components/LoadingIndicator/LoadingIndicator.stories.jsx`",1.0,"Write stories for LoadingIndicator - ## Issue Description Using the documentation found in [the markdown file for `LoadingIndicator`](https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/tree/master/packages/formation-react/src/components/LoadingIndicator/LoadingIndicator.mdx), write Storybook stories for the component. ## Acceptance Criteria - [ ] All the ""stories"" found in `LoadingIndicator.mdx` are written as Storybook stories - [ ] These stories are found in `packages/formation-react/src/components/LoadingIndicator/LoadingIndicator.stories.jsx`",1,write stories for loadingindicator issue description using the documentation found in write storybook stories for the component acceptance criteria all the stories found in loadingindicator mdx are written as storybook stories these stories are found in packages formation react src components loadingindicator loadingindicator stories jsx ,1 94474,11874365199.0,IssuesEvent,2020-03-26 18:52:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Research] BDD: Initial Usability Testing/Discovery with Mocked Up BDD Based on Original Claims,BDD design research vsa vsa-benefits,"## User Story or Problem Statement As a UX designer, I need to test the Benefits Delivery at Discharge digital form mockup so I can receive feedback on the initial design and improve it. This will not be a ""true"" usability study with a built out front-end, we will collect feedback on the BDD digital form mockup. ## Tasks - [x] Conduct interviews and collect notes - [x] Create readout and schedule readout review meeting - [x] Share with design team/lead - [x] Upload to GitHub and update [this ](https://docs.google.com/spreadsheets/d/191FcWP_pqq2jnPnEJ1OXjLvaflYszt5VKuSw8NMe3FY)document ## Acceptance Criteria - [x] Test the mockup with 8-10 users - [x] Create notes and drop scrubbed data into GH - [x] Share notes with team - [x] Conduct first readout of research findings",1.0,"[Research] BDD: Initial Usability Testing/Discovery with Mocked Up BDD Based on Original Claims - ## User Story or Problem Statement As a UX designer, I need to test the Benefits Delivery at Discharge digital form mockup so I can receive feedback on the initial design and improve it. This will not be a ""true"" usability study with a built out front-end, we will collect feedback on the BDD digital form mockup. ## Tasks - [x] Conduct interviews and collect notes - [x] Create readout and schedule readout review meeting - [x] Share with design team/lead - [x] Upload to GitHub and update [this ](https://docs.google.com/spreadsheets/d/191FcWP_pqq2jnPnEJ1OXjLvaflYszt5VKuSw8NMe3FY)document ## Acceptance Criteria - [x] Test the mockup with 8-10 users - [x] Create notes and drop scrubbed data into GH - [x] Share notes with team - [x] Conduct first readout of research findings",1, bdd initial usability testing discovery with mocked up bdd based on original claims user story or problem statement as a ux designer i need to test the benefits delivery at discharge digital form mockup so i can receive feedback on the initial design and improve it this will not be a true usability study with a built out front end we will collect feedback on the bdd digital form mockup tasks conduct interviews and collect notes create readout and schedule readout review meeting share with design team lead upload to github and update acceptance criteria test the mockup with users create notes and drop scrubbed data into gh share notes with team conduct first readout of research findings,1 90189,11356057748.0,IssuesEvent,2020-01-24 21:38:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Implement Accessibility Feedback for ""View Dependents""",508/Accessibility design vsa vsa-ebenefits,"## Goal To perform a review on the latest design mockups ahead of frontend implementation on staging and consider some accessibility improvements so the more final review(s) are smoother. ## Tasks - [ ] Collaborate with Jennifer Strickland on accessibility improvements - [ ] Share feedback results with FE team ## Acceptance Criteria - [ ] Feedback has been provided and shared with FE team",1.0,"Implement Accessibility Feedback for ""View Dependents"" - ## Goal To perform a review on the latest design mockups ahead of frontend implementation on staging and consider some accessibility improvements so the more final review(s) are smoother. ## Tasks - [ ] Collaborate with Jennifer Strickland on accessibility improvements - [ ] Share feedback results with FE team ## Acceptance Criteria - [ ] Feedback has been provided and shared with FE team",1,implement accessibility feedback for view dependents goal to perform a review on the latest design mockups ahead of frontend implementation on staging and consider some accessibility improvements so the more final review s are smoother tasks collaborate with jennifer strickland on accessibility improvements share feedback results with fe team acceptance criteria feedback has been provided and shared with fe team,1 141877,21635262542.0,IssuesEvent,2022-05-05 13:43:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.1),content design 508/Accessibility ia vsa-ebenefits collab-cycle-feedback 686 Dependency Verification Staging CCIssue04.07 CC-Dashboard,"### General Information #### VFS team name eBenefits #### VFS product name Dependency Verification #### Point of Contact/Reviewers Angela Fowler (Accessibility) --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details Form elements should be labeled according to the data required. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA --- ### Platform Recommendation When adding a dependent, the street address field is simply labeled ""street,"" potentially causing the user to think that is all that is required. ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] VFS team closes the ticket when the issue has been resolved",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.1) - ### General Information #### VFS team name eBenefits #### VFS product name Dependency Verification #### Point of Contact/Reviewers Angela Fowler (Accessibility) --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details Form elements should be labeled according to the data required. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA --- ### Platform Recommendation When adding a dependent, the street address field is simply labeled ""street,"" potentially causing the user to think that is all that is required. ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] VFS team closes the ticket when the issue has been resolved",1, design components or patterns don t align with design system guidelines general information vfs team name ebenefits vfs product name dependency verification point of contact reviewers angela fowler accessibility platform issue design components or patterns don t align with design system guidelines issue details form elements should be labeled according to the data required link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation when adding a dependent the street address field is simply labeled street potentially causing the user to think that is all that is required vfs team tasks to complete comment on the ticket if there are questions or concerns vfs team closes the ticket when the issue has been resolved,1 174744,27719764247.0,IssuesEvent,2023-03-14 19:37:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Gain understanding of what current MHV preferences entail and document,design research ux my-health my-health-CTO-HEALTH-TEAM my-health-INTEGRATION,"## Overview Before we can make recommendations and design an experience for MHV preferences on VA.gov, we must first understand the current preferences on MHV, as well as how they overlap with preferences on VA.gov. ## Acceptance Criteria / Deliverables **Gain an understanding of what current MHV preferences entail and document** - [x] What data is available? - [x] Where can view preferences? - [x] Where can edit preferences? - [x] Document findings",1.0,"Gain understanding of what current MHV preferences entail and document - ## Overview Before we can make recommendations and design an experience for MHV preferences on VA.gov, we must first understand the current preferences on MHV, as well as how they overlap with preferences on VA.gov. ## Acceptance Criteria / Deliverables **Gain an understanding of what current MHV preferences entail and document** - [x] What data is available? - [x] Where can view preferences? - [x] Where can edit preferences? - [x] Document findings",1,gain understanding of what current mhv preferences entail and document overview before we can make recommendations and design an experience for mhv preferences on va gov we must first understand the current preferences on mhv as well as how they overlap with preferences on va gov acceptance criteria deliverables gain an understanding of what current mhv preferences entail and document what data is available where can view preferences where can edit preferences document findings,1 135383,19566529300.0,IssuesEvent,2022-01-04 01:47:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Capture web components used with React bindings in component usage metrics,vsp-design-system-team,"## Description Currently our component usage metrics for our web components do not cover instances where the web components are used with React bindings. For example, to use the `va-select` component with React bindings, you would import the `VaSelect` component from web-components/react-bindings instead of using `va-select` directly. so we need to search for the React binding component names in addition to the regular web-component names. ## Details The component usage report code is contained in the [design-system-dashboard-cli](https://github.com/department-of-veterans-affairs/design-system-dashboard-cli) repo. ## Acceptance Criteria - [ ] The component usage report includes both regular web component usage and web components with React bindings",1.0,"Capture web components used with React bindings in component usage metrics - ## Description Currently our component usage metrics for our web components do not cover instances where the web components are used with React bindings. For example, to use the `va-select` component with React bindings, you would import the `VaSelect` component from web-components/react-bindings instead of using `va-select` directly. so we need to search for the React binding component names in addition to the regular web-component names. ## Details The component usage report code is contained in the [design-system-dashboard-cli](https://github.com/department-of-veterans-affairs/design-system-dashboard-cli) repo. ## Acceptance Criteria - [ ] The component usage report includes both regular web component usage and web components with React bindings",1,capture web components used with react bindings in component usage metrics description currently our component usage metrics for our web components do not cover instances where the web components are used with react bindings for example to use the va select component with react bindings you would import the vaselect component from web components react bindings instead of using va select directly so we need to search for the react binding component names in addition to the regular web component names details the component usage report code is contained in the repo acceptance criteria the component usage report includes both regular web component usage and web components with react bindings,1 175703,27962696343.0,IssuesEvent,2023-03-24 16:49:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Add complete page variation for when vets api fails to talk to BTSSS API ,design ux HCE-Checkin,"### Description How might we communicate to Veterans that something went wrong on our end when vets api fails when attempting to submit the travel reimbursement claim request? https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1677531124203/5edcfd3ea4b1eaf1ef082d56782a8b3291ef3932?sender=u37bb983bd3fc3cc00c7d3286 ",1.0,"[Design] Add complete page variation for when vets api fails to talk to BTSSS API - ### Description How might we communicate to Veterans that something went wrong on our end when vets api fails when attempting to submit the travel reimbursement claim request? https://app.mural.co/t/departmentofveteransaffairs9999/m/departmentofveteransaffairs9999/1677531124203/5edcfd3ea4b1eaf1ef082d56782a8b3291ef3932?sender=u37bb983bd3fc3cc00c7d3286 ",1, add complete page variation for when vets api fails to talk to btsss api description how might we communicate to veterans that something went wrong on our end when vets api fails when attempting to submit the travel reimbursement claim request ,1 160945,25258781258.0,IssuesEvent,2022-11-15 20:37:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design Intent - Accessibility Feedback - 10-10EZ Household Information Optimization,508/Accessibility collaboration-cycle collab-cycle-feedback 1010-ez design-intent household-info-optimization,"## VFS acceptance criteria - [x] Let Platform know when the **Must** feedback has been incorporated - [x] Leave any comments for feedback you decide _not_ to take - [ ] VFS team closes the ticket ## Thoughts/questions - Overall I think this is looking good! I'm looking forward to seeing what ## Feedback - Practice areas will document their feedback following the [Must, Should, and Consider Framework](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/must-should-and-consider-framework-for-feedback). **Must:** **Should:** - In the meeting there was some discussion about one-thing-per-page and the conditional display of certain fields. As much as possible, avoid conditional display of fields. In situations where breaking questions out into follow-up pages feels onerous, see if there are ways to re-word or re-order questions to make them more natural together without having conditional display. If there's no better way of presenting the information and conditional display tests better with users, that's fine -- but be sure to keep it as simple as possible. I'd recommend working with the Shared Support accessibility specialists on this. **Consider:** - When using the Additional Info component, make sure it makes sense to hide information in the first place. In particular, I'm thinking about the [Veteran annual income](https://www.sketch.com/s/da85cf44-4503-4e98-834e-ff068b242ef6/v/5LaJRx/p/208CCE1E-DC03-457F-B2FA-1232663983CF/canvas?posX=-21698.978515625&posY=-3367.021484375&zoom=0.5) questions. Inputs at that step have a label and some pretty lengthy helper text, and then some extra definitions hidden inside the Additional Info component. Since there's already a lot of helper text on screen, it's not clear to me that you gain a lot by hiding information for these questions. The pattern is accessible, but every time we add an extra click or other user interaction (especially for assistive technology users), it's worth verifying that it's an extra interaction that provides value. ## Platform directions - Remove the governance-team label - Update ""Issue Title"" - Link to collab cycle Request epic - Add your feedback - Remove the CC-Request label (only if you created the ticket using the New Issue link from the Collaboration Cycle Reviews board) - Add assignees based on collab cycle touchpoint - **Design Intent**: VFS designer, VFS PM (optional), yourself (optional) - **Midpoint Review**: VFS PM, yourself (optional) - **Staging Review QA Only**: VFS PM, yourself (optional) ",1.0,"Design Intent - Accessibility Feedback - 10-10EZ Household Information Optimization - ## VFS acceptance criteria - [x] Let Platform know when the **Must** feedback has been incorporated - [x] Leave any comments for feedback you decide _not_ to take - [ ] VFS team closes the ticket ## Thoughts/questions - Overall I think this is looking good! I'm looking forward to seeing what ## Feedback - Practice areas will document their feedback following the [Must, Should, and Consider Framework](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/must-should-and-consider-framework-for-feedback). **Must:** **Should:** - In the meeting there was some discussion about one-thing-per-page and the conditional display of certain fields. As much as possible, avoid conditional display of fields. In situations where breaking questions out into follow-up pages feels onerous, see if there are ways to re-word or re-order questions to make them more natural together without having conditional display. If there's no better way of presenting the information and conditional display tests better with users, that's fine -- but be sure to keep it as simple as possible. I'd recommend working with the Shared Support accessibility specialists on this. **Consider:** - When using the Additional Info component, make sure it makes sense to hide information in the first place. In particular, I'm thinking about the [Veteran annual income](https://www.sketch.com/s/da85cf44-4503-4e98-834e-ff068b242ef6/v/5LaJRx/p/208CCE1E-DC03-457F-B2FA-1232663983CF/canvas?posX=-21698.978515625&posY=-3367.021484375&zoom=0.5) questions. Inputs at that step have a label and some pretty lengthy helper text, and then some extra definitions hidden inside the Additional Info component. Since there's already a lot of helper text on screen, it's not clear to me that you gain a lot by hiding information for these questions. The pattern is accessible, but every time we add an extra click or other user interaction (especially for assistive technology users), it's worth verifying that it's an extra interaction that provides value. ## Platform directions - Remove the governance-team label - Update ""Issue Title"" - Link to collab cycle Request epic - Add your feedback - Remove the CC-Request label (only if you created the ticket using the New Issue link from the Collaboration Cycle Reviews board) - Add assignees based on collab cycle touchpoint - **Design Intent**: VFS designer, VFS PM (optional), yourself (optional) - **Midpoint Review**: VFS PM, yourself (optional) - **Staging Review QA Only**: VFS PM, yourself (optional) ",1,design intent accessibility feedback household information optimization vfs acceptance criteria let platform know when the must feedback has been incorporated leave any comments for feedback you decide not to take vfs team closes the ticket thoughts questions overall i think this is looking good i m looking forward to seeing what feedback practice areas will document their feedback following the must should in the meeting there was some discussion about one thing per page and the conditional display of certain fields as much as possible avoid conditional display of fields in situations where breaking questions out into follow up pages feels onerous see if there are ways to re word or re order questions to make them more natural together without having conditional display if there s no better way of presenting the information and conditional display tests better with users that s fine but be sure to keep it as simple as possible i d recommend working with the shared support accessibility specialists on this consider when using the additional info component make sure it makes sense to hide information in the first place in particular i m thinking about the questions inputs at that step have a label and some pretty lengthy helper text and then some extra definitions hidden inside the additional info component since there s already a lot of helper text on screen it s not clear to me that you gain a lot by hiding information for these questions the pattern is accessible but every time we add an extra click or other user interaction especially for assistive technology users it s worth verifying that it s an extra interaction that provides value platform directions remove the governance team label update issue title link to collab cycle request epic add your feedback remove the cc request label only if you created the ticket using the new issue link from the collaboration cycle reviews board add assignees based on collab cycle touchpoint design intent vfs designer vfs pm optional yourself optional midpoint review vfs pm yourself optional staging review qa only vfs pm yourself optional ,1 134776,19339871572.0,IssuesEvent,2021-12-15 02:20:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Update Mockups for Rated Disabilities,design vsa vsa-ebenefits Rated Disabilities,"## Background There is a new pattern for certain types of lists and Rated Disabilities might be a candidate for this work; we should update the mockups to reflect this new pattern and ensure it makes sense for our product before FE's implementation. ## Considerations - Has this been thoroughly researched? Do we have a choice? ## Tasks - [ ] Parlay the recent pattern changes into a mockup for FE to potentially implement. - [ ] TBD ## Acceptance Criteria - [ ] A mockup has been adjusted to include the latest pattern",1.0,"Update Mockups for Rated Disabilities - ## Background There is a new pattern for certain types of lists and Rated Disabilities might be a candidate for this work; we should update the mockups to reflect this new pattern and ensure it makes sense for our product before FE's implementation. ## Considerations - Has this been thoroughly researched? Do we have a choice? ## Tasks - [ ] Parlay the recent pattern changes into a mockup for FE to potentially implement. - [ ] TBD ## Acceptance Criteria - [ ] A mockup has been adjusted to include the latest pattern",1,update mockups for rated disabilities background there is a new pattern for certain types of lists and rated disabilities might be a candidate for this work we should update the mockups to reflect this new pattern and ensure it makes sense for our product before fe s implementation considerations has this been thoroughly researched do we have a choice tasks parlay the recent pattern changes into a mockup for fe to potentially implement tbd acceptance criteria a mockup has been adjusted to include the latest pattern,1 184748,32038709652.0,IssuesEvent,2023-09-22 17:24:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Bug - USWDS Pagination Component doesn't navigate pages,bug unplanned-work platform-design-system-team,"## Description [Original support request](https://dsva.slack.com/archives/CBU0KDSB1/p1695143745752579) USWDS Pagination doesn't handle keydown, so navigation between pages using previous and next, as well as clicking on page numbers, doesn't work. ## Steps to reproduce 1. Go to storybook 2. Scroll down to uswds pagination 3. Attempt to navigate ## Suggested fix Currently, previous, next, and page numbers are implemented as links. These links all contain `href=""javascript:void(0)""` but need to handle onClick. `onClick` should be added to the uswds links used to navigate. ## Tasks - [ ] Navigation in uswds pagination is handled properly ## Acceptance Criteria - [ ] Navigation has been fixed",1.0,"Bug - USWDS Pagination Component doesn't navigate pages - ## Description [Original support request](https://dsva.slack.com/archives/CBU0KDSB1/p1695143745752579) USWDS Pagination doesn't handle keydown, so navigation between pages using previous and next, as well as clicking on page numbers, doesn't work. ## Steps to reproduce 1. Go to storybook 2. Scroll down to uswds pagination 3. Attempt to navigate ## Suggested fix Currently, previous, next, and page numbers are implemented as links. These links all contain `href=""javascript:void(0)""` but need to handle onClick. `onClick` should be added to the uswds links used to navigate. ## Tasks - [ ] Navigation in uswds pagination is handled properly ## Acceptance Criteria - [ ] Navigation has been fixed",1,bug uswds pagination component doesn t navigate pages description uswds pagination doesn t handle keydown so navigation between pages using previous and next as well as clicking on page numbers doesn t work steps to reproduce go to storybook scroll down to uswds pagination attempt to navigate suggested fix currently previous next and page numbers are implemented as links these links all contain href javascript void but need to handle onclick onclick should be added to the uswds links used to navigate tasks navigation in uswds pagination is handled properly acceptance criteria navigation has been fixed,1 132790,18763593017.0,IssuesEvent,2021-11-05 19:43:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Request access to Google Analytics and/or Domo,analytics-insights analytics-request vaos-product-design access-request,"# Request Google Analytics and/or Domo access ## What this form is for Use this template to request access to Google Analytics and/or Domo. Please complete steps 1 & 2 below. ## 1. Access Requirements Please check the analytics tool(s) you need access to: - [x] Google Analytics - [x] Domo - [ ] (Platform Teams only) BigQuery ## 2. User Email Address to Receive Access **Due to privacy concerns, please do not put your email in this ticket.** Instead please use `/support` on the DSVA Slack channel [#vfs-platform-support](https://dsva.slack.com/channels/vfs-platform-support), select `Analytics` in the ""I need help from"" dropdown, and then add in the `Summary of request` section: 1. This issue's link 2. Emails that need access _Please note: For Google Analytics, if the user has a VA.gov email address or does not yet have a Google account, they will need to create one by visiting [this link](https://accounts.google.com/signup/v2/webcreateaccount?continue=https%3A%2F%2Faccounts.google.com%2FManageAccount&gmb=exp&biz=false&flowName=GlifWebSignIn&flowEntry=SignUp). Once at that link, VA.gov users and external users with email accounts that are not Google based should select the option ""Use my current email address instead""._ _Please list any additional requirements, if any (i.e. edit access). If you are requesting BigQuery access, please share if you will be hooking up an API._ _Once you receive access, you should receive a confirmation email directly from Google or Domo._ --- ## VSP Analytics & Insights Acceptance Criteria ### Definition of Done - [ ] Provide access to user - [ ] Ensure user received email confirmation ",1.0,"Request access to Google Analytics and/or Domo - # Request Google Analytics and/or Domo access ## What this form is for Use this template to request access to Google Analytics and/or Domo. Please complete steps 1 & 2 below. ## 1. Access Requirements Please check the analytics tool(s) you need access to: - [x] Google Analytics - [x] Domo - [ ] (Platform Teams only) BigQuery ## 2. User Email Address to Receive Access **Due to privacy concerns, please do not put your email in this ticket.** Instead please use `/support` on the DSVA Slack channel [#vfs-platform-support](https://dsva.slack.com/channels/vfs-platform-support), select `Analytics` in the ""I need help from"" dropdown, and then add in the `Summary of request` section: 1. This issue's link 2. Emails that need access _Please note: For Google Analytics, if the user has a VA.gov email address or does not yet have a Google account, they will need to create one by visiting [this link](https://accounts.google.com/signup/v2/webcreateaccount?continue=https%3A%2F%2Faccounts.google.com%2FManageAccount&gmb=exp&biz=false&flowName=GlifWebSignIn&flowEntry=SignUp). Once at that link, VA.gov users and external users with email accounts that are not Google based should select the option ""Use my current email address instead""._ _Please list any additional requirements, if any (i.e. edit access). If you are requesting BigQuery access, please share if you will be hooking up an API._ _Once you receive access, you should receive a confirmation email directly from Google or Domo._ --- ## VSP Analytics & Insights Acceptance Criteria ### Definition of Done - [ ] Provide access to user - [ ] Ensure user received email confirmation ",1,request access to google analytics and or domo request google analytics and or domo access what this form is for use this template to request access to google analytics and or domo please complete steps below access requirements please check the analytics tool s you need access to google analytics domo platform teams only bigquery user email address to receive access due to privacy concerns please do not put your email in this ticket instead please use support on the dsva slack channel select analytics in the i need help from dropdown and then add in the summary of request section this issue s link emails that need access please note for google analytics if the user has a va gov email address or does not yet have a google account they will need to create one by visiting once at that link va gov users and external users with email accounts that are not google based should select the option use my current email address instead please list any additional requirements if any i e edit access if you are requesting bigquery access please share if you will be hooking up an api once you receive access you should receive a confirmation email directly from google or domo vsp analytics insights acceptance criteria definition of done provide access to user ensure user received email confirmation ,1 137708,20201106181.0,IssuesEvent,2022-02-11 15:20:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,PromoBanner web component: accessibility review,vsp-design-system-team,"## Description We need to conduct a full accessibility review of the new PromoBanner web component. The component can be viewed in Storybook here: [insert Chromatic link] ## Acceptance Criteria - [ ] Full accessibility review of the PromoBanner component is completed - [ ] Add descriptions of any issues found to this ticket - [ ] If any problems are found, add screen recordings and/or screenshots to comments on this ticket that show the problem. - [ ] Alert Katy and the developer who built the component when the review is complete - [ ] Re-review any fixes the developer makes to the component",1.0,"PromoBanner web component: accessibility review - ## Description We need to conduct a full accessibility review of the new PromoBanner web component. The component can be viewed in Storybook here: [insert Chromatic link] ## Acceptance Criteria - [ ] Full accessibility review of the PromoBanner component is completed - [ ] Add descriptions of any issues found to this ticket - [ ] If any problems are found, add screen recordings and/or screenshots to comments on this ticket that show the problem. - [ ] Alert Katy and the developer who built the component when the review is complete - [ ] Re-review any fixes the developer makes to the component",1,promobanner web component accessibility review description we need to conduct a full accessibility review of the new promobanner web component the component can be viewed in storybook here acceptance criteria full accessibility review of the promobanner component is completed add descriptions of any issues found to this ticket if any problems are found add screen recordings and or screenshots to comments on this ticket that show the problem alert katy and the developer who built the component when the review is complete re review any fixes the developer makes to the component,1 135795,19665763422.0,IssuesEvent,2022-01-10 22:17:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Develop ProcessList web component,vsp-design-system-team,"## Description Build a web-component version of our [ProcessList React component](https://github.com/department-of-veterans-affairs/component-library/tree/master/packages/react-components/src/components/ProcessList). ## Details Styles: https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/blob/8ce0431d342a5be24170d9329e19257eb6e678db/packages/formation/sass/modules/_m-process-list.scss ## Acceptance Criteria - [ ] `va-process-list` is written - [ ] E2E tests are written - [ ] Storybook is updated",1.0,"Develop ProcessList web component - ## Description Build a web-component version of our [ProcessList React component](https://github.com/department-of-veterans-affairs/component-library/tree/master/packages/react-components/src/components/ProcessList). ## Details Styles: https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/blob/8ce0431d342a5be24170d9329e19257eb6e678db/packages/formation/sass/modules/_m-process-list.scss ## Acceptance Criteria - [ ] `va-process-list` is written - [ ] E2E tests are written - [ ] Storybook is updated",1,develop processlist web component description build a web component version of our details styles acceptance criteria va process list is written tests are written storybook is updated,1 80784,10059262541.0,IssuesEvent,2019-07-22 15:30:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Add Sub-brand guidelines to Design System, Content Section",content design system,"Suggestion: add page entitled Sub-brands to the content section at: https://design.va.gov/content-style-guide/sub-brands Proposed content (links to a page that does not yet exist, also a proposed issue): # Sub-brands VA.gov is designed to be a consistent and Veteran centered user experience. For that reason, it does not support the use of customized language, imagery, logos, word marks to represent sub-brands within the content of VA.gov outside of primary VA branding elements, VA.gov approved design system components, and visuals executed within the VA brand guidelines. This includes customized language, imagery, logos, and word marks for sub-brands such as * Departments * Sub-groups and/or committees * Special programs * Initiatives * Events Read about the design guidelines for VA.gov regarding the use of [custom logos](https://design.va.gov/design/using-custom-logos). Download the [VA Graphic Standards (PDF)](https://www.va.gov/opa/publications/graphicstandards/va_graphicstandardsguide_508_0113.pdf) to learn about the VA brand, visual identity, and related topics.",1.0,"Add Sub-brand guidelines to Design System, Content Section - Suggestion: add page entitled Sub-brands to the content section at: https://design.va.gov/content-style-guide/sub-brands Proposed content (links to a page that does not yet exist, also a proposed issue): # Sub-brands VA.gov is designed to be a consistent and Veteran centered user experience. For that reason, it does not support the use of customized language, imagery, logos, word marks to represent sub-brands within the content of VA.gov outside of primary VA branding elements, VA.gov approved design system components, and visuals executed within the VA brand guidelines. This includes customized language, imagery, logos, and word marks for sub-brands such as * Departments * Sub-groups and/or committees * Special programs * Initiatives * Events Read about the design guidelines for VA.gov regarding the use of [custom logos](https://design.va.gov/design/using-custom-logos). Download the [VA Graphic Standards (PDF)](https://www.va.gov/opa/publications/graphicstandards/va_graphicstandardsguide_508_0113.pdf) to learn about the VA brand, visual identity, and related topics.",1,add sub brand guidelines to design system content section suggestion add page entitled sub brands to the content section at proposed content links to a page that does not yet exist also a proposed issue sub brands va gov is designed to be a consistent and veteran centered user experience for that reason it does not support the use of customized language imagery logos word marks to represent sub brands within the content of va gov outside of primary va branding elements va gov approved design system components and visuals executed within the va brand guidelines this includes customized language imagery logos and word marks for sub brands such as departments sub groups and or committees special programs initiatives events read about the design guidelines for va gov regarding the use of download the to learn about the va brand visual identity and related topics ,1 131485,18291063601.0,IssuesEvent,2021-10-05 15:17:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Claim Status Tool - Research Discovery & Mapping,design vsa vsa-claims-appeals Claim Status Tool,"## Issue Description Review previous research. --- ## Tasks - [ ] Review data - [ ] Document known items in preparation for stakeholder meeting ## Acceptance Criteria - [ ] Document in GitHub --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Claim Status Tool - Research Discovery & Mapping - ## Issue Description Review previous research. --- ## Tasks - [ ] Review data - [ ] Document known items in preparation for stakeholder meeting ## Acceptance Criteria - [ ] Document in GitHub --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,claim status tool research discovery mapping issue description review previous research tasks review data document known items in preparation for stakeholder meeting acceptance criteria document in github how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 165813,26229039506.0,IssuesEvent,2023-01-04 21:44:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Objective: Improving the Legal Representative Experience,Epic design 1010-team legal-rep 1010-cg,"## User Story As a legal representative of a veteran I would like to know which files I should, and should not, upload to prove I have the ability to make healthcare decisions on behalf of a veteran. ## Expected Behavior - Decreased form drop off at file upload - Minimization of incorrect form(s) uploaded ## Acceptance Criteria ### What must be true in order for you to consider this epic complete? - [x] Research usability & Content Comprehension - [x] Design - [x] Improvements added to 10-10CG - [x] Staging review completed and approved - [x] ES accepts 10-10CG submissions ### Tickets to be created/groomed: - [x] Feature turned on in Staging, Prod - [x] Collab Cycle request (PM) - [x] Analytics - [ ] Update tags - [ ] Validate data flow - [x] QA (Collab Cycle) - [ ] Generate use cases (Engs) - [ ] Write test cases (QA) - [ ] Release plan complete - [x] Go/No-Go - [ ] Logging ",1.0,"Objective: Improving the Legal Representative Experience - ## User Story As a legal representative of a veteran I would like to know which files I should, and should not, upload to prove I have the ability to make healthcare decisions on behalf of a veteran. ## Expected Behavior - Decreased form drop off at file upload - Minimization of incorrect form(s) uploaded ## Acceptance Criteria ### What must be true in order for you to consider this epic complete? - [x] Research usability & Content Comprehension - [x] Design - [x] Improvements added to 10-10CG - [x] Staging review completed and approved - [x] ES accepts 10-10CG submissions ### Tickets to be created/groomed: - [x] Feature turned on in Staging, Prod - [x] Collab Cycle request (PM) - [x] Analytics - [ ] Update tags - [ ] Validate data flow - [x] QA (Collab Cycle) - [ ] Generate use cases (Engs) - [ ] Write test cases (QA) - [ ] Release plan complete - [x] Go/No-Go - [ ] Logging ",1,objective improving the legal representative experience user story as a legal representative of a veteran i would like to know which files i should and should not upload to prove i have the ability to make healthcare decisions on behalf of a veteran expected behavior decreased form drop off at file upload minimization of incorrect form s uploaded acceptance criteria what must be true in order for you to consider this epic complete research usability content comprehension design improvements added to staging review completed and approved es accepts submissions tickets to be created groomed feature turned on in staging prod collab cycle request pm analytics update tags validate data flow qa collab cycle generate use cases engs write test cases qa release plan complete go no go logging ,1 184073,31815308212.0,IssuesEvent,2023-09-13 19:58:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Update Support question in Satisfaction Survey,service-design,"## Purpose The Support team has reached out to ask if we can update the question about their channel, particularly to make it easier to understand. After some discussion and exchanges, here is the new form of the question that needs to replace the existing one in the Survey: _I receive the help I need from the Platform Support Team (#vfs-platform-support)_ ## Tasks - [ ] Update the question in the Survey ## Acceptance Criteria - [ ] Survey displays the updated question ",1.0,"Update Support question in Satisfaction Survey - ## Purpose The Support team has reached out to ask if we can update the question about their channel, particularly to make it easier to understand. After some discussion and exchanges, here is the new form of the question that needs to replace the existing one in the Survey: _I receive the help I need from the Platform Support Team (#vfs-platform-support)_ ## Tasks - [ ] Update the question in the Survey ## Acceptance Criteria - [ ] Survey displays the updated question ",1,update support question in satisfaction survey purpose the support team has reached out to ask if we can update the question about their channel particularly to make it easier to understand after some discussion and exchanges here is the new form of the question that needs to replace the existing one in the survey i receive the help i need from the platform support team vfs platform support tasks update the question in the survey acceptance criteria survey displays the updated question ,1 167706,26537316381.0,IssuesEvent,2023-01-19 16:31:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[EPIC] MVH to VA.gov: Immunizations: Knowledge transfer to MHV,Epic backend design research product my-health my-health-MR-CORE MHV-to-VA.gov-PI9,"[ ] Review user interview findings, recommendations, and provide links to documentation and related Murals [ ] Review low-fi mockups [ ] Review feedback from Design Intent [ ] Provide links to mockups, decision logs, domain brief, comparative analysis, and any other pertinent design documents or assets [ ] Provide overview of technical discovery findings and links to technical documentation [ ] Tag ByLight team on Collab Cycle ticket and feedback",1.0,"[EPIC] MVH to VA.gov: Immunizations: Knowledge transfer to MHV - [ ] Review user interview findings, recommendations, and provide links to documentation and related Murals [ ] Review low-fi mockups [ ] Review feedback from Design Intent [ ] Provide links to mockups, decision logs, domain brief, comparative analysis, and any other pertinent design documents or assets [ ] Provide overview of technical discovery findings and links to technical documentation [ ] Tag ByLight team on Collab Cycle ticket and feedback",1, mvh to va gov immunizations knowledge transfer to mhv review user interview findings recommendations and provide links to documentation and related murals review low fi mockups review feedback from design intent provide links to mockups decision logs domain brief comparative analysis and any other pertinent design documents or assets provide overview of technical discovery findings and links to technical documentation tag bylight team on collab cycle ticket and feedback,1 164796,26025202303.0,IssuesEvent,2022-12-21 15:47:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,MyHealth - Assist with onboarding new MHV team for Medical Records,frontend backend design research product onboarding my-health my-health-MR-CORE MHV-to-VA.gov-PI9,"## Issue Description The team that will be building Medical Records on VA.gov has not worked on VA.gov before and will need some assistance with getting onboarded and acclimated to the environment. --- ## Tasks - [ ] Introduce the team to the [Onboarding Documentation in GitHub](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/digital-health-modernization/mhv-to-va.gov/team-onboarding/product-team-onboarding.md) ## Acceptance Criteria - [ ] The new team will have access to a quick guide that hits the highlights of how to get onboarded. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"MyHealth - Assist with onboarding new MHV team for Medical Records - ## Issue Description The team that will be building Medical Records on VA.gov has not worked on VA.gov before and will need some assistance with getting onboarded and acclimated to the environment. --- ## Tasks - [ ] Introduce the team to the [Onboarding Documentation in GitHub](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/digital-health-modernization/mhv-to-va.gov/team-onboarding/product-team-onboarding.md) ## Acceptance Criteria - [ ] The new team will have access to a quick guide that hits the highlights of how to get onboarded. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,myhealth assist with onboarding new mhv team for medical records issue description the team that will be building medical records on va gov has not worked on va gov before and will need some assistance with getting onboarded and acclimated to the environment tasks introduce the team to the acceptance criteria the new team will have access to a quick guide that hits the highlights of how to get onboarded how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 149187,23442278292.0,IssuesEvent,2022-08-15 15:59:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Update Wireframes to Use New Memorable DS Component,design HCE-Checkin,"## Tasks - Pull in VA DS library for the new Memorable DS component - Update the Abstract wireframes for LoROTA Security Updates to use the new Memorable DS component from the library",1.0,"[Design] Update Wireframes to Use New Memorable DS Component - ## Tasks - Pull in VA DS library for the new Memorable DS component - Update the Abstract wireframes for LoROTA Security Updates to use the new Memorable DS component from the library",1, update wireframes to use new memorable ds component tasks pull in va ds library for the new memorable ds component update the abstract wireframes for lorota security updates to use the new memorable ds component from the library,1 102163,12748530113.0,IssuesEvent,2020-06-26 20:20:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Update time and notify parties for URL redirect,design needs-grooming profile vsa-authenticated-exp,"I am creating this ticket to remind myself to update the time and notify parties for URL redirect once we know the dates that the profile will be 100% rolled out. [Redirect issue](https://github.com/department-of-veterans-affairs/va.gov-team/issues/10688)",1.0,"[Design] Update time and notify parties for URL redirect - I am creating this ticket to remind myself to update the time and notify parties for URL redirect once we know the dates that the profile will be 100% rolled out. [Redirect issue](https://github.com/department-of-veterans-affairs/va.gov-team/issues/10688)",1, update time and notify parties for url redirect i am creating this ticket to remind myself to update the time and notify parties for url redirect once we know the dates that the profile will be rolled out ,1 142984,21923203056.0,IssuesEvent,2022-05-22 21:56:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Clean up dependencies in component-library,discovery vsp-design-system-team,"## Issue Description Now that we have moved `formation-react` into a new [`component-library` repo](https://github.com/department-of-veterans-affairs/component-library), we've discovered some dependencies that aren't really necessary. They are artifacts of the old lerna structure. As an example, `react-router` is a dependency, but it is only used in a unit test. This is an example of something that can probably be removed and be handled in a better way. --- ## Tasks - [ ] See which dependencies can be removed/upgraded ## Acceptance Criteria - [ ] Dependencies are simplified",1.0,"Clean up dependencies in component-library - ## Issue Description Now that we have moved `formation-react` into a new [`component-library` repo](https://github.com/department-of-veterans-affairs/component-library), we've discovered some dependencies that aren't really necessary. They are artifacts of the old lerna structure. As an example, `react-router` is a dependency, but it is only used in a unit test. This is an example of something that can probably be removed and be handled in a better way. --- ## Tasks - [ ] See which dependencies can be removed/upgraded ## Acceptance Criteria - [ ] Dependencies are simplified",1,clean up dependencies in component library issue description now that we have moved formation react into a new we ve discovered some dependencies that aren t really necessary they are artifacts of the old lerna structure as an example react router is a dependency but it is only used in a unit test this is an example of something that can probably be removed and be handled in a better way tasks see which dependencies can be removed upgraded acceptance criteria dependencies are simplified,1 129539,17793602096.0,IssuesEvent,2021-08-31 19:13:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Notice of Disagreement - Decision Date language change,design vsa vsa-claims-appeals NOD,"## Issue Description When entering issues by hand, the decision date entry screen displays an error if the date is in the future. The error says “Please add a past decision date.” Recommend the language be changed to something more understandable, like “You can only appeal a decision that has already been issued. Please check the date and try again.” --- ## Tasks - [ ] Update language for clarity ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Notice of Disagreement - Decision Date language change - ## Issue Description When entering issues by hand, the decision date entry screen displays an error if the date is in the future. The error says “Please add a past decision date.” Recommend the language be changed to something more understandable, like “You can only appeal a decision that has already been issued. Please check the date and try again.” --- ## Tasks - [ ] Update language for clarity ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,notice of disagreement decision date language change issue description when entering issues by hand the decision date entry screen displays an error if the date is in the future the error says “please add a past decision date ” recommend the language be changed to something more understandable like “you can only appeal a decision that has already been issued please check the date and try again ” tasks update language for clarity acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 182824,30989414307.0,IssuesEvent,2023-08-09 02:25:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,FE Implementation of New Claim Card,frontend backend design Claim Status Tool benefits-team-1 squad-1,"## Value Statement **_As a_** veteran checking the status of their disability claim **_I want to_** be able to distinguish my claims from one another **_So that_** I can reference it if I need to contact the call center or provide that info to my representative. --- ## Background Context - Initial decision research shows that veterans would like this feature. ## Design Concept ![Group 20](https://github.com/department-of-veterans-affairs/va.gov-team/assets/95102058/5291ffe0-263a-4d6b-bd7e-f01a94898a8b) ## Acceptance Criteria - [x] Implementation is complete for all claim & decision review cards ## Designs and Build Notes - [x] Implementation should match the [Sketch](https://www.sketch.com/s/98e35645-34eb-40cf-80c1-6c4952943584/p/B9C46ABC-36AD-4CA8-9896-55762FC6912E/canvas) design ## Out of scope - Claim details page ## Open questions - Add here ## Tasks - [ ] _Task_ - [ ] _Task_ - [ ] _Task_ ## Definition of Ready - [ ] Clear value description - [ ] Testable acceptance criteria - [ ] Accessibility added to acceptance criteria - [ ] Approved designs attached - [ ] Sample data provided where appropriate - [ ] Estimated to fit within the sprint - [ ] Dependencies and blockers linked ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"FE Implementation of New Claim Card - ## Value Statement **_As a_** veteran checking the status of their disability claim **_I want to_** be able to distinguish my claims from one another **_So that_** I can reference it if I need to contact the call center or provide that info to my representative. --- ## Background Context - Initial decision research shows that veterans would like this feature. ## Design Concept ![Group 20](https://github.com/department-of-veterans-affairs/va.gov-team/assets/95102058/5291ffe0-263a-4d6b-bd7e-f01a94898a8b) ## Acceptance Criteria - [x] Implementation is complete for all claim & decision review cards ## Designs and Build Notes - [x] Implementation should match the [Sketch](https://www.sketch.com/s/98e35645-34eb-40cf-80c1-6c4952943584/p/B9C46ABC-36AD-4CA8-9896-55762FC6912E/canvas) design ## Out of scope - Claim details page ## Open questions - Add here ## Tasks - [ ] _Task_ - [ ] _Task_ - [ ] _Task_ ## Definition of Ready - [ ] Clear value description - [ ] Testable acceptance criteria - [ ] Accessibility added to acceptance criteria - [ ] Approved designs attached - [ ] Sample data provided where appropriate - [ ] Estimated to fit within the sprint - [ ] Dependencies and blockers linked ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,fe implementation of new claim card value statement as a veteran checking the status of their disability claim i want to be able to distinguish my claims from one another so that i can reference it if i need to contact the call center or provide that info to my representative background context initial decision research shows that veterans would like this feature design concept acceptance criteria implementation is complete for all claim decision review cards designs and build notes implementation should match the design out of scope claim details page open questions add here tasks task task task definition of ready clear value description testable acceptance criteria accessibility added to acceptance criteria approved designs attached sample data provided where appropriate estimated to fit within the sprint dependencies and blockers linked definition of done meets acceptance criteria passed testing coverage passed unit testing coverage passed integration testing if applicable code reviewed internal submitted to staging reviewed and approved by product and or design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 184216,31840472356.0,IssuesEvent,2023-09-14 15:58:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Feedback portal log/review,service-design,"## Purpose HMW Portal submission --> action? How/When should we review items submitted to the Feedback Portal? Update: having an automated Domo dashboard eliminates this, unless team wants to take on addressing issues rather than presenting them To make good on our bet for continuous feedback, the feedback must reach viable parties continuously as well. What would be the best way for SDT to review the feedback as it comes in, and where/how should that get shared out? -Constantly available repository? -Directed communications to relevant team(s)? -Who needs to see what? Page [here](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2737700945/Platform+Feedback+Portal+Log+Review). ### Bets: -Teams are more likely to go to a Domo page (which many teams already use) to view these when they want to -Seems like a good idea to also include these w/ Platform Satisfaction Survey readout ## Tasks - [x] Decided on MVP being Airtable to Domo - [x] decide whether we need to build out the airtable w/ additional functionality or references? - [x] Get access to Domo Dashboard - [x] Can hook Airtable data to Domo Dashboard? - [x] create a test Domo page from Airtable data (many steps to learn [here](https://domo-support.domo.com/s/article/360043427613?language=en_US)) - [x] Prep and share [deck](https://docs.google.com/presentation/d/1DywD_d-YQpemaEbG4LOc7wHm9gPJa26abkhKBahkr9g/edit#slide=id.g243d846b8ce_0_18) for Demo Day - [x] Get team feedback and revise - [x] Share at Demo Day - [x] [Draft Slack announcement](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2763587617/Feedback+Portal+Domo+announcement) to #platform-team - [x] Share/announce resource ## Acceptance Criteria - [ ] Resource is created - [ ] Resource is publicized ",1.0,"Feedback portal log/review - ## Purpose HMW Portal submission --> action? How/When should we review items submitted to the Feedback Portal? Update: having an automated Domo dashboard eliminates this, unless team wants to take on addressing issues rather than presenting them To make good on our bet for continuous feedback, the feedback must reach viable parties continuously as well. What would be the best way for SDT to review the feedback as it comes in, and where/how should that get shared out? -Constantly available repository? -Directed communications to relevant team(s)? -Who needs to see what? Page [here](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2737700945/Platform+Feedback+Portal+Log+Review). ### Bets: -Teams are more likely to go to a Domo page (which many teams already use) to view these when they want to -Seems like a good idea to also include these w/ Platform Satisfaction Survey readout ## Tasks - [x] Decided on MVP being Airtable to Domo - [x] decide whether we need to build out the airtable w/ additional functionality or references? - [x] Get access to Domo Dashboard - [x] Can hook Airtable data to Domo Dashboard? - [x] create a test Domo page from Airtable data (many steps to learn [here](https://domo-support.domo.com/s/article/360043427613?language=en_US)) - [x] Prep and share [deck](https://docs.google.com/presentation/d/1DywD_d-YQpemaEbG4LOc7wHm9gPJa26abkhKBahkr9g/edit#slide=id.g243d846b8ce_0_18) for Demo Day - [x] Get team feedback and revise - [x] Share at Demo Day - [x] [Draft Slack announcement](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2763587617/Feedback+Portal+Domo+announcement) to #platform-team - [x] Share/announce resource ## Acceptance Criteria - [ ] Resource is created - [ ] Resource is publicized ",1,feedback portal log review purpose hmw portal submission action how when should we review items submitted to the feedback portal update having an automated domo dashboard eliminates this unless team wants to take on addressing issues rather than presenting them to make good on our bet for continuous feedback the feedback must reach viable parties continuously as well what would be the best way for sdt to review the feedback as it comes in and where how should that get shared out constantly available repository directed communications to relevant team s who needs to see what page bets teams are more likely to go to a domo page which many teams already use to view these when they want to seems like a good idea to also include these w platform satisfaction survey readout tasks decided on mvp being airtable to domo decide whether we need to build out the airtable w additional functionality or references get access to domo dashboard can hook airtable data to domo dashboard create a test domo page from airtable data many steps to learn prep and share for demo day get team feedback and revise share at demo day to platform team share announce resource acceptance criteria resource is created resource is publicized ,1 179285,30213165538.0,IssuesEvent,2023-07-05 14:01:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Spike] - Identify Appointment Types being Displayed in VAOS,frontend backend spike appointments-product-design,"## Background/Request It is believed that Compensation & Pension (C&P) appointments are now being displayed in VAOS after the move to the new VAOS service. However, we have no evidence that this is happening. This request is to create logging to capture the different appointment types being displayed in VAOS to veterans. ### Goal The goal is to determine if C&P appointments are currently being displayed in VAOS. Secondary to that goal would be to capture any other appointment types that are also being displayed. ### Requirements to Consider Not looking to capture details of the C&P Appointments. Ideally, a count of the number of different appointment types would be useful, but not necessary. The main goal is to identify the distinct types of appointments being displayed in VAOS. ### **Technical Notes** To determine the appointment type look at `Appointment.serviceCategory` A Compensation & Pension appointment will look like this: ``` serviceCategory = [ { ""coding"": [ { ""system"": ""http://www.va.gov/Terminology/VistADefinedTerms/409_1"", ""code"": ""COMPENSATION & PENSION"" } ] ] ``` This is the list of national values that will appear for the code: ``` COMPENSATION & PENSION CLASS II DENTAL ORGAN DONORS EMPLOYEE PRIMA FACIA RESEARCH COLLATERAL OF VET. SHARING AGREEMENT REGULAR COMPUTER GENERATED SERVICE CONNECTED ``` If a site has defined a custom appointment type _it's possible_ you might see other values. An appointment type of `REGULAR` is a health appointment. To test this in SQA you need an appointment created that has that appt type, and the clinic has to be returned by the CDW service with `displayAppointment` set to true. For testing, create an appointment in an existing clinic in SQA (that is technically not a C&P clinic). Per Marcy, we don't have any C&P clinics configured in Staging. However, she can make an appointment for you in a clinic and set the appointment type to C&P. If she needs to create C&P Clinics for testing then that takes time, because she needs to know stop codes and then log a ticket to get created in Mock CDW. Use `Judy Morrison` as the test user. --- ## Tasks - Answer the following questions: - Q Are C&P appointments being displayed in VAOS? - Q What other appointment types are also being displayed in VAOS? ## Time Box 6 hours ## Definition of Done - Tasks are complete - Research and recommendations are documented in this ticket --- ## How to configure this issue - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) ",1.0,"[Spike] - Identify Appointment Types being Displayed in VAOS - ## Background/Request It is believed that Compensation & Pension (C&P) appointments are now being displayed in VAOS after the move to the new VAOS service. However, we have no evidence that this is happening. This request is to create logging to capture the different appointment types being displayed in VAOS to veterans. ### Goal The goal is to determine if C&P appointments are currently being displayed in VAOS. Secondary to that goal would be to capture any other appointment types that are also being displayed. ### Requirements to Consider Not looking to capture details of the C&P Appointments. Ideally, a count of the number of different appointment types would be useful, but not necessary. The main goal is to identify the distinct types of appointments being displayed in VAOS. ### **Technical Notes** To determine the appointment type look at `Appointment.serviceCategory` A Compensation & Pension appointment will look like this: ``` serviceCategory = [ { ""coding"": [ { ""system"": ""http://www.va.gov/Terminology/VistADefinedTerms/409_1"", ""code"": ""COMPENSATION & PENSION"" } ] ] ``` This is the list of national values that will appear for the code: ``` COMPENSATION & PENSION CLASS II DENTAL ORGAN DONORS EMPLOYEE PRIMA FACIA RESEARCH COLLATERAL OF VET. SHARING AGREEMENT REGULAR COMPUTER GENERATED SERVICE CONNECTED ``` If a site has defined a custom appointment type _it's possible_ you might see other values. An appointment type of `REGULAR` is a health appointment. To test this in SQA you need an appointment created that has that appt type, and the clinic has to be returned by the CDW service with `displayAppointment` set to true. For testing, create an appointment in an existing clinic in SQA (that is technically not a C&P clinic). Per Marcy, we don't have any C&P clinics configured in Staging. However, she can make an appointment for you in a clinic and set the appointment type to C&P. If she needs to create C&P Clinics for testing then that takes time, because she needs to know stop codes and then log a ticket to get created in Mock CDW. Use `Judy Morrison` as the test user. --- ## Tasks - Answer the following questions: - Q Are C&P appointments being displayed in VAOS? - Q What other appointment types are also being displayed in VAOS? ## Time Box 6 hours ## Definition of Done - Tasks are complete - Research and recommendations are documented in this ticket --- ## How to configure this issue - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) ",1, identify appointment types being displayed in vaos background request it is believed that compensation pension c p appointments are now being displayed in vaos after the move to the new vaos service however we have no evidence that this is happening this request is to create logging to capture the different appointment types being displayed in vaos to veterans goal the goal is to determine if c p appointments are currently being displayed in vaos secondary to that goal would be to capture any other appointment types that are also being displayed requirements to consider not looking to capture details of the c p appointments ideally a count of the number of different appointment types would be useful but not necessary the main goal is to identify the distinct types of appointments being displayed in vaos technical notes to determine the appointment type look at appointment servicecategory a compensation pension appointment will look like this servicecategory coding system code compensation pension this is the list of national values that will appear for the code compensation pension class ii dental organ donors employee prima facia research collateral of vet sharing agreement regular computer generated service connected if a site has defined a custom appointment type it s possible you might see other values an appointment type of regular is a health appointment to test this in sqa you need an appointment created that has that appt type and the clinic has to be returned by the cdw service with displayappointment set to true for testing create an appointment in an existing clinic in sqa that is technically not a c p clinic per marcy we don t have any c p clinics configured in staging however she can make an appointment for you in a clinic and set the appointment type to c p if she needs to create c p clinics for testing then that takes time because she needs to know stop codes and then log a ticket to get created in mock cdw use judy morrison as the test user tasks answer the following questions q are c p appointments being displayed in vaos q what other appointment types are also being displayed in vaos time box hours definition of done tasks are complete research and recommendations are documented in this ticket how to configure this issue attached to an epic what body of work is this a part of labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 138254,20379985877.0,IssuesEvent,2022-02-21 20:16:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Customer Feedback Loop - Measuring Impact of Platform Product Launches and Updates,Epic service-design VSP-Initiative,"## Problem Statement As a VSP lead or product manager, I need to be able to determine if my products are having a measurable impact on VFS teams. How might we make a habit of building feedback loops for individual Platform products to drive decision-making based on granular user feedback and analytics? ## Hypothesis or Bet If we track the impact of product launches based on usage and other metrics, we expect to set up KPIs and strategies to improve our products based on a better understanding of how they are being used ## We will know we're done when... (""Definition of Done"") We have implemented the continuous customer feedback loops for all Platform products: https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1580853363126/ef5036613c38f1afeffbc082f28d2d8016c66a4a ## Known Blockers/Dependencies *List any blockers or dependencies for this work to be completed* ## Projected Launch Date * When do you expect to be completed rolling out this initiative* ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. [VSP Product Terminology](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md) for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1.0,"Customer Feedback Loop - Measuring Impact of Platform Product Launches and Updates - ## Problem Statement As a VSP lead or product manager, I need to be able to determine if my products are having a measurable impact on VFS teams. How might we make a habit of building feedback loops for individual Platform products to drive decision-making based on granular user feedback and analytics? ## Hypothesis or Bet If we track the impact of product launches based on usage and other metrics, we expect to set up KPIs and strategies to improve our products based on a better understanding of how they are being used ## We will know we're done when... (""Definition of Done"") We have implemented the continuous customer feedback loops for all Platform products: https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1580853363126/ef5036613c38f1afeffbc082f28d2d8016c66a4a ## Known Blockers/Dependencies *List any blockers or dependencies for this work to be completed* ## Projected Launch Date * When do you expect to be completed rolling out this initiative* ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. [VSP Product Terminology](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md) for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1,customer feedback loop measuring impact of platform product launches and updates problem statement as a vsp lead or product manager i need to be able to determine if my products are having a measurable impact on vfs teams how might we make a habit of building feedback loops for individual platform products to drive decision making based on granular user feedback and analytics hypothesis or bet if we track the impact of product launches based on usage and other metrics we expect to set up kpis and strategies to improve our products based on a better understanding of how they are being used we will know we re done when definition of done we have implemented the continuous customer feedback loops for all platform products known blockers dependencies list any blockers or dependencies for this work to be completed projected launch date when do you expect to be completed rolling out this initiative launch checklist guidance delete before posting this checklist is intended to be used to help answer is my vsp initiative ready for launch all of the items in this checklist should be completed with artifacts linked or have a brief explanation of why they ve been skipped before launching a given vsp initiative all links or explanations can be provided in required artifacts sections the items that can be skipped are marked as such keep in mind the distinction between product and initiative each product needs specific supporting documentation but initiatives to improve existing products should reuse existing documentation for that product for details is this service tool feature tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a checked into note the product directory name should match with the list of vsp products external facing a exists for this product feature tool and should be located at platform product name readme md external facing a exists for this product feature tool and is updated for changes from this initiative and should be linked from the vfs facing readme for your product and should be located within platform product name unless you already have another location for it if applicable and post to about whether this should be added to the if applicable post to for external communication about this change e g vsp newsletter customer facing meetings measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying required artifacts documentation product name directory name used for your product documentation product outline link to product outline readme link to vfs facing readme for your product user guide link to user guide testing usability test link to github issue or provide reason for skipping manual qa link to github issue or documented results automated tests link to tests or n a measurement success metrics link to where success metrics are measured or where they re defined product outline is ok or provide reason for skipping release plan link to release plan ticket todos convert this issue to an epic add your team s label to this epic ,1 55526,14532718756.0,IssuesEvent,2020-12-14 22:57:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"508-defect-2 [ZOOM, MOBILE DESIGN]: Screen content must be responsive to the viewport size",508-defect-2 508-issue-mobile-design 508/Accessibility vsa vsa-facilities,"# [508-defect-2](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-2) ## Feedback framework - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix.
## Point of Contact **VFS Point of Contact:** Jennifer ## User Story or Problem Statement As a user who uses magnification plugins, I expect screen content to adjust to a magnified screen sizing, so that I am able to understand and interact with screen content. ## Details When the screen is zoomed to 200% or 400%, the page content is cut off. 400% isn't too bad, but due to the tabs, it's not usable with the search results. ## Acceptance Criteria - [ ] When the screen is zoomed, the screen content should responsively render and be usable. ## Environment * Operating System: all * Browser: all * Server destination: staging ## Steps to Recreate 1. Enter `https://staging.va.gov/find-locations/?address=Portland%2C%20Maine%2004103%2C%20United%20States&context=Portland%2C%20Maine%2004103%2C%20United%20States&facilityType=health&location=43.69%2C-70.30&page=1&serviceType&searchString=Portland%2C%20Maine%2004103%2C%20United%20States#content` in browser 2. Use developer tools to set the browser width to 1280 pixels wide 3. Zoom the browser to 200%, then 400% 4. Verify that the map UI is cut off and it isn't possible to scroll to use see the button and map ## WCAG or Vendor Guidance (optional) * [WCAG 2.0 Level A - 1.4.4, F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured](https://www.w3.org/TR/WCAG20-TECHS/F69.html) ## Screenshots or Trace Logs ![Screen Shot 2020-12-14 at 5 35 27 PM](https://user-images.githubusercontent.com/57469/102145654-9b9eda80-3e35-11eb-801d-58f693eb965d.png) ![Screen Shot 2020-12-14 at 5 32 34 PM](https://user-images.githubusercontent.com/57469/102145656-9c377100-3e35-11eb-865c-5f42c835707b.png) ",1.0,"508-defect-2 [ZOOM, MOBILE DESIGN]: Screen content must be responsive to the viewport size - # [508-defect-2](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/defect-severity-rubric.md#508-defect-2) ## Feedback framework - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix.
## Point of Contact **VFS Point of Contact:** Jennifer ## User Story or Problem Statement As a user who uses magnification plugins, I expect screen content to adjust to a magnified screen sizing, so that I am able to understand and interact with screen content. ## Details When the screen is zoomed to 200% or 400%, the page content is cut off. 400% isn't too bad, but due to the tabs, it's not usable with the search results. ## Acceptance Criteria - [ ] When the screen is zoomed, the screen content should responsively render and be usable. ## Environment * Operating System: all * Browser: all * Server destination: staging ## Steps to Recreate 1. Enter `https://staging.va.gov/find-locations/?address=Portland%2C%20Maine%2004103%2C%20United%20States&context=Portland%2C%20Maine%2004103%2C%20United%20States&facilityType=health&location=43.69%2C-70.30&page=1&serviceType&searchString=Portland%2C%20Maine%2004103%2C%20United%20States#content` in browser 2. Use developer tools to set the browser width to 1280 pixels wide 3. Zoom the browser to 200%, then 400% 4. Verify that the map UI is cut off and it isn't possible to scroll to use see the button and map ## WCAG or Vendor Guidance (optional) * [WCAG 2.0 Level A - 1.4.4, F69: Failure of Success Criterion 1.4.4 when resizing visually rendered text up to 200 percent causes the text, image or controls to be clipped, truncated or obscured](https://www.w3.org/TR/WCAG20-TECHS/F69.html) ## Screenshots or Trace Logs ![Screen Shot 2020-12-14 at 5 35 27 PM](https://user-images.githubusercontent.com/57469/102145654-9b9eda80-3e35-11eb-801d-58f693eb965d.png) ![Screen Shot 2020-12-14 at 5 32 34 PM](https://user-images.githubusercontent.com/57469/102145656-9c377100-3e35-11eb-865c-5f42c835707b.png) ",0, defect screen content must be responsive to the viewport size feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact jennifer user story or problem statement as a user who uses magnification plugins i expect screen content to adjust to a magnified screen sizing so that i am able to understand and interact with screen content details when the screen is zoomed to or the page content is cut off isn t too bad but due to the tabs it s not usable with the search results acceptance criteria when the screen is zoomed the screen content should responsively render and be usable environment operating system all browser all server destination staging steps to recreate enter in browser use developer tools to set the browser width to pixels wide zoom the browser to then verify that the map ui is cut off and it isn t possible to scroll to use see the button and map wcag or vendor guidance optional screenshots or trace logs ,0 154190,24258397608.0,IssuesEvent,2022-09-27 19:58:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Host workshop to consider scenarios,service-design,"## Issue Description Discuss scenarios to consider for the map concept **Proposed: Change this time slot to unpacking Project-based structure changes, with understanding of how this affects mapping progress later.** Scenarios [mural](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1662520899531/f689e9b30e36c43e40b04bdee26ef55f25b45635?sender=u4397b715dc3690a417b71483) ## Tasks - [x] schedule workshop - [x] conduct workshop to discuss and prioritize scenarios for the map See Pivot - [ ] synthesize rankings and findings from this exercise ## Acceptance Criteria - [x] scenarios discussed and prioritized See Pivot - [ ] synthesis completed ### Pivot Due to change from team to project-focused technical teams, the mapping artifact was removed. The scenarios exploration will instead serve as a lens that we will consider future initiatives through.",1.0,"Host workshop to consider scenarios - ## Issue Description Discuss scenarios to consider for the map concept **Proposed: Change this time slot to unpacking Project-based structure changes, with understanding of how this affects mapping progress later.** Scenarios [mural](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1662520899531/f689e9b30e36c43e40b04bdee26ef55f25b45635?sender=u4397b715dc3690a417b71483) ## Tasks - [x] schedule workshop - [x] conduct workshop to discuss and prioritize scenarios for the map See Pivot - [ ] synthesize rankings and findings from this exercise ## Acceptance Criteria - [x] scenarios discussed and prioritized See Pivot - [ ] synthesis completed ### Pivot Due to change from team to project-focused technical teams, the mapping artifact was removed. The scenarios exploration will instead serve as a lens that we will consider future initiatives through.",1,host workshop to consider scenarios issue description discuss scenarios to consider for the map concept proposed change this time slot to unpacking project based structure changes with understanding of how this affects mapping progress later scenarios tasks schedule workshop conduct workshop to discuss and prioritize scenarios for the map see pivot synthesize rankings and findings from this exercise acceptance criteria scenarios discussed and prioritized see pivot synthesis completed pivot due to change from team to project focused technical teams the mapping artifact was removed the scenarios exploration will instead serve as a lens that we will consider future initiatives through ,1 128701,17601166625.0,IssuesEvent,2021-08-17 12:03:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Displaying the Call Center phone number (Vet Center),design vsa vsa-facilities vet-center,"## Issue Description As a Veteran, I need to know how to contact someone representing my local Vet Center. **Current protocol** - As of 12/21, the Vet Center call center only does warm handoffs to the crisis line. - The Call center gives the local Vet Center contact info to the Veteran and sends an email to the relevant local Vet Center about the Veteran's call (generally within a few hours) - If a Veteran calls the Vet Center directly after hours, he/she is patched through to the Call Center. - There is a new director for the Call Center so this process is subject to change. --- ## Tasks - [ ] Consider the best display for the Call Center considering no warm handoff is given ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Displaying the Call Center phone number (Vet Center) - ## Issue Description As a Veteran, I need to know how to contact someone representing my local Vet Center. **Current protocol** - As of 12/21, the Vet Center call center only does warm handoffs to the crisis line. - The Call center gives the local Vet Center contact info to the Veteran and sends an email to the relevant local Vet Center about the Veteran's call (generally within a few hours) - If a Veteran calls the Vet Center directly after hours, he/she is patched through to the Call Center. - There is a new director for the Call Center so this process is subject to change. --- ## Tasks - [ ] Consider the best display for the Call Center considering no warm handoff is given ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,displaying the call center phone number vet center issue description as a veteran i need to know how to contact someone representing my local vet center current protocol as of the vet center call center only does warm handoffs to the crisis line the call center gives the local vet center contact info to the veteran and sends an email to the relevant local vet center about the veteran s call generally within a few hours if a veteran calls the vet center directly after hours he she is patched through to the call center there is a new director for the call center so this process is subject to change tasks consider the best display for the call center considering no warm handoff is given acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 124552,16614121296.0,IssuesEvent,2021-06-02 14:47:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Request Content Review for Search Representative,design vsa vsa-ebenefits,"### Background There are currently two tools for searching for accredited representative to help Veterans with their VA benefits claims. the office of General Counsel supports one, the other is connected to the ""add representative"" feature in eBenefits. Neither is an optimal experience for users. The EBN team is migrating the feature from the eBenefits site and decoupling it from the digital form. A set of static mockup were created to explore a stepwise approach to search functionality. It has minimal textual content but will require review for adherence to plain-language mandates. ### Tasks - [ ] Provide context to sitewide content team - [ ] Provide access to the latest mocks or prototypes - [ ] Attend office hours to discuss content needs a nd direction ### Acceptance criteria - [x] Search rep feature is scheduled for content review or submitted and pending",1.0,"Request Content Review for Search Representative - ### Background There are currently two tools for searching for accredited representative to help Veterans with their VA benefits claims. the office of General Counsel supports one, the other is connected to the ""add representative"" feature in eBenefits. Neither is an optimal experience for users. The EBN team is migrating the feature from the eBenefits site and decoupling it from the digital form. A set of static mockup were created to explore a stepwise approach to search functionality. It has minimal textual content but will require review for adherence to plain-language mandates. ### Tasks - [ ] Provide context to sitewide content team - [ ] Provide access to the latest mocks or prototypes - [ ] Attend office hours to discuss content needs a nd direction ### Acceptance criteria - [x] Search rep feature is scheduled for content review or submitted and pending",1,request content review for search representative background there are currently two tools for searching for accredited representative to help veterans with their va benefits claims the office of general counsel supports one the other is connected to the add representative feature in ebenefits neither is an optimal experience for users the ebn team is migrating the feature from the ebenefits site and decoupling it from the digital form a set of static mockup were created to explore a stepwise approach to search functionality it has minimal textual content but will require review for adherence to plain language mandates tasks provide context to sitewide content team provide access to the latest mocks or prototypes attend office hours to discuss content needs a nd direction acceptance criteria search rep feature is scheduled for content review or submitted and pending,1 105573,13196811917.0,IssuesEvent,2020-08-13 21:27:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Placeholder for urgent care mashup punchlist,design frontend vsa vsa-facilities,This issue to document design changes which need to be implemented following Leyda's review of the new mashup design. ,1.0,Placeholder for urgent care mashup punchlist - This issue to document design changes which need to be implemented following Leyda's review of the new mashup design. ,1,placeholder for urgent care mashup punchlist this issue to document design changes which need to be implemented following leyda s review of the new mashup design ,1 119047,15394718305.0,IssuesEvent,2021-03-03 18:16:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Research][UI] Health Record Usability Research Assets,design research vsa-healthcare-exp,"## Product Links - [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md) - [Medications Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/medications.md) - [Allergies Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/allergies.md) - [Immunizations Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/immunizations.md) ## Description All assets for the usability prototype(s) needed to run the health record user usability study will be completed by the end of this ticket. ## Tasks - [ ] Create assets for UX Pin prototype(s) ## Acceptance Criteria - [ ] The prototype(s) is ready to be utilized within research session - [ ] Review assets with the team (particularly product)",1.0,"[Research][UI] Health Record Usability Research Assets - ## Product Links - [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md) - [Medications Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/medications.md) - [Allergies Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/allergies.md) - [Immunizations Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/immunizations.md) ## Description All assets for the usability prototype(s) needed to run the health record user usability study will be completed by the end of this ticket. ## Tasks - [ ] Create assets for UX Pin prototype(s) ## Acceptance Criteria - [ ] The prototype(s) is ready to be utilized within research session - [ ] Review assets with the team (particularly product)",1, health record usability research assets product links description all assets for the usability prototype s needed to run the health record user usability study will be completed by the end of this ticket tasks create assets for ux pin prototype s acceptance criteria the prototype s is ready to be utilized within research session review assets with the team particularly product ,1 100508,12531031895.0,IssuesEvent,2020-06-04 13:57:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Create Wireflows for 'Debt Letters MVP' ,design vsa vsa-benefits-2,"## Issue Description _Once the team participates in the ideation/brainstorming session and finalizes the 'Debt Letters MVP''s features for MVP, the design team will take everyone's ideas and create wireflows. These wireflows will be reviewed with the team and stakeholders and may be iterated on._ --- ## Tasks - [x] _Wireflows will be created in Miro/Mural capturing the required features for MVP and following VA's design system library components_ - [x] _Design team presents the wireflows to BaM2 team and stakeholders for feedback_ - [x] _If feedback needs to be incorporated, design team will create another ticket to capture that work_ - [x] _This iteration of the wireflows is documented in GH and linked to this ticket_ ## Acceptance Criteria - [x] _Wireflows are created in Mural/Miro based on ideation session_ - [x] _Wireflows have been presented to team/stakeholders_ - [x] _(Optional) If feedback needs to be incorporated, a ticket has been created to capture that work_ - [x] _Wireflows are documented in GH and linked to this ticket_ --- ",1.0,"[Design] Create Wireflows for 'Debt Letters MVP' - ## Issue Description _Once the team participates in the ideation/brainstorming session and finalizes the 'Debt Letters MVP''s features for MVP, the design team will take everyone's ideas and create wireflows. These wireflows will be reviewed with the team and stakeholders and may be iterated on._ --- ## Tasks - [x] _Wireflows will be created in Miro/Mural capturing the required features for MVP and following VA's design system library components_ - [x] _Design team presents the wireflows to BaM2 team and stakeholders for feedback_ - [x] _If feedback needs to be incorporated, design team will create another ticket to capture that work_ - [x] _This iteration of the wireflows is documented in GH and linked to this ticket_ ## Acceptance Criteria - [x] _Wireflows are created in Mural/Miro based on ideation session_ - [x] _Wireflows have been presented to team/stakeholders_ - [x] _(Optional) If feedback needs to be incorporated, a ticket has been created to capture that work_ - [x] _Wireflows are documented in GH and linked to this ticket_ --- ",1, create wireflows for debt letters mvp issue description once the team participates in the ideation brainstorming session and finalizes the debt letters mvp s features for mvp the design team will take everyone s ideas and create wireflows these wireflows will be reviewed with the team and stakeholders and may be iterated on tasks wireflows will be created in miro mural capturing the required features for mvp and following va s design system library components design team presents the wireflows to team and stakeholders for feedback if feedback needs to be incorporated design team will create another ticket to capture that work this iteration of the wireflows is documented in gh and linked to this ticket acceptance criteria wireflows are created in mural miro based on ideation session wireflows have been presented to team stakeholders optional if feedback needs to be incorporated a ticket has been created to capture that work wireflows are documented in gh and linked to this ticket ,1 41021,10266565021.0,IssuesEvent,2019-08-22 21:50:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[SCREENREADER]: GIBCT® VETTEC - Learn more buttons would benefit from ARIA-LABELs to provide more context,508-defect-3 508/Accessibility BAH,"## Description The `Learn more` buttons rely on proximity to a label or heading to answer the question ""Learn more about what?"". This can be improved for assistive devices and screen readers by adding `aria-label` attributes to the buttons. Example screenshots attached. ## Point of Contact **VFS Point of Contact:** _Trevor_ ## Acceptance Criteria * As a screen reader user, I want to hear contextual aria-labels read aloud. This text could sound like ""Learn more about GI Bill benefits"" or ""Learn more about cumulative Post-9/11 active duty service"". * The text ""Learn more"" should be included in each `aria-label`, ideally as the first text. See the second WCAG guidance link for more on this point. ## Environment * Windows 10 * Chrome * JAWS * https://staging.va.gov/gi-bill-comparison-tool/ * https://staging.va.gov/gi-bill-comparison-tool/ VET TEC school profile ## WCAG or Vendor Guidance (optional) * [Name, Role, Value: Understanding SC 4.1.2](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html) * [Understanding Success Criterion 2.5.3: Label in Name](https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html) ## Screenshots or Trace Logs ![Screen Shot 2019-08-22 at 4.37.04 PM.png](https://images.zenhubusercontent.com/5ac217b74b5806bc2bcd3fc8/e508e6a0-62ab-4d3f-b5c0-b128027046ec) --- ![Screen Shot 2019-08-22 at 4.37.19 PM.png](https://images.zenhubusercontent.com/5ac217b74b5806bc2bcd3fc8/4a172926-3237-4c6d-afbc-07b5eb73564a)",1.0,"[SCREENREADER]: GIBCT® VETTEC - Learn more buttons would benefit from ARIA-LABELs to provide more context - ## Description The `Learn more` buttons rely on proximity to a label or heading to answer the question ""Learn more about what?"". This can be improved for assistive devices and screen readers by adding `aria-label` attributes to the buttons. Example screenshots attached. ## Point of Contact **VFS Point of Contact:** _Trevor_ ## Acceptance Criteria * As a screen reader user, I want to hear contextual aria-labels read aloud. This text could sound like ""Learn more about GI Bill benefits"" or ""Learn more about cumulative Post-9/11 active duty service"". * The text ""Learn more"" should be included in each `aria-label`, ideally as the first text. See the second WCAG guidance link for more on this point. ## Environment * Windows 10 * Chrome * JAWS * https://staging.va.gov/gi-bill-comparison-tool/ * https://staging.va.gov/gi-bill-comparison-tool/ VET TEC school profile ## WCAG or Vendor Guidance (optional) * [Name, Role, Value: Understanding SC 4.1.2](https://www.w3.org/TR/UNDERSTANDING-WCAG20/ensure-compat-rsv.html) * [Understanding Success Criterion 2.5.3: Label in Name](https://www.w3.org/WAI/WCAG21/Understanding/label-in-name.html) ## Screenshots or Trace Logs ![Screen Shot 2019-08-22 at 4.37.04 PM.png](https://images.zenhubusercontent.com/5ac217b74b5806bc2bcd3fc8/e508e6a0-62ab-4d3f-b5c0-b128027046ec) --- ![Screen Shot 2019-08-22 at 4.37.19 PM.png](https://images.zenhubusercontent.com/5ac217b74b5806bc2bcd3fc8/4a172926-3237-4c6d-afbc-07b5eb73564a)",0, gibct® vettec learn more buttons would benefit from aria labels to provide more context description the learn more buttons rely on proximity to a label or heading to answer the question learn more about what this can be improved for assistive devices and screen readers by adding aria label attributes to the buttons example screenshots attached point of contact if this issue is being opened by a vfs team member please add a point of contact usually this is the same person who enters the issue ticket vfs point of contact trevor acceptance criteria as a screen reader user i want to hear contextual aria labels read aloud this text could sound like learn more about gi bill benefits or learn more about cumulative post active duty service the text learn more should be included in each aria label ideally as the first text see the second wcag guidance link for more on this point environment windows chrome jaws vet tec school profile wcag or vendor guidance optional screenshots or trace logs ,0 167736,26542783407.0,IssuesEvent,2023-01-19 20:47:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Components and pattern standards] Navigation mechanisms aren't consistent across pages. (04.10.2),content design 508/Accessibility ia collab-cycle-feedback Staging launch-blocking CC-Dashboard my-education-benefits education-letters CCIssue04.10,"### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name VA Education Letters #### VFS feature name #### Point of Contact/Reviewers Sara Sterkenburg - @sterkenburgsara - IA *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Navigation mechanisms aren't consistent across pages. ### Issue Details One section of the breadcrumb is spelled wrong across all pages of this product (eduction and training) ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 10](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.3_AA ### Platform Recommendation Fix spelling error in breadcrumbs across all pages --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Navigation mechanisms aren't consistent across pages. (04.10.2) - ### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name VA Education Letters #### VFS feature name #### Point of Contact/Reviewers Sara Sterkenburg - @sterkenburgsara - IA *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Navigation mechanisms aren't consistent across pages. ### Issue Details One section of the breadcrumb is spelled wrong across all pages of this product (eduction and training) ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 10](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.3_AA ### Platform Recommendation Fix spelling error in breadcrumbs across all pages --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, navigation mechanisms aren t consistent across pages general information vfs team name dgib my education benefits vfs product name va education letters vfs feature name point of contact reviewers sara sterkenburg sterkenburgsara ia for more information on how to interpret this ticket please refer to the guidance on platform website platform issue navigation mechanisms aren t consistent across pages issue details one section of the breadcrumb is spelled wrong across all pages of this product eduction and training link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation fix spelling error in breadcrumbs across all pages vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 93849,11812826163.0,IssuesEvent,2020-03-19 20:58:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Synthesize research from sessions on user search expectations,design research vsa vsa-facilities,"## User Story As a Veteran, I need the Facility Locator to return meaningful results to my search so I can select a facility which will meet my need. ## Goals Learn from Veterans about their search expectations for map interaction, defaults and facility detail information to inform our search iterations. Learn how expectations for search differ based on geographic area (rural vs urban) Learn how expectations for search differ based on device (mobile vs desktop) ## Tasks [ ] Synthesize findings from research sessions [ ] Make recommendations on iterations for search features including the search itself, user-map interactions and search results with consideration for: > Needs based on urban/rural location > Impact of facility/service type on expectations > Number of search results > Map interaction > Search refinement Acceptance Criteria [ ] Research readout and recommendations as above ",1.0,"Synthesize research from sessions on user search expectations - ## User Story As a Veteran, I need the Facility Locator to return meaningful results to my search so I can select a facility which will meet my need. ## Goals Learn from Veterans about their search expectations for map interaction, defaults and facility detail information to inform our search iterations. Learn how expectations for search differ based on geographic area (rural vs urban) Learn how expectations for search differ based on device (mobile vs desktop) ## Tasks [ ] Synthesize findings from research sessions [ ] Make recommendations on iterations for search features including the search itself, user-map interactions and search results with consideration for: > Needs based on urban/rural location > Impact of facility/service type on expectations > Number of search results > Map interaction > Search refinement Acceptance Criteria [ ] Research readout and recommendations as above ",1,synthesize research from sessions on user search expectations user story as a veteran i need the facility locator to return meaningful results to my search so i can select a facility which will meet my need goals learn from veterans about their search expectations for map interaction defaults and facility detail information to inform our search iterations learn how expectations for search differ based on geographic area rural vs urban learn how expectations for search differ based on device mobile vs desktop tasks synthesize findings from research sessions make recommendations on iterations for search features including the search itself user map interactions and search results with consideration for needs based on urban rural location impact of facility service type on expectations number of search results map interaction search refinement acceptance criteria research readout and recommendations as above ,1 92075,11597521477.0,IssuesEvent,2020-02-24 21:03:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Profile 2.0: Create mockups of the Account security screen,design personalization-2.0 profile vsa-authenticated-exp,"## User story As a veteran, I need to be able to easily verify my identity, add 2FA, or find and update my login information with the VA to keep my account information updated, safe, and secure. ## Additional background Epic #5092 ## Tasks - [x] Create desktop mockups of the Account security screen. - [x] Create mobile mockups of the Account security screen. ## Acceptance Criteria - [x] All mockups have been produced",1.0,"[Design] Profile 2.0: Create mockups of the Account security screen - ## User story As a veteran, I need to be able to easily verify my identity, add 2FA, or find and update my login information with the VA to keep my account information updated, safe, and secure. ## Additional background Epic #5092 ## Tasks - [x] Create desktop mockups of the Account security screen. - [x] Create mobile mockups of the Account security screen. ## Acceptance Criteria - [x] All mockups have been produced",1, profile create mockups of the account security screen user story as a veteran i need to be able to easily verify my identity add or find and update my login information with the va to keep my account information updated safe and secure additional background epic tasks create desktop mockups of the account security screen create mobile mockups of the account security screen acceptance criteria all mockups have been produced,1 131512,18294713605.0,IssuesEvent,2021-10-05 19:12:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My VA Alerts: Incorporate an alerts link into the IA/header,design my-va-dashboard vsa-authenticated-exp unplanned-work,"## Background We need to determine how we will incorporate a link to the alerts feature in the IA/header. ## Tasks - [x] Explore ways to show an Alerts link in the navigation - [x] Meet with Ryan Thurlwell to review discuss ideas for this - [x] Include IA in conversations ## Acceptance Criteria - [x] Updated designs and accompanying documentation",1.0,"[Design] My VA Alerts: Incorporate an alerts link into the IA/header - ## Background We need to determine how we will incorporate a link to the alerts feature in the IA/header. ## Tasks - [x] Explore ways to show an Alerts link in the navigation - [x] Meet with Ryan Thurlwell to review discuss ideas for this - [x] Include IA in conversations ## Acceptance Criteria - [x] Updated designs and accompanying documentation",1, my va alerts incorporate an alerts link into the ia header background we need to determine how we will incorporate a link to the alerts feature in the ia header tasks explore ways to show an alerts link in the navigation meet with ryan thurlwell to review discuss ideas for this include ia in conversations acceptance criteria updated designs and accompanying documentation,1 181286,30658741438.0,IssuesEvent,2023-07-25 13:47:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Copy of [Design] My VA Audit UX Improvements: Explore Designs for Incorporating Multiple Open Claims,design my-va-dashboard authenticated-experience,"## Background As detailed in this [slack thread](https://dsva.slack.com/archives/C909ZG2BB/p1668004758040209), users may have multiple open claims at one time and currently we only show them their most recent one the My VA dashboard. We want to explore design options for showing users all of their open claims. ## Tasks - [ ] Create design options for open claims - [ ] Review designs with team - [ ] PM to create any follow up FE tickets if needed ## Acceptance Criteria - [ ] Design options for multiple open claims are reviewed ",1.0,"Copy of [Design] My VA Audit UX Improvements: Explore Designs for Incorporating Multiple Open Claims - ## Background As detailed in this [slack thread](https://dsva.slack.com/archives/C909ZG2BB/p1668004758040209), users may have multiple open claims at one time and currently we only show them their most recent one the My VA dashboard. We want to explore design options for showing users all of their open claims. ## Tasks - [ ] Create design options for open claims - [ ] Review designs with team - [ ] PM to create any follow up FE tickets if needed ## Acceptance Criteria - [ ] Design options for multiple open claims are reviewed ",1,copy of my va audit ux improvements explore designs for incorporating multiple open claims background as detailed in this users may have multiple open claims at one time and currently we only show them their most recent one the my va dashboard we want to explore design options for showing users all of their open claims tasks create design options for open claims review designs with team pm to create any follow up fe tickets if needed acceptance criteria design options for multiple open claims are reviewed ,1 164461,25975404983.0,IssuesEvent,2022-12-19 14:31:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Update the VAOS Appointment Wireframes,design HCE-Checkin,"## Tasks - Update the wireframes to include the ""label"" that was discussed in planning - Address Ben 's comments. - Add annotations to help engineering understand what is different from what is in production ",1.0,"[Design] Update the VAOS Appointment Wireframes - ## Tasks - Update the wireframes to include the ""label"" that was discussed in planning - Address Ben 's comments. - Add annotations to help engineering understand what is different from what is in production ",1, update the vaos appointment wireframes tasks update the wireframes to include the label that was discussed in planning address ben s comments add annotations to help engineering understand what is different from what is in production ,1 143629,22108820752.0,IssuesEvent,2022-06-01 19:17:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design]Onsite Notifications: Notification Component Design,design my-va-dashboard vsa-authenticated-exp planned-work onsite-notifications,"## Background After our initial onsite notification review Angela received feedback from accessibility on a proposed design that will require more iteration. Matt Dingee recommended we work with the platform team to propose a notification component on the VA pattern library. ## Tasks - [ ] Iterate on notification component design - [ ] Review with team - [ ] Review with accessibility team in Slack - [ ] Review with Matt Dingee ## Acceptance Criteria - [ ] Notification component design is complete and reviewed with appropriate parties ## Resources - [original ticket](https://app.zenhub.com/workspaces/vft-59c95ae5fda7577a9b3184f8/issues/department-of-veterans-affairs/va.gov-team/39090) ",1.0,"[Design]Onsite Notifications: Notification Component Design - ## Background After our initial onsite notification review Angela received feedback from accessibility on a proposed design that will require more iteration. Matt Dingee recommended we work with the platform team to propose a notification component on the VA pattern library. ## Tasks - [ ] Iterate on notification component design - [ ] Review with team - [ ] Review with accessibility team in Slack - [ ] Review with Matt Dingee ## Acceptance Criteria - [ ] Notification component design is complete and reviewed with appropriate parties ## Resources - [original ticket](https://app.zenhub.com/workspaces/vft-59c95ae5fda7577a9b3184f8/issues/department-of-veterans-affairs/va.gov-team/39090) ",1, onsite notifications notification component design background after our initial onsite notification review angela received feedback from accessibility on a proposed design that will require more iteration matt dingee recommended we work with the platform team to propose a notification component on the va pattern library tasks iterate on notification component design review with team review with accessibility team in slack review with matt dingee acceptance criteria notification component design is complete and reviewed with appropriate parties resources ,1 184233,31844458606.0,IssuesEvent,2023-09-14 18:46:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Talk w/ Lee about Lighthouse-API and forms,service-design,"## Purpose What can we learn from Lee about how a team would work w/ Lighthouse to get an API set up for processing of their form? ## Tasks - [ ] Prep questions - [ ] schedule time w/ Lee - [ ] Meet w/ Lee - [ ] Capture takeaways ## Acceptance Criteria - [ ] Learnings documented ",1.0,"Talk w/ Lee about Lighthouse-API and forms - ## Purpose What can we learn from Lee about how a team would work w/ Lighthouse to get an API set up for processing of their form? ## Tasks - [ ] Prep questions - [ ] schedule time w/ Lee - [ ] Meet w/ Lee - [ ] Capture takeaways ## Acceptance Criteria - [ ] Learnings documented ",1,talk w lee about lighthouse api and forms purpose what can we learn from lee about how a team would work w lighthouse to get an api set up for processing of their form tasks prep questions schedule time w lee meet w lee capture takeaways acceptance criteria learnings documented ,1 120751,15798236375.0,IssuesEvent,2021-04-02 18:17:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My VA: Update copy documentation with final copy,design documentation my-va-dashboard planned-work vsa-authenticated-exp,"## Background We're finalizing all copy for the My VA redesign #21543, and we need [the copy documentation for FE](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/frontend/documentation/my-va-copy.md) updated so they can put those changes into the build. ## Tasks - [x] Update [the copy documentation for FE](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/frontend/documentation/my-va-copy.md) with final copy once it's ready.",1.0,"[Design] My VA: Update copy documentation with final copy - ## Background We're finalizing all copy for the My VA redesign #21543, and we need [the copy documentation for FE](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/frontend/documentation/my-va-copy.md) updated so they can put those changes into the build. ## Tasks - [x] Update [the copy documentation for FE](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/frontend/documentation/my-va-copy.md) with final copy once it's ready.",1, my va update copy documentation with final copy background we re finalizing all copy for the my va redesign and we need updated so they can put those changes into the build tasks update with final copy once it s ready ,1 98617,12341893667.0,IssuesEvent,2020-05-14 23:06:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Design profile page for when a user is not in MVI,design needs-grooming profile vsa-authenticated-exp,"## Background We noticed that we do not have a state in profile for when a user is not in the MVI. We need to create a design that will work with profile 2.0 to represent this. There is no user who is not in the MVI to show this - Erik hacked it locally. ## Additional information Epic # ![image (2).png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/bebbfa3![profilev1-not-in-mvi.png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/44731345-e17e-4250-acbf-f84b2b1825ec)8-6a67-49f1-922f-6c7be2bac209) ##Tasks [ ]- Create updated designs for users who is not in MVI [ ]- Update any copy that is needed ##Acceptance criteria [ ] - All mocks have been updated and added to prototype",1.0,"Design profile page for when a user is not in MVI - ## Background We noticed that we do not have a state in profile for when a user is not in the MVI. We need to create a design that will work with profile 2.0 to represent this. There is no user who is not in the MVI to show this - Erik hacked it locally. ## Additional information Epic # ![image (2).png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/bebbfa3![profilev1-not-in-mvi.png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/44731345-e17e-4250-acbf-f84b2b1825ec)8-6a67-49f1-922f-6c7be2bac209) ##Tasks [ ]- Create updated designs for users who is not in MVI [ ]- Update any copy that is needed ##Acceptance criteria [ ] - All mocks have been updated and added to prototype",1,design profile page for when a user is not in mvi background we noticed that we do not have a state in profile for when a user is not in the mvi we need to create a design that will work with profile to represent this there is no user who is not in the mvi to show this erik hacked it locally additional information epic tasks create updated designs for users who is not in mvi update any copy that is needed acceptance criteria all mocks have been updated and added to prototype,1 85162,10593279738.0,IssuesEvent,2019-10-09 14:36:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Request Design QA for Epic #756 Texting for Medical Appointments,By Light design product support,"Functionality adds a new text box field under Mobile Phone Number on profiles page, This field will allow users to receive text notifications for their medical appointments. URL: https://staging.va.gov/ Mock up: https://vsateams.invisionapp.com/share/FSTDOO0WUHC#/screens/378179664 Note: The green box containing the save message that appears after the user clicks UPDATE in the pop-up window does not have a check box as the mock up shows. This is due to the fact that the check mark is not in the style guide for alert messages. There is one existing defect: The cancel button does not appear to clear the unsaved checked box in the pop-up. Steps: 1- On the profile screen, start with an existing mobile number, but the text box unchecked. 2- Click on Edit to open pop-up. 3- Click on the text box 4- Click on Cancel—which takes you back to the profile page. 5- Click on Edit to open pop-up. 6- The text box is still checked. I would expect that the check box would not be checked since the user pressed cancel and it was never saved. ",1.0,"Request Design QA for Epic #756 Texting for Medical Appointments - Functionality adds a new text box field under Mobile Phone Number on profiles page, This field will allow users to receive text notifications for their medical appointments. URL: https://staging.va.gov/ Mock up: https://vsateams.invisionapp.com/share/FSTDOO0WUHC#/screens/378179664 Note: The green box containing the save message that appears after the user clicks UPDATE in the pop-up window does not have a check box as the mock up shows. This is due to the fact that the check mark is not in the style guide for alert messages. There is one existing defect: The cancel button does not appear to clear the unsaved checked box in the pop-up. Steps: 1- On the profile screen, start with an existing mobile number, but the text box unchecked. 2- Click on Edit to open pop-up. 3- Click on the text box 4- Click on Cancel—which takes you back to the profile page. 5- Click on Edit to open pop-up. 6- The text box is still checked. I would expect that the check box would not be checked since the user pressed cancel and it was never saved. ",1,request design qa for epic texting for medical appointments functionality adds a new text box field under mobile phone number on profiles page this field will allow users to receive text notifications for their medical appointments url mock up note the green box containing the save message that appears after the user clicks update in the pop up window does not have a check box as the mock up shows this is due to the fact that the check mark is not in the style guide for alert messages there is one existing defect the cancel button does not appear to clear the unsaved checked box in the pop up steps on the profile screen start with an existing mobile number but the text box unchecked click on edit to open pop up click on the text box click on cancel—which takes you back to the profile page click on edit to open pop up the text box is still checked i would expect that the check box would not be checked since the user pressed cancel and it was never saved ,1 88955,11184029451.0,IssuesEvent,2019-12-31 16:05:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Profile 2.0: Initial design explorations,design personalization-2.0 profile vsa,"## User Story: As a user, I need to be able to easily find and manage my personal information. ## Tasks In Sprint 12, Tressa will revisit the initial Profile 2.0 designs created by Samara. - [ ] Initial design explorations/vision - [ ] Share initial proposal with Samara, get feedback, and make updates - [ ] Share proposal with larger design team, get feedback, and make updates - [ ] Settle on final design proposal ## Acceptance Criteria: - [ ] There is a final design proposal for profile 2.0. All designs/states do NOT need to be done. These can be produced in Sprint 13.",1.0,"[Design] Profile 2.0: Initial design explorations - ## User Story: As a user, I need to be able to easily find and manage my personal information. ## Tasks In Sprint 12, Tressa will revisit the initial Profile 2.0 designs created by Samara. - [ ] Initial design explorations/vision - [ ] Share initial proposal with Samara, get feedback, and make updates - [ ] Share proposal with larger design team, get feedback, and make updates - [ ] Settle on final design proposal ## Acceptance Criteria: - [ ] There is a final design proposal for profile 2.0. All designs/states do NOT need to be done. These can be produced in Sprint 13.",1, profile initial design explorations user story as a user i need to be able to easily find and manage my personal information tasks in sprint tressa will revisit the initial profile designs created by samara initial design explorations vision share initial proposal with samara get feedback and make updates share proposal with larger design team get feedback and make updates settle on final design proposal acceptance criteria there is a final design proposal for profile all designs states do not need to be done these can be produced in sprint ,1 143869,22194168178.0,IssuesEvent,2022-06-07 04:28:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Storybook Addons - Storysource and a11y,vsp-design-system-team,"## Description We would like to have additional addons within our Storybook ecosystem * https://storybook.js.org/addons/@storybook/addon-storysource/ * This shows the way we built the story without having to dig into the code via the repo within the Canvas tab * https://storybook.js.org/addons/@storybook/addon-a11y/ * This provides general accessibility testing prior to accessibility reviews within the Canvas tab ## Acceptance Criteria - [x] Install new dependencies - [x] Add references in main.js addons array to connect the dependencies with Storybook - [x] Confirm dependencies are workin the canvas tab within Storybook",1.0,"Storybook Addons - Storysource and a11y - ## Description We would like to have additional addons within our Storybook ecosystem * https://storybook.js.org/addons/@storybook/addon-storysource/ * This shows the way we built the story without having to dig into the code via the repo within the Canvas tab * https://storybook.js.org/addons/@storybook/addon-a11y/ * This provides general accessibility testing prior to accessibility reviews within the Canvas tab ## Acceptance Criteria - [x] Install new dependencies - [x] Add references in main.js addons array to connect the dependencies with Storybook - [x] Confirm dependencies are workin the canvas tab within Storybook",1,storybook addons storysource and description we would like to have additional addons within our storybook ecosystem this shows the way we built the story without having to dig into the code via the repo within the canvas tab this provides general accessibility testing prior to accessibility reviews within the canvas tab acceptance criteria install new dependencies add references in main js addons array to connect the dependencies with storybook confirm dependencies are workin the canvas tab within storybook,1 97474,12237314211.0,IssuesEvent,2020-05-04 17:49:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Implement and Refine Feedback From Design Intent for PCPG,design vsa vsa-ebenefits,"## Goal After recieving feedback from the Design Intent Review, we need to implement those recommendations where they make sense ## Considerations If the Veteran is logged in, does that change the options on Step 1 at all? (Would we make any assumptions about who they are if they already have an account? For example - would we remove “Active duty service member with 6 months or less before discharge”?--We discussed this and for MVP we will give all the options--there’s talks in the future that it’d be more specialized. ## Tasks - [x] Make changes to the screens to align with [recommendations](https://github.com/department-of-veterans-affairs/va.gov-team/issues/8294) as necessary. ## Acceptance Criteria - [x] Changes have been made and team and interested parties have been notified",1.0,"Implement and Refine Feedback From Design Intent for PCPG - ## Goal After recieving feedback from the Design Intent Review, we need to implement those recommendations where they make sense ## Considerations If the Veteran is logged in, does that change the options on Step 1 at all? (Would we make any assumptions about who they are if they already have an account? For example - would we remove “Active duty service member with 6 months or less before discharge”?--We discussed this and for MVP we will give all the options--there’s talks in the future that it’d be more specialized. ## Tasks - [x] Make changes to the screens to align with [recommendations](https://github.com/department-of-veterans-affairs/va.gov-team/issues/8294) as necessary. ## Acceptance Criteria - [x] Changes have been made and team and interested parties have been notified",1,implement and refine feedback from design intent for pcpg goal after recieving feedback from the design intent review we need to implement those recommendations where they make sense considerations if the veteran is logged in does that change the options on step at all would we make any assumptions about who they are if they already have an account for example would we remove “active duty service member with months or less before discharge” we discussed this and for mvp we will give all the options there’s talks in the future that it’d be more specialized tasks make changes to the screens to align with as necessary acceptance criteria changes have been made and team and interested parties have been notified,1 163096,25754964635.0,IssuesEvent,2022-12-08 15:46:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Change action link on pre-check-in intro page,design ux HCE-Checkin,"## Description Although it doesn't have an incredibly higher bounce rate compared to other pages in pre-check-in, do an A/B test to see if the bounce rate decreases on the /introduction page by make the Get Started link more visually prominent. Right now, it uses the [action link component](https://design.va.gov/components/link/action). Look to see if there's another acceptable component to use and test. https://share.goabstract.com/4f416207-0fd1-4b05-8ba5-21b6e688e75a?collectionLayerId=2b0235d1-b68a-4a9f-a8db-515c403c391c&mode=design&sha=latest Shawn mentioned this on a call on 12/7/2022. ## Tasks - [ ] Check with Kristen and UX team on history of the decision of that component - [ ] Create wireframe - [ ] Prepare wireframe for engineers - [ ] Depending on solution, discuss with UX and product whether this needs to be submitted as experimental design component, whether it needs to go to collab cycle, or whether it's acceptable enough to proceed without doing those things - [ ] Determine test plan. E.g., A/B. Add test plan to ticket for engineers to evaluate whether feature toggle can be used, identify other concerns, etc. ## AC - [ ] Branch in abstract and wireframes delivered - [ ] Test plan documented and questions documented for engineers - [ ] Decision made on how to proceed regarding collab cycle, experimental design component, etc. ",1.0,"Change action link on pre-check-in intro page - ## Description Although it doesn't have an incredibly higher bounce rate compared to other pages in pre-check-in, do an A/B test to see if the bounce rate decreases on the /introduction page by make the Get Started link more visually prominent. Right now, it uses the [action link component](https://design.va.gov/components/link/action). Look to see if there's another acceptable component to use and test. https://share.goabstract.com/4f416207-0fd1-4b05-8ba5-21b6e688e75a?collectionLayerId=2b0235d1-b68a-4a9f-a8db-515c403c391c&mode=design&sha=latest Shawn mentioned this on a call on 12/7/2022. ## Tasks - [ ] Check with Kristen and UX team on history of the decision of that component - [ ] Create wireframe - [ ] Prepare wireframe for engineers - [ ] Depending on solution, discuss with UX and product whether this needs to be submitted as experimental design component, whether it needs to go to collab cycle, or whether it's acceptable enough to proceed without doing those things - [ ] Determine test plan. E.g., A/B. Add test plan to ticket for engineers to evaluate whether feature toggle can be used, identify other concerns, etc. ## AC - [ ] Branch in abstract and wireframes delivered - [ ] Test plan documented and questions documented for engineers - [ ] Decision made on how to proceed regarding collab cycle, experimental design component, etc. ",1,change action link on pre check in intro page description although it doesn t have an incredibly higher bounce rate compared to other pages in pre check in do an a b test to see if the bounce rate decreases on the introduction page by make the get started link more visually prominent right now it uses the look to see if there s another acceptable component to use and test shawn mentioned this on a call on tasks check with kristen and ux team on history of the decision of that component create wireframe prepare wireframe for engineers depending on solution discuss with ux and product whether this needs to be submitted as experimental design component whether it needs to go to collab cycle or whether it s acceptable enough to proceed without doing those things determine test plan e g a b add test plan to ticket for engineers to evaluate whether feature toggle can be used identify other concerns etc ac branch in abstract and wireframes delivered test plan documented and questions documented for engineers decision made on how to proceed regarding collab cycle experimental design component etc ,1 110636,13922826987.0,IssuesEvent,2020-10-21 13:44:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Change all imports of formation-react in vets-website to the new NPM package,backend design-system-team,"## Issue Description Change all imports of formation-react in vets-website to the new NPM package for Storybook --- ## Tasks - [ ] Change all imports of formation-react in vets-website to the new NPM package ## Acceptance Criteria - [ ] Imports of formation-reaction in vets-website go to new NPM package for Storybook --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Change all imports of formation-react in vets-website to the new NPM package - ## Issue Description Change all imports of formation-react in vets-website to the new NPM package for Storybook --- ## Tasks - [ ] Change all imports of formation-react in vets-website to the new NPM package ## Acceptance Criteria - [ ] Imports of formation-reaction in vets-website go to new NPM package for Storybook --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,change all imports of formation react in vets website to the new npm package issue description change all imports of formation react in vets website to the new npm package for storybook tasks change all imports of formation react in vets website to the new npm package acceptance criteria imports of formation reaction in vets website go to new npm package for storybook how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 167355,26488689523.0,IssuesEvent,2023-01-17 20:24:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyHealth: Medical Records: Concepts,design ux my-health my-health-MR-CORE MHV-to-VA.gov-PI9,"**What do we need to do?** We need to: - [ ] Analyze workshop data and develop takeaways/questions - [ ] Create pen & paper concepts using the discovery research, generative interviews, technical discovery, and proposed IA (and the use cases that came out of research) - [ ] Create concepts in Sketch - [ ] Share concepts in ""Medical Records: design and research critique"" weekly meeting (shooting for Dec 14 due to increment planning) - [ ] Share concepts with core Health Apartment team - [ ] Share concepts with broader stakeholders in VA.gov / MHV Weekly Design Review - [ ] Ideate on concepts **Why are we doing this?** We need to translate our research findings into design concepts. This will be the base to then develop user flows, wireframes, and lo-fi prototype **Who needs to be involved?** @jonathanjnelson to carry out design work",1.0,"[Design] MyHealth: Medical Records: Concepts - **What do we need to do?** We need to: - [ ] Analyze workshop data and develop takeaways/questions - [ ] Create pen & paper concepts using the discovery research, generative interviews, technical discovery, and proposed IA (and the use cases that came out of research) - [ ] Create concepts in Sketch - [ ] Share concepts in ""Medical Records: design and research critique"" weekly meeting (shooting for Dec 14 due to increment planning) - [ ] Share concepts with core Health Apartment team - [ ] Share concepts with broader stakeholders in VA.gov / MHV Weekly Design Review - [ ] Ideate on concepts **Why are we doing this?** We need to translate our research findings into design concepts. This will be the base to then develop user flows, wireframes, and lo-fi prototype **Who needs to be involved?** @jonathanjnelson to carry out design work",1, myhealth medical records concepts what do we need to do we need to analyze workshop data and develop takeaways questions create pen paper concepts using the discovery research generative interviews technical discovery and proposed ia and the use cases that came out of research create concepts in sketch share concepts in medical records design and research critique weekly meeting shooting for dec due to increment planning share concepts with core health apartment team share concepts with broader stakeholders in va gov mhv weekly design review ideate on concepts why are we doing this we need to translate our research findings into design concepts this will be the base to then develop user flows wireframes and lo fi prototype who needs to be involved jonathanjnelson to carry out design work,1 132487,18726272179.0,IssuesEvent,2021-11-03 16:34:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Determine Deltas for My Docs (EBN) and CST (VA.gov),design vsa vsa-ebenefits,"## Background We need to determine what functionality gaps exist between the My Documents feature in eBenefits and the Claim Status Tool in VA.gov so that we can address any outstanding functionality. ## Considerations - Not every file in the Veteran's eFolder is applicable for the Veteran to view. - Downloads seems to be the largest issue - Can we simply mirror the gaps in EBN on to VA.gov? - Check in with Cameron Testerman on BAM2 to see if they did any work here - Keep in mind that there is a place for standardized letters from the VA - Consider the profile as a potential home for the Veterans docs (IA question) ## Tasks - [x] Review both features - [x] Document deltas for both - [x] Share with team - [ ] (Jason) find a stakeholder - [x] Check in with Mikki ## Acceptance Criteria - [x] Results have been shared with the team - [ ] Mikki's thoughts have been documented, if available",1.0,"Determine Deltas for My Docs (EBN) and CST (VA.gov) - ## Background We need to determine what functionality gaps exist between the My Documents feature in eBenefits and the Claim Status Tool in VA.gov so that we can address any outstanding functionality. ## Considerations - Not every file in the Veteran's eFolder is applicable for the Veteran to view. - Downloads seems to be the largest issue - Can we simply mirror the gaps in EBN on to VA.gov? - Check in with Cameron Testerman on BAM2 to see if they did any work here - Keep in mind that there is a place for standardized letters from the VA - Consider the profile as a potential home for the Veterans docs (IA question) ## Tasks - [x] Review both features - [x] Document deltas for both - [x] Share with team - [ ] (Jason) find a stakeholder - [x] Check in with Mikki ## Acceptance Criteria - [x] Results have been shared with the team - [ ] Mikki's thoughts have been documented, if available",1,determine deltas for my docs ebn and cst va gov background we need to determine what functionality gaps exist between the my documents feature in ebenefits and the claim status tool in va gov so that we can address any outstanding functionality considerations not every file in the veteran s efolder is applicable for the veteran to view downloads seems to be the largest issue can we simply mirror the gaps in ebn on to va gov check in with cameron testerman on to see if they did any work here keep in mind that there is a place for standardized letters from the va consider the profile as a potential home for the veterans docs ia question tasks review both features document deltas for both share with team jason find a stakeholder check in with mikki acceptance criteria results have been shared with the team mikki s thoughts have been documented if available,1 110551,13913517940.0,IssuesEvent,2020-10-20 20:34:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Review map enhancement discovery,design research vsa vsa-facilities,"## Issue Description Creating a new Facility Locator user search experience is a 4Q2020 priority. There are a number of problems which need to be solved for our Veterans users, including: - An upcoming data limitation which will impact the search radius - When a Veteran initiates a search, the map continues to zoom out until results are found. If no results are found, we display a general error message. - The Facility Locator actively searches and re-searches as the user interacts with the map. The user does not have a way to stop this process or indicate that the map is set for a search. - Veterans are not given information in all scenarios to understand why the search failed or how to be more successful. - Implementing “predictive search” is a planned enhancement to the search on Facility Locator. This will allow us to show the list of matching place names in a scrolling div under the text field. Leyda has done comparative analysis of how other modern websites are handling these scenarios. We need to fine-tune our solution approach with Veteran research. ### Comparative analysis of searches limited to 250 miles [#12635](https://github.com/department-of-veterans-affairs/va.gov-team/issues/12635) - [Analysis in Google Sheets](https://docs.google.com/spreadsheets/d/1sIqiSYLL6JXqaQJ3iGUnBYYjOxFLTmn0TRWeN0HcDbM/edit?usp=sharing) - [Recommendations with supporting visual examples](https://docs.google.com/presentation/d/1FNvhu7peex3EfufXeNWZYIA4F2cZs2RuArdaBOwT9zg/edit?usp=sharing) ### Comparative analysis for map interaction [#13568](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13568) - Link to [competitive analysis in a Google Sheet](https://docs.google.com/spreadsheets/d/1sIqiSYLL6JXqaQJ3iGUnBYYjOxFLTmn0TRWeN0HcDbM/edit?usp=sharing) - Link to [competitive analysis in PDF](https://app.zenhub.com/files/133843125/315c0bd6-e7c8-4144-9222-19670e7b25e2/download) - Link to [recommendations in Google Slides](https://docs.google.com/presentation/d/1FNvhu7peex3EfufXeNWZYIA4F2cZs2RuArdaBOwT9zg/edit?usp=sharing) - Link to [recommendations in PDF](https://app.zenhub.com/files/133843125/c4cfa450-1831-4e8a-a79e-7453fa26d507/download) ### Comparative analysis for predictive search [#13567](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13567) - [Comparative map analysis](https://docs.google.com/spreadsheets/d/1sIqiSYLL6JXqaQJ3iGUnBYYjOxFLTmn0TRWeN0HcDbM/edit?usp=sharing) ### Related issues [#13229](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13229) for map display when zooming [#9498](https://github.com/department-of-veterans-affairs/va.gov-team/issues/9498) for supporting users when no results are found [#5201](https://github.com/department-of-veterans-affairs/va.gov-team/issues/5201) for proposed 250 mile limitation [#13299](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13299) for optimizing map view --- ## Tasks - [ ] Review issues linked above to understand problems which need to be solved - [ ] Review comparative analysis artifacts for discovery findings - [ ] Formulate list of areas to research/questions to answer ## Acceptance Criteria - [ ] Designer/Researcher is prepared to participate in Map enhancement solutioning workshop - [ ] List of areas to research/questions to answer --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Review map enhancement discovery - ## Issue Description Creating a new Facility Locator user search experience is a 4Q2020 priority. There are a number of problems which need to be solved for our Veterans users, including: - An upcoming data limitation which will impact the search radius - When a Veteran initiates a search, the map continues to zoom out until results are found. If no results are found, we display a general error message. - The Facility Locator actively searches and re-searches as the user interacts with the map. The user does not have a way to stop this process or indicate that the map is set for a search. - Veterans are not given information in all scenarios to understand why the search failed or how to be more successful. - Implementing “predictive search” is a planned enhancement to the search on Facility Locator. This will allow us to show the list of matching place names in a scrolling div under the text field. Leyda has done comparative analysis of how other modern websites are handling these scenarios. We need to fine-tune our solution approach with Veteran research. ### Comparative analysis of searches limited to 250 miles [#12635](https://github.com/department-of-veterans-affairs/va.gov-team/issues/12635) - [Analysis in Google Sheets](https://docs.google.com/spreadsheets/d/1sIqiSYLL6JXqaQJ3iGUnBYYjOxFLTmn0TRWeN0HcDbM/edit?usp=sharing) - [Recommendations with supporting visual examples](https://docs.google.com/presentation/d/1FNvhu7peex3EfufXeNWZYIA4F2cZs2RuArdaBOwT9zg/edit?usp=sharing) ### Comparative analysis for map interaction [#13568](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13568) - Link to [competitive analysis in a Google Sheet](https://docs.google.com/spreadsheets/d/1sIqiSYLL6JXqaQJ3iGUnBYYjOxFLTmn0TRWeN0HcDbM/edit?usp=sharing) - Link to [competitive analysis in PDF](https://app.zenhub.com/files/133843125/315c0bd6-e7c8-4144-9222-19670e7b25e2/download) - Link to [recommendations in Google Slides](https://docs.google.com/presentation/d/1FNvhu7peex3EfufXeNWZYIA4F2cZs2RuArdaBOwT9zg/edit?usp=sharing) - Link to [recommendations in PDF](https://app.zenhub.com/files/133843125/c4cfa450-1831-4e8a-a79e-7453fa26d507/download) ### Comparative analysis for predictive search [#13567](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13567) - [Comparative map analysis](https://docs.google.com/spreadsheets/d/1sIqiSYLL6JXqaQJ3iGUnBYYjOxFLTmn0TRWeN0HcDbM/edit?usp=sharing) ### Related issues [#13229](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13229) for map display when zooming [#9498](https://github.com/department-of-veterans-affairs/va.gov-team/issues/9498) for supporting users when no results are found [#5201](https://github.com/department-of-veterans-affairs/va.gov-team/issues/5201) for proposed 250 mile limitation [#13299](https://github.com/department-of-veterans-affairs/va.gov-team/issues/13299) for optimizing map view --- ## Tasks - [ ] Review issues linked above to understand problems which need to be solved - [ ] Review comparative analysis artifacts for discovery findings - [ ] Formulate list of areas to research/questions to answer ## Acceptance Criteria - [ ] Designer/Researcher is prepared to participate in Map enhancement solutioning workshop - [ ] List of areas to research/questions to answer --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,review map enhancement discovery issue description creating a new facility locator user search experience is a priority there are a number of problems which need to be solved for our veterans users including an upcoming data limitation which will impact the search radius when a veteran initiates a search the map continues to zoom out until results are found if no results are found we display a general error message the facility locator actively searches and re searches as the user interacts with the map the user does not have a way to stop this process or indicate that the map is set for a search veterans are not given information in all scenarios to understand why the search failed or how to be more successful implementing “predictive search” is a planned enhancement to the search on facility locator this will allow us to show the list of matching place names in a scrolling div under the text field leyda has done comparative analysis of how other modern websites are handling these scenarios we need to fine tune our solution approach with veteran research comparative analysis of searches limited to miles comparative analysis for map interaction link to link to link to link to comparative analysis for predictive search related issues for map display when zooming for supporting users when no results are found for proposed mile limitation for optimizing map view tasks review issues linked above to understand problems which need to be solved review comparative analysis artifacts for discovery findings formulate list of areas to research questions to answer acceptance criteria designer researcher is prepared to participate in map enhancement solutioning workshop list of areas to research questions to answer how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 138261,20380165458.0,IssuesEvent,2022-02-21 20:31:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Customer Support Tracking - Dashboard ,Epic service-design VSP-Initiative,"## Problem Statement Without a better understanding of how VSP teams' time is spent on customer support work, it is difficult to identify areas to focus on to make improvements that enable VFS teams to find answers or get unblocked on their own. How might we make customer support data available to VSP stakeholders so we can identify areas with high burdens of manual support and track the volume of support by team and practice area over time? ## Hypothesis or Bet By collecting data on Slack customer support requests and making it easy the generate reports, we expect to identify “problem areas” with high burdens of manual support to be prioritized in future VSP initiatives. ## We will know we're done when... (""Definition of Done"") When we can generate reports on the following metrics: - [ ] Total Slack customer support requests - by VFS team, practice area - [ ] Request type: no documentation, category - [ ] VSP time spent: per request, category, week, practice area ## Known Blockers/Dependencies - VSP Engineering Leadership designating a BE developer to help us maintain the database and iterate on the Support Bot. - Planning to work with the Analytics Team to pull data generated by the Support Bot into BigQuery. - If it turns out BigQuery is not an option in Q1, the backup plan is to use Grafana to generate customer support reports with the data archived in Loki or Datadog. This work would be dependent on the BE developer referenced in the first bullet point. ## Projected Launch Date February 2021 - assuming the resource referenced above is available at the beginning of Q1. ## Launch Checklist ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/customer-support-tracking/product-outline.md * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/customer-support-tracking/product-outline.md * **Release plan**: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/.github/ISSUE_TEMPLATE/vsp-release-plan.md ## TODOs - [x] Convert this issue to an epic - [x] Add your team's label to this epic ",1.0,"Customer Support Tracking - Dashboard - ## Problem Statement Without a better understanding of how VSP teams' time is spent on customer support work, it is difficult to identify areas to focus on to make improvements that enable VFS teams to find answers or get unblocked on their own. How might we make customer support data available to VSP stakeholders so we can identify areas with high burdens of manual support and track the volume of support by team and practice area over time? ## Hypothesis or Bet By collecting data on Slack customer support requests and making it easy the generate reports, we expect to identify “problem areas” with high burdens of manual support to be prioritized in future VSP initiatives. ## We will know we're done when... (""Definition of Done"") When we can generate reports on the following metrics: - [ ] Total Slack customer support requests - by VFS team, practice area - [ ] Request type: no documentation, category - [ ] VSP time spent: per request, category, week, practice area ## Known Blockers/Dependencies - VSP Engineering Leadership designating a BE developer to help us maintain the database and iterate on the Support Bot. - Planning to work with the Analytics Team to pull data generated by the Support Bot into BigQuery. - If it turns out BigQuery is not an option in Q1, the backup plan is to use Grafana to generate customer support reports with the data archived in Loki or Datadog. This work would be dependent on the BE developer referenced in the first bullet point. ## Projected Launch Date February 2021 - assuming the resource referenced above is available at the beginning of Q1. ## Launch Checklist ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/customer-support-tracking/product-outline.md * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/customer-support-tracking/product-outline.md * **Release plan**: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/.github/ISSUE_TEMPLATE/vsp-release-plan.md ## TODOs - [x] Convert this issue to an epic - [x] Add your team's label to this epic ",1,customer support tracking dashboard problem statement without a better understanding of how vsp teams time is spent on customer support work it is difficult to identify areas to focus on to make improvements that enable vfs teams to find answers or get unblocked on their own how might we make customer support data available to vsp stakeholders so we can identify areas with high burdens of manual support and track the volume of support by team and practice area over time hypothesis or bet by collecting data on slack customer support requests and making it easy the generate reports we expect to identify “problem areas” with high burdens of manual support to be prioritized in future vsp initiatives we will know we re done when definition of done when we can generate reports on the following metrics total slack customer support requests by vfs team practice area request type no documentation category vsp time spent per request category week practice area known blockers dependencies vsp engineering leadership designating a be developer to help us maintain the database and iterate on the support bot planning to work with the analytics team to pull data generated by the support bot into bigquery if it turns out bigquery is not an option in the backup plan is to use grafana to generate customer support reports with the data archived in loki or datadog this work would be dependent on the be developer referenced in the first bullet point projected launch date february assuming the resource referenced above is available at the beginning of launch checklist is this service tool feature tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a checked into note the product directory name should match with the list of vsp products external facing a exists for this product feature tool and should be located at platform product name readme md external facing a exists for this product feature tool and is updated for changes from this initiative and should be linked from the vfs facing readme for your product and should be located within platform product name unless you already have another location for it if applicable and post to about whether this should be added to the if applicable post to for external communication about this change e g vsp newsletter customer facing meetings measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying required artifacts documentation product name directory name used for your product documentation product outline readme link to vfs facing readme for your product user guide link to user guide testing usability test link to github issue or provide reason for skipping manual qa link to github issue or documented results automated tests link to tests or n a measurement success metrics release plan todos convert this issue to an epic add your team s label to this epic ,1 132144,18525644151.0,IssuesEvent,2021-10-20 20:07:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Profile: Personal Info Revision - Update designs per design intent review feedback,design vsa vsa-authenticated-exp profile personal-information,"## Issue Description Update Profile Personal Information Revision Mockups per feedback from design intent review --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] Profile: Personal Info Revision - Update designs per design intent review feedback - ## Issue Description Update Profile Personal Information Revision Mockups per feedback from design intent review --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, profile personal info revision update designs per design intent review feedback issue description update profile personal information revision mockups per feedback from design intent review tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 124542,16613216120.0,IssuesEvent,2021-06-02 13:55:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Implement mid-point review and LGY stakeholder feedback within COE prototype,LGY design vsa vsa-ebenefits,"### Background COE midpoint review was conducted 5/27; a stakeholder walkthrough was was given to LGY stakeholders earlier in the same week. The COE prototype received feedback on content, UX, design, accessibility and functionality. The prototype will be updated to incorporate revisions deemed mandatory (Must). ### Tasks Implement mandatory revisions per: - [x] Content revisions - [x] Design feedback - [x] UX considerations - [x] Accessibility mandates - [x] Stakeholder input ### Acceptance criteria - [x] COE prototype reflects mandatory revisions in text and screen layouts (will not necessarily be functional) ",1.0,"Implement mid-point review and LGY stakeholder feedback within COE prototype - ### Background COE midpoint review was conducted 5/27; a stakeholder walkthrough was was given to LGY stakeholders earlier in the same week. The COE prototype received feedback on content, UX, design, accessibility and functionality. The prototype will be updated to incorporate revisions deemed mandatory (Must). ### Tasks Implement mandatory revisions per: - [x] Content revisions - [x] Design feedback - [x] UX considerations - [x] Accessibility mandates - [x] Stakeholder input ### Acceptance criteria - [x] COE prototype reflects mandatory revisions in text and screen layouts (will not necessarily be functional) ",1,implement mid point review and lgy stakeholder feedback within coe prototype background coe midpoint review was conducted a stakeholder walkthrough was was given to lgy stakeholders earlier in the same week the coe prototype received feedback on content ux design accessibility and functionality the prototype will be updated to incorporate revisions deemed mandatory must tasks implement mandatory revisions per content revisions design feedback ux considerations accessibility mandates stakeholder input acceptance criteria coe prototype reflects mandatory revisions in text and screen layouts will not necessarily be functional ,1 136682,19911091813.0,IssuesEvent,2022-01-25 17:13:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Accessibility Linting Issues,triage needs-grooming vsp-design-system-team,"## Description We have some `jsx/a11y` linting rules that were turned off during an eslint upgrade. I'm attempting to turn them all back on. These are the forms library errors that would need to be fixed: ### DateWidget.jsx ``` ./src/platform/forms-system/src/js/widgets/DateWidget.jsx 104:13 error A control must be associated with a text label jsx-a11y/control-has-associated-label 124:15 error A control must be associated with a text label jsx-a11y/control-has-associated-label 94:11 error A form label must be associated with a control jsx-a11y/label-has-associated-control 114:13 error A form label must be associated with a control jsx-a11y/label-has-associated-control 135:11 error A form label must be associated with a control jsx-a11y/label-has-associated-control 114:13 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for 135:11 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### GenericError.jsx ``` ./src/platform/forms-system/src/js/review/submit-states/GenericError.jsx 36:9 error Visible, non-interactive elements with click handlers must have at least one keyboard listener jsx-a11y/click-events-have-key-events 36:9 error Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid 36:9 error Static HTML elements with event handlers require a role jsx-a11y/no-static-element-interactions ``` ### ErrorLinks.jsx ``` 72:23 error Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid ``` ### ui.unit.spec.js ``` 150:9 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for 120:9 error The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value. If you cannot provide a valid href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid 150:9 error A form label must be associated with a control jsx-a11y/label-has-associated-control 147:9 error The href attribute is required for an anchor to be keyboard accessible. Provide a valid, navigable address as the href value. If you cannot provide an href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid 167:9 error The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value. If you cannot provide a valid href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid ``` ### FormStartControls.jsx ``` ./src/platform/forms/save-in-progress/ 143:7 error Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid ``` ### FieldTemplate.jsx ``` ./src/platform/forms-system/src/js/components/FieldTemplate.jsx 93:5 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### FileField.jsx ``` ./src/platform/forms-system/src/js/fields/FileField.jsx 503:17 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### CheckboxWidget.jsx ``` /src/platform/forms-system/src/js/widgets/CheckboxWidget.jsx 35:7 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### RadioWidget.jsx ``` ./src/platform/forms-system/src/js/widgets/RadioWidget.jsx 49:13 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### YesNoWidget.jsx ``` ./src/platform/forms-system/src/js/widgets/YesNoWidget.jsx 39:7 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for 50:7 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### Form.unit.spec.jsx ``` ./src/platform/forms/formulate-integration/Form.unit.spec.jsx 29:11 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` There are currently 6 rules that need to be turned on via: https://github.com/department-of-veterans-affairs/vets-website/blob/master/.eslintrc.js#L192 ## Steps to replicate 1. Pull latest vets-website 2. Open /.eslintrc.js 3. Search for `jsx/a11y` 4. If the rule is set to `0`, set it to `2` (ignore `href-no-hash` as it has been deprecated) 5. Run `yarn lint:js` 6. View errors",1.0,"Accessibility Linting Issues - ## Description We have some `jsx/a11y` linting rules that were turned off during an eslint upgrade. I'm attempting to turn them all back on. These are the forms library errors that would need to be fixed: ### DateWidget.jsx ``` ./src/platform/forms-system/src/js/widgets/DateWidget.jsx 104:13 error A control must be associated with a text label jsx-a11y/control-has-associated-label 124:15 error A control must be associated with a text label jsx-a11y/control-has-associated-label 94:11 error A form label must be associated with a control jsx-a11y/label-has-associated-control 114:13 error A form label must be associated with a control jsx-a11y/label-has-associated-control 135:11 error A form label must be associated with a control jsx-a11y/label-has-associated-control 114:13 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for 135:11 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### GenericError.jsx ``` ./src/platform/forms-system/src/js/review/submit-states/GenericError.jsx 36:9 error Visible, non-interactive elements with click handlers must have at least one keyboard listener jsx-a11y/click-events-have-key-events 36:9 error Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid 36:9 error Static HTML elements with event handlers require a role jsx-a11y/no-static-element-interactions ``` ### ErrorLinks.jsx ``` 72:23 error Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid ``` ### ui.unit.spec.js ``` 150:9 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for 120:9 error The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value. If you cannot provide a valid href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid 150:9 error A form label must be associated with a control jsx-a11y/label-has-associated-control 147:9 error The href attribute is required for an anchor to be keyboard accessible. Provide a valid, navigable address as the href value. If you cannot provide an href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid 167:9 error The href attribute requires a valid value to be accessible. Provide a valid, navigable address as the href value. If you cannot provide a valid href, but still need the element to resemble a link, use a button and change it with appropriate styles. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid ``` ### FormStartControls.jsx ``` ./src/platform/forms/save-in-progress/ 143:7 error Anchor used as a button. Anchors are primarily expected to navigate. Use the button element instead. Learn more: https://github.com/jsx-eslint/eslint-plugin-jsx-a11y/blob/HEAD/docs/rules/anchor-is-valid.md jsx-a11y/anchor-is-valid ``` ### FieldTemplate.jsx ``` ./src/platform/forms-system/src/js/components/FieldTemplate.jsx 93:5 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### FileField.jsx ``` ./src/platform/forms-system/src/js/fields/FileField.jsx 503:17 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### CheckboxWidget.jsx ``` /src/platform/forms-system/src/js/widgets/CheckboxWidget.jsx 35:7 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### RadioWidget.jsx ``` ./src/platform/forms-system/src/js/widgets/RadioWidget.jsx 49:13 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### YesNoWidget.jsx ``` ./src/platform/forms-system/src/js/widgets/YesNoWidget.jsx 39:7 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for 50:7 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` ### Form.unit.spec.jsx ``` ./src/platform/forms/formulate-integration/Form.unit.spec.jsx 29:11 error Form label must have ALL of the following types of associated control: nesting, id jsx-a11y/label-has-for ``` There are currently 6 rules that need to be turned on via: https://github.com/department-of-veterans-affairs/vets-website/blob/master/.eslintrc.js#L192 ## Steps to replicate 1. Pull latest vets-website 2. Open /.eslintrc.js 3. Search for `jsx/a11y` 4. If the rule is set to `0`, set it to `2` (ignore `href-no-hash` as it has been deprecated) 5. Run `yarn lint:js` 6. View errors",1,accessibility linting issues description we have some jsx linting rules that were turned off during an eslint upgrade i m attempting to turn them all back on these are the forms library errors that would need to be fixed datewidget jsx src platform forms system src js widgets datewidget jsx error a control must be associated with a text label jsx control has associated label error a control must be associated with a text label jsx control has associated label error a form label must be associated with a control jsx label has associated control error a form label must be associated with a control jsx label has associated control error a form label must be associated with a control jsx label has associated control error form label must have all of the following types of associated control nesting id jsx label has for error form label must have all of the following types of associated control nesting id jsx label has for genericerror jsx src platform forms system src js review submit states genericerror jsx error visible non interactive elements with click handlers must have at least one keyboard listener jsx click events have key events error anchor used as a button anchors are primarily expected to navigate use the button element instead learn more jsx anchor is valid error static html elements with event handlers require a role jsx no static element interactions errorlinks jsx error anchor used as a button anchors are primarily expected to navigate use the button element instead learn more jsx anchor is valid ui unit spec js error form label must have all of the following types of associated control nesting id jsx label has for error the href attribute requires a valid value to be accessible provide a valid navigable address as the href value if you cannot provide a valid href but still need the element to resemble a link use a button and change it with appropriate styles learn more jsx anchor is valid error a form label must be associated with a control jsx label has associated control error the href attribute is required for an anchor to be keyboard accessible provide a valid navigable address as the href value if you cannot provide an href but still need the element to resemble a link use a button and change it with appropriate styles learn more jsx anchor is valid error the href attribute requires a valid value to be accessible provide a valid navigable address as the href value if you cannot provide a valid href but still need the element to resemble a link use a button and change it with appropriate styles learn more jsx anchor is valid formstartcontrols jsx src platform forms save in progress error anchor used as a button anchors are primarily expected to navigate use the button element instead learn more jsx anchor is valid fieldtemplate jsx src platform forms system src js components fieldtemplate jsx error form label must have all of the following types of associated control nesting id jsx label has for filefield jsx src platform forms system src js fields filefield jsx error form label must have all of the following types of associated control nesting id jsx label has for checkboxwidget jsx src platform forms system src js widgets checkboxwidget jsx error form label must have all of the following types of associated control nesting id jsx label has for radiowidget jsx src platform forms system src js widgets radiowidget jsx error form label must have all of the following types of associated control nesting id jsx label has for yesnowidget jsx src platform forms system src js widgets yesnowidget jsx error form label must have all of the following types of associated control nesting id jsx label has for error form label must have all of the following types of associated control nesting id jsx label has for form unit spec jsx src platform forms formulate integration form unit spec jsx error form label must have all of the following types of associated control nesting id jsx label has for there are currently rules that need to be turned on via steps to replicate pull latest vets website open eslintrc js search for jsx if the rule is set to set it to ignore href no hash as it has been deprecated run yarn lint js view errors,1 132819,18765252197.0,IssuesEvent,2021-11-05 22:28:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Content] Calendar - no slots near future alert,content vaos-product-design,"## Request Request review and recommendation for the alert on the direct schedule calendar page. - If no slots in the next 2 months - If no slots in the next 4 months ## Background When a user inputs today's date in the preferred date, an ""urgent care"" alert appears above the calendar. The app queries for 2 months worth of slots. If there's a slot the alert copy is populated with the earliest available date. If there are no open slots, then the copy currently shows today's date (bug/no handling #30480) ## Screenshot ![image.png](https://images.zenhubusercontent.com/5f2d82e4a65f7435058cfd75/e1613a03-342f-4a64-b27e-8c4d48027ca4)",1.0,"[Content] Calendar - no slots near future alert - ## Request Request review and recommendation for the alert on the direct schedule calendar page. - If no slots in the next 2 months - If no slots in the next 4 months ## Background When a user inputs today's date in the preferred date, an ""urgent care"" alert appears above the calendar. The app queries for 2 months worth of slots. If there's a slot the alert copy is populated with the earliest available date. If there are no open slots, then the copy currently shows today's date (bug/no handling #30480) ## Screenshot ![image.png](https://images.zenhubusercontent.com/5f2d82e4a65f7435058cfd75/e1613a03-342f-4a64-b27e-8c4d48027ca4)",1, calendar no slots near future alert request request review and recommendation for the alert on the direct schedule calendar page if no slots in the next months if no slots in the next months background when a user inputs today s date in the preferred date an urgent care alert appears above the calendar the app queries for months worth of slots if there s a slot the alert copy is populated with the earliest available date if there are no open slots then the copy currently shows today s date bug no handling screenshot ,1 167703,26537084104.0,IssuesEvent,2023-01-19 16:22:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Provide a definitive space for Platform users to access mappings, workflows, and diagrams of Platform offerings",service-design,"## Problem Statement Platform team members need a common repository where they can access these documents without needing to know who “owns” or originated them. Further, since project teams will produce these items and move on, it would be very difficult for a consumer to know the artifact even exists, or how to track it down Our team should begin to consider a space that makes these artifacts very visible to Platform team members. They would do well not to be nested too far down in a directory. We may want categories for each finding as they grow in number: i.e. Architectural Diagrams, VFS tasks, Workflows, Processes, etc. This also means we have a responsibility to aggregate these items, so that is something we will need to socialize. Architectural diagrams will be particularly critical to Security, as we have Project Teams changing the fabric of the Platform continually now. [Sync](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2494136321/1+19+23-+PO+PM+Sync#From-PO%3A) conversation w/ PO: ## High Level User Stories As Platform leadership, I want easy access to current artifacts that describe Platform processes and offerings so that I can quickly understand how various offerings are intended to work, as well as the resources and services involved. As a Platform team member, I want easy access to current artifacts that describe Platform processes and offerings so that I can quickly understand how various offerings are intended to work, as well as the resources and services involved. As a Platform Security expert, I want easy access to current architectural diagrams of products and services so that I can quickly understand how various offerings are intended to work, helping me understand the risks involved to the services we provide. ## Bet By providing a well-socialized and accessible space for Platform-produced visual mappings, users will know where to go for access to the extensive resources that teams have produced. By aggregating platform team-produced visual mappings, we can ensure that knowledge of key processes is transferred to others as teams change in endeavor and makeup. ## Desirable Outcomes: -Leadership is provided with easy access to visualizations that convey the workings of key processes and the resources involved. -Platform team members are provided with easy access to visualizations that convey the workings of key processes and the resources involved, thereby spreading understanding. ## Definition of Done - [ ] A landing will be produced and maintained that provides easy access to all personas - [ ] A landing will be easy to understand with respect to groupings of visualizations. ### KRs / HMs HM: The landing is accessed/referenced regularly by users ### Documentation - Artifact: link to artifact - Product Outline: link to Product Outline (or Research Plan) ",1.0,"Provide a definitive space for Platform users to access mappings, workflows, and diagrams of Platform offerings - ## Problem Statement Platform team members need a common repository where they can access these documents without needing to know who “owns” or originated them. Further, since project teams will produce these items and move on, it would be very difficult for a consumer to know the artifact even exists, or how to track it down Our team should begin to consider a space that makes these artifacts very visible to Platform team members. They would do well not to be nested too far down in a directory. We may want categories for each finding as they grow in number: i.e. Architectural Diagrams, VFS tasks, Workflows, Processes, etc. This also means we have a responsibility to aggregate these items, so that is something we will need to socialize. Architectural diagrams will be particularly critical to Security, as we have Project Teams changing the fabric of the Platform continually now. [Sync](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2494136321/1+19+23-+PO+PM+Sync#From-PO%3A) conversation w/ PO: ## High Level User Stories As Platform leadership, I want easy access to current artifacts that describe Platform processes and offerings so that I can quickly understand how various offerings are intended to work, as well as the resources and services involved. As a Platform team member, I want easy access to current artifacts that describe Platform processes and offerings so that I can quickly understand how various offerings are intended to work, as well as the resources and services involved. As a Platform Security expert, I want easy access to current architectural diagrams of products and services so that I can quickly understand how various offerings are intended to work, helping me understand the risks involved to the services we provide. ## Bet By providing a well-socialized and accessible space for Platform-produced visual mappings, users will know where to go for access to the extensive resources that teams have produced. By aggregating platform team-produced visual mappings, we can ensure that knowledge of key processes is transferred to others as teams change in endeavor and makeup. ## Desirable Outcomes: -Leadership is provided with easy access to visualizations that convey the workings of key processes and the resources involved. -Platform team members are provided with easy access to visualizations that convey the workings of key processes and the resources involved, thereby spreading understanding. ## Definition of Done - [ ] A landing will be produced and maintained that provides easy access to all personas - [ ] A landing will be easy to understand with respect to groupings of visualizations. ### KRs / HMs HM: The landing is accessed/referenced regularly by users ### Documentation - Artifact: link to artifact - Product Outline: link to Product Outline (or Research Plan) ",1,provide a definitive space for platform users to access mappings workflows and diagrams of platform offerings problem statement platform team members need a common repository where they can access these documents without needing to know who “owns” or originated them further since project teams will produce these items and move on it would be very difficult for a consumer to know the artifact even exists or how to track it down our team should begin to consider a space that makes these artifacts very visible to platform team members they would do well not to be nested too far down in a directory we may want categories for each finding as they grow in number i e architectural diagrams vfs tasks workflows processes etc this also means we have a responsibility to aggregate these items so that is something we will need to socialize architectural diagrams will be particularly critical to security as we have project teams changing the fabric of the platform continually now conversation w po high level user stories as platform leadership i want easy access to current artifacts that describe platform processes and offerings so that i can quickly understand how various offerings are intended to work as well as the resources and services involved as a platform team member i want easy access to current artifacts that describe platform processes and offerings so that i can quickly understand how various offerings are intended to work as well as the resources and services involved as a platform security expert i want easy access to current architectural diagrams of products and services so that i can quickly understand how various offerings are intended to work helping me understand the risks involved to the services we provide bet by providing a well socialized and accessible space for platform produced visual mappings users will know where to go for access to the extensive resources that teams have produced by aggregating platform team produced visual mappings we can ensure that knowledge of key processes is transferred to others as teams change in endeavor and makeup desirable outcomes leadership is provided with easy access to visualizations that convey the workings of key processes and the resources involved platform team members are provided with easy access to visualizations that convey the workings of key processes and the resources involved thereby spreading understanding definition of done a landing will be produced and maintained that provides easy access to all personas a landing will be easy to understand with respect to groupings of visualizations krs hms hm the landing is accessed referenced regularly by users documentation artifact link to artifact product outline link to product outline or research plan ,1 110555,13913943658.0,IssuesEvent,2020-10-20 21:15:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create Final Punch List of Copy Changes,design vsa vsa-ebenefits,"## Background ## Tasks Take Peggy's feedback Update prototypes Share list of changes to FE for implementation ",1.0,"Create Final Punch List of Copy Changes - ## Background ## Tasks Take Peggy's feedback Update prototypes Share list of changes to FE for implementation ",1,create final punch list of copy changes background tasks take peggy s feedback update prototypes share list of changes to fe for implementation ,1 176098,28030679747.0,IssuesEvent,2023-03-28 12:11:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Review Platform Content team's proposed Research plan,service-design,"## Purpose Platform Content [reached out](https://dsva.slack.com/archives/CPCGRR7F1/p1679501102512609) about an upcoming research initiative. They'd like us to review their plan and get some time to discuss it. ## Tasks Review [Plan](https://vfs.atlassian.net/wiki/spaces/CIT/pages/2546270209/Platform+Website+User+Experience+Research): - [x] Taylor - [x] Bryan - [x] Dan - [x] Nicole - [x] Establish a meetup ## Acceptance Criteria - [x] Reviews are complete - [x] meetup scheduled ",1.0,"Review Platform Content team's proposed Research plan - ## Purpose Platform Content [reached out](https://dsva.slack.com/archives/CPCGRR7F1/p1679501102512609) about an upcoming research initiative. They'd like us to review their plan and get some time to discuss it. ## Tasks Review [Plan](https://vfs.atlassian.net/wiki/spaces/CIT/pages/2546270209/Platform+Website+User+Experience+Research): - [x] Taylor - [x] Bryan - [x] Dan - [x] Nicole - [x] Establish a meetup ## Acceptance Criteria - [x] Reviews are complete - [x] meetup scheduled ",1,review platform content team s proposed research plan purpose platform content about an upcoming research initiative they d like us to review their plan and get some time to discuss it tasks review taylor bryan dan nicole establish a meetup acceptance criteria reviews are complete meetup scheduled ,1 135925,19684036019.0,IssuesEvent,2022-01-11 19:52:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Modal: Change header to H1,508/Accessibility components vsp-design-system-team,"## Description When the component library ""alert"" modal is visible, an `h1` header should be present to fulfill a11y scans. To test: - Go to https://design.va.gov/storybook/iframe.html?id=components-modal--default&viewMode=story - Open the modal - Run axe DevTools Note: the page itself doesn't have an H1, but even if it did, it gets ignored by the scan.
a11y error ![Screen Shot 2021-08-25 at 11 20 16 AM](https://user-images.githubusercontent.com/136959/130827782-54e14caf-792a-4b4d-b1ab-3a64349adcad.png)
## Tasks - [ ] Change modal `h3` to an `h1` & adjust header size - [ ] Add unit/a11y tests ## Definition of done - [ ] All tasks done - [ ] All tests passing",1.0,"Modal: Change header to H1 - ## Description When the component library ""alert"" modal is visible, an `h1` header should be present to fulfill a11y scans. To test: - Go to https://design.va.gov/storybook/iframe.html?id=components-modal--default&viewMode=story - Open the modal - Run axe DevTools Note: the page itself doesn't have an H1, but even if it did, it gets ignored by the scan.
a11y error ![Screen Shot 2021-08-25 at 11 20 16 AM](https://user-images.githubusercontent.com/136959/130827782-54e14caf-792a-4b4d-b1ab-3a64349adcad.png)
## Tasks - [ ] Change modal `h3` to an `h1` & adjust header size - [ ] Add unit/a11y tests ## Definition of done - [ ] All tasks done - [ ] All tests passing",1,modal change header to description when the component library alert modal is visible an header should be present to fulfill scans to test go to open the modal run axe devtools note the page itself doesn t have an but even if it did it gets ignored by the scan error tasks change modal to an adjust header size add unit tests definition of done all tasks done all tests passing,1 117304,15086673914.0,IssuesEvent,2021-02-05 20:44:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Homepage research synthesis,design vaos-product-design,Synthesis will be saved in the research folder when it's complete: https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/health-care/appointments/va-online-scheduling/research/jan-2021-appts-list-test,2.0,[Design] Homepage research synthesis - Synthesis will be saved in the research folder when it's complete: https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/health-care/appointments/va-online-scheduling/research/jan-2021-appts-list-test,1, homepage research synthesis synthesis will be saved in the research folder when it s complete ,1 128738,17604837420.0,IssuesEvent,2021-08-17 15:46:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Notification Prefs: Share revised designs with partners,design notifications-preferences vsa-authenticated-exp planned-work,"Share revised designs with VA Profile and VA Notify teams **Tasks** - [ ] Share with VA Profile - [x] Share with VA Notify ",1.0,"[Design] Notification Prefs: Share revised designs with partners - Share revised designs with VA Profile and VA Notify teams **Tasks** - [ ] Share with VA Profile - [x] Share with VA Notify ",1, notification prefs share revised designs with partners share revised designs with va profile and va notify teams tasks share with va profile share with va notify ,1 110056,13895485283.0,IssuesEvent,2020-10-19 15:54:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Conduct My Documents discovery research,design eFolders research vsa vsa-benefits-2,"## Issue Description _In order to understand what Veterans expect in VA.gov's version of the My Documents tool, we need to uncover their successes and pain points with the eBenefits version of the tool._ --- ## Tasks - [x] _Conduct user research sessions_ - [x] _Upload transcripts (scrubbed of PII) to GH_ - [x] _Upload a topline summary to GH_ ## Acceptance Criteria - [x] _User research sessions are completed_ - [x] _Transcripts have been scrubbed of PII and uploaded to GH_ - [x] _A link to the topline summary has been provided as a comment on this ticket_ ",1.0,"[Design] Conduct My Documents discovery research - ## Issue Description _In order to understand what Veterans expect in VA.gov's version of the My Documents tool, we need to uncover their successes and pain points with the eBenefits version of the tool._ --- ## Tasks - [x] _Conduct user research sessions_ - [x] _Upload transcripts (scrubbed of PII) to GH_ - [x] _Upload a topline summary to GH_ ## Acceptance Criteria - [x] _User research sessions are completed_ - [x] _Transcripts have been scrubbed of PII and uploaded to GH_ - [x] _A link to the topline summary has been provided as a comment on this ticket_ ",1, conduct my documents discovery research issue description in order to understand what veterans expect in va gov s version of the my documents tool we need to uncover their successes and pain points with the ebenefits version of the tool tasks conduct user research sessions upload transcripts scrubbed of pii to gh upload a topline summary to gh acceptance criteria user research sessions are completed transcripts have been scrubbed of pii and uploaded to gh a link to the topline summary has been provided as a comment on this ticket ,1 121079,15836812121.0,IssuesEvent,2021-04-06 19:52:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[MCP] Veteran codesign research plan,MCP design research vsa vsa-benefits-2,"## Issue Description We need to do a codesign workshop with Veterans in order to better understand how they think of both benefit and copay debt. --- ## Tasks - [ ] Create a research plan for codesign with Veterans around MCP - [ ] Upload research plan to GH and link to this ticket ## Acceptance Criteria - [ ] Research plan linked in this ticket",1.0,"[MCP] Veteran codesign research plan - ## Issue Description We need to do a codesign workshop with Veterans in order to better understand how they think of both benefit and copay debt. --- ## Tasks - [ ] Create a research plan for codesign with Veterans around MCP - [ ] Upload research plan to GH and link to this ticket ## Acceptance Criteria - [ ] Research plan linked in this ticket",1, veteran codesign research plan issue description we need to do a codesign workshop with veterans in order to better understand how they think of both benefit and copay debt tasks create a research plan for codesign with veterans around mcp upload research plan to gh and link to this ticket acceptance criteria research plan linked in this ticket,1 136680,19910694514.0,IssuesEvent,2022-01-25 16:52:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Discovery: Try out using one of our web components in a simple Vue app,vsp-design-system-team,"## Description Our theory is that it should be relatively easy to use our web components inside any framework, but we want to experiment and find out for sure. If possible, please run this experiment in an online coding environment like Codepen or Repl where you can share a link to your work. (It doesn't matter what you use, just something where it would be easy for someone else to view and run the code without installing a bunch of stuff locally) For this ticket, you'll need to: - build a quick ""hello world"" Vue app (use the latest version of Vue) - import a couple of our web components and display it in the app - maybe start with a simple one, then try one that takes a function as a prop - write up the process, noting any special things you had to do to make it work. ## Acceptance Criteria - [ ] Build a simple Vue app in an online coding environment - [ ] Import one of our simpler web components and use it in the app - [ ] Import a web component that will take a function as a prop and use it in the app - [ ] Record your process in a comment on this ticket. Include a link to your experiment.",1.0,"Discovery: Try out using one of our web components in a simple Vue app - ## Description Our theory is that it should be relatively easy to use our web components inside any framework, but we want to experiment and find out for sure. If possible, please run this experiment in an online coding environment like Codepen or Repl where you can share a link to your work. (It doesn't matter what you use, just something where it would be easy for someone else to view and run the code without installing a bunch of stuff locally) For this ticket, you'll need to: - build a quick ""hello world"" Vue app (use the latest version of Vue) - import a couple of our web components and display it in the app - maybe start with a simple one, then try one that takes a function as a prop - write up the process, noting any special things you had to do to make it work. ## Acceptance Criteria - [ ] Build a simple Vue app in an online coding environment - [ ] Import one of our simpler web components and use it in the app - [ ] Import a web component that will take a function as a prop and use it in the app - [ ] Record your process in a comment on this ticket. Include a link to your experiment.",1,discovery try out using one of our web components in a simple vue app description our theory is that it should be relatively easy to use our web components inside any framework but we want to experiment and find out for sure if possible please run this experiment in an online coding environment like codepen or repl where you can share a link to your work it doesn t matter what you use just something where it would be easy for someone else to view and run the code without installing a bunch of stuff locally for this ticket you ll need to build a quick hello world vue app use the latest version of vue import a couple of our web components and display it in the app maybe start with a simple one then try one that takes a function as a prop write up the process noting any special things you had to do to make it work acceptance criteria build a simple vue app in an online coding environment import one of our simpler web components and use it in the app import a web component that will take a function as a prop and use it in the app record your process in a comment on this ticket include a link to your experiment ,1 146773,23119677131.0,IssuesEvent,2022-07-27 20:03:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Profile | Sprint 78 (July 13 - July 26),Epic design research vsa-authenticated-exp profile personal-information bad-address-indicator Military Info Migration,"## PTO/OOO/Unavailable - **Christina**: - **Sharon**: - **Tom**: - **Samara**: 7/18 - **Adam**: - **Liz**: 7/21, and 1/2 day on 7/25 and 7/26. ## Sprint Priorities - Bad address indicator: Research summary and design updates - Documentation: Contact info and Military info - Forms system updates: Discovery and scoping - Military info: UAT and start launch (pending VA Profile being ready) ## Notes: - New sign-in flow may impact sprint - tbd. ## Personal Info ### FE - Adam - [x] #43482 Remove FF ### Design - Christina - [ ] #43713 Update sketch files (carry over to sprint 79) ### BE - Tom - [x] #44082 Discovery re limitations and LOE for Preferred name (UAT issue). ## Military Information ### BE - Tom - [x] #43582 eMIS deprecation ### PM - Sharon - [x] #42968 Analytics to check for successful/failed retrievals of military info ### FE - Adam - [x] #44075 FE GA tags ### BE - Tom - [x] #44232 Documentation ## Bad Address Indicator ### PM - Sharon - [ ] #42706 Con't prep for staging review cycle work (release plan, QA etc) - [ ] #42265 Analytics (carry over to sprint 79) - [x] #43388 QA Use Cases ### FE - Adam - [x] #44310 ### Design - Christina - [x] #42965 Research sessions - [ ] #43384 Full research report (carry-over) - [x] #43439 User flow doc - [x] #43383 Topline summary ## New Forms Library PoC ### FE - Adam - [ ] #43727 Phone number field (carry-over to Sprint 79) ## Change Address Messaging Prompt - [x] #44230 Analytics Bug/Turn off FF toggle at 50% - [x] #44380 Analytics ticket for custom event ## 🛠️ General / Tech Debt ### BE - Tom - [x] #44193 Sign on issues - [x] #44249 Test BGS prod access ### FE - Adam Stretch goal: - [x] #42734 dd routing number/invalid error message ### Design - Liz - [x] #43750 Contact documentation ",1.0,"Profile | Sprint 78 (July 13 - July 26) - ## PTO/OOO/Unavailable - **Christina**: - **Sharon**: - **Tom**: - **Samara**: 7/18 - **Adam**: - **Liz**: 7/21, and 1/2 day on 7/25 and 7/26. ## Sprint Priorities - Bad address indicator: Research summary and design updates - Documentation: Contact info and Military info - Forms system updates: Discovery and scoping - Military info: UAT and start launch (pending VA Profile being ready) ## Notes: - New sign-in flow may impact sprint - tbd. ## Personal Info ### FE - Adam - [x] #43482 Remove FF ### Design - Christina - [ ] #43713 Update sketch files (carry over to sprint 79) ### BE - Tom - [x] #44082 Discovery re limitations and LOE for Preferred name (UAT issue). ## Military Information ### BE - Tom - [x] #43582 eMIS deprecation ### PM - Sharon - [x] #42968 Analytics to check for successful/failed retrievals of military info ### FE - Adam - [x] #44075 FE GA tags ### BE - Tom - [x] #44232 Documentation ## Bad Address Indicator ### PM - Sharon - [ ] #42706 Con't prep for staging review cycle work (release plan, QA etc) - [ ] #42265 Analytics (carry over to sprint 79) - [x] #43388 QA Use Cases ### FE - Adam - [x] #44310 ### Design - Christina - [x] #42965 Research sessions - [ ] #43384 Full research report (carry-over) - [x] #43439 User flow doc - [x] #43383 Topline summary ## New Forms Library PoC ### FE - Adam - [ ] #43727 Phone number field (carry-over to Sprint 79) ## Change Address Messaging Prompt - [x] #44230 Analytics Bug/Turn off FF toggle at 50% - [x] #44380 Analytics ticket for custom event ## 🛠️ General / Tech Debt ### BE - Tom - [x] #44193 Sign on issues - [x] #44249 Test BGS prod access ### FE - Adam Stretch goal: - [x] #42734 dd routing number/invalid error message ### Design - Liz - [x] #43750 Contact documentation ",1,profile sprint july july pto ooo unavailable christina sharon tom samara adam liz and day on and sprint priorities bad address indicator research summary and design updates documentation contact info and military info forms system updates discovery and scoping military info uat and start launch pending va profile being ready notes new sign in flow may impact sprint tbd personal info fe adam remove ff design christina update sketch files carry over to sprint be tom discovery re limitations and loe for preferred name uat issue military information be tom emis deprecation pm sharon analytics to check for successful failed retrievals of military info fe adam fe ga tags be tom documentation bad address indicator pm sharon con t prep for staging review cycle work release plan qa etc analytics carry over to sprint qa use cases fe adam design christina research sessions full research report carry over user flow doc topline summary new forms library poc fe adam phone number field carry over to sprint change address messaging prompt analytics bug turn off ff toggle at analytics ticket for custom event 🛠️ general tech debt be tom sign on issues test bgs prod access fe adam stretch goal dd routing number invalid error message design liz contact documentation ,1 154215,24260871709.0,IssuesEvent,2022-09-27 22:34:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design | Profile | Account Security | Documentation,design documentation vsa profile,"## Background We need to audit, update and/or create design documentation for the Account Security section of the Profile located [here](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/identity-personalization/profile/account-security). Good examples can be found within Direct deposit or Contact info features which have recently been updated. ## Tasks - [x] Update and/or create use cases for this feature - [x] Create user flows - [x] Create/update screen mocks and text ## Acceptance Criteria - [x] Post to appropriate sections of GitHub and sketch - [x] Check that links from product outline are up to date ",1.0,"Design | Profile | Account Security | Documentation - ## Background We need to audit, update and/or create design documentation for the Account Security section of the Profile located [here](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/identity-personalization/profile/account-security). Good examples can be found within Direct deposit or Contact info features which have recently been updated. ## Tasks - [x] Update and/or create use cases for this feature - [x] Create user flows - [x] Create/update screen mocks and text ## Acceptance Criteria - [x] Post to appropriate sections of GitHub and sketch - [x] Check that links from product outline are up to date ",1,design profile account security documentation background we need to audit update and or create design documentation for the account security section of the profile located good examples can be found within direct deposit or contact info features which have recently been updated tasks update and or create use cases for this feature create user flows create update screen mocks and text acceptance criteria post to appropriate sections of github and sketch check that links from product outline are up to date ,1 129525,17792790856.0,IssuesEvent,2021-08-31 18:13:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Render ui:objectViewField for nested objects,vsp-design-system-team,"## Issue Description [Original Slack conversation](https://dsva.slack.com/archives/CBU0KDSB1/p1630348001096600). The short story: We have a `ui:objectViewField` option to render a custom component on the review page for `object` schema types. Right now, it only renders this custom component if the `object` is the root for the page. The task here is to expand the usefulness of that property to render the custom component for nested objects. Specifically, this is useful for rendering groups of check boxes in one line item instead of one line item per check box. ## Acceptance Criteria - [ ] The custom component in a `ui:objectViewField` property of a nested object within a page is rendered - [ ] The custom component in a `ui:objectViewField` property on the root of a page is rendered",1.0,"Render ui:objectViewField for nested objects - ## Issue Description [Original Slack conversation](https://dsva.slack.com/archives/CBU0KDSB1/p1630348001096600). The short story: We have a `ui:objectViewField` option to render a custom component on the review page for `object` schema types. Right now, it only renders this custom component if the `object` is the root for the page. The task here is to expand the usefulness of that property to render the custom component for nested objects. Specifically, this is useful for rendering groups of check boxes in one line item instead of one line item per check box. ## Acceptance Criteria - [ ] The custom component in a `ui:objectViewField` property of a nested object within a page is rendered - [ ] The custom component in a `ui:objectViewField` property on the root of a page is rendered",1,render ui objectviewfield for nested objects issue description the short story we have a ui objectviewfield option to render a custom component on the review page for object schema types right now it only renders this custom component if the object is the root for the page the task here is to expand the usefulness of that property to render the custom component for nested objects specifically this is useful for rendering groups of check boxes in one line item instead of one line item per check box acceptance criteria the custom component in a ui objectviewfield property of a nested object within a page is rendered the custom component in a ui objectviewfield property on the root of a page is rendered,1 104410,13066110669.0,IssuesEvent,2020-07-30 21:01:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Bottom padding for VAMC pages,design frontend-vamc needs-grooming vsa vsa-facilities,"## Issue Description VAMC page has 0 padding along bottom bar ![image (43).png](https://images.zenhubusercontent.com/5d8a47393ac3440001d1a2ed/5141c234-904d-4adb-8a45-073ba206e764) ## Front end tasks - Ensure the page is styled according to design spec. - Ensure the back end data from API is displayed in local and review instance - Ensure unit tests are available. - Ensure your code changes are covered by E2E tests - Run axe checks using the Chrome or Firefox browser plugin - Test for color contrast and color blindness issues - Zoom layouts to 400% at 1280px width - Test with 1 or 2 screen readers - Navigate using the keyboard only ## Acceptance Criteria - [ ] Designer comments on this issue to approve page styling - [ ] Unit tests pass - [ ] E2E tests cover current code and regression - [ ] End-to-end tests show 0 violations. - [ ] The data returned matches API response (for given user or scenario) - [ ] All axe checks pass - [ ] All color contrast checks pass - [ ] All zoom testing passes - [ ] All keyboard checks pass - [ ] All screenreader checks pass ## Appendix
Ensure your code changes are covered by E2E tests (expand) - Add E2E tests if none exist for this addition/change. - Update existing E2E tests if this code will change functionality. - Include axe checks, including hidden content
Run axe checks using the Chrome or Firefox browser plugin (expand) - Ensure no heading levels are skipped. - Ensure all buttons and labeled inputs use semantic HTML elements. - Ensure all buttons, labeled elements and images are identified using HTML semantic markers or ARIA roles. - Ensure form fields have clearly defined boundaries or outlines. - Ensure form fields do not use placeholder text. - Ensure form fields have highly visible and specific error states.
Test for color contrast and color blindness issues (expand) - All text has appropriate contrast.
Zoom layouts to 400% at 1280px width (expand) - Ensure readability and usability are supported when zoomed up to 400% at 1280px browser width - Ensure no content gets focused offscreen or is hidden from view.
Test with 1 or 2 screen readers (expand) - Ensure the page includes a skip navigation link. - Ensure all links are properly descriptive. - Ensure screen reader users can hear the text equivalent for each image conveying information. - Ensure screen reader users can hear the text equivalent for each image button. - Ensure screen reader users can hear labels and instructions for inputs. - Ensure purely decorative images are not announced by the screenreader.
Navigate using the keyboard only (expand) - Ensure all links (navigation, text and/or image), form controls and page functions can be reached with the tab key in a logical order. - Ensure all links (navigation, text and/or image), form controls and page functions can be triggered with the spacebar, enter key, or arrow keys. - Ensure all interactive elements can be reached with the tab key in a logical order - Ensure all interactive elements can be triggered with the spacebar, enter key, or arrow keys. - Ensure focus is always visible and appears in logical order. - Ensure each interactive element has visible focus state which appears in logical order.
--- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Bottom padding for VAMC pages - ## Issue Description VAMC page has 0 padding along bottom bar ![image (43).png](https://images.zenhubusercontent.com/5d8a47393ac3440001d1a2ed/5141c234-904d-4adb-8a45-073ba206e764) ## Front end tasks - Ensure the page is styled according to design spec. - Ensure the back end data from API is displayed in local and review instance - Ensure unit tests are available. - Ensure your code changes are covered by E2E tests - Run axe checks using the Chrome or Firefox browser plugin - Test for color contrast and color blindness issues - Zoom layouts to 400% at 1280px width - Test with 1 or 2 screen readers - Navigate using the keyboard only ## Acceptance Criteria - [ ] Designer comments on this issue to approve page styling - [ ] Unit tests pass - [ ] E2E tests cover current code and regression - [ ] End-to-end tests show 0 violations. - [ ] The data returned matches API response (for given user or scenario) - [ ] All axe checks pass - [ ] All color contrast checks pass - [ ] All zoom testing passes - [ ] All keyboard checks pass - [ ] All screenreader checks pass ## Appendix
Ensure your code changes are covered by E2E tests (expand) - Add E2E tests if none exist for this addition/change. - Update existing E2E tests if this code will change functionality. - Include axe checks, including hidden content
Run axe checks using the Chrome or Firefox browser plugin (expand) - Ensure no heading levels are skipped. - Ensure all buttons and labeled inputs use semantic HTML elements. - Ensure all buttons, labeled elements and images are identified using HTML semantic markers or ARIA roles. - Ensure form fields have clearly defined boundaries or outlines. - Ensure form fields do not use placeholder text. - Ensure form fields have highly visible and specific error states.
Test for color contrast and color blindness issues (expand) - All text has appropriate contrast.
Zoom layouts to 400% at 1280px width (expand) - Ensure readability and usability are supported when zoomed up to 400% at 1280px browser width - Ensure no content gets focused offscreen or is hidden from view.
Test with 1 or 2 screen readers (expand) - Ensure the page includes a skip navigation link. - Ensure all links are properly descriptive. - Ensure screen reader users can hear the text equivalent for each image conveying information. - Ensure screen reader users can hear the text equivalent for each image button. - Ensure screen reader users can hear labels and instructions for inputs. - Ensure purely decorative images are not announced by the screenreader.
Navigate using the keyboard only (expand) - Ensure all links (navigation, text and/or image), form controls and page functions can be reached with the tab key in a logical order. - Ensure all links (navigation, text and/or image), form controls and page functions can be triggered with the spacebar, enter key, or arrow keys. - Ensure all interactive elements can be reached with the tab key in a logical order - Ensure all interactive elements can be triggered with the spacebar, enter key, or arrow keys. - Ensure focus is always visible and appears in logical order. - Ensure each interactive element has visible focus state which appears in logical order.
--- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,bottom padding for vamc pages issue description vamc page has padding along bottom bar front end tasks ensure the page is styled according to design spec ensure the back end data from api is displayed in local and review instance ensure unit tests are available ensure your code changes are covered by tests run axe checks using the chrome or firefox browser plugin test for color contrast and color blindness issues zoom layouts to at width test with or screen readers navigate using the keyboard only acceptance criteria designer comments on this issue to approve page styling unit tests pass tests cover current code and regression end to end tests show violations the data returned matches api response for given user or scenario all axe checks pass all color contrast checks pass all zoom testing passes all keyboard checks pass all screenreader checks pass appendix ensure your code changes are covered by tests expand add tests if none exist for this addition change update existing tests if this code will change functionality include axe checks including hidden content run axe checks using the chrome or firefox browser plugin expand ensure no heading levels are skipped ensure all buttons and labeled inputs use semantic html elements ensure all buttons labeled elements and images are identified using html semantic markers or aria roles ensure form fields have clearly defined boundaries or outlines ensure form fields do not use placeholder text ensure form fields have highly visible and specific error states test for color contrast and color blindness issues expand all text has appropriate contrast zoom layouts to at width expand ensure readability and usability are supported when zoomed up to at browser width ensure no content gets focused offscreen or is hidden from view test with or screen readers expand ensure the page includes a skip navigation link ensure all links are properly descriptive ensure screen reader users can hear the text equivalent for each image conveying information ensure screen reader users can hear the text equivalent for each image button ensure screen reader users can hear labels and instructions for inputs ensure purely decorative images are not announced by the screenreader navigate using the keyboard only expand ensure all links navigation text and or image form controls and page functions can be reached with the tab key in a logical order ensure all links navigation text and or image form controls and page functions can be triggered with the spacebar enter key or arrow keys ensure all interactive elements can be reached with the tab key in a logical order ensure all interactive elements can be triggered with the spacebar enter key or arrow keys ensure focus is always visible and appears in logical order ensure each interactive element has visible focus state which appears in logical order how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 118051,15217719515.0,IssuesEvent,2021-02-17 16:56:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"[UI] Immunizations, Allergies, and Medications Wireframes",design vsa-healthcare-exp,"## User Story - As a Veteran, I want to be able to notify my VA provider of changes to my medication, allergies, and immunization history. ## Related Documentation - [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md) - [Medications Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/medications.md) - [Allergies Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/allergies.md) - [Immunizations Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/immunizations.md) ## Description A wireframe set on immunizations, allergies, and medications within a questionnaire will be delivered, so it can be utilized: - as a discussion guide with internal stakeholders, accessibility, and content - within a usability test - further work will probably be needed to make the wireframes interactive for the actual test. - within collab cycle meetings (design intent) ## Tasks - [ ] Create a draft set of [wireframes](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product and team for feature capabilities",1.0,"[UI] Immunizations, Allergies, and Medications Wireframes - ## User Story - As a Veteran, I want to be able to notify my VA provider of changes to my medication, allergies, and immunization history. ## Related Documentation - [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md) - [Medications Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/medications.md) - [Allergies Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/allergies.md) - [Immunizations Feature Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/health-record/immunizations.md) ## Description A wireframe set on immunizations, allergies, and medications within a questionnaire will be delivered, so it can be utilized: - as a discussion guide with internal stakeholders, accessibility, and content - within a usability test - further work will probably be needed to make the wireframes interactive for the actual test. - within collab cycle meetings (design intent) ## Tasks - [ ] Create a draft set of [wireframes](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product and team for feature capabilities",1, immunizations allergies and medications wireframes user story as a veteran i want to be able to notify my va provider of changes to my medication allergies and immunization history related documentation description a wireframe set on immunizations allergies and medications within a questionnaire will be delivered so it can be utilized as a discussion guide with internal stakeholders accessibility and content within a usability test further work will probably be needed to make the wireframes interactive for the actual test within collab cycle meetings design intent tasks create a draft set of link to prototype acceptance criteria ui review meeting with product and team for feature capabilities,1 153812,24191467674.0,IssuesEvent,2022-09-23 18:02:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Q4 Planning - scheduling the tasks,service-design,"## Purpose Schedule the tasks to accomplish Q4 Initiatives ## Tasks - [x] schedule session - [x] establish potential positioning for work - [x] lead session - [x] finalize intended tasks - [x] move tasks into sprints to plan work ## Acceptance Criteria - [x] Tasks are moved to intended Sprints and reviewed",1.0,"Q4 Planning - scheduling the tasks - ## Purpose Schedule the tasks to accomplish Q4 Initiatives ## Tasks - [x] schedule session - [x] establish potential positioning for work - [x] lead session - [x] finalize intended tasks - [x] move tasks into sprints to plan work ## Acceptance Criteria - [x] Tasks are moved to intended Sprints and reviewed",1, planning scheduling the tasks purpose schedule the tasks to accomplish initiatives tasks schedule session establish potential positioning for work lead session finalize intended tasks move tasks into sprints to plan work acceptance criteria tasks are moved to intended sprints and reviewed,1 116022,14917027587.0,IssuesEvent,2021-01-22 19:10:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create a pattern for The header / hero area with the veteran's name and info,vsp-design-system-team,"## Issue Description Create a pattern for The header / hero area with the veteran's name and info --- ## Tasks - [ ] Add header/hero pattern to Sketch library - [ ] Create documentation for header hero pattern - [ ] Develop header/hero component if needed ## Acceptance Criteria - [ ] Sketch library update - [ ] Pattern is on design.va.gov --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Create a pattern for The header / hero area with the veteran's name and info - ## Issue Description Create a pattern for The header / hero area with the veteran's name and info --- ## Tasks - [ ] Add header/hero pattern to Sketch library - [ ] Create documentation for header hero pattern - [ ] Develop header/hero component if needed ## Acceptance Criteria - [ ] Sketch library update - [ ] Pattern is on design.va.gov --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,create a pattern for the header hero area with the veteran s name and info issue description create a pattern for the header hero area with the veteran s name and info tasks add header hero pattern to sketch library create documentation for header hero pattern develop header hero component if needed acceptance criteria sketch library update pattern is on design va gov how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 153826,24192637299.0,IssuesEvent,2022-09-23 19:18:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Certificate of Eligibility | Improve status document upload UX,design needs-grooming ux needs-design benefits-team-1 squad-2 needs-estimate COE,"## Value Statement **_As a_** screen reader user that needs to upload a document to the COE status page **_We want the_** upload experience to be straightforward and accessible **_So that_** the instructions make sense and I don't get confused on next steps, or error messages ## Background Context [Design document](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140741546/specification/sitemap) The COE status app has some UX & a11y issues: - Choosing a document type is _required_ before using ""Upload your document"" - if not done first, it allows the user to choose a file, but then shows an error - The error is shown above the button, when it should be shown above the select - This select really should be moved up into the gray box that appears after a file has been selected - Submit files button is always visible, and in close proximity to the ""Upload your document"" button - After ""submit files"" is used, the success message now includes the files that were just uploaded, this is missing in the design - We direct the Veteran to read their notification letter to determine which documents need to be uploaded, but the design shows a list - was this not possible? ## Tasks - [ ] Get UX review of this behavior - [ ] Update design - [ ] Determine if this upload functionality could be moved to a separate page? - [ ] Fix a11y issues ## Definition of done - [ ] All tasks complete ",2.0,"Certificate of Eligibility | Improve status document upload UX - ## Value Statement **_As a_** screen reader user that needs to upload a document to the COE status page **_We want the_** upload experience to be straightforward and accessible **_So that_** the instructions make sense and I don't get confused on next steps, or error messages ## Background Context [Design document](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140741546/specification/sitemap) The COE status app has some UX & a11y issues: - Choosing a document type is _required_ before using ""Upload your document"" - if not done first, it allows the user to choose a file, but then shows an error - The error is shown above the button, when it should be shown above the select - This select really should be moved up into the gray box that appears after a file has been selected - Submit files button is always visible, and in close proximity to the ""Upload your document"" button - After ""submit files"" is used, the success message now includes the files that were just uploaded, this is missing in the design - We direct the Veteran to read their notification letter to determine which documents need to be uploaded, but the design shows a list - was this not possible? ## Tasks - [ ] Get UX review of this behavior - [ ] Update design - [ ] Determine if this upload functionality could be moved to a separate page? - [ ] Fix a11y issues ## Definition of done - [ ] All tasks complete ",1,certificate of eligibility improve status document upload ux value statement as a screen reader user that needs to upload a document to the coe status page we want the upload experience to be straightforward and accessible so that the instructions make sense and i don t get confused on next steps or error messages background context the coe status app has some ux issues choosing a document type is required before using upload your document if not done first it allows the user to choose a file but then shows an error the error is shown above the button when it should be shown above the select this select really should be moved up into the gray box that appears after a file has been selected submit files button is always visible and in close proximity to the upload your document button after submit files is used the success message now includes the files that were just uploaded this is missing in the design we direct the veteran to read their notification letter to determine which documents need to be uploaded but the design shows a list was this not possible tasks get ux review of this behavior update design determine if this upload functionality could be moved to a separate page fix issues definition of done all tasks complete ,1 173129,27389618785.0,IssuesEvent,2023-02-28 15:28:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.3),content design 508/Accessibility ia collab-cycle-feedback VA Lovell Staging CCIssue04.07 CC-Dashboard VAMC,"### General Information #### VFS team name Sitewide Facilities #### VFS product name VAMC #### VFS feature name VAMC Lovell Federal Health care #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details There are several instances where the address is buried in content and does not have the address block applied to it. ### Link, screenshot or steps to recreate https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/52672_allison_040703.png ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Add the address block when addresses are buried in content. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.3) - ### General Information #### VFS team name Sitewide Facilities #### VFS product name VAMC #### VFS feature name VAMC Lovell Federal Health care #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details There are several instances where the address is buried in content and does not have the address block applied to it. ### Link, screenshot or steps to recreate https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/52672_allison_040703.png ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Add the address block when addresses are buried in content. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, design components or patterns don t align with design system guidelines general information vfs team name sitewide facilities vfs product name vamc vfs feature name vamc lovell federal health care point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details there are several instances where the address is buried in content and does not have the address block applied to it link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation add the address block when addresses are buried in content vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 118038,15216755249.0,IssuesEvent,2021-02-17 15:51:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Refactor some of the names in theme,Design -> Frontend Theme frontend va-mobile-app,"UI/UX is working on a design library to use for building new screens. In order to help us transfer design to front end code, we need to change some things to use a shared nomenclature. The following names need to be changed in the theme files: - [ ] `marginBetween` should be renamed to `standardMarginBetween` and `condensedMarginBetween: 10` should replace any other dimension we use in places like cards and cta's for vertical spacing of 10. `theme.colors.background.main` should change from `#F2F2F7` to `colors.grayLightest` - [ ] button colors need to reflect whether they are for `buttonPrimary` or `buttonSecondary`. This means that `theme.colors.background.button` will need to change to `buttonPrimary`, and anywhere that we use a border color or text color should now have a `buttonPrimary` or `buttonSecondary` prefix, i.e. `theme.border` should now have a `buttonSecondary`, `buttonSecondaryActive`, and `buttonSecondaryDisabled` color added. Any special text colors should also get added if we are using them. This is a start to some larger changes that will be happening in the theme area over the coming sprints. ",1.0,"Refactor some of the names in theme - UI/UX is working on a design library to use for building new screens. In order to help us transfer design to front end code, we need to change some things to use a shared nomenclature. The following names need to be changed in the theme files: - [ ] `marginBetween` should be renamed to `standardMarginBetween` and `condensedMarginBetween: 10` should replace any other dimension we use in places like cards and cta's for vertical spacing of 10. `theme.colors.background.main` should change from `#F2F2F7` to `colors.grayLightest` - [ ] button colors need to reflect whether they are for `buttonPrimary` or `buttonSecondary`. This means that `theme.colors.background.button` will need to change to `buttonPrimary`, and anywhere that we use a border color or text color should now have a `buttonPrimary` or `buttonSecondary` prefix, i.e. `theme.border` should now have a `buttonSecondary`, `buttonSecondaryActive`, and `buttonSecondaryDisabled` color added. Any special text colors should also get added if we are using them. This is a start to some larger changes that will be happening in the theme area over the coming sprints. ",1,refactor some of the names in theme ui ux is working on a design library to use for building new screens in order to help us transfer design to front end code we need to change some things to use a shared nomenclature the following names need to be changed in the theme files marginbetween should be renamed to standardmarginbetween and condensedmarginbetween should replace any other dimension we use in places like cards and cta s for vertical spacing of theme colors background main should change from to colors graylightest button colors need to reflect whether they are for buttonprimary or buttonsecondary this means that theme colors background button will need to change to buttonprimary and anywhere that we use a border color or text color should now have a buttonprimary or buttonsecondary prefix i e theme border should now have a buttonsecondary buttonsecondaryactive and buttonsecondarydisabled color added any special text colors should also get added if we are using them this is a start to some larger changes that will be happening in the theme area over the coming sprints ,1 135918,19683236175.0,IssuesEvent,2022-01-11 18:58:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Table web component: migration,vsp-design-system-team,"## Description Dependent on #35107 Write the migration script for the Table web component. This component is not used in the Forms library, so no need to perform any migration there. ## Acceptance Criteria - [ ] write migration script - [ ] test migration script",1.0,"Table web component: migration - ## Description Dependent on #35107 Write the migration script for the Table web component. This component is not used in the Forms library, so no need to perform any migration there. ## Acceptance Criteria - [ ] write migration script - [ ] test migration script",1,table web component migration description dependent on write the migration script for the table web component this component is not used in the forms library so no need to perform any migration there acceptance criteria write migration script test migration script,1 147055,23159916569.0,IssuesEvent,2022-07-29 16:32:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Supplemental Claims UX Design,design benefits-team-1 squad-2,"## Supplemental Claims Product Outline [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/readme.md) ## High Level User Story/ies As a Claimant, I want the claims I submit to be visible to me as they move through VA systems, and I want proactive communications about their progress. As a Claimant, I want the process of choosing and filing a decision review (and by extension supplemental claim) to be easily understandable. ## Purpose This epic is intended to house the UX tickets specific to the initial build of Supplemental Claims. ## Definition of done We'll close this epic once we've resolved all content issues related to MVP. ## Important Links * [Supplemental Claims Content Brief](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/content/content-briefs/supplemental-claims-content-brief.md) * [Draft of Supplemental Claims Content Source of Truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/design/%5Bdraft%5Dcontent.md) ",1.0,"Supplemental Claims UX Design - ## Supplemental Claims Product Outline [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/readme.md) ## High Level User Story/ies As a Claimant, I want the claims I submit to be visible to me as they move through VA systems, and I want proactive communications about their progress. As a Claimant, I want the process of choosing and filing a decision review (and by extension supplemental claim) to be easily understandable. ## Purpose This epic is intended to house the UX tickets specific to the initial build of Supplemental Claims. ## Definition of done We'll close this epic once we've resolved all content issues related to MVP. ## Important Links * [Supplemental Claims Content Brief](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/content/content-briefs/supplemental-claims-content-brief.md) * [Draft of Supplemental Claims Content Source of Truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/design/%5Bdraft%5Dcontent.md) ",1,supplemental claims ux design supplemental claims product outline high level user story ies as a claimant i want the claims i submit to be visible to me as they move through va systems and i want proactive communications about their progress as a claimant i want the process of choosing and filing a decision review and by extension supplemental claim to be easily understandable purpose this epic is intended to house the ux tickets specific to the initial build of supplemental claims definition of done we ll close this epic once we ve resolved all content issues related to mvp important links ,1 117711,15167416294.0,IssuesEvent,2021-02-12 17:45:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Initial content review - VAOS for vaccine distribution ,design vaos,"This is an initial content review of the prototype we plan to test with Veterans: https://adhoc.invisionapp.com/share/GU1028Y9YDTX#/screens/443560117 @DanielleThierryUSDSVA I added some tour points you can click for more context on certain screens. @peggygannon adding you for visibility. Let me know if you have any questions.",1.0,"Initial content review - VAOS for vaccine distribution - This is an initial content review of the prototype we plan to test with Veterans: https://adhoc.invisionapp.com/share/GU1028Y9YDTX#/screens/443560117 @DanielleThierryUSDSVA I added some tour points you can click for more context on certain screens. @peggygannon adding you for visibility. Let me know if you have any questions.",1,initial content review vaos for vaccine distribution this is an initial content review of the prototype we plan to test with veterans daniellethierryusdsva i added some tour points you can click for more context on certain screens peggygannon adding you for visibility let me know if you have any questions ,1 88961,11184066861.0,IssuesEvent,2019-12-31 16:16:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Discovery: Synthesize User Interview Findings,design discovery documentation research vsa-benefits-2,"## User Story or Problem Statement As a UX Designer, I need to synthesize gathered data from interview sessions so I can discover common themes among interviewed Veterans. ## Goal _A document containing data from interview sessions that has been organized into common themes_ ## Objectives or Key Results this is meant to further - _Discovery sprint_ - _Finding pain points in the ordering process_ - _Discovering improvements to the ordering process_ - _The form's flow and design_ ## Tasks - [x] Create spreadsheet and organize data from interview sessions (8-12 hours for each designer) - [x] Create themes (document already created in ticket #3424)_ (8-12 hours for each designer) ## Acceptance Criteria - [x] Create Miro board ## Next Steps - Create research artifacts (personas, user journeys) ## Blockers - None",1.0,"Discovery: Synthesize User Interview Findings - ## User Story or Problem Statement As a UX Designer, I need to synthesize gathered data from interview sessions so I can discover common themes among interviewed Veterans. ## Goal _A document containing data from interview sessions that has been organized into common themes_ ## Objectives or Key Results this is meant to further - _Discovery sprint_ - _Finding pain points in the ordering process_ - _Discovering improvements to the ordering process_ - _The form's flow and design_ ## Tasks - [x] Create spreadsheet and organize data from interview sessions (8-12 hours for each designer) - [x] Create themes (document already created in ticket #3424)_ (8-12 hours for each designer) ## Acceptance Criteria - [x] Create Miro board ## Next Steps - Create research artifacts (personas, user journeys) ## Blockers - None",1,discovery synthesize user interview findings user story or problem statement as a ux designer i need to synthesize gathered data from interview sessions so i can discover common themes among interviewed veterans goal a document containing data from interview sessions that has been organized into common themes objectives or key results this is meant to further discovery sprint finding pain points in the ordering process discovering improvements to the ordering process the form s flow and design tasks create spreadsheet and organize data from interview sessions hours for each designer create themes document already created in ticket hours for each designer acceptance criteria create miro board next steps create research artifacts personas user journeys blockers none,1 110641,13923748633.0,IssuesEvent,2020-10-21 14:46:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[DESIGN] MyVA Dashboard: Revisit Direction/Wireframe explorations (1 week),design my-va-dashboard needs-grooming vsa-authenticated-exp,"## Background We are taking the first week of this sprint (S33) to revisit the direction of the MyVA dashboard redesign and explore different options and decide upon the approach going forward. The focus should be on sketches/low-fi wireframes not on detailed visual design. My VA goals: Get users to personalized information and tasks as quickly as possible. The page should be personalized, actionable, and scalable. ## Tasks - [ ] Wireframe explorations - [ ] Sketches/low-fi wireframes - [ ] Meet and review with Samara/Ryan/Matt - [ ] Decide on direction going forward ",1.0,"[DESIGN] MyVA Dashboard: Revisit Direction/Wireframe explorations (1 week) - ## Background We are taking the first week of this sprint (S33) to revisit the direction of the MyVA dashboard redesign and explore different options and decide upon the approach going forward. The focus should be on sketches/low-fi wireframes not on detailed visual design. My VA goals: Get users to personalized information and tasks as quickly as possible. The page should be personalized, actionable, and scalable. ## Tasks - [ ] Wireframe explorations - [ ] Sketches/low-fi wireframes - [ ] Meet and review with Samara/Ryan/Matt - [ ] Decide on direction going forward ",1, myva dashboard revisit direction wireframe explorations week background we are taking the first week of this sprint to revisit the direction of the myva dashboard redesign and explore different options and decide upon the approach going forward the focus should be on sketches low fi wireframes not on detailed visual design my va goals get users to personalized information and tasks as quickly as possible the page should be personalized actionable and scalable tasks wireframe explorations sketches low fi wireframes meet and review with samara ryan matt decide on direction going forward ,1 172531,27293935883.0,IssuesEvent,2023-02-23 18:40:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Communicate change to Survey,service-design,"## Purpose Because we are changing the survey, we need to speak to the change and establish the key differences the new one will bring to the table. Existing Survey documentation in the SDT Confluence Space: Overview page -- Schedule (with links to artifacts such as decks and Murals) -- How to [launch the Survey](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1445724309/How-to+Launch+the+Platform+Satisfaction+Survey) (tools and steps) -- Aggregated results of themes per survey Reference material: [Product Outline](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2487091201/Product+Outline+-+Platform+Feedback+portal) Needs for this ticket: Transition announcement (one more Survey, then new modality, pointers to in-depth links) -- Why the new modality (needs, benefits) -- What this will mean for you the user How might we display old results and new types of results? ## Tasks - [x] Determine date of the upcoming and final Quarterly Survey (previous dates: closed in August 2022, closed late October 2022, closed December 2022) - [ ] Draft ""What will be changing, when, and why"" content for existing Confluence page - [ ] Site should address that a change is coming w/ the next survey - [x] Determine format - [x] List Slack channels for change announcement to Platform teams - [x] #vfs-all-teams - [x] #platform-service-design - [x] #platform-team - [x] List Slack channels for change announcement to VFS teams - [x] #vfs-change-announcements - [ ] Draft content for new Confluence page - [ ] Site should speak to new makeup of survey - [ ] Determine where and how to archive past Quarterly Survey content ## Acceptance Criteria - [ ] Site addresses each item above. ",1.0,"Communicate change to Survey - ## Purpose Because we are changing the survey, we need to speak to the change and establish the key differences the new one will bring to the table. Existing Survey documentation in the SDT Confluence Space: Overview page -- Schedule (with links to artifacts such as decks and Murals) -- How to [launch the Survey](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1445724309/How-to+Launch+the+Platform+Satisfaction+Survey) (tools and steps) -- Aggregated results of themes per survey Reference material: [Product Outline](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2487091201/Product+Outline+-+Platform+Feedback+portal) Needs for this ticket: Transition announcement (one more Survey, then new modality, pointers to in-depth links) -- Why the new modality (needs, benefits) -- What this will mean for you the user How might we display old results and new types of results? ## Tasks - [x] Determine date of the upcoming and final Quarterly Survey (previous dates: closed in August 2022, closed late October 2022, closed December 2022) - [ ] Draft ""What will be changing, when, and why"" content for existing Confluence page - [ ] Site should address that a change is coming w/ the next survey - [x] Determine format - [x] List Slack channels for change announcement to Platform teams - [x] #vfs-all-teams - [x] #platform-service-design - [x] #platform-team - [x] List Slack channels for change announcement to VFS teams - [x] #vfs-change-announcements - [ ] Draft content for new Confluence page - [ ] Site should speak to new makeup of survey - [ ] Determine where and how to archive past Quarterly Survey content ## Acceptance Criteria - [ ] Site addresses each item above. ",1,communicate change to survey purpose because we are changing the survey we need to speak to the change and establish the key differences the new one will bring to the table existing survey documentation in the sdt confluence space overview page schedule with links to artifacts such as decks and murals how to tools and steps aggregated results of themes per survey reference material needs for this ticket transition announcement one more survey then new modality pointers to in depth links why the new modality needs benefits what this will mean for you the user how might we display old results and new types of results tasks determine date of the upcoming and final quarterly survey previous dates closed in august closed late october closed december draft what will be changing when and why content for existing confluence page site should address that a change is coming w the next survey determine format list slack channels for change announcement to platform teams vfs all teams platform service design platform team list slack channels for change announcement to vfs teams vfs change announcements draft content for new confluence page site should speak to new makeup of survey determine where and how to archive past quarterly survey content acceptance criteria site addresses each item above ,1 107293,13450182119.0,IssuesEvent,2020-09-08 18:06:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[UI] UX Design Demographics,design vsa-healthcare-exp,"## Product Documentation [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) - [Feature - Demographics](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/demographics.md) ## User Story/ies * **Use Case:** Veterans need the ability to see the demographic information that is on record to ensure accuracy and be able to verbally with the care team or through a digital edit experience update for the most up to date information. --- ## Tasks - [x] See demographic feature outline for fields and valuation - [x] Create detailed mockups and callouts of demographic page ## Acceptance Criteria - [x] UI review with team for feature capabilities and engineering callouts - [x] published to [Zeplin](https://zpl.io/2p9EOr8) ",1.0,"[UI] UX Design Demographics - ## Product Documentation [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md) - [Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) - [Feature - Demographics](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/features/demographics.md) ## User Story/ies * **Use Case:** Veterans need the ability to see the demographic information that is on record to ensure accuracy and be able to verbally with the care team or through a digital edit experience update for the most up to date information. --- ## Tasks - [x] See demographic feature outline for fields and valuation - [x] Create detailed mockups and callouts of demographic page ## Acceptance Criteria - [x] UI review with team for feature capabilities and engineering callouts - [x] published to [Zeplin](https://zpl.io/2p9EOr8) ",1, ux design demographics product documentation user story ies use case veterans need the ability to see the demographic information that is on record to ensure accuracy and be able to verbally with the care team or through a digital edit experience update for the most up to date information tasks see demographic feature outline for fields and valuation create detailed mockups and callouts of demographic page acceptance criteria ui review with team for feature capabilities and engineering callouts published to ,1 107606,13490063458.0,IssuesEvent,2020-09-11 14:39:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Schedule Design-Intent checkpoint meeting for LIH,auth-homepage design vsa-authenticated-exp,"## Background [Design-Intent checkpoint requirements](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#design-intent-collaboration) ## Tasks - [x] prepare needed artifacts and place them in the DI checkpoint request ticket - [x] Schedule design-intent checkpoint ",1.0,"Schedule Design-Intent checkpoint meeting for LIH - ## Background [Design-Intent checkpoint requirements](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#design-intent-collaboration) ## Tasks - [x] prepare needed artifacts and place them in the DI checkpoint request ticket - [x] Schedule design-intent checkpoint ",1,schedule design intent checkpoint meeting for lih background tasks prepare needed artifacts and place them in the di checkpoint request ticket schedule design intent checkpoint ,1 91257,11489824015.0,IssuesEvent,2020-02-11 16:05:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] HLR: Introduction Page Improvements,HLR design vsa-benefits vsa-decision-reviews,"## User Story: As a veteran, I need a submit requests for higher level review in an easy to navigate and understand fashion so that I can successfully get my benefits. After the usability testing research, we found some opportunities to enhance the user experience on the Introduction Page to the HLR form. Some of these improvements include: - Consider adding an info box about the Opt out process, or adding a F.A.Q. section (why should I do this, what are the benefits, what are the implications, what the difference between new and old appeals process? etc.) - Increase visibility by moving info about New Evidence up to the first paragraph (with the link “Learn more about review options” - Consider if more info about this rule is needed on this page ## Tasks - [x] Revise intro page mockup to incorporate recommended design changes - [x] Communicate with Christian to ensure conceptual symmetry ## Acceptance Criteria: - [x] Updated intro page mockup has been delivered - [x] Design reviewed and accepted by design team ## Configuration - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (e.g. `vsa-authenticated-exp`, `vsa-caregiver`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] HLR: Introduction Page Improvements - ## User Story: As a veteran, I need a submit requests for higher level review in an easy to navigate and understand fashion so that I can successfully get my benefits. After the usability testing research, we found some opportunities to enhance the user experience on the Introduction Page to the HLR form. Some of these improvements include: - Consider adding an info box about the Opt out process, or adding a F.A.Q. section (why should I do this, what are the benefits, what are the implications, what the difference between new and old appeals process? etc.) - Increase visibility by moving info about New Evidence up to the first paragraph (with the link “Learn more about review options” - Consider if more info about this rule is needed on this page ## Tasks - [x] Revise intro page mockup to incorporate recommended design changes - [x] Communicate with Christian to ensure conceptual symmetry ## Acceptance Criteria: - [x] Updated intro page mockup has been delivered - [x] Design reviewed and accepted by design team ## Configuration - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (e.g. `vsa-authenticated-exp`, `vsa-caregiver`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, hlr introduction page improvements user story as a veteran i need a submit requests for higher level review in an easy to navigate and understand fashion so that i can successfully get my benefits after the usability testing research we found some opportunities to enhance the user experience on the introduction page to the hlr form some of these improvements include consider adding an info box about the opt out process or adding a f a q section why should i do this what are the benefits what are the implications what the difference between new and old appeals process etc increase visibility by moving info about new evidence up to the first paragraph with the link “learn more about review options” consider if more info about this rule is needed on this page tasks revise intro page mockup to incorporate recommended design changes communicate with christian to ensure conceptual symmetry acceptance criteria updated intro page mockup has been delivered design reviewed and accepted by design team configuration attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team e g vsa authenticated exp vsa caregiver labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 115704,14876405171.0,IssuesEvent,2021-01-20 00:47:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] CC - No providers found error ,content design vaos vsp-product-support,"Update language for error message that shows when providers are not found in CC Provider list. ## Use Case 1 - [ ] Technical issue retrieving providers ([current error)](https://user-images.githubusercontent.com/8315447/101203702-19463780-3639-11eb-9064-683656909878.png) ### Questions/Considerations - Should we prompt the user to refresh the page/widget to retry? - Should the FE detect the error and automatically retry fetching the providers? (not something we currently do in VAOS) - Should we direct them to call their VA? --- ## Use Case 2 - [ ] Able to retrieve providers, but 0 are returned ### Questions/Considerations - Should we direct them to call their VA? - Should the FE try to fetch another set of specialty codes?",1.0,"[Design] CC - No providers found error - Update language for error message that shows when providers are not found in CC Provider list. ## Use Case 1 - [ ] Technical issue retrieving providers ([current error)](https://user-images.githubusercontent.com/8315447/101203702-19463780-3639-11eb-9064-683656909878.png) ### Questions/Considerations - Should we prompt the user to refresh the page/widget to retry? - Should the FE detect the error and automatically retry fetching the providers? (not something we currently do in VAOS) - Should we direct them to call their VA? --- ## Use Case 2 - [ ] Able to retrieve providers, but 0 are returned ### Questions/Considerations - Should we direct them to call their VA? - Should the FE try to fetch another set of specialty codes?",1, cc no providers found error update language for error message that shows when providers are not found in cc provider list use case technical issue retrieving providers questions considerations should we prompt the user to refresh the page widget to retry should the fe detect the error and automatically retry fetching the providers not something we currently do in vaos should we direct them to call their va use case able to retrieve providers but are returned questions considerations should we direct them to call their va should the fe try to fetch another set of specialty codes ,1 152680,24003390992.0,IssuesEvent,2022-09-14 13:12:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Travel Pay: Create Final Wireframes,design ux HCE-Checkin CIE-next,"## User Story As a Veteran, I would like to be able to submit a BT reimbursement claim so that I can get reimbursed. ## Tasks - [ ] Create final wireframes and callouts for the Beneficiary Travel MVP - [ ] Add OMB, Expiration Date and Estimated Burden to the design. ([Slack thread](https://dsva.slack.com/archives/C022AC2STBM/p1660138758818239)) - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [x] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [x] Wireframe available on Abstract Collection - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ## UX/UI Deliverable - [x] [Wireframes in Ccollection](https://share.goabstract.com/cd14def3-a950-48df-94b0-904c52ca4850) - [x] [Clickthrough link](https://share.goabstract.com/cd14def3-a950-48df-94b0-904c52ca4850?collectionLayerId=11842933-81f3-4651-86c5-220d77e2c649&mode=design&present=true)",1.0,"[Design] Travel Pay: Create Final Wireframes - ## User Story As a Veteran, I would like to be able to submit a BT reimbursement claim so that I can get reimbursed. ## Tasks - [ ] Create final wireframes and callouts for the Beneficiary Travel MVP - [ ] Add OMB, Expiration Date and Estimated Burden to the design. ([Slack thread](https://dsva.slack.com/archives/C022AC2STBM/p1660138758818239)) - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [x] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [x] Wireframe available on Abstract Collection - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ## UX/UI Deliverable - [x] [Wireframes in Ccollection](https://share.goabstract.com/cd14def3-a950-48df-94b0-904c52ca4850) - [x] [Clickthrough link](https://share.goabstract.com/cd14def3-a950-48df-94b0-904c52ca4850?collectionLayerId=11842933-81f3-4651-86c5-220d77e2c649&mode=design&present=true)",1, travel pay create final wireframes user story as a veteran i would like to be able to submit a bt reimbursement claim so that i can get reimbursed tasks create final wireframes and callouts for the beneficiary travel mvp add omb expiration date and estimated burden to the design decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on abstract collection wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation ux ui deliverable ,1 157773,24726013447.0,IssuesEvent,2022-10-20 14:06:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] 1010EZ Introduction page variations,design 1010-team 1010-ez story improvement,"## Description The introduction page of the 1010EZ looks different depending on the status of the user: whether they are authenticated, not authenticated, or verified. We need mockups to match these states. ## Tasks **Authenticated pages** - [x] Authenticated user that has already applied for healthcare - [x] Authenticated user that has not been verified - [x] Authenticated user with in progress application - [x] Authenticated user new application - [x] Authenticated prefill notice - [x] Authenticated application not accepted - [x] Authenticated application loading page - [x] Authenticated downtime alert page **Unauthenticated pages** - [x] Unauthenticated user new application - [x] Unauthenticated downtime alert page - [x] Unauthenticated application loading page ## Acceptance Criteria - [x] Confirm the intro page variations with engineering team - [x] Mockups for each page variation - [x] Pages are updated to current design system standards ",1.0,"[DESIGN] 1010EZ Introduction page variations - ## Description The introduction page of the 1010EZ looks different depending on the status of the user: whether they are authenticated, not authenticated, or verified. We need mockups to match these states. ## Tasks **Authenticated pages** - [x] Authenticated user that has already applied for healthcare - [x] Authenticated user that has not been verified - [x] Authenticated user with in progress application - [x] Authenticated user new application - [x] Authenticated prefill notice - [x] Authenticated application not accepted - [x] Authenticated application loading page - [x] Authenticated downtime alert page **Unauthenticated pages** - [x] Unauthenticated user new application - [x] Unauthenticated downtime alert page - [x] Unauthenticated application loading page ## Acceptance Criteria - [x] Confirm the intro page variations with engineering team - [x] Mockups for each page variation - [x] Pages are updated to current design system standards ",1, introduction page variations description the introduction page of the looks different depending on the status of the user whether they are authenticated not authenticated or verified we need mockups to match these states tasks authenticated pages authenticated user that has already applied for healthcare authenticated user that has not been verified authenticated user with in progress application authenticated user new application authenticated prefill notice authenticated application not accepted authenticated application loading page authenticated downtime alert page unauthenticated pages unauthenticated user new application unauthenticated downtime alert page unauthenticated application loading page acceptance criteria confirm the intro page variations with engineering team mockups for each page variation pages are updated to current design system standards ,1 180612,30536084831.0,IssuesEvent,2023-07-19 17:27:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Interview VFS teams to learn about DI experiences,service-design,"## Purpose Let's learn from VFS teams about what made DI clear, unclear, difficult, time-consuming, easier, etc ## Tasks - [ ] Get list of teams from Governance who have gone through DI recently - [ ] Schedule sessions - [ ] Interview VFS teams - [ ] Synthesize takeaways ## Acceptance Criteria - [ ] Documented learnings ",1.0,"Interview VFS teams to learn about DI experiences - ## Purpose Let's learn from VFS teams about what made DI clear, unclear, difficult, time-consuming, easier, etc ## Tasks - [ ] Get list of teams from Governance who have gone through DI recently - [ ] Schedule sessions - [ ] Interview VFS teams - [ ] Synthesize takeaways ## Acceptance Criteria - [ ] Documented learnings ",1,interview vfs teams to learn about di experiences purpose let s learn from vfs teams about what made di clear unclear difficult time consuming easier etc tasks get list of teams from governance who have gone through di recently schedule sessions interview vfs teams synthesize takeaways acceptance criteria documented learnings ,1 93730,11801336880.0,IssuesEvent,2020-03-18 19:15:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Add mobile text styles ,design system,"refer to this ticket: https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/178 h1 desktop = 40/52 mobile = 32/39 h2 desktop = 30/39 mobile = 24/31 Lead desktop = 20/34 mobile = 16/27 - [ ] Add mobile text tyles",1.0,"Add mobile text styles - refer to this ticket: https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/178 h1 desktop = 40/52 mobile = 32/39 h2 desktop = 30/39 mobile = 24/31 Lead desktop = 20/34 mobile = 16/27 - [ ] Add mobile text tyles",1,add mobile text styles refer to this ticket desktop mobile desktop mobile lead desktop mobile add mobile text tyles,1 184600,32012691463.0,IssuesEvent,2023-09-21 19:10:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Low-fi explorations of replacement for claim process stepper,design benefits-team-1 squad-1,"#### Background [Product initiative brief](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/claim-appeal-status/CST%20Product/Improved%20Claims%20Process%20Understanding%20Initiative.md) #### Desired outcomes (from product brief) - Veterans have a clear understanding of the claims process, their responsibilities, and the VA's responsibilities at each stage. - Veterans can easily differentiate between their own tasks and those of the VA at each stage of the claims process. - Veterans understand why specific evidence is requested and what constitutes strong evidence, leading to more timely and effective submissions. - The CST provides a more accurate depiction of the claims process, better aligning veterans' expectations with the reality of claim progression. #### Acceptance criteria Create a first set of low-fidelity design explorations to discuss as a team. Some initial concepts can be found [here](https://docs.google.com/presentation/d/164q6M7MJAVxFjhvU8UjDaiSK0sUSDtEcokF2CULzPRo/edit#slide=id.g247d5e81071_1_27). #### Actions to take - [ ] Meet with the 526 team to get early feedback and learn if what we are suggesting will impact the form and are there things we need to consider in the design. - [ ] Maybe doing a series of concept testing with veterans to get their thoughts - [ ] Working with content team - [ ] Narrow down the design more to prepare for the collaboration team. ",1.0,"[Design] Low-fi explorations of replacement for claim process stepper - #### Background [Product initiative brief](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/claim-appeal-status/CST%20Product/Improved%20Claims%20Process%20Understanding%20Initiative.md) #### Desired outcomes (from product brief) - Veterans have a clear understanding of the claims process, their responsibilities, and the VA's responsibilities at each stage. - Veterans can easily differentiate between their own tasks and those of the VA at each stage of the claims process. - Veterans understand why specific evidence is requested and what constitutes strong evidence, leading to more timely and effective submissions. - The CST provides a more accurate depiction of the claims process, better aligning veterans' expectations with the reality of claim progression. #### Acceptance criteria Create a first set of low-fidelity design explorations to discuss as a team. Some initial concepts can be found [here](https://docs.google.com/presentation/d/164q6M7MJAVxFjhvU8UjDaiSK0sUSDtEcokF2CULzPRo/edit#slide=id.g247d5e81071_1_27). #### Actions to take - [ ] Meet with the 526 team to get early feedback and learn if what we are suggesting will impact the form and are there things we need to consider in the design. - [ ] Maybe doing a series of concept testing with veterans to get their thoughts - [ ] Working with content team - [ ] Narrow down the design more to prepare for the collaboration team. ",1, low fi explorations of replacement for claim process stepper background desired outcomes from product brief veterans have a clear understanding of the claims process their responsibilities and the va s responsibilities at each stage veterans can easily differentiate between their own tasks and those of the va at each stage of the claims process veterans understand why specific evidence is requested and what constitutes strong evidence leading to more timely and effective submissions the cst provides a more accurate depiction of the claims process better aligning veterans expectations with the reality of claim progression acceptance criteria create a first set of low fidelity design explorations to discuss as a team some initial concepts can be found actions to take meet with the team to get early feedback and learn if what we are suggesting will impact the form and are there things we need to consider in the design maybe doing a series of concept testing with veterans to get their thoughts working with content team narrow down the design more to prepare for the collaboration team ,1 167894,26564980988.0,IssuesEvent,2023-01-20 19:15:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reopened,Design System Update: Update background colors shown on new homepage hero veteran images,vsp-design-system-team,"To learn more about contributing to the Design System or requesting new components, requesting changes to existing components, and reporting bugs, go here. https://design.va.gov/about/contributing-to-the-design-system/ --- # Design System update - [x] I’ve searched for any related issues and avoided creating a duplicate issue. ## Proposed Changes On the new homepage: when no V2 Home page benefit promo custom block is published to the Home page benefit promo entity queue, a series of veteran images will show: https://www.sketch.com/s/3aa40506-4be2-46cc-876b-93f1a9f3a857/a/WKW7xVA During prototype build, the background colors for images in that space were hard coded. Those colors are not in the design system and are unique to this homepage design. These colors should be moved into the design system. ",1.0,"Design System Update: Update background colors shown on new homepage hero veteran images - To learn more about contributing to the Design System or requesting new components, requesting changes to existing components, and reporting bugs, go here. https://design.va.gov/about/contributing-to-the-design-system/ --- # Design System update - [x] I’ve searched for any related issues and avoided creating a duplicate issue. ## Proposed Changes On the new homepage: when no V2 Home page benefit promo custom block is published to the Home page benefit promo entity queue, a series of veteran images will show: https://www.sketch.com/s/3aa40506-4be2-46cc-876b-93f1a9f3a857/a/WKW7xVA During prototype build, the background colors for images in that space were hard coded. Those colors are not in the design system and are unique to this homepage design. These colors should be moved into the design system. ",1,design system update update background colors shown on new homepage hero veteran images to learn more about contributing to the design system or requesting new components requesting changes to existing components and reporting bugs go here design system update i’ve searched for any related issues and avoided creating a duplicate issue proposed changes describe in detail what went wrong screenshots videos or gifs are strongly encouraged on the new homepage when no home page benefit promo custom block is published to the home page benefit promo entity queue a series of veteran images will show during prototype build the background colors for images in that space were hard coded those colors are not in the design system and are unique to this homepage design these colors should be moved into the design system img width alt screenshot at pm src thanks for reaching out we are happy to help and will get back to you as soon as possible 😸 ,1 158315,24822235427.0,IssuesEvent,2022-10-25 17:25:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Fix Wireframes to Match Production,design ux HCE-Checkin,"## Tasks - Fix Wireframes to Match Production - If there are designs in the wireframes that SHOULD be in the product, please bring these to Lori's attention. Here is [**the list of UX items**](https://docs.google.com/spreadsheets/d/1vr5m0tfqAtCtBFLMvn54aU9bdWhxR7GRxNkZzw42G10/edit#gid=0) that are reviewed with Lori in which we would need to update. - Delete any wireframes that are not needed or obsolete (once collections are merged to the main Abstract branch we should consider archiving them)",1.0,"Fix Wireframes to Match Production - ## Tasks - Fix Wireframes to Match Production - If there are designs in the wireframes that SHOULD be in the product, please bring these to Lori's attention. Here is [**the list of UX items**](https://docs.google.com/spreadsheets/d/1vr5m0tfqAtCtBFLMvn54aU9bdWhxR7GRxNkZzw42G10/edit#gid=0) that are reviewed with Lori in which we would need to update. - Delete any wireframes that are not needed or obsolete (once collections are merged to the main Abstract branch we should consider archiving them)",1,fix wireframes to match production tasks fix wireframes to match production if there are designs in the wireframes that should be in the product please bring these to lori s attention here is that are reviewed with lori in which we would need to update delete any wireframes that are not needed or obsolete once collections are merged to the main abstract branch we should consider archiving them ,1 120119,15704829542.0,IssuesEvent,2021-03-26 15:26:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Standardized Design System Components - Modals,analytics-insights design system gtm,"# Google Analytics Implementation ## Description - Standardize data layer events and variables to track [modals](https://design.va.gov/components/modal) across va.gov ## Data Layer Specification ```javascript 'event': 'int-modal-show', 'modal-status': this.props.status, 'modal-title': this.props.title, 'modal-primaryButton-text': this.props.primaryButton.text, 'modal-secondaryButton-text': this.props.secondaryButton.text, ``` ## Acceptance Criteria - [ ] Data layer for modals has been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1.0,"Standardized Design System Components - Modals - # Google Analytics Implementation ## Description - Standardize data layer events and variables to track [modals](https://design.va.gov/components/modal) across va.gov ## Data Layer Specification ```javascript 'event': 'int-modal-show', 'modal-status': this.props.status, 'modal-title': this.props.title, 'modal-primaryButton-text': this.props.primaryButton.text, 'modal-secondaryButton-text': this.props.secondaryButton.text, ``` ## Acceptance Criteria - [ ] Data layer for modals has been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1,standardized design system components modals google analytics implementation description standardize data layer events and variables to track across va gov data layer specification javascript event int modal show modal status this props status modal title this props title modal primarybutton text this props primarybutton text modal secondarybutton text this props secondarybutton text acceptance criteria data layer for modals has been deployed universally qa has been completed definition of done all appropriate issue tagging is completed all ac completed ,1 142217,21691974059.0,IssuesEvent,2022-05-09 16:09:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Design intent [My Education Benefits - Authenticated 22-5490 Form Updates],collaboration-cycle governance-team collab-cycle-review design-intent,"# Steps to complete Design Intent Collaboration ## Before meeting **VFS Product Manager or Designer** - [ ] Create this issue and schedule meeting via Calendly (you are responsible for adding the VFS attendees). - [ ] Notify the Collaboration Cycle team of this ticket with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)). - [ ] Add artifacts listed below to the ticket at least 2 days before the scheduled meeting. **Platform** - [ ] Add the Platform reviewers to scheduled meeting - [ ] Add Zoom information to scheduled meeting ## After meeting **Platform** - [ ] Create feedback tickets and link to the Design Intent epic (if no feedback, please comment stating that). - [ ] Update [Platform Collaboration Point Tracker](https://docs.google.com/spreadsheets/d/1OgPyEvUlNF6EnaYMFAXJkV6FKOvZnlPnbOQ2fAJ7W7A/edit#gid=266151061). **VFS** - [ ] Respond to Platform feedback tickets. - [ ] Close this ticket when review is complete and feedback has been addressed. ## Artifacts Provide links or documents for the following: - [x] Product outline https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/my-education-benefits/Form%2022-5490%20Updates/Product%20Outline.md - [x] Whiteboard sketch or other lo-fi prototypes or wireframes https://accenturefederal.invisionapp.com/freehand/22-5490-FryDEA-Design-Intent-Updates-VIQCynPNO?zoomToItems=Y2wyeXg0azdiMDBhcjN4NnNscWQ5cWZ5Mw%3D%3D - [ ] User flow - [ ] Research Plan - [ ] Any other artifacts you have so far ## Scheduling - Open the [Calendly design intent calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses. - Click Schedule Event ## Additional information For the Design Intent, you'll receive feedback from design, accessibility and IA only. You won't receive feedback from content, or QA, as it's too early in the development process. Please refer to [Platform Collaboration Cycle](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/index.html) or the [Design Intent Touchpoint](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Design-intent.1782153235.html) on Platform website for more information about the Collaboration Cycle. FYI: @shiragoodman , @chaseakirby ",1.0,"Design intent [My Education Benefits - Authenticated 22-5490 Form Updates] - # Steps to complete Design Intent Collaboration ## Before meeting **VFS Product Manager or Designer** - [ ] Create this issue and schedule meeting via Calendly (you are responsible for adding the VFS attendees). - [ ] Notify the Collaboration Cycle team of this ticket with scheduled date/time in #vfs-platform-support ([see Slack Workflow User guide](https://depo-platform-documentation.scrollhelp.site/support/Getting-help-from-the-Platform-in-Slack.1439138197.html)). - [ ] Add artifacts listed below to the ticket at least 2 days before the scheduled meeting. **Platform** - [ ] Add the Platform reviewers to scheduled meeting - [ ] Add Zoom information to scheduled meeting ## After meeting **Platform** - [ ] Create feedback tickets and link to the Design Intent epic (if no feedback, please comment stating that). - [ ] Update [Platform Collaboration Point Tracker](https://docs.google.com/spreadsheets/d/1OgPyEvUlNF6EnaYMFAXJkV6FKOvZnlPnbOQ2fAJ7W7A/edit#gid=266151061). **VFS** - [ ] Respond to Platform feedback tickets. - [ ] Close this ticket when review is complete and feedback has been addressed. ## Artifacts Provide links or documents for the following: - [x] Product outline https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/my-education-benefits/Form%2022-5490%20Updates/Product%20Outline.md - [x] Whiteboard sketch or other lo-fi prototypes or wireframes https://accenturefederal.invisionapp.com/freehand/22-5490-FryDEA-Design-Intent-Updates-VIQCynPNO?zoomToItems=Y2wyeXg0azdiMDBhcjN4NnNscWQ5cWZ5Mw%3D%3D - [ ] User flow - [ ] Research Plan - [ ] Any other artifacts you have so far ## Scheduling - Open the [Calendly design intent calendar](https://calendly.com/collaboration-cycle/design-intent-or-midpoint-review) - Select a date and time and click “Confirm” - Add your name and email - Click ""Add Guests"" and enter the VFS meeting attendees email addresses. - Click Schedule Event ## Additional information For the Design Intent, you'll receive feedback from design, accessibility and IA only. You won't receive feedback from content, or QA, as it's too early in the development process. Please refer to [Platform Collaboration Cycle](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/index.html) or the [Design Intent Touchpoint](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Design-intent.1782153235.html) on Platform website for more information about the Collaboration Cycle. FYI: @shiragoodman , @chaseakirby ",1,design intent steps to complete design intent collaboration before meeting vfs product manager or designer create this issue and schedule meeting via calendly you are responsible for adding the vfs attendees notify the collaboration cycle team of this ticket with scheduled date time in vfs platform support add artifacts listed below to the ticket at least days before the scheduled meeting platform add the platform reviewers to scheduled meeting add zoom information to scheduled meeting after meeting platform create feedback tickets and link to the design intent epic if no feedback please comment stating that update vfs respond to platform feedback tickets close this ticket when review is complete and feedback has been addressed artifacts provide links or documents for the following product outline whiteboard sketch or other lo fi prototypes or wireframes user flow research plan any other artifacts you have so far scheduling open the select a date and time and click “confirm” add your name and email click add guests and enter the vfs meeting attendees email addresses click schedule event please note you are responsible for adding the vfs attendees if you have more than vfs attendees you can forward the invite after it is scheduled platform will add the platform reviewers you will receive an email and the meeting will be automatically added to your calendar additional information for the design intent you ll receive feedback from design accessibility and ia only you won t receive feedback from content or qa as it s too early in the development process please refer to or the on platform website for more information about the collaboration cycle fyi shiragoodman chaseakirby ,1 157803,24730508452.0,IssuesEvent,2022-10-20 17:09:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,DDL: Create designs for any error messages,design Claim Status Tool benefits-team-1 squad-1 download-decision-letter,"Identify and design error messages for the following: - Authenticated Veteran attempts to access URL where there decision letter would be, but they don't have any - Letters list fails to load Figure out other error states and design for those. Tasks: - [x] Determine what sort of errors could occur - [x] Determine which errors need designs - [x] Design error states",1.0,"DDL: Create designs for any error messages - Identify and design error messages for the following: - Authenticated Veteran attempts to access URL where there decision letter would be, but they don't have any - Letters list fails to load Figure out other error states and design for those. Tasks: - [x] Determine what sort of errors could occur - [x] Determine which errors need designs - [x] Design error states",1,ddl create designs for any error messages identify and design error messages for the following authenticated veteran attempts to access url where there decision letter would be but they don t have any letters list fails to load figure out other error states and design for those tasks determine what sort of errors could occur determine which errors need designs design error states,1 105566,13196693338.0,IssuesEvent,2020-08-13 21:11:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Urgent care mashup internal UI design review,Q32020-priority design frontend vsa vsa-facilities,"## Goal To insure front end implementation is consistent with specifications from designer, style guide and design system. --- ## Tasks - [ ] Review front end implementation to ensure alignment with intended design - [ ] Discuss differences with engineering team ## Acceptance Criteria Implementation reflects intended design with regard to - [ ] Defined color palette for all elements (foreground, background and fonts) - [ ] Defined states - Enabled vs disabled - Hover vs active - Focus - [ ] Defined margin and padding spacing - [ ] Defined fonts and sizes - [ ] Defined iconography, as appropriate - [ ] Field labels - [ ] Error messaging, as appropriate - [ ] References to style guide/design system components - [ ] Link words and urls - [ ] Responsiveness breakpoints - [ ] Expected interactive behavior --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Urgent care mashup internal UI design review - ## Goal To insure front end implementation is consistent with specifications from designer, style guide and design system. --- ## Tasks - [ ] Review front end implementation to ensure alignment with intended design - [ ] Discuss differences with engineering team ## Acceptance Criteria Implementation reflects intended design with regard to - [ ] Defined color palette for all elements (foreground, background and fonts) - [ ] Defined states - Enabled vs disabled - Hover vs active - Focus - [ ] Defined margin and padding spacing - [ ] Defined fonts and sizes - [ ] Defined iconography, as appropriate - [ ] Field labels - [ ] Error messaging, as appropriate - [ ] References to style guide/design system components - [ ] Link words and urls - [ ] Responsiveness breakpoints - [ ] Expected interactive behavior --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,urgent care mashup internal ui design review goal to insure front end implementation is consistent with specifications from designer style guide and design system tasks review front end implementation to ensure alignment with intended design discuss differences with engineering team acceptance criteria implementation reflects intended design with regard to defined color palette for all elements foreground background and fonts defined states enabled vs disabled hover vs active focus defined margin and padding spacing defined fonts and sizes defined iconography as appropriate field labels error messaging as appropriate references to style guide design system components link words and urls responsiveness breakpoints expected interactive behavior how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 155276,24438865114.0,IssuesEvent,2022-10-06 13:23:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Create Final Wireframes,design ux HCE-Checkin,"## User Story As a Veteran, when I do Pre-Check-in, I would like to be able to see all of my upcoming appointments so that will understand what appointments I have. ## Description A wireframes set will be delivered with the technical specifications needed for engineering to implement said feature. ## Tasks - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1.0,"[Design] Create Final Wireframes - ## User Story As a Veteran, when I do Pre-Check-in, I would like to be able to see all of my upcoming appointments so that will understand what appointments I have. ## Description A wireframes set will be delivered with the technical specifications needed for engineering to implement said feature. ## Tasks - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1, create final wireframes user story as a veteran when i do pre check in i would like to be able to see all of my upcoming appointments so that will understand what appointments i have description a wireframes set will be delivered with the technical specifications needed for engineering to implement said feature tasks finalize detailed mockup and callouts of link to prototype decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation ,1 118048,15217393623.0,IssuesEvent,2021-02-17 16:33:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyVA 2.0: Recruit for research,design vsa-authenticated-exp,"## Background We need to recruit participants for usability testing for MyVA dashboard 2.0. # Tasks - [x] Tressa kicks off recruiting with Lauren Alexanderson.",1.0,"[Design] MyVA 2.0: Recruit for research - ## Background We need to recruit participants for usability testing for MyVA dashboard 2.0. # Tasks - [x] Tressa kicks off recruiting with Lauren Alexanderson.",1, myva recruit for research background we need to recruit participants for usability testing for myva dashboard tasks tressa kicks off recruiting with lauren alexanderson ,1 138349,20404357162.0,IssuesEvent,2022-02-23 02:16:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Remove date-fns from maintenanceBanner.js,frontend vsp-design-system-team,"## Prerequisite https://github.com/department-of-veterans-affairs/va.gov-team/issues/23523 ## Issue Description The site-wide [`maintenanceBanner.js`](https://github.com/department-of-veterans-affairs/vets-website/blob/direct-deposit-review-fix-cv/src/platform/site-wide/banners/config/maintenanceBanner.js#L2) uses `date-fns`. Because we can't get the webpack tree-shaking to remove the unused parts of the library, it's adding the whole library (~20kb) to the JS bundle. Once we [remove `date-fns` from the `component-library`](https://github.com/department-of-veterans-affairs/va.gov-team/issues/23523) and use that version in `vets-website`, we need to remove the `date-fns` dependency from the `maintenanceBanner.js` module. --- ## Tasks - [ ] Use the latest version of `component-library` when `date-fns` has been removed from it - [ ] Remove the `date-fns` usage from `maintenanceBanner.js` - I'd like to just temporarily re-write the functions we're using so we don't have to use `moment`, but if that's not straightforward, we can fall back to `moment` again ## Acceptance Criteria - [ ] `date-fns` is no longer included in the `maintenanceBanner.js` - Probably this will mean it's removed from the `static-pages` bundle, but I'm not sure if it also shows up in application bundles; need to confirm where `date-fns` is included first",1.0,"Remove date-fns from maintenanceBanner.js - ## Prerequisite https://github.com/department-of-veterans-affairs/va.gov-team/issues/23523 ## Issue Description The site-wide [`maintenanceBanner.js`](https://github.com/department-of-veterans-affairs/vets-website/blob/direct-deposit-review-fix-cv/src/platform/site-wide/banners/config/maintenanceBanner.js#L2) uses `date-fns`. Because we can't get the webpack tree-shaking to remove the unused parts of the library, it's adding the whole library (~20kb) to the JS bundle. Once we [remove `date-fns` from the `component-library`](https://github.com/department-of-veterans-affairs/va.gov-team/issues/23523) and use that version in `vets-website`, we need to remove the `date-fns` dependency from the `maintenanceBanner.js` module. --- ## Tasks - [ ] Use the latest version of `component-library` when `date-fns` has been removed from it - [ ] Remove the `date-fns` usage from `maintenanceBanner.js` - I'd like to just temporarily re-write the functions we're using so we don't have to use `moment`, but if that's not straightforward, we can fall back to `moment` again ## Acceptance Criteria - [ ] `date-fns` is no longer included in the `maintenanceBanner.js` - Probably this will mean it's removed from the `static-pages` bundle, but I'm not sure if it also shows up in application bundles; need to confirm where `date-fns` is included first",1,remove date fns from maintenancebanner js prerequisite issue description the site wide uses date fns because we can t get the webpack tree shaking to remove the unused parts of the library it s adding the whole library to the js bundle once we and use that version in vets website we need to remove the date fns dependency from the maintenancebanner js module tasks use the latest version of component library when date fns has been removed from it remove the date fns usage from maintenancebanner js i d like to just temporarily re write the functions we re using so we don t have to use moment but if that s not straightforward we can fall back to moment again acceptance criteria date fns is no longer included in the maintenancebanner js probably this will mean it s removed from the static pages bundle but i m not sure if it also shows up in application bundles need to confirm where date fns is included first,1 171257,27089457423.0,IssuesEvent,2023-02-14 19:42:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Create Content and Final Wireframes,content design ux HCE-Checkin,"## Scenario Veteran is checked-in AND we submitted a travel claim for them. We need to tell them that we are going to send them a text message with the submission status of their travel claim. ## Tasks - [ ] Create content for message - [ ] Create final mockups with callouts - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1.0,"[Design] Create Content and Final Wireframes - ## Scenario Veteran is checked-in AND we submitted a travel claim for them. We need to tell them that we are going to send them a text message with the submission status of their travel claim. ## Tasks - [ ] Create content for message - [ ] Create final mockups with callouts - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1, create content and final wireframes scenario veteran is checked in and we submitted a travel claim for them we need to tell them that we are going to send them a text message with the submission status of their travel claim tasks create content for message create final mockups with callouts decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation ,1 170633,26991944541.0,IssuesEvent,2023-02-09 20:41:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design | Profile | Accessibility | Update documentation for personal information and account security,design documentation 508/Accessibility authenticated-experience profile,"## Background These sections need to be reviewed/updated now due to completed accessibility work: - Personal information - Account security once docs are launched ## Tasks - [x] Update account security [""all tasks"" complete docs](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/account-security/use-cases/complete-tasks-loa3.md) so content reflects changes, and links point to latest Sketch files - [x] Review other account security sections to determine what needs to be updated - [x] Review personal information section and update accordingly - [x] Make the the identified updates - [x] add user 11 to fiduciary use case ## Acceptance Criteria - [x] All personal info docs are updated - [x] All account security docs are updated ## Validation Anyone on team can validate the docs",1.0,"Design | Profile | Accessibility | Update documentation for personal information and account security - ## Background These sections need to be reviewed/updated now due to completed accessibility work: - Personal information - Account security once docs are launched ## Tasks - [x] Update account security [""all tasks"" complete docs](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/account-security/use-cases/complete-tasks-loa3.md) so content reflects changes, and links point to latest Sketch files - [x] Review other account security sections to determine what needs to be updated - [x] Review personal information section and update accordingly - [x] Make the the identified updates - [x] add user 11 to fiduciary use case ## Acceptance Criteria - [x] All personal info docs are updated - [x] All account security docs are updated ## Validation Anyone on team can validate the docs",1,design profile accessibility update documentation for personal information and account security background these sections need to be reviewed updated now due to completed accessibility work personal information account security once docs are launched tasks update account security so content reflects changes and links point to latest sketch files review other account security sections to determine what needs to be updated review personal information section and update accordingly make the the identified updates add user to fiduciary use case acceptance criteria all personal info docs are updated all account security docs are updated validation anyone on team can validate the docs,1 83404,10349156811.0,IssuesEvent,2019-09-04 21:36:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Build 'confirm address' page,design frontend vaos,"## Story As the VA, I want to enable veterans to confirm & update their address on file so that we can determine their Community Care eligibility (based on drive time) accurately ## AC - [ ] Page shows existing address on file from PSSG / E&E (i.e., the address with which a veteran enrolls in healthcare) - [ ] Page allows veteran to update the address on file - [ ] Page (roughly, since the mock has some wonky formatting) conforms to the latest mock: ![Screen Shot 2019-09-04 at 4.32.59 PM.png](https://images.zenhubusercontent.com/59c29173b0222d5de478791d/ee8046ba-d9b4-4fda-9206-163914940967)",1.0,"Build 'confirm address' page - ## Story As the VA, I want to enable veterans to confirm & update their address on file so that we can determine their Community Care eligibility (based on drive time) accurately ## AC - [ ] Page shows existing address on file from PSSG / E&E (i.e., the address with which a veteran enrolls in healthcare) - [ ] Page allows veteran to update the address on file - [ ] Page (roughly, since the mock has some wonky formatting) conforms to the latest mock: ![Screen Shot 2019-09-04 at 4.32.59 PM.png](https://images.zenhubusercontent.com/59c29173b0222d5de478791d/ee8046ba-d9b4-4fda-9206-163914940967)",1,build confirm address page story as the va i want to enable veterans to confirm update their address on file so that we can determine their community care eligibility based on drive time accurately ac page shows existing address on file from pssg e e i e the address with which a veteran enrolls in healthcare page allows veteran to update the address on file page roughly since the mock has some wonky formatting conforms to the latest mock ,1 95699,12034195091.0,IssuesEvent,2020-04-13 15:36:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,QA Design Review: Left Nav upgrade,design vsa vsa-facilities,"## Problem Statement How might we ensure that the developed UI to upgrade the Left Nav menu is consistent with design spec? ## Goal Ensuring consistency between design spec and development before release ## Objectives or Key Results this is meant to further Objective 2: Deliver meaningful facility information ## Tasks - [ ] Review and compare the most up-to-date UI with design spec - [ ] Meet with the frontend engineer to review any needed changes - [ ] Document meeting notes in this ticket - [ ] Create tickets for FE as needed ## Acceptance Criteria - [ ] Differences between development and design are documented and understood",1.0,"QA Design Review: Left Nav upgrade - ## Problem Statement How might we ensure that the developed UI to upgrade the Left Nav menu is consistent with design spec? ## Goal Ensuring consistency between design spec and development before release ## Objectives or Key Results this is meant to further Objective 2: Deliver meaningful facility information ## Tasks - [ ] Review and compare the most up-to-date UI with design spec - [ ] Meet with the frontend engineer to review any needed changes - [ ] Document meeting notes in this ticket - [ ] Create tickets for FE as needed ## Acceptance Criteria - [ ] Differences between development and design are documented and understood",1,qa design review left nav upgrade problem statement how might we ensure that the developed ui to upgrade the left nav menu is consistent with design spec goal ensuring consistency between design spec and development before release objectives or key results this is meant to further objective deliver meaningful facility information tasks review and compare the most up to date ui with design spec meet with the frontend engineer to review any needed changes document meeting notes in this ticket create tickets for fe as needed acceptance criteria differences between development and design are documented and understood,1 133237,18849622385.0,IssuesEvent,2021-11-11 19:01:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Content] Review appointment requests research prototype,research vsp-product-support vaos-product-design,"**Assets** - [Prototype for content review](https://va-scheduling.invisionapp.com/overview/Request-clarification---content-review-ckuspnfbr00z90151bjq20cdg/screens?sortBy=1&sortOrder=1&viewLayout=1) - [Research plan ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/appointments/va-online-scheduling/research/2021-request-clarification/research-plan.md) **Notes** Not all screens are modified from the current flow. I labeled screens that need review with an ![Review blob.png](https://images.zenhubusercontent.com/5f7ce3163782a585b910eaf3/eeb23767-9e2e-4e7d-8793-ee1894f21011) in the upper right corner (near the breadcrumb) along with notes specific to that screen. Along with content feedback, any questions that you would like answers to during this research would be helpful!",1.0,"[Content] Review appointment requests research prototype - **Assets** - [Prototype for content review](https://va-scheduling.invisionapp.com/overview/Request-clarification---content-review-ckuspnfbr00z90151bjq20cdg/screens?sortBy=1&sortOrder=1&viewLayout=1) - [Research plan ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/appointments/va-online-scheduling/research/2021-request-clarification/research-plan.md) **Notes** Not all screens are modified from the current flow. I labeled screens that need review with an ![Review blob.png](https://images.zenhubusercontent.com/5f7ce3163782a585b910eaf3/eeb23767-9e2e-4e7d-8793-ee1894f21011) in the upper right corner (near the breadcrumb) along with notes specific to that screen. Along with content feedback, any questions that you would like answers to during this research would be helpful!",1, review appointment requests research prototype assets notes not all screens are modified from the current flow i labeled screens that need review with an in the upper right corner near the breadcrumb along with notes specific to that screen along with content feedback any questions that you would like answers to during this research would be helpful ,1 94266,11859655193.0,IssuesEvent,2020-03-25 13:44:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DE] Profile 2.0: VSP Usability Testing Design Review,design profile vsa-authenticated-exp,"[Fill this out to submit VSP Usability Testing Review](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=andreahewitt-odd%2C+meganhkelley&labels=product+support%2C+content-ia-team&template=usability-testing-prep.md&title=Pre-Usability+Review+%5BFeature-Name%5D) ## Steps to complete Usability Testing Prep: - [x] Product Manager: create this issue and fill in feature name in the title and other bolded information appropriately - [x] Link to this issue once created in #vfs-platform-support in Slack; tag @ Megan Kelley @ AndreaHewitt - [x] Andrea and Megan to schedule meeting with VSP reviewers and **requesting team** attendees (as listed below) - [x] At least 2 days before scheduled meeting, you must complete list of artifacts below - [x] VSP <> **requesting team** review meeting completed - [ ] Practice area reviewers create sub-issues attached to this one with feedback for your team on *feature name* - [x] **Requesting team** completes attached feedback tickets based on definition of done included in each practice area feedback ticket (may differ for each practice area, please refer to attached tickets for further instruction) - [x] All requesting team attendees complete brief [VSP Collaboration Cycle Feedback](https://adhoc.optimalworkshop.com/questions/20260uu8-0-0/questions/before) survey ## Additional Notes: During this collaboration point, you will receive feedback from the following practice areas: design, accessibility, content, QA, and optional: information architecture (IA), product ",1.0,"[DE] Profile 2.0: VSP Usability Testing Design Review - [Fill this out to submit VSP Usability Testing Review](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=andreahewitt-odd%2C+meganhkelley&labels=product+support%2C+content-ia-team&template=usability-testing-prep.md&title=Pre-Usability+Review+%5BFeature-Name%5D) ## Steps to complete Usability Testing Prep: - [x] Product Manager: create this issue and fill in feature name in the title and other bolded information appropriately - [x] Link to this issue once created in #vfs-platform-support in Slack; tag @ Megan Kelley @ AndreaHewitt - [x] Andrea and Megan to schedule meeting with VSP reviewers and **requesting team** attendees (as listed below) - [x] At least 2 days before scheduled meeting, you must complete list of artifacts below - [x] VSP <> **requesting team** review meeting completed - [ ] Practice area reviewers create sub-issues attached to this one with feedback for your team on *feature name* - [x] **Requesting team** completes attached feedback tickets based on definition of done included in each practice area feedback ticket (may differ for each practice area, please refer to attached tickets for further instruction) - [x] All requesting team attendees complete brief [VSP Collaboration Cycle Feedback](https://adhoc.optimalworkshop.com/questions/20260uu8-0-0/questions/before) survey ## Additional Notes: During this collaboration point, you will receive feedback from the following practice areas: design, accessibility, content, QA, and optional: information architecture (IA), product ",1, profile vsp usability testing design review steps to complete usability testing prep product manager create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in vfs platform support in slack tag megan kelley andreahewitt andrea and megan to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must complete list of artifacts below vsp requesting team review meeting completed practice area reviewers create sub issues attached to this one with feedback for your team on feature name requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket may differ for each practice area please refer to attached tickets for further instruction all requesting team attendees complete brief survey additional notes during this collaboration point you will receive feedback from the following practice areas design accessibility content qa and optional information architecture ia product ,1 91424,11501269506.0,IssuesEvent,2020-02-12 16:52:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"[designer] MDT- Select supplies, batteries - rechargeable only, v1",design vsa vsa-benefits-2," ## User story: ## Tasks: Create a high fidelity mockup of the battery supply selection page when a user has only rechargeable hearing aids eligible for resupply Upload to Invision with a comment to highlight initial focus state ## Acceptance criteria: Mockup aligns with VA.gov’s design system Include information box with explanation of eligibility issue and next step Include text in each device’s card about their last order date and next eligibility date Initial focus point documented in Invision Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Dependencies: ",1.0,"[designer] MDT- Select supplies, batteries - rechargeable only, v1 - ## User story: ## Tasks: Create a high fidelity mockup of the battery supply selection page when a user has only rechargeable hearing aids eligible for resupply Upload to Invision with a comment to highlight initial focus state ## Acceptance criteria: Mockup aligns with VA.gov’s design system Include information box with explanation of eligibility issue and next step Include text in each device’s card about their last order date and next eligibility date Initial focus point documented in Invision Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Dependencies: ",1, mdt select supplies batteries rechargeable only user story tasks create a high fidelity mockup of the battery supply selection page when a user has only rechargeable hearing aids eligible for resupply upload to invision with a comment to highlight initial focus state acceptance criteria mockup aligns with va gov’s design system include information box with explanation of eligibility issue and next step include text in each device’s card about their last order date and next eligibility date initial focus point documented in invision sketch artboards are uploaded to invision and linked in this ticket as a comment dependencies ,1 139597,20916223305.0,IssuesEvent,2022-03-24 13:40:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Date web component: announcement and documentation update,vsp-design-system-team,"## Description Announce the component in the #vfs-frontend and #vfs-all-teams channel. The Date React component is used in two applications: - [disability-benefits](https://github.com/department-of-veterans-affairs/vets-website/blob/24cf7a9fafebb3b9c6e67bc5173ca780e46b9205/src/applications/disability-benefits/wizard/pages/bdd.jsx#L3) - [va-forms-system-core](https://github.com/department-of-veterans-affairs/va-forms-system-core/blob/73541c97307ba61a6064077b66e5192ac1e0c789/src/form-builder/DateField.tsx#L12) Add component to Storybook, update component documentation in design.va.gov, and add note about component release to the [What's new?](https://design.va.gov/documentation/whats-new) page. ## Details Sample announcement: >:wave: The Design System has just published a new version of component-library which includes , as well as made it available in vets-website. The migration script is also capable of automatically migrating your directories to this new component. Why does this matter to me The new additional info Web Component has a number of enhancements/fixes: Keyboard control with space and ""Enter"" key Design fix for the blue border when expanded Improved colors for contrast & consistency The web component is already loaded into the site, so removing your old AdditionalInfo imports will reduce application bundle size and improve performance. How do I migrate First, make sure your branch is using the latest master, and run yarn install. We have a script that you can use to assist with this process. You pass it two arguments: --directory - the directory you wish to migrate --component - the name of the React component to find and transform into a web component For example, to run this migration in the platform directory, you would run: yarn migrate-component --dir src/platform --component AdditionalInfo >--- >*NOTE:* One change with is that it no longer exposes onClick for an external analytics event. There is still an internal component-library-analytics event that gets fired which includes the action (expand/collapse) and the trigger text. Just be aware of this so that you don't lose any tracking data that may be used in your dashboards. Reach out to us if you have any questions/concerns about this. ## Acceptance Criteria - [ ] Craft announcement and post in #vfs-frontend and #vfs-all-teams - [ ] Reach out to teams individually about migration - [ ] Add component to Storybook - [ ] Update design.va.gov - [ ] Add note to What's new? page",1.0,"Date web component: announcement and documentation update - ## Description Announce the component in the #vfs-frontend and #vfs-all-teams channel. The Date React component is used in two applications: - [disability-benefits](https://github.com/department-of-veterans-affairs/vets-website/blob/24cf7a9fafebb3b9c6e67bc5173ca780e46b9205/src/applications/disability-benefits/wizard/pages/bdd.jsx#L3) - [va-forms-system-core](https://github.com/department-of-veterans-affairs/va-forms-system-core/blob/73541c97307ba61a6064077b66e5192ac1e0c789/src/form-builder/DateField.tsx#L12) Add component to Storybook, update component documentation in design.va.gov, and add note about component release to the [What's new?](https://design.va.gov/documentation/whats-new) page. ## Details Sample announcement: >:wave: The Design System has just published a new version of component-library which includes , as well as made it available in vets-website. The migration script is also capable of automatically migrating your directories to this new component. Why does this matter to me The new additional info Web Component has a number of enhancements/fixes: Keyboard control with space and ""Enter"" key Design fix for the blue border when expanded Improved colors for contrast & consistency The web component is already loaded into the site, so removing your old AdditionalInfo imports will reduce application bundle size and improve performance. How do I migrate First, make sure your branch is using the latest master, and run yarn install. We have a script that you can use to assist with this process. You pass it two arguments: --directory - the directory you wish to migrate --component - the name of the React component to find and transform into a web component For example, to run this migration in the platform directory, you would run: yarn migrate-component --dir src/platform --component AdditionalInfo >--- >*NOTE:* One change with is that it no longer exposes onClick for an external analytics event. There is still an internal component-library-analytics event that gets fired which includes the action (expand/collapse) and the trigger text. Just be aware of this so that you don't lose any tracking data that may be used in your dashboards. Reach out to us if you have any questions/concerns about this. ## Acceptance Criteria - [ ] Craft announcement and post in #vfs-frontend and #vfs-all-teams - [ ] Reach out to teams individually about migration - [ ] Add component to Storybook - [ ] Update design.va.gov - [ ] Add note to What's new? page",1,date web component announcement and documentation update description announce the component in the vfs frontend and vfs all teams channel the date react component is used in two applications add component to storybook update component documentation in design va gov and add note about component release to the page details sample announcement wave the design system has just published a new version of component library which includes as well as made it available in vets website the migration script is also capable of automatically migrating your directories to this new component why does this matter to me the new additional info web component has a number of enhancements fixes keyboard control with space and enter key design fix for the blue border when expanded improved colors for contrast consistency the web component is already loaded into the site so removing your old additionalinfo imports will reduce application bundle size and improve performance how do i migrate first make sure your branch is using the latest master and run yarn install we have a script that you can use to assist with this process you pass it two arguments directory the directory you wish to migrate component the name of the react component to find and transform into a web component for example to run this migration in the platform directory you would run yarn migrate component dir src platform component additionalinfo note one change with is that it no longer exposes onclick for an external analytics event there is still an internal component library analytics event that gets fired which includes the action expand collapse and the trigger text just be aware of this so that you don t lose any tracking data that may be used in your dashboards reach out to us if you have any questions concerns about this acceptance criteria craft announcement and post in vfs frontend and vfs all teams reach out to teams individually about migration add component to storybook update design va gov add note to what s new page,1 151040,23750634556.0,IssuesEvent,2022-08-31 20:14:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Notice of Disagreement | Make submissions retryable,frontend needs-grooming NOD needs-design benefits-team-1 squad-2 needs-estimate,"## Value statement **_As a_** Veteran that had just submitted an HLR form **_I want to_** know that my submission was successful, and if not immediately successful, it should keep retrying and show me a message **_So that_** I know my submission was successful, or that the system will continue trying to submit my form when the service doesn't accept my form right away. ## Background content The current Lighthouse endpoint we use to submit an HLR is pretty reliable, but the upstream VA ""systems of record"" Lighthouse relies on is sometimes down for maintenance, both planned and unplanned. The backend work to retry submissions has already been complete](https://github.com/department-of-veterans-affairs/va.gov-team/issues/42976) For form 526, the confirmation page will show a ""It's taking longer than expected"" message after about 30 seconds. ## Acceptance criteria - [ ] When a HLR is submitted, it should show a success message if immediately successful - [ ] When a HLR is submitted, it should show a message telling the Veteran that we're still trying if not immediately successful ## Tasks - [ ] Update confirmation page to show a success message when immediately successful - [ ] Update confirmation page to show a message, like ""it's taking longer than we expected"" when not immediately successful ",1.0,"Notice of Disagreement | Make submissions retryable - ## Value statement **_As a_** Veteran that had just submitted an HLR form **_I want to_** know that my submission was successful, and if not immediately successful, it should keep retrying and show me a message **_So that_** I know my submission was successful, or that the system will continue trying to submit my form when the service doesn't accept my form right away. ## Background content The current Lighthouse endpoint we use to submit an HLR is pretty reliable, but the upstream VA ""systems of record"" Lighthouse relies on is sometimes down for maintenance, both planned and unplanned. The backend work to retry submissions has already been complete](https://github.com/department-of-veterans-affairs/va.gov-team/issues/42976) For form 526, the confirmation page will show a ""It's taking longer than expected"" message after about 30 seconds. ## Acceptance criteria - [ ] When a HLR is submitted, it should show a success message if immediately successful - [ ] When a HLR is submitted, it should show a message telling the Veteran that we're still trying if not immediately successful ## Tasks - [ ] Update confirmation page to show a success message when immediately successful - [ ] Update confirmation page to show a message, like ""it's taking longer than we expected"" when not immediately successful ",1,notice of disagreement make submissions retryable value statement as a veteran that had just submitted an hlr form i want to know that my submission was successful and if not immediately successful it should keep retrying and show me a message so that i know my submission was successful or that the system will continue trying to submit my form when the service doesn t accept my form right away background content the current lighthouse endpoint we use to submit an hlr is pretty reliable but the upstream va systems of record lighthouse relies on is sometimes down for maintenance both planned and unplanned the backend work to retry submissions has already been complete for form the confirmation page will show a it s taking longer than expected message after about seconds acceptance criteria when a hlr is submitted it should show a success message if immediately successful when a hlr is submitted it should show a message telling the veteran that we re still trying if not immediately successful tasks update confirmation page to show a success message when immediately successful update confirmation page to show a message like it s taking longer than we expected when not immediately successful ,1 113903,14502106333.0,IssuesEvent,2020-12-11 20:30:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Support Bot v2,VSP-Initiative service-design,"## Problem Statement *In a couple of sentences, describe the Who, What, Why, and Where of the challenge / pain point you seek to address.* *Follow your problem description up with a ""How might we... _______"" statement re-framing that challenge as an opportunity. Don't hint too much at what the solution might be, you should have enough of a focal point here to guide your ideas, but plenty of freedom to think laterally and innovatively as you experiment and prototype later.* ## Hypothesis or Bet *How will this initiative impact the quality of VFS or VSP teams' work?* *How will this initiative be easy for VFS or VSP teams? Or how will it be easier than what they did before?* ## We will know we're done when... (""Definition of Done"") *What requirements does this project need to meet for you to finish this initiative?* ## Known Blockers/Dependencies *List any blockers or dependencies for this work to be completed* ## Projected Launch Date * When do you expect to be completed rolling out this initiative* ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. [VSP Product Terminology](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md) for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1.0,"Support Bot v2 - ## Problem Statement *In a couple of sentences, describe the Who, What, Why, and Where of the challenge / pain point you seek to address.* *Follow your problem description up with a ""How might we... _______"" statement re-framing that challenge as an opportunity. Don't hint too much at what the solution might be, you should have enough of a focal point here to guide your ideas, but plenty of freedom to think laterally and innovatively as you experiment and prototype later.* ## Hypothesis or Bet *How will this initiative impact the quality of VFS or VSP teams' work?* *How will this initiative be easy for VFS or VSP teams? Or how will it be easier than what they did before?* ## We will know we're done when... (""Definition of Done"") *What requirements does this project need to meet for you to finish this initiative?* ## Known Blockers/Dependencies *List any blockers or dependencies for this work to be completed* ## Projected Launch Date * When do you expect to be completed rolling out this initiative* ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. [VSP Product Terminology](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md) for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1,support bot problem statement in a couple of sentences describe the who what why and where of the challenge pain point you seek to address follow your problem description up with a how might we statement re framing that challenge as an opportunity don t hint too much at what the solution might be you should have enough of a focal point here to guide your ideas but plenty of freedom to think laterally and innovatively as you experiment and prototype later hypothesis or bet how will this initiative impact the quality of vfs or vsp teams work how will this initiative be easy for vfs or vsp teams or how will it be easier than what they did before we will know we re done when definition of done what requirements does this project need to meet for you to finish this initiative known blockers dependencies list any blockers or dependencies for this work to be completed projected launch date when do you expect to be completed rolling out this initiative launch checklist guidance delete before posting this checklist is intended to be used to help answer is my vsp initiative ready for launch all of the items in this checklist should be completed with artifacts linked or have a brief explanation of why they ve been skipped before launching a given vsp initiative all links or explanations can be provided in required artifacts sections the items that can be skipped are marked as such keep in mind the distinction between product and initiative each product needs specific supporting documentation but initiatives to improve existing products should reuse existing documentation for that product for details is this service tool feature tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a checked into note the product directory name should match with the list of vsp products external facing a exists for this product feature tool and should be located at platform product name readme md external facing a exists for this product feature tool and is updated for changes from this initiative and should be linked from the vfs facing readme for your product and should be located within platform product name unless you already have another location for it if applicable and post to about whether this should be added to the if applicable post to for external communication about this change e g vsp newsletter customer facing meetings measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying required artifacts documentation product name directory name used for your product documentation product outline link to product outline readme link to vfs facing readme for your product user guide link to user guide testing usability test link to github issue or provide reason for skipping manual qa link to github issue or documented results automated tests link to tests or n a measurement success metrics link to where success metrics are measured or where they re defined product outline is ok or provide reason for skipping release plan link to release plan ticket todos convert this issue to an epic add your team s label to this epic ,1 120139,15705711795.0,IssuesEvent,2021-03-26 16:29:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Standardized Design System Components - Buttons,analytics-insights design system gtm,"## Description * Standardize data layer events and variables to track [button components](https://design.va.gov/components/buttons) across [www.va.gov](http://www.va.gov) ## Full Code Sample ```javascript 'event': 'cta-button-click', 'button-type': 'primary', 'button-click-label': 'Make an appointment', 'button-background-color': '#0071bb', ``` ## Data Layer Specification
Event / Variable Name Description of Event/Variable Example Value
'event': 'cta-button-click' Triggered when the user clicks on the button will consistently be 'cta-button-click for all buttons
'button-type' Primary, Secondary, Default button type 'primary' //'secondary', 'default'
'button-click-label' Text of button clicked on 'Make an appointment' //dynamic according to click text label
'button-background-color' RGB color code for button '#92a8d1' //dynamic according to button button-background-color/code>
'button-is-disabled' Boolean true|false when button is clicked on in a disabled state true
'button-is-progress' Boolean true|false when button is of progress button
true
'button-is-progress-icon-position' Captures the icon progress position Default populate with undefined if button is not a progress button,

otherwise when is a progress button populate with 'before-text' or 'after-text'
'button-is-within-logical-group' Boolean true|false engineers / designers can set when logically grouping buttons for design purposes Default: Populate with undefined,
Designer will have the option to set true/false at points in futuretrue|false
'button-type-index-number' Starting with 1, index number in HTML sequence of button on page of same type (primary, secondary) as button clicked on 2
'button-type-markup-on-page' Array of button breakdown on current page, returning number of buttons of same types { ""primary-button-page-count"": 3, ""secondary-button-page-count"": 2, ""default-button-page-count""1 }
### _Stretch_ - This is a stretch to bake-in as a ""prop"" analytics data layer variables that can be used with ANY design system component - Many of these align with ""utilities"" for each component - Would like to discuss next steps with you to programmatically paramaterize these so they may be used with any component
Variable Name Description of Variable Example Value
'icon-name' Icon used with component 'warning' //friendly name to describe icon
'text-decoration' Text decoration used, css styling '.vads-u-text-decoration--underline'
'font-weight' font weight used, css styling '.vads-u-font-weight--bold'
'background-color' RGP code of background color used, css styling '#ffffff'
'breakpoint-sass-variable' When a breakpoint sass variable is used, populate the value '$xsmall-screen'
'font-style' front style used, css styling '.vads-u-font-style--italic'
'font-size' font size used, css styling '40px .vads-u-font-size--2xl'
## Acceptance Criteria - [ ] Data layer for button component as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed",1.0,"Standardized Design System Components - Buttons - ## Description * Standardize data layer events and variables to track [button components](https://design.va.gov/components/buttons) across [www.va.gov](http://www.va.gov) ## Full Code Sample ```javascript 'event': 'cta-button-click', 'button-type': 'primary', 'button-click-label': 'Make an appointment', 'button-background-color': '#0071bb', ``` ## Data Layer Specification
Event / Variable Name Description of Event/Variable Example Value
'event': 'cta-button-click' Triggered when the user clicks on the button will consistently be 'cta-button-click for all buttons
'button-type' Primary, Secondary, Default button type 'primary' //'secondary', 'default'
'button-click-label' Text of button clicked on 'Make an appointment' //dynamic according to click text label
'button-background-color' RGB color code for button '#92a8d1' //dynamic according to button button-background-color/code>
'button-is-disabled' Boolean true|false when button is clicked on in a disabled state true
'button-is-progress' Boolean true|false when button is of progress button
true
'button-is-progress-icon-position' Captures the icon progress position Default populate with undefined if button is not a progress button,

otherwise when is a progress button populate with 'before-text' or 'after-text'
'button-is-within-logical-group' Boolean true|false engineers / designers can set when logically grouping buttons for design purposes Default: Populate with undefined,
Designer will have the option to set true/false at points in futuretrue|false
'button-type-index-number' Starting with 1, index number in HTML sequence of button on page of same type (primary, secondary) as button clicked on 2
'button-type-markup-on-page' Array of button breakdown on current page, returning number of buttons of same types { ""primary-button-page-count"": 3, ""secondary-button-page-count"": 2, ""default-button-page-count""1 }
### _Stretch_ - This is a stretch to bake-in as a ""prop"" analytics data layer variables that can be used with ANY design system component - Many of these align with ""utilities"" for each component - Would like to discuss next steps with you to programmatically paramaterize these so they may be used with any component
Variable Name Description of Variable Example Value
'icon-name' Icon used with component 'warning' //friendly name to describe icon
'text-decoration' Text decoration used, css styling '.vads-u-text-decoration--underline'
'font-weight' font weight used, css styling '.vads-u-font-weight--bold'
'background-color' RGP code of background color used, css styling '#ffffff'
'breakpoint-sass-variable' When a breakpoint sass variable is used, populate the value '$xsmall-screen'
'font-style' front style used, css styling '.vads-u-font-style--italic'
'font-size' font size used, css styling '40px .vads-u-font-size--2xl'
## Acceptance Criteria - [ ] Data layer for button component as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed",1,standardized design system components buttons description standardize data layer events and variables to track across full code sample javascript event cta button click button type primary button click label make an appointment button background color data layer specification event variable name description of event variable example value event cta button click triggered when the user clicks on the button will consistently be cta button click for all buttons button type primary secondary default button type primary secondary default button click label text of button clicked on make an appointment dynamic according to click text label button background color rgb color code for button dynamic according to button button background color code button is disabled boolean true false when button is clicked on in a disabled state true button is progress boolean true false when button is of progress button true button is progress icon position captures the icon progress position default populate with undefined if button is not a progress button otherwise when is a progress button populate with before text or after text button is within logical group boolean true false engineers designers can set when logically grouping buttons for design purposes default populate with undefined designer will have the option to set true false at points in future true false button type index number starting with index number in html sequence of button on page of same type primary secondary as button clicked on button type markup on page array of button breakdown on current page returning number of buttons of same types primary button page count secondary button page count default button page count stretch this is a stretch to bake in as a prop analytics data layer variables that can be used with any design system component many of these align with utilities for each component would like to discuss next steps with you to programmatically paramaterize these so they may be used with any component variable name description of variable example value icon name icon used with component warning friendly name to describe icon text decoration text decoration used css styling vads u text decoration underline font weight font weight used css styling vads u font weight bold background color rgp code of background color used css styling ffffff breakpoint sass variable when a breakpoint sass variable is used populate the value xsmall screen font style front style used css styling vads u font style italic font size font size used css styling vads u font size acceptance criteria data layer for button component as been deployed universally qa has been completed definition of done all appropriate issue tagging is completed all ac completed,1 90375,11387396891.0,IssuesEvent,2020-01-29 14:57:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"MDT- Introduction page- Form introduction page - default state, v1",design vsa vsa-benefits-2,"## User story: As a Veteran interested in reordering medical device resupply items, I need an introduction about the ordering process so I know what to expect before placing my order. ## Tasks: - Create a high fidelity mockup of the order flow introduction page - Upload mockup to Invision and indicate initial focus point as a comment ## Acceptance criteria: - [ ] Mockup aligns with VA.gov’s design system - [ ] There is an alert notifying the Veteran that they are logged in - [ ] The subway map contains all of the steps the Veteran can expect during the order flow - [ ] (Optional) Any additional helpful content for the Veteran is included - [ ] The screen’s initial focus point is incorporated - [ ] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps -TBD ## Dependencies: No currently known dependencies ",1.0,"MDT- Introduction page- Form introduction page - default state, v1 - ## User story: As a Veteran interested in reordering medical device resupply items, I need an introduction about the ordering process so I know what to expect before placing my order. ## Tasks: - Create a high fidelity mockup of the order flow introduction page - Upload mockup to Invision and indicate initial focus point as a comment ## Acceptance criteria: - [ ] Mockup aligns with VA.gov’s design system - [ ] There is an alert notifying the Veteran that they are logged in - [ ] The subway map contains all of the steps the Veteran can expect during the order flow - [ ] (Optional) Any additional helpful content for the Veteran is included - [ ] The screen’s initial focus point is incorporated - [ ] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps -TBD ## Dependencies: No currently known dependencies ",1,mdt introduction page form introduction page default state user story as a veteran interested in reordering medical device resupply items i need an introduction about the ordering process so i know what to expect before placing my order tasks create a high fidelity mockup of the order flow introduction page upload mockup to invision and indicate initial focus point as a comment acceptance criteria mockup aligns with va gov’s design system there is an alert notifying the veteran that they are logged in the subway map contains all of the steps the veteran can expect during the order flow optional any additional helpful content for the veteran is included the screen’s initial focus point is incorporated sketch artboards are uploaded to invision and linked in this ticket as a comment next steps tbd dependencies no currently known dependencies ,1 138350,20404367536.0,IssuesEvent,2022-02-23 02:17:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Investigate date-fns tree shaking,vsp-design-system-team,"@cvalarida commented on [Tue Feb 16 2021](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/issues/256) ## Issue Description When we [introduced `date-fns` to the maintenance banner](https://github.com/department-of-veterans-affairs/vets-website/pull/16043), it apparently added the whole library to the application bundles. I investigated this for a while and put my discoveries in a [Slack thread](https://dsva.slack.com/archives/GLDNCMRSP/p1613423077097300), but I didn't ever figure out what the cause was. --- ## Tasks - [ ] Determine whether the issue is indeed that tree-shaking isn't working on the `date-fns` dependency when building application bundles - [ ] Figure out the cause - [ ] Propose or implement a solution ",1.0,"Investigate date-fns tree shaking - @cvalarida commented on [Tue Feb 16 2021](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/issues/256) ## Issue Description When we [introduced `date-fns` to the maintenance banner](https://github.com/department-of-veterans-affairs/vets-website/pull/16043), it apparently added the whole library to the application bundles. I investigated this for a while and put my discoveries in a [Slack thread](https://dsva.slack.com/archives/GLDNCMRSP/p1613423077097300), but I didn't ever figure out what the cause was. --- ## Tasks - [ ] Determine whether the issue is indeed that tree-shaking isn't working on the `date-fns` dependency when building application bundles - [ ] Figure out the cause - [ ] Propose or implement a solution ",1,investigate date fns tree shaking cvalarida commented on issue description when we it apparently added the whole library to the application bundles i investigated this for a while and put my discoveries in a but i didn t ever figure out what the cause was tasks determine whether the issue is indeed that tree shaking isn t working on the date fns dependency when building application bundles figure out the cause propose or implement a solution ,1 87744,10963844916.0,IssuesEvent,2019-11-27 20:46:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] HLR: Incorporate Design Feedback for Review Submission ,HLR design vsa-benefits vsa-decision-reviews,"## User Story: As a designer on the Benefits and Memorials team, I need to update the Review Submission design so that I can ensure it follows the recommendation of the design team's review. ## Tasks - [ ] Update the Review Submissions page with design feedback from Emily ## Acceptance Criteria: - [ ] Design team's feedback has been incorporated into the Review Submission page",1.0,"[Design] HLR: Incorporate Design Feedback for Review Submission - ## User Story: As a designer on the Benefits and Memorials team, I need to update the Review Submission design so that I can ensure it follows the recommendation of the design team's review. ## Tasks - [ ] Update the Review Submissions page with design feedback from Emily ## Acceptance Criteria: - [ ] Design team's feedback has been incorporated into the Review Submission page",1, hlr incorporate design feedback for review submission user story as a designer on the benefits and memorials team i need to update the review submission design so that i can ensure it follows the recommendation of the design team s review tasks update the review submissions page with design feedback from emily acceptance criteria design team s feedback has been incorporated into the review submission page,1 127853,17372813910.0,IssuesEvent,2021-07-30 16:10:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[UI] Check-in Posters Available on GitHUB,HCE-Checkin design vsa-healthcare-exp,"# Description As a member of the check-in team, I want easy access to the latest Check-in posters (so I can send them to sites, etc.). # Tasks - [x] Create GitHUB page for poster files. - [x] Add PDFs to the page. - [x] Create a .zip file for others with all the source files, then upload it to GitHUB. ## Acceptance Criteria - [x] Message the team to let them know the GitHUB page is finished.",1.0,"[UI] Check-in Posters Available on GitHUB - # Description As a member of the check-in team, I want easy access to the latest Check-in posters (so I can send them to sites, etc.). # Tasks - [x] Create GitHUB page for poster files. - [x] Add PDFs to the page. - [x] Create a .zip file for others with all the source files, then upload it to GitHUB. ## Acceptance Criteria - [x] Message the team to let them know the GitHUB page is finished.",1, check in posters available on github description as a member of the check in team i want easy access to the latest check in posters so i can send them to sites etc tasks create github page for poster files add pdfs to the page create a zip file for others with all the source files then upload it to github acceptance criteria message the team to let them know the github page is finished ,1 140006,20996231652.0,IssuesEvent,2022-03-29 13:43:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Direct User how to Update their VA Profile,design ux HCE-Checkin,"## How to configure this issue - [ ] Attached to an Epic (what body of work is this a part of?) - [ ] Labeled with HCE-Checkin, ux, design - [ ] Prepend [Design] to the beginning of the ticket title - [ ] Fill in User Story - [ ] Fill in Description - [ ] Fill in Tasks - [ ] Fill in Acceptance Criteria --- ## User Story As a Veteran, when I am completing my pre-check-in workflow, if I have some updates to my demographics, emergency contact, and/or next of kin, I would like to understand how and where I can make those changes so that I will know what the next step is. ## Description We need wireframes that will: - Tell the user what to do and where to go to update their demographics information - Tell the user what to do and where to go to update their EC and NOK information ## Workflow - Given I - Am a Veteran who has received a link to complete pre-check-in for an appointment - When I - Complete the pre-check-in process - Have answered ""No"" to one or more of these questions - ""Is this your current contact information?"" - ""Is this your current emergency contact?"" - ""Is this your current next of kin?"" - Then I - See messaging that indicates how to update my information based on to which of the 3 questions I answered ""no"" - For contact info - See messaging that tells me I will need to update my info in my VA profile or with a staff member on the day of my appointment - See a link to my VA profile - For EC info - See messaging that tells me I will need to update the information with a staff member on the day of my appointment - For NOK info - See messaging that tells me I will need to update the information with a staff member on the day of my appointment ## Tasks - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1.0,"[Design] Direct User how to Update their VA Profile - ## How to configure this issue - [ ] Attached to an Epic (what body of work is this a part of?) - [ ] Labeled with HCE-Checkin, ux, design - [ ] Prepend [Design] to the beginning of the ticket title - [ ] Fill in User Story - [ ] Fill in Description - [ ] Fill in Tasks - [ ] Fill in Acceptance Criteria --- ## User Story As a Veteran, when I am completing my pre-check-in workflow, if I have some updates to my demographics, emergency contact, and/or next of kin, I would like to understand how and where I can make those changes so that I will know what the next step is. ## Description We need wireframes that will: - Tell the user what to do and where to go to update their demographics information - Tell the user what to do and where to go to update their EC and NOK information ## Workflow - Given I - Am a Veteran who has received a link to complete pre-check-in for an appointment - When I - Complete the pre-check-in process - Have answered ""No"" to one or more of these questions - ""Is this your current contact information?"" - ""Is this your current emergency contact?"" - ""Is this your current next of kin?"" - Then I - See messaging that indicates how to update my information based on to which of the 3 questions I answered ""no"" - For contact info - See messaging that tells me I will need to update my info in my VA profile or with a staff member on the day of my appointment - See a link to my VA profile - For EC info - See messaging that tells me I will need to update the information with a staff member on the day of my appointment - For NOK info - See messaging that tells me I will need to update the information with a staff member on the day of my appointment ## Tasks - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1, direct user how to update their va profile how to configure this issue attached to an epic what body of work is this a part of labeled with hce checkin ux design prepend to the beginning of the ticket title fill in user story fill in description fill in tasks fill in acceptance criteria user story as a veteran when i am completing my pre check in workflow if i have some updates to my demographics emergency contact and or next of kin i would like to understand how and where i can make those changes so that i will know what the next step is description we need wireframes that will tell the user what to do and where to go to update their demographics information tell the user what to do and where to go to update their ec and nok information workflow given i am a veteran who has received a link to complete pre check in for an appointment when i complete the pre check in process have answered no to one or more of these questions is this your current contact information is this your current emergency contact is this your current next of kin then i see messaging that indicates how to update my information based on to which of the questions i answered no for contact info see messaging that tells me i will need to update my info in my va profile or with a staff member on the day of my appointment see a link to my va profile for ec info see messaging that tells me i will need to update the information with a staff member on the day of my appointment for nok info see messaging that tells me i will need to update the information with a staff member on the day of my appointment tasks finalize detailed mockup and callouts of link to prototype decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation ,1 120428,15765412966.0,IssuesEvent,2021-03-31 14:07:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Standardized Design System Components - Additional Info,analytics-insights design system gtm,"## Description * Standardize data layer events and variables to track [additional info component](https://design.va.gov/components/additional-info) across [www.va.gov](http://www.va.gov) ## Data Layer Specification - Click to Expand/Collapse ```javascript 'event': 'int-additional-info-expand', //OR 'int-additional-info-collapse', 'additional-info-click-label': triggerText ``` ## Acceptance Criteria - [ ] Data layer for additional info component as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1.0,"Standardized Design System Components - Additional Info - ## Description * Standardize data layer events and variables to track [additional info component](https://design.va.gov/components/additional-info) across [www.va.gov](http://www.va.gov) ## Data Layer Specification - Click to Expand/Collapse ```javascript 'event': 'int-additional-info-expand', //OR 'int-additional-info-collapse', 'additional-info-click-label': triggerText ``` ## Acceptance Criteria - [ ] Data layer for additional info component as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1,standardized design system components additional info description standardize data layer events and variables to track across data layer specification click to expand collapse javascript event int additional info expand or int additional info collapse additional info click label triggertext acceptance criteria data layer for additional info component as been deployed universally qa has been completed definition of done all appropriate issue tagging is completed all ac completed ,1 116462,14966184982.0,IssuesEvent,2021-01-27 14:18:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] MyVA 2.0 Research plan for usability of finalized designs,design my-va-dashboard needs-grooming vsa-authenticated-exp,"## Background Now that we have finalized design for MyVA, we need to create a research plan and convo guide in preparation for usability testing. ## Tasks - [ ] Create research plan - [ ] Review with Matt/Samara",1.0,"[Design] MyVA 2.0 Research plan for usability of finalized designs - ## Background Now that we have finalized design for MyVA, we need to create a research plan and convo guide in preparation for usability testing. ## Tasks - [ ] Create research plan - [ ] Review with Matt/Samara",1, myva research plan for usability of finalized designs background now that we have finalized design for myva we need to create a research plan and convo guide in preparation for usability testing tasks create research plan review with matt samara,1 103689,12962781790.0,IssuesEvent,2020-07-20 17:42:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Account for varying times for Express Care offered by a facility,design frontend needs-grooming vaos,"Need to account for VATS configuration being different every day for a given facility. Right now our current prompt on the homepage assumes facilities are offering a consistent time window each day. ",1.0,"Account for varying times for Express Care offered by a facility - Need to account for VATS configuration being different every day for a given facility. Right now our current prompt on the homepage assumes facilities are offering a consistent time window each day. ",1,account for varying times for express care offered by a facility need to account for vats configuration being different every day for a given facility right now our current prompt on the homepage assumes facilities are offering a consistent time window each day ,1 138239,20377374001.0,IssuesEvent,2022-02-21 16:57:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Add component migration functionality for va-breadcrumbs,vsp-design-system-team,"## Issue Description Create an ESLint rule for the new `va-breadcrumbs` web component. `` -> `` For an example ESLint rule, see https://github.com/department-of-veterans-affairs/vets-website/pull/20002 --- ## Tasks - [ ] Add ESLint rule ",1.0,"Add component migration functionality for va-breadcrumbs - ## Issue Description Create an ESLint rule for the new `va-breadcrumbs` web component. `` -> `` For an example ESLint rule, see https://github.com/department-of-veterans-affairs/vets-website/pull/20002 --- ## Tasks - [ ] Add ESLint rule ",1,add component migration functionality for va breadcrumbs issue description create an eslint rule for the new va breadcrumbs web component for an example eslint rule see tasks add eslint rule ,1 166675,26393839591.0,IssuesEvent,2023-01-12 17:36:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.1),content design 508/Accessibility ia collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard my-education-benefits education-letters,"### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name VA Education Letters #### VFS feature name #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details On the ""Please sign in to check your VA education letter."" alert there is a blue button being used with the green lock alert. ### Link, screenshot or steps to recreate https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/50481-Allison-4701.png ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation The latest guidlelines have been updated and the green button with the green alert for sign in is the current style. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.1) - ### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name VA Education Letters #### VFS feature name #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details On the ""Please sign in to check your VA education letter."" alert there is a blue button being used with the green lock alert. ### Link, screenshot or steps to recreate https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/50481-Allison-4701.png ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation The latest guidlelines have been updated and the green button with the green alert for sign in is the current style. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, design components or patterns don t align with design system guidelines general information vfs team name dgib my education benefits vfs product name va education letters vfs feature name point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details on the please sign in to check your va education letter alert there is a blue button being used with the green lock alert link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation the latest guidlelines have been updated and the green button with the green alert for sign in is the current style vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 118496,15302452837.0,IssuesEvent,2021-02-24 14:45:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] DD4edu - Kick off UAT recruiting,EDU DD design direct deposit needs-grooming vsa-authenticated-exp,"## Background We need to kick off the recruiting process for DD4edu UAT. ## Tasks - [ ] Confirm recruiting has been kicked off",1.0,"[Design] DD4edu - Kick off UAT recruiting - ## Background We need to kick off the recruiting process for DD4edu UAT. ## Tasks - [ ] Confirm recruiting has been kicked off",1, kick off uat recruiting background we need to kick off the recruiting process for uat tasks confirm recruiting has been kicked off,1 181695,30726876621.0,IssuesEvent,2023-07-27 20:27:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Design System Staging Review - Accessibility Feedback - Converted components: Text input, Text area, Number input",accessibility collaboration-cycle platform-design-system-team collab-cycle-feedback DS-Staging-Review,"## VFS actions - [ ] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform. - [ ] Comment on this ticket: - [ ] If the Platform reviewer has any **Thoughts/Questions** that require responses. - [ ] When **Must** feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback. - [ ] When **Should/Consider** feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback. - [ ] Close the ticket when all feedback has been addressed. ## Thoughts/questions - On the [number input component](https://design.va.gov/storybook/?path=/docs/uswds-va-number-input--default), the `currency` prop doesn't seem to do anything. Is there any intended behavior there? Possibly a Storybook issue? ## Feedback Practice areas will document their feedback on the VFS-provided artifacts following the [Must, Should, and Consider Framework](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/must-should-and-consider-framework-for-feedback). Platform reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes). - **Must:** On all three components, the `hint` text isn't programmatically associated with the input. That means it won't be announced by screen readers when tabbing into the input, so a screen reader user may miss out on important context or instructions. Recommendation here would be to associate the `hint` using `aria-describedby`. - **Must:** On the text input component, the character min/max length text isn't programmatically associated with the input. It sounds like this might be in flux with changes coming to better match USWDS. Either way, similar behavior as the `hint` text. - **Consider:** On the number input component, there's no visible text (or text announced by screen reader) to reflect the min/max values. Not sure if it's desirable from a design standpoint, but it seems like a similar use case as the character min/max length on the text input. - **Should:** From the meeting, I think I better understand the intention behind `message-aria-describedby` on the text input. I think it makes sense to make that property available on all three of these components.",1.0,"Design System Staging Review - Accessibility Feedback - Converted components: Text input, Text area, Number input - ## VFS actions - [ ] Assign this ticket to the team member(s) responsible for addressing feedback provided by Platform. - [ ] Comment on this ticket: - [ ] If the Platform reviewer has any **Thoughts/Questions** that require responses. - [ ] When **Must** feedback has been incorporated. As appropriate, link to any other GitHub issues or PRs related to this feedback. - [ ] When **Should/Consider** feedback has been incorporated, or if any feedback will not be addressed. As appropriate, link to any other GitHub issues or PRs related to this feedback. - [ ] Close the ticket when all feedback has been addressed. ## Thoughts/questions - On the [number input component](https://design.va.gov/storybook/?path=/docs/uswds-va-number-input--default), the `currency` prop doesn't seem to do anything. Is there any intended behavior there? Possibly a Storybook issue? ## Feedback Practice areas will document their feedback on the VFS-provided artifacts following the [Must, Should, and Consider Framework](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/must-should-and-consider-framework-for-feedback). Platform reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation (eg. engineering/coding notes). - **Must:** On all three components, the `hint` text isn't programmatically associated with the input. That means it won't be announced by screen readers when tabbing into the input, so a screen reader user may miss out on important context or instructions. Recommendation here would be to associate the `hint` using `aria-describedby`. - **Must:** On the text input component, the character min/max length text isn't programmatically associated with the input. It sounds like this might be in flux with changes coming to better match USWDS. Either way, similar behavior as the `hint` text. - **Consider:** On the number input component, there's no visible text (or text announced by screen reader) to reflect the min/max values. Not sure if it's desirable from a design standpoint, but it seems like a similar use case as the character min/max length on the text input. - **Should:** From the meeting, I think I better understand the intention behind `message-aria-describedby` on the text input. I think it makes sense to make that property available on all three of these components.",1,design system staging review accessibility feedback converted components text input text area number input vfs actions assign this ticket to the team member s responsible for addressing feedback provided by platform comment on this ticket if the platform reviewer has any thoughts questions that require responses when must feedback has been incorporated as appropriate link to any other github issues or prs related to this feedback when should consider feedback has been incorporated or if any feedback will not be addressed as appropriate link to any other github issues or prs related to this feedback close the ticket when all feedback has been addressed thoughts questions on the the currency prop doesn t seem to do anything is there any intended behavior there possibly a storybook issue feedback practice areas will document their feedback on the vfs provided artifacts following the platform reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation eg engineering coding notes must on all three components the hint text isn t programmatically associated with the input that means it won t be announced by screen readers when tabbing into the input so a screen reader user may miss out on important context or instructions recommendation here would be to associate the hint using aria describedby must on the text input component the character min max length text isn t programmatically associated with the input it sounds like this might be in flux with changes coming to better match uswds either way similar behavior as the hint text consider on the number input component there s no visible text or text announced by screen reader to reflect the min max values not sure if it s desirable from a design standpoint but it seems like a similar use case as the character min max length on the text input should from the meeting i think i better understand the intention behind message aria describedby on the text input i think it makes sense to make that property available on all three of these components ,1 144363,22336356842.0,IssuesEvent,2022-06-14 18:53:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Building Web Components [Q3 2022],Epic platform-initiative vsp-design-system-team,"## Problem Statement In order to have a consistent user experience, individual components in applications and content should be identical across the user experience. For example, the user interface of a simple form should not appear or behave differently in different parts of VA.gov. However we currently do not maintain a library of components that is technically agnostic, so teams building in each of the three technical approaches draw from different shared/reusable code bases. The Forms Library Team is beginning work on building out their proposed vision for a new forms library and will need to use Design System components as part of their work. We would like to provide them with web component versions of the Design System form control components as well as several other components that would be useful for them. How might we create a technically agnostic approach to our design system and the components and patterns within it that will allow a team to build a new React app, new content, or hybrids without recreating components from a specific technical stack or creating more code that is unique to a single component. ## Hypothesis or Bet - VFS teams will be able to build more consistent applications across different technical environments - VSP will be able to maintain a single source of truth for multiple technical environments ## We will know we're done when... (""Definition of Done"") We have created 4 new web components - File Upload - Link - OMB Info - Privacy Agreement ## Known Blockers/Dependencies n/a ## Projected Launch Date By end of Q3 2022 ## Required Artifacts ### Documentation PRODUCT_NAME: Web Components Product Outline: Design System Product Outline https://vfs.atlassian.net/wiki/spaces/DST/pages/2133557283 ### Measurement * **Success metrics**: Success metrics: Increased use of web components version and decrease in React components ",1.0,"Building Web Components [Q3 2022] - ## Problem Statement In order to have a consistent user experience, individual components in applications and content should be identical across the user experience. For example, the user interface of a simple form should not appear or behave differently in different parts of VA.gov. However we currently do not maintain a library of components that is technically agnostic, so teams building in each of the three technical approaches draw from different shared/reusable code bases. The Forms Library Team is beginning work on building out their proposed vision for a new forms library and will need to use Design System components as part of their work. We would like to provide them with web component versions of the Design System form control components as well as several other components that would be useful for them. How might we create a technically agnostic approach to our design system and the components and patterns within it that will allow a team to build a new React app, new content, or hybrids without recreating components from a specific technical stack or creating more code that is unique to a single component. ## Hypothesis or Bet - VFS teams will be able to build more consistent applications across different technical environments - VSP will be able to maintain a single source of truth for multiple technical environments ## We will know we're done when... (""Definition of Done"") We have created 4 new web components - File Upload - Link - OMB Info - Privacy Agreement ## Known Blockers/Dependencies n/a ## Projected Launch Date By end of Q3 2022 ## Required Artifacts ### Documentation PRODUCT_NAME: Web Components Product Outline: Design System Product Outline https://vfs.atlassian.net/wiki/spaces/DST/pages/2133557283 ### Measurement * **Success metrics**: Success metrics: Increased use of web components version and decrease in React components ",1,building web components problem statement in order to have a consistent user experience individual components in applications and content should be identical across the user experience for example the user interface of a simple form should not appear or behave differently in different parts of va gov however we currently do not maintain a library of components that is technically agnostic so teams building in each of the three technical approaches draw from different shared reusable code bases the forms library team is beginning work on building out their proposed vision for a new forms library and will need to use design system components as part of their work we would like to provide them with web component versions of the design system form control components as well as several other components that would be useful for them how might we create a technically agnostic approach to our design system and the components and patterns within it that will allow a team to build a new react app new content or hybrids without recreating components from a specific technical stack or creating more code that is unique to a single component hypothesis or bet vfs teams will be able to build more consistent applications across different technical environments vsp will be able to maintain a single source of truth for multiple technical environments we will know we re done when definition of done we have created new web components file upload link omb info privacy agreement known blockers dependencies n a projected launch date by end of required artifacts documentation product name web components product outline design system product outline measurement success metrics success metrics increased use of web components version and decrease in react components ,1 146564,23087815226.0,IssuesEvent,2022-07-26 12:58:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Where should the updated playbook live?,service-design,"## Issue Description Where should the updated playbook live? (who needs it and where makes the most sense) ## Problem Statement We need to make sure we understand and agree who the primary or secondary users of the CCP will be so as to place it in a place that is logically accessed and accessible. ## Tasks - [x] Determine who potential consumers are - [x] Determine where the playbook should reside ## Acceptance Criteria - [x] Location is determined ## Next Steps In order to keep the Change Playbook and Principles, we intend to place them in separate locations, based on likelihood of engagement: 1) Change Communication Playbook: Prod. Mgmt. Comm. of Practice / (existing Playbook landing) 2) Platform Communication Principles: About the Platform / How we work /",1.0,"Where should the updated playbook live? - ## Issue Description Where should the updated playbook live? (who needs it and where makes the most sense) ## Problem Statement We need to make sure we understand and agree who the primary or secondary users of the CCP will be so as to place it in a place that is logically accessed and accessible. ## Tasks - [x] Determine who potential consumers are - [x] Determine where the playbook should reside ## Acceptance Criteria - [x] Location is determined ## Next Steps In order to keep the Change Playbook and Principles, we intend to place them in separate locations, based on likelihood of engagement: 1) Change Communication Playbook: Prod. Mgmt. Comm. of Practice / (existing Playbook landing) 2) Platform Communication Principles: About the Platform / How we work /",1,where should the updated playbook live issue description where should the updated playbook live who needs it and where makes the most sense problem statement we need to make sure we understand and agree who the primary or secondary users of the ccp will be so as to place it in a place that is logically accessed and accessible tasks determine who potential consumers are determine where the playbook should reside acceptance criteria location is determined next steps in order to keep the change playbook and principles we intend to place them in separate locations based on likelihood of engagement change communication playbook prod mgmt comm of practice existing playbook landing platform communication principles about the platform how we work ,1 100690,12546589697.0,IssuesEvent,2020-06-05 21:00:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Consider moving content links down, to match the YR search results page",design frontend vsa-public-websites,"Consider moving the static content links on the YR tool search page, so they appear below the search button, just like they do on the results page as ""Helpful links"" below the button. (I.e., make them consistent) On this page: https://www.va.gov/education/yellow-ribbon-participating-schools Move content page links so it's the same as what we show on the results page: https://www.va.gov/education/yellow-ribbon-participating-schools/? ![image.png](https://images.zenhubusercontent.com/5bb2975c143b4d2ee7a35ef6/ee408650-1f76-4aef-a79b-1b3c8e41f8bd)",1.0,"Consider moving content links down, to match the YR search results page - Consider moving the static content links on the YR tool search page, so they appear below the search button, just like they do on the results page as ""Helpful links"" below the button. (I.e., make them consistent) On this page: https://www.va.gov/education/yellow-ribbon-participating-schools Move content page links so it's the same as what we show on the results page: https://www.va.gov/education/yellow-ribbon-participating-schools/? ![image.png](https://images.zenhubusercontent.com/5bb2975c143b4d2ee7a35ef6/ee408650-1f76-4aef-a79b-1b3c8e41f8bd)",1,consider moving content links down to match the yr search results page consider moving the static content links on the yr tool search page so they appear below the search button just like they do on the results page as helpful links below the button i e make them consistent on this page move content page links so it s the same as what we show on the results page ,1 184588,32010752383.0,IssuesEvent,2023-09-21 17:49:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Copy of Conduct DI interviews w/ VFS teams,service-design,"## Purpose What would improve the experience of VFS teams going through DI? Let's ask them ## Tasks - [ ] Conduct interview sessions - [ ] debrief after interview ## Acceptance Criteria - [ ] interviews complete ",1.0,"Copy of Conduct DI interviews w/ VFS teams - ## Purpose What would improve the experience of VFS teams going through DI? Let's ask them ## Tasks - [ ] Conduct interview sessions - [ ] debrief after interview ## Acceptance Criteria - [ ] interviews complete ",1,copy of conduct di interviews w vfs teams purpose what would improve the experience of vfs teams going through di let s ask them tasks conduct interview sessions debrief after interview acceptance criteria interviews complete ,1 171064,27056114369.0,IssuesEvent,2023-02-13 16:16:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Acquire existing Mappings and Workflows from current project teams, and current fixed teams",service-design,"## Purpose Aggregate mappings for future organization. Question: should we make it part of the Platform Initiative to pass along any visual mappings/workflows to the SDT upon a project's completion? ## Tasks Contact Project teams for any existing mappings of processes/services or workflows: - [x] Tech Team 1 - [x] Tech Team 2 - [x] Tech Team 3 - [x] Tech Team 4 Contact Fixed teams for any existing mappings of processes/services or workflows - [x] Platform Content - [x] Design Systems - [x] Governance ## Acceptance Criteria - [x] Asks and correspondence completed",1.0,"Acquire existing Mappings and Workflows from current project teams, and current fixed teams - ## Purpose Aggregate mappings for future organization. Question: should we make it part of the Platform Initiative to pass along any visual mappings/workflows to the SDT upon a project's completion? ## Tasks Contact Project teams for any existing mappings of processes/services or workflows: - [x] Tech Team 1 - [x] Tech Team 2 - [x] Tech Team 3 - [x] Tech Team 4 Contact Fixed teams for any existing mappings of processes/services or workflows - [x] Platform Content - [x] Design Systems - [x] Governance ## Acceptance Criteria - [x] Asks and correspondence completed",1,acquire existing mappings and workflows from current project teams and current fixed teams purpose aggregate mappings for future organization question should we make it part of the platform initiative to pass along any visual mappings workflows to the sdt upon a project s completion tasks contact project teams for any existing mappings of processes services or workflows tech team tech team tech team tech team contact fixed teams for any existing mappings of processes services or workflows platform content design systems governance acceptance criteria asks and correspondence completed,1 124875,16673665263.0,IssuesEvent,2021-06-07 13:54:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[MCP] Veteran low fidelity usability conversation guide,MCP design research vsa vsa-benefits-2,"## Issue Description As part of our research for the Medical Copayment enhancement to Debt Portal, we want to test low fidelity design concepts with veterans. We must create a conversation guide for approval and scheduling. --- ## Tasks - [x] Create a conversation guide, upload it to GH - [x] Create usability workspace - [x] Send conversation guide to Lauryl for review / approval - [x] Send plan to Lauren for review ## Acceptance Criteria - [x] Conversation guide completed and linked below - [x] Workspace linked below - [x] Convo guide sent to Lauryl for feedback - [x] Convo guide sent to Lauren for scheduling ",1.0,"[MCP] Veteran low fidelity usability conversation guide - ## Issue Description As part of our research for the Medical Copayment enhancement to Debt Portal, we want to test low fidelity design concepts with veterans. We must create a conversation guide for approval and scheduling. --- ## Tasks - [x] Create a conversation guide, upload it to GH - [x] Create usability workspace - [x] Send conversation guide to Lauryl for review / approval - [x] Send plan to Lauren for review ## Acceptance Criteria - [x] Conversation guide completed and linked below - [x] Workspace linked below - [x] Convo guide sent to Lauryl for feedback - [x] Convo guide sent to Lauren for scheduling ",1, veteran low fidelity usability conversation guide issue description as part of our research for the medical copayment enhancement to debt portal we want to test low fidelity design concepts with veterans we must create a conversation guide for approval and scheduling tasks create a conversation guide upload it to gh create usability workspace send conversation guide to lauryl for review approval send plan to lauren for review acceptance criteria conversation guide completed and linked below workspace linked below convo guide sent to lauryl for feedback convo guide sent to lauren for scheduling ,1 91426,11501329909.0,IssuesEvent,2020-02-12 16:58:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] HLR: Update Higher Level Review Design Artifacts Based on AMO Comments,HLR design discovery vsa vsa-benefits,"## User Story or Problem Statement As a veteran, I need a submit requests for higher level review in an easy to navigate and understand fashion so that I can successfully get my benefits. We've done the redesign at this point but we will likely have some more comments flowing in from AMO. This is the follow-up ticket to #5259. ## Goal Final design blessed by AMO. ##Tasks - [ ] Meet with AMO and get feedback into the design ## Acceptance Criteria - [ ] InVision design is done and blessed by AMO. ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] HLR: Update Higher Level Review Design Artifacts Based on AMO Comments - ## User Story or Problem Statement As a veteran, I need a submit requests for higher level review in an easy to navigate and understand fashion so that I can successfully get my benefits. We've done the redesign at this point but we will likely have some more comments flowing in from AMO. This is the follow-up ticket to #5259. ## Goal Final design blessed by AMO. ##Tasks - [ ] Meet with AMO and get feedback into the design ## Acceptance Criteria - [ ] InVision design is done and blessed by AMO. ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, hlr update higher level review design artifacts based on amo comments user story or problem statement as a veteran i need a submit requests for higher level review in an easy to navigate and understand fashion so that i can successfully get my benefits we ve done the redesign at this point but we will likely have some more comments flowing in from amo this is the follow up ticket to goal final design blessed by amo tasks meet with amo and get feedback into the design acceptance criteria invision design is done and blessed by amo how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 150161,23614645199.0,IssuesEvent,2022-08-24 14:56:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Create Final Wireframes,design ux HCE-Checkin,"## User Story As a [role], I want to [what] so that I can [do something]. ## User Workflows - Given I - When I - Then I ## Tasks - [ ] Create final mockups with callouts - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1.0,"[Design] Create Final Wireframes - ## User Story As a [role], I want to [what] so that I can [do something]. ## User Workflows - Given I - When I - Then I ## Tasks - [ ] Create final mockups with callouts - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1, create final wireframes user story as a i want to so that i can user workflows given i when i then i tasks create final mockups with callouts decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation ,1 132794,18763858062.0,IssuesEvent,2021-11-05 20:07:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] - Profile: Create updated Sketch file for Direct Deposit,design vsa-authenticated-exp profile direct deposit,"## Background Our Profile 2.0 Sketch file is become unwieldy and out of date, so we need to split it out so that it's more maintainable. This ticket covers the work needed to create a Sketch file that contains all the states of the direct deposit section of profile. ## Known updates - [ ] Replace global profile elements (header with nametag, side navigation, section headings) with the symbols from the Profile pattern library - [ ] Replace footers with the symbols from the VA.gov pattern library - [ ] Make sure any buttons that look like links are replaced with the secondary button symbol from the VA.gov pattern library - [ ] Align margins/padding of containers with what is on staging - [ ] Alerts should be updated to reflect changes in [this document ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/maintenance/front-end/alert-updates-Sept-2021.md#3-successfully-updated-direct-deposit-information-in-profile-31404)(don't hesitate to ask Liz, this is complicated) - [ ] Additional info components should match what is on [design.va.gov documentation](https://design.va.gov/components/additional-info) (gray chevron w/ dotted line underneath) ## Updates you'll probably need to make but I'm not totally sure about: In March 2021, education benefits were added to direct deposit and I'm not sure if the Sketch file was updated. @sporeboy (Jim Adams) worked on those updates, and he typically works in XD. You can chat with him about that, or log into staging and manually compare what you see in Sketch to what's out there. [Staging user log information](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-direct-deposit.md) I would recommend logging into staging regardless to check for differences in copy, how headings display etc (especially on mobile). ## Acceptance criteria - [ ] Direct deposit sketch file appropriately matches what we have on staging. ",1.0,"[Design] - Profile: Create updated Sketch file for Direct Deposit - ## Background Our Profile 2.0 Sketch file is become unwieldy and out of date, so we need to split it out so that it's more maintainable. This ticket covers the work needed to create a Sketch file that contains all the states of the direct deposit section of profile. ## Known updates - [ ] Replace global profile elements (header with nametag, side navigation, section headings) with the symbols from the Profile pattern library - [ ] Replace footers with the symbols from the VA.gov pattern library - [ ] Make sure any buttons that look like links are replaced with the secondary button symbol from the VA.gov pattern library - [ ] Align margins/padding of containers with what is on staging - [ ] Alerts should be updated to reflect changes in [this document ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/maintenance/front-end/alert-updates-Sept-2021.md#3-successfully-updated-direct-deposit-information-in-profile-31404)(don't hesitate to ask Liz, this is complicated) - [ ] Additional info components should match what is on [design.va.gov documentation](https://design.va.gov/components/additional-info) (gray chevron w/ dotted line underneath) ## Updates you'll probably need to make but I'm not totally sure about: In March 2021, education benefits were added to direct deposit and I'm not sure if the Sketch file was updated. @sporeboy (Jim Adams) worked on those updates, and he typically works in XD. You can chat with him about that, or log into staging and manually compare what you see in Sketch to what's out there. [Staging user log information](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-direct-deposit.md) I would recommend logging into staging regardless to check for differences in copy, how headings display etc (especially on mobile). ## Acceptance criteria - [ ] Direct deposit sketch file appropriately matches what we have on staging. ",1, profile create updated sketch file for direct deposit background our profile sketch file is become unwieldy and out of date so we need to split it out so that it s more maintainable this ticket covers the work needed to create a sketch file that contains all the states of the direct deposit section of profile known updates replace global profile elements header with nametag side navigation section headings with the symbols from the profile pattern library replace footers with the symbols from the va gov pattern library make sure any buttons that look like links are replaced with the secondary button symbol from the va gov pattern library align margins padding of containers with what is on staging alerts should be updated to reflect changes in hesitate to ask liz this is complicated additional info components should match what is on gray chevron w dotted line underneath updates you ll probably need to make but i m not totally sure about in march education benefits were added to direct deposit and i m not sure if the sketch file was updated sporeboy jim adams worked on those updates and he typically works in xd you can chat with him about that or log into staging and manually compare what you see in sketch to what s out there i would recommend logging into staging regardless to check for differences in copy how headings display etc especially on mobile acceptance criteria direct deposit sketch file appropriately matches what we have on staging ,1 127723,17357413042.0,IssuesEvent,2021-07-29 15:53:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Forms Library: Create a Date Picker ,vsp-design-system-team,"Forms Library: Create a Date Picker for the new forms library. Chris/Brooks - please add details for the work to create a date picker. ",1.0,"Forms Library: Create a Date Picker - Forms Library: Create a Date Picker for the new forms library. Chris/Brooks - please add details for the work to create a date picker. ",1,forms library create a date picker forms library create a date picker for the new forms library chris brooks please add details for the work to create a date picker ,1 144913,22585619168.0,IssuesEvent,2022-06-28 15:00:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Break Plays into discrete tasks,service-design,"## Issue Description Create an easy, step-by-step guide --- ## Tasks - [ ] layout steps ## Acceptance Criteria - [ ] guide is created",1.0,"Break Plays into discrete tasks - ## Issue Description Create an easy, step-by-step guide --- ## Tasks - [ ] layout steps ## Acceptance Criteria - [ ] guide is created",1,break plays into discrete tasks issue description create an easy step by step guide tasks layout steps acceptance criteria guide is created,1 146235,23034597547.0,IssuesEvent,2022-07-22 17:13:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Conduct VFS poll,service-design,"## Issue Description Get feedback from VFS - how do they receive or expect to receive information? (also an introduction of sorts to working w/ team) ## User Story As a SDT member, I want to know how VFS users prefer to get their communications, currently or possibly, so that we can determine how to recommend or create communication channels. ## Tasks - [x] Launch poll in predetermined channels - [x] Gather feedback via poll ## Acceptance Criteria - [x] List of preferred comm channels",1.0,"Conduct VFS poll - ## Issue Description Get feedback from VFS - how do they receive or expect to receive information? (also an introduction of sorts to working w/ team) ## User Story As a SDT member, I want to know how VFS users prefer to get their communications, currently or possibly, so that we can determine how to recommend or create communication channels. ## Tasks - [x] Launch poll in predetermined channels - [x] Gather feedback via poll ## Acceptance Criteria - [x] List of preferred comm channels",1,conduct vfs poll issue description get feedback from vfs how do they receive or expect to receive information also an introduction of sorts to working w team user story as a sdt member i want to know how vfs users prefer to get their communications currently or possibly so that we can determine how to recommend or create communication channels tasks launch poll in predetermined channels gather feedback via poll acceptance criteria list of preferred comm channels,1 183881,31779123266.0,IssuesEvent,2023-09-12 16:09:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Synthesis of VFS team research,service-design,"## Purpose Upon completion of all VFS team interviews Possible approach: [mini blueprint template](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1608229028620/f6a4a5864fa1eed7af90a1a71a6e454558d7a048?sender=u9ea6bd3ca12795949b606150) ## Tasks - [x] Schedule [mini-blueprint](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1692915056654/3e98d76a662e97592fcf6ab5f1a116b1d53173e1?sender=u9ea6bd3ca12795949b606150) workshop to test viability (8/25/23) - [x] Prepare a [synthesis mural](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1693258366432/73ef92d0f7b2c786e0fdc3ddbbe022a475bc5307?sender=u9ea6bd3ca12795949b606150) - [x] Schedule team workshop (9/1/23) - [x] Synthesize findings, formulate hypothesis, determine merging patterns ## Acceptance Criteria - [x] Initial Workshop is conducted - [x] Internal team workshop is conducted - [x] Findings from workshops 3-6 are synthesized ",1.0,"Synthesis of VFS team research - ## Purpose Upon completion of all VFS team interviews Possible approach: [mini blueprint template](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1608229028620/f6a4a5864fa1eed7af90a1a71a6e454558d7a048?sender=u9ea6bd3ca12795949b606150) ## Tasks - [x] Schedule [mini-blueprint](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1692915056654/3e98d76a662e97592fcf6ab5f1a116b1d53173e1?sender=u9ea6bd3ca12795949b606150) workshop to test viability (8/25/23) - [x] Prepare a [synthesis mural](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1693258366432/73ef92d0f7b2c786e0fdc3ddbbe022a475bc5307?sender=u9ea6bd3ca12795949b606150) - [x] Schedule team workshop (9/1/23) - [x] Synthesize findings, formulate hypothesis, determine merging patterns ## Acceptance Criteria - [x] Initial Workshop is conducted - [x] Internal team workshop is conducted - [x] Findings from workshops 3-6 are synthesized ",1,synthesis of vfs team research purpose upon completion of all vfs team interviews possible approach tasks schedule workshop to test viability prepare a schedule team workshop synthesize findings formulate hypothesis determine merging patterns acceptance criteria initial workshop is conducted internal team workshop is conducted findings from workshops are synthesized ,1 164785,26024114857.0,IssuesEvent,2022-12-21 15:00:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[User flows and navigating] Static content pages and entry points (including CTAs) aren't updated to support a tool or feature launch. (03.07.),content design 508/Accessibility ia collaboration-cycle collab-cycle-feedback afs-dgib Staging launch-blocking CCIssue03.07 CC-Dashboard authenticated-22-1990e,"### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name Authenticated 22-1990e Transfer of Entitlement (TOE) Form Updates #### VFS feature name #### Point of Contact/Reviewers Sara Sterkenburg - @sterkenburgsara - IA *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Static content pages and entry points (including CTAs) aren't updated to support a tool or feature launch. ### Issue Details The breadcrumbs and URL indicate that the new form is a child of the ""survivor and dependent benefits"" page/section of the site. However, this page does not include an entry point to the form. The form can only be found under the wizard on the ""how to apply"" page. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 03, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References [WCAG SC 3.2.4 AA](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=246#consistent-identification) ### Platform Recommendation Your team should coordinate with sitewide content & IA regarding the publication of new static Drupal pages that were a part of your sitewide content & IA ticket. Those pages will correctly situate the new 22-1990e form in the correct location according to established content hierarchy (URLs, breadcrumbs). Until there is an entry point within the correct navigation, this should not go to launch. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[User flows and navigating] Static content pages and entry points (including CTAs) aren't updated to support a tool or feature launch. (03.07.) - ### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name Authenticated 22-1990e Transfer of Entitlement (TOE) Form Updates #### VFS feature name #### Point of Contact/Reviewers Sara Sterkenburg - @sterkenburgsara - IA *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Static content pages and entry points (including CTAs) aren't updated to support a tool or feature launch. ### Issue Details The breadcrumbs and URL indicate that the new form is a child of the ""survivor and dependent benefits"" page/section of the site. However, this page does not include an entry point to the form. The form can only be found under the wizard on the ""how to apply"" page. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 03, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References [WCAG SC 3.2.4 AA](https://www.w3.org/WAI/WCAG21/quickref/?showtechniques=246#consistent-identification) ### Platform Recommendation Your team should coordinate with sitewide content & IA regarding the publication of new static Drupal pages that were a part of your sitewide content & IA ticket. Those pages will correctly situate the new 22-1990e form in the correct location according to established content hierarchy (URLs, breadcrumbs). Until there is an entry point within the correct navigation, this should not go to launch. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, static content pages and entry points including ctas aren t updated to support a tool or feature launch general information vfs team name dgib my education benefits vfs product name authenticated transfer of entitlement toe form updates vfs feature name point of contact reviewers sara sterkenburg sterkenburgsara ia for more information on how to interpret this ticket please refer to the guidance on platform website platform issue static content pages and entry points including ctas aren t updated to support a tool or feature launch issue details the breadcrumbs and url indicate that the new form is a child of the survivor and dependent benefits page section of the site however this page does not include an entry point to the form the form can only be found under the wizard on the how to apply page link screenshot or steps to recreate va gov experience standard other references platform recommendation your team should coordinate with sitewide content ia regarding the publication of new static drupal pages that were a part of your sitewide content ia ticket those pages will correctly situate the new form in the correct location according to established content hierarchy urls breadcrumbs until there is an entry point within the correct navigation this should not go to launch vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 159266,24964622914.0,IssuesEvent,2022-11-01 18:17:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] Design/Accessibility feedback - collab cycle iteration,design 1010-team 1010-ez household-info-optimization,"## Description Recent design & accessibility feedback from the household section collab cycle process is ready to be incorporated into the initial design. - [Design intent feedback #48260](https://github.com/department-of-veterans-affairs/va.gov-team/issues/48260) - [Accessibility feedback #48324](https://github.com/department-of-veterans-affairs/va.gov-team/issues/48324) - [Content/IA feedback #48245](https://github.com/department-of-veterans-affairs/va.gov-team/issues/48245) - [Overall Household section collab cycle issue #47766](https://github.com/department-of-veterans-affairs/va.gov-team/issues/47766) ## Design Tasks **Must include** - [x] Follow our current [list/loop design pattern](https://design.va.gov/patterns/ask-users-for/multiple-responses) and style (eg. no blue background). - [ ] Consider the [expandable alert style](https://design.va.gov/components/alert-expandable) when you have additional info **Should include** - [ ] (Optional) Use a card with a drop shadow there instead (and white background); submit this to experimental design - [x] Instead of doing conditional logic, consider doing 1 question per page. - [x] H1 should be ""Apply for VA health care"" to match the breadcrumb ## Accessibility Tasks **Should do** - [x] As much as possible, avoid conditional display of fields - [x] See if there are ways to re-word or re-order questions to make them more natural together without having conditional display **Consider doing** - [x] When using the Additional Info component, make sure it makes sense to hide information in the first place (ie. Veteran annual income). Since there's already a lot of helper text on screen, it's not clear to me that you gain a lot by hiding information for these questions. ## Additional tasks - [x] Remove expandable component on radio button conditionals ## Acceptance Criteria - [x] ""Must include"" items are updated in the household section mockups - [x] ""Should include"" items are updated in the household section mockups ",1.0,"[DESIGN] Design/Accessibility feedback - collab cycle iteration - ## Description Recent design & accessibility feedback from the household section collab cycle process is ready to be incorporated into the initial design. - [Design intent feedback #48260](https://github.com/department-of-veterans-affairs/va.gov-team/issues/48260) - [Accessibility feedback #48324](https://github.com/department-of-veterans-affairs/va.gov-team/issues/48324) - [Content/IA feedback #48245](https://github.com/department-of-veterans-affairs/va.gov-team/issues/48245) - [Overall Household section collab cycle issue #47766](https://github.com/department-of-veterans-affairs/va.gov-team/issues/47766) ## Design Tasks **Must include** - [x] Follow our current [list/loop design pattern](https://design.va.gov/patterns/ask-users-for/multiple-responses) and style (eg. no blue background). - [ ] Consider the [expandable alert style](https://design.va.gov/components/alert-expandable) when you have additional info **Should include** - [ ] (Optional) Use a card with a drop shadow there instead (and white background); submit this to experimental design - [x] Instead of doing conditional logic, consider doing 1 question per page. - [x] H1 should be ""Apply for VA health care"" to match the breadcrumb ## Accessibility Tasks **Should do** - [x] As much as possible, avoid conditional display of fields - [x] See if there are ways to re-word or re-order questions to make them more natural together without having conditional display **Consider doing** - [x] When using the Additional Info component, make sure it makes sense to hide information in the first place (ie. Veteran annual income). Since there's already a lot of helper text on screen, it's not clear to me that you gain a lot by hiding information for these questions. ## Additional tasks - [x] Remove expandable component on radio button conditionals ## Acceptance Criteria - [x] ""Must include"" items are updated in the household section mockups - [x] ""Should include"" items are updated in the household section mockups ",1, design accessibility feedback collab cycle iteration description recent design accessibility feedback from the household section collab cycle process is ready to be incorporated into the initial design design tasks must include follow our current and style eg no blue background consider the when you have additional info should include optional use a card with a drop shadow there instead and white background submit this to experimental design instead of doing conditional logic consider doing question per page should be apply for va health care to match the breadcrumb accessibility tasks should do as much as possible avoid conditional display of fields see if there are ways to re word or re order questions to make them more natural together without having conditional display consider doing when using the additional info component make sure it makes sense to hide information in the first place ie veteran annual income since there s already a lot of helper text on screen it s not clear to me that you gain a lot by hiding information for these questions additional tasks remove expandable component on radio button conditionals acceptance criteria must include items are updated in the household section mockups should include items are updated in the household section mockups ,1 154390,24285315616.0,IssuesEvent,2022-09-28 21:26:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My Health - Secure Messaging - Update SM mockups/prototype based on Round 1 testing,design my-health my-health-SM-CORE,"## Issue Description Some changes are ready to be made for further testing after the first round of Secure Messaging usability testing --- ## Tasks - [x] Replace ""Delete"" labels with ""Trash"" ## Acceptance Criteria - [x] Secure Messaging mockups and prototype will be updated --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] My Health - Secure Messaging - Update SM mockups/prototype based on Round 1 testing - ## Issue Description Some changes are ready to be made for further testing after the first round of Secure Messaging usability testing --- ## Tasks - [x] Replace ""Delete"" labels with ""Trash"" ## Acceptance Criteria - [x] Secure Messaging mockups and prototype will be updated --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, my health secure messaging update sm mockups prototype based on round testing issue description some changes are ready to be made for further testing after the first round of secure messaging usability testing tasks replace delete labels with trash acceptance criteria secure messaging mockups and prototype will be updated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 111915,14172136699.0,IssuesEvent,2020-11-12 16:33:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design System Storybook Implementation: Release plan,design-system-team,"## Acceptance Criteria - [ ] Make a copy of the [release plan template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/release-plan-template.md) and add to the respective product folder - [ ] Complete release plan for launch ## How to configure this issue - [ ] **Attach to appropriate Epic** - [ ] **Labeled with Team** ",1.0,"Design System Storybook Implementation: Release plan - ## Acceptance Criteria - [ ] Make a copy of the [release plan template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/release-plan-template.md) and add to the respective product folder - [ ] Complete release plan for launch ## How to configure this issue - [ ] **Attach to appropriate Epic** - [ ] **Labeled with Team** ",1,design system storybook implementation release plan acceptance criteria make a copy of the and add to the respective product folder complete release plan for launch how to configure this issue attach to appropriate epic labeled with team ,1 135380,19565919117.0,IssuesEvent,2022-01-04 00:15:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My VA - Payment Information: Create copy documentation,design my-va-dashboard vsa-authenticated-exp planned-work,"## Background After Liz' meeting with Mikki and Danielle with Content, we're ready to create a copy document for the payment section of my VA. - Update Payment information heading to Benefit payments and debts - Update the alert copy from a single link to improve clarity about where the user would go if they clicked the link, and to align with other similar CTAs on VA.gov. The new copy is: You have 3 outstanding debt. [Manage your VA debt] - Update the card copy to use active voice. It now reads: We deposited [$$] in your account ending in [acct] on [date]. ## Tasks - [ ] Create copy documentation reflecting cards and alerts ## Acceptance Criteria - [ ] The documentation for this initiative will be aligned with the feedback from Content ",1.0,"[Design] My VA - Payment Information: Create copy documentation - ## Background After Liz' meeting with Mikki and Danielle with Content, we're ready to create a copy document for the payment section of my VA. - Update Payment information heading to Benefit payments and debts - Update the alert copy from a single link to improve clarity about where the user would go if they clicked the link, and to align with other similar CTAs on VA.gov. The new copy is: You have 3 outstanding debt. [Manage your VA debt] - Update the card copy to use active voice. It now reads: We deposited [$$] in your account ending in [acct] on [date]. ## Tasks - [ ] Create copy documentation reflecting cards and alerts ## Acceptance Criteria - [ ] The documentation for this initiative will be aligned with the feedback from Content ",1, my va payment information create copy documentation background after liz meeting with mikki and danielle with content we re ready to create a copy document for the payment section of my va update payment information heading to benefit payments and debts update the alert copy from a single link to improve clarity about where the user would go if they clicked the link and to align with other similar ctas on va gov the new copy is you have outstanding debt update the card copy to use active voice it now reads we deposited in your account ending in on tasks create copy documentation reflecting cards and alerts acceptance criteria the documentation for this initiative will be aligned with the feedback from content ,1 94318,11862976651.0,IssuesEvent,2020-03-25 18:52:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Connected accounts updates,design personalization-2.0 profile vsa-authenticated-exp,"## User Story As a user who has allowed a 3rd-party application to access my VA.gov account, I need to be able to access and manage these permissions quickly and easily from VA.gov ## Additional background Carey works with the VA API team and will be managing connected accounts going forward. She would like to make some updates for profile 2.0. We'll use this ticket to track the proposed design updates. [Carey's Figma prototype](https://www.figma.com/proto/Za0usVKp8l80mlrsx7FaB0/Account?node-id=13%3A1690&scaling=min-zoom) ## Tasks - [x] Carey to share design patterns/interactions you'd like to see @tressaellen implement - [x] Iterate design with team - [x] Settle on a final proposal **We can create a separate ticket to get copy help from Peggy or someone else on the team*. ## Acceptance Criteria - [x] Carey, Tressa, and Samara are in agreement about the connected accounts direction",1.0,"[Design] Connected accounts updates - ## User Story As a user who has allowed a 3rd-party application to access my VA.gov account, I need to be able to access and manage these permissions quickly and easily from VA.gov ## Additional background Carey works with the VA API team and will be managing connected accounts going forward. She would like to make some updates for profile 2.0. We'll use this ticket to track the proposed design updates. [Carey's Figma prototype](https://www.figma.com/proto/Za0usVKp8l80mlrsx7FaB0/Account?node-id=13%3A1690&scaling=min-zoom) ## Tasks - [x] Carey to share design patterns/interactions you'd like to see @tressaellen implement - [x] Iterate design with team - [x] Settle on a final proposal **We can create a separate ticket to get copy help from Peggy or someone else on the team*. ## Acceptance Criteria - [x] Carey, Tressa, and Samara are in agreement about the connected accounts direction",1, connected accounts updates user story as a user who has allowed a party application to access my va gov account i need to be able to access and manage these permissions quickly and easily from va gov additional background carey works with the va api team and will be managing connected accounts going forward she would like to make some updates for profile we ll use this ticket to track the proposed design updates tasks carey to share design patterns interactions you d like to see tressaellen implement iterate design with team settle on a final proposal we can create a separate ticket to get copy help from peggy or someone else on the team acceptance criteria carey tressa and samara are in agreement about the connected accounts direction,1 88247,11047825145.0,IssuesEvent,2019-12-09 19:48:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Design and test a jump link pattern and experience,508/Accessibility Epic design,"The facility sub-sections have surfaced an in-page ""jump link"" design that we believe should become a pattern for wide use. To facilitate this, we want to capture the following items: 1. Find a way to add `tabindex=""-1""` to the targets, so IE11 will honor them correctly 2. Semantic HTML that can be inserted into multiple situations, multiple pages, seamlessly 3. Manage the scroll speed. Explore CSS media queries like `prefers-reduced-motion` for best accessibility. 4. Research the experience for mobile users, desktop users, assistive tech and magnifier users",1.0,"Design and test a jump link pattern and experience - The facility sub-sections have surfaced an in-page ""jump link"" design that we believe should become a pattern for wide use. To facilitate this, we want to capture the following items: 1. Find a way to add `tabindex=""-1""` to the targets, so IE11 will honor them correctly 2. Semantic HTML that can be inserted into multiple situations, multiple pages, seamlessly 3. Manage the scroll speed. Explore CSS media queries like `prefers-reduced-motion` for best accessibility. 4. Research the experience for mobile users, desktop users, assistive tech and magnifier users",1,design and test a jump link pattern and experience the facility sub sections have surfaced an in page jump link design that we believe should become a pattern for wide use to facilitate this we want to capture the following items find a way to add tabindex to the targets so will honor them correctly semantic html that can be inserted into multiple situations multiple pages seamlessly manage the scroll speed explore css media queries like prefers reduced motion for best accessibility research the experience for mobile users desktop users assistive tech and magnifier users,1 133690,18942409776.0,IssuesEvent,2021-11-18 05:38:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Feature Request Process: Create Github Project Board for Feature Requests,service-design,"## Issue Description As a Platform Crew, VFS, or OCTO-DE team member, I want to view all feature requests submitted to the Platform and their status in a single place. --- ## Tasks - [x] Investigate creating Github Projects - [x] Setup project board - [x] Manual QA to validate project board works as expected. ## Acceptance Criteria - [x] The Platform has a customer-facing kanban board showing status of feature requests. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Feature Request Process: Create Github Project Board for Feature Requests - ## Issue Description As a Platform Crew, VFS, or OCTO-DE team member, I want to view all feature requests submitted to the Platform and their status in a single place. --- ## Tasks - [x] Investigate creating Github Projects - [x] Setup project board - [x] Manual QA to validate project board works as expected. ## Acceptance Criteria - [x] The Platform has a customer-facing kanban board showing status of feature requests. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,feature request process create github project board for feature requests issue description as a platform crew vfs or octo de team member i want to view all feature requests submitted to the platform and their status in a single place tasks investigate creating github projects setup project board manual qa to validate project board works as expected acceptance criteria the platform has a customer facing kanban board showing status of feature requests how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 93702,11799320298.0,IssuesEvent,2020-03-18 15:43:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Discovery: Profile 2.0 badge/logos,design frontend profile vsa-authenticated-exp,"## Background We would like to provide the users service badge/logo on their profile in order to provide a more customized profile experience. Tressa to meet with Erik to determine the following: - Which logos are stored (if any)? - Where are they stored? - How do we retrieve badges/logos? ## Tasks - [x] Erik to provide relevant information related to to badges and logo storage/retrieval/availability etc to Tressa - [ ] Post discovery findings on this ticket and copy Matt and Tressa",1.0,"[Design] Discovery: Profile 2.0 badge/logos - ## Background We would like to provide the users service badge/logo on their profile in order to provide a more customized profile experience. Tressa to meet with Erik to determine the following: - Which logos are stored (if any)? - Where are they stored? - How do we retrieve badges/logos? ## Tasks - [x] Erik to provide relevant information related to to badges and logo storage/retrieval/availability etc to Tressa - [ ] Post discovery findings on this ticket and copy Matt and Tressa",1, discovery profile badge logos background we would like to provide the users service badge logo on their profile in order to provide a more customized profile experience tressa to meet with erik to determine the following which logos are stored if any where are they stored how do we retrieve badges logos tasks erik to provide relevant information related to to badges and logo storage retrieval availability etc to tressa post discovery findings on this ticket and copy matt and tressa,1 113749,14483671500.0,IssuesEvent,2020-12-10 15:25:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Bug] HLR - Form intro - Copy mismatch,HLR bug design frontend vsa-benefits vsa-qa-false-positive,"## What happened? On Staging **Request a Higher-Level Review** form intro page, the **Respondent burden** duration didn't match design prototypes. ## Specs: - Device: [device-agnostic] - Browser: [browser-agnostic] - Test User _(if applicable)_: `vetsgov+test238@id.me` ## Steps to Reproduce 1. Go to https://staging.va.gov/ and sign-in as **`vetsgovtest+238@id.me` (Nerea)**. [See [this doc](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-HLR.docx) for all test-accounts and credentials.] 1. Go to https://staging.va.gov/decision-reviews/higher-level-review/request-higher-level-review-form-20-0996/introduction 1. IF eligibility wizard (**Is this the form I need?** section) is displayed, click **Disability...**, **No**, then **Request...**. Browser replaces wizard content with standard intro content. 1. Scroll down and observe that **Respondent burden** is 15 minutes [not 30 as spec'ed in design prototypes]. **Screenshot** ![hlr-bug-intro-respondent-burden](https://user-images.githubusercontent.com/587583/98610646-465b3080-22ad-11eb-9f9c-48efb4801033.png) ## Desired copy **Respondent burden** should be **30** minutes [per [design prototypes](https://vsateams.invisionapp.com/share/W5U21BDFTQK#/screens/404076957)]: ![hlr-spec-intro-respondent-burden](https://user-images.githubusercontent.com/587583/98610685-64289580-22ad-11eb-92e3-216b1af08ebd.png) ## Acceptance Criteria [See **Desired copy** above] ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to Epic** (what body of work is this a part of? possibly `Ongoing Maintenance`) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with `Bug`** ",1.0,"[Bug] HLR - Form intro - Copy mismatch - ## What happened? On Staging **Request a Higher-Level Review** form intro page, the **Respondent burden** duration didn't match design prototypes. ## Specs: - Device: [device-agnostic] - Browser: [browser-agnostic] - Test User _(if applicable)_: `vetsgov+test238@id.me` ## Steps to Reproduce 1. Go to https://staging.va.gov/ and sign-in as **`vetsgovtest+238@id.me` (Nerea)**. [See [this doc](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-HLR.docx) for all test-accounts and credentials.] 1. Go to https://staging.va.gov/decision-reviews/higher-level-review/request-higher-level-review-form-20-0996/introduction 1. IF eligibility wizard (**Is this the form I need?** section) is displayed, click **Disability...**, **No**, then **Request...**. Browser replaces wizard content with standard intro content. 1. Scroll down and observe that **Respondent burden** is 15 minutes [not 30 as spec'ed in design prototypes]. **Screenshot** ![hlr-bug-intro-respondent-burden](https://user-images.githubusercontent.com/587583/98610646-465b3080-22ad-11eb-9f9c-48efb4801033.png) ## Desired copy **Respondent burden** should be **30** minutes [per [design prototypes](https://vsateams.invisionapp.com/share/W5U21BDFTQK#/screens/404076957)]: ![hlr-spec-intro-respondent-burden](https://user-images.githubusercontent.com/587583/98610685-64289580-22ad-11eb-92e3-216b1af08ebd.png) ## Acceptance Criteria [See **Desired copy** above] ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to Epic** (what body of work is this a part of? possibly `Ongoing Maintenance`) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with `Bug`** ",1, hlr form intro copy mismatch what happened on staging request a higher level review form intro page the respondent burden duration didn t match design prototypes specs device browser test user if applicable vetsgov id me steps to reproduce go to and sign in as vetsgovtest id me nerea for all test accounts and credentials go to if eligibility wizard is this the form i need section is displayed click disability no then request browser replaces wizard content with standard intro content scroll down and observe that respondent burden is minutes screenshot desired copy respondent burden should be minutes acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 116278,14940422025.0,IssuesEvent,2021-01-25 18:15:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Add analytics to Storybook,frontend vsp-design-system-team,"## Issue Description To capture usage data on Storybook, we need to add the [Google Analytics Addon](https://storybook.js.org/addons/@storybook/addon-google-analytics). ## Questions Is the GA ID sensitive information? Do we need to add that into the Storybook deploy via CI?",1.0,"Add analytics to Storybook - ## Issue Description To capture usage data on Storybook, we need to add the [Google Analytics Addon](https://storybook.js.org/addons/@storybook/addon-google-analytics). ## Questions Is the GA ID sensitive information? Do we need to add that into the Storybook deploy via CI?",1,add analytics to storybook issue description to capture usage data on storybook we need to add the questions is the ga id sensitive information do we need to add that into the storybook deploy via ci ,1 176441,28097101691.0,IssuesEvent,2023-03-30 16:33:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2),content design 508/Accessibility ia Supplemental Claims collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard benefits-team-1,"### General Information #### VFS team name Benefits Team 1 #### VFS product name Supplemental Claims Form 20-0995 #### VFS feature name Supplemental Claims Form 20-0995 #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details If a user uploads evidence and gets an error message, the message reads ""something went wrong..."". ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Follow the [files design pattern](https://design.va.gov/patterns/ask-users-for/files#error-state) and chancge the text to ""We couldn't upload your file"" --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2) - ### General Information #### VFS team name Benefits Team 1 #### VFS product name Supplemental Claims Form 20-0995 #### VFS feature name Supplemental Claims Form 20-0995 #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details If a user uploads evidence and gets an error message, the message reads ""something went wrong..."". ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Follow the [files design pattern](https://design.va.gov/patterns/ask-users-for/files#error-state) and chancge the text to ""We couldn't upload your file"" --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, design components or patterns don t align with design system guidelines general information vfs team name benefits team vfs product name supplemental claims form vfs feature name supplemental claims form point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details if a user uploads evidence and gets an error message the message reads something went wrong link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation follow the and chancge the text to we couldn t upload your file vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 140718,21189224572.0,IssuesEvent,2022-04-08 15:33:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design, FE] My VA: Align Health care link list on left when there are no appointments or messages",frontend design my-va-dashboard vsa-authenticated-exp planned-work,"## Background Now that we have added the 'no appointment' text for users that have no upcoming health care appointments, we need to ensure the alignment of the link list is consistent on the page. This change will be behind the same feature flag as payment info changes. For the Health Care section, when there are no unread messages AND no upcoming appointments, the link list should align to the left side, underneath the message ""You have no appointments scheduled in the next 30 days."" ![image](https://user-images.githubusercontent.com/92328831/158676464-a562a7f5-90d3-492e-a0cf-abab7aca3c2c.png) ## Tasks - [x] Update design sketch file to include a mockup of the alignment update - [x] Update the code to align the link list in the event of no unread messages and no upcoming appointments ## Acceptance Criteria - Health care link list will be aligned appropriately, depending on whether there are unread messages and/or upcoming appointments",1.0,"[Design, FE] My VA: Align Health care link list on left when there are no appointments or messages - ## Background Now that we have added the 'no appointment' text for users that have no upcoming health care appointments, we need to ensure the alignment of the link list is consistent on the page. This change will be behind the same feature flag as payment info changes. For the Health Care section, when there are no unread messages AND no upcoming appointments, the link list should align to the left side, underneath the message ""You have no appointments scheduled in the next 30 days."" ![image](https://user-images.githubusercontent.com/92328831/158676464-a562a7f5-90d3-492e-a0cf-abab7aca3c2c.png) ## Tasks - [x] Update design sketch file to include a mockup of the alignment update - [x] Update the code to align the link list in the event of no unread messages and no upcoming appointments ## Acceptance Criteria - Health care link list will be aligned appropriately, depending on whether there are unread messages and/or upcoming appointments",1, my va align health care link list on left when there are no appointments or messages background now that we have added the no appointment text for users that have no upcoming health care appointments we need to ensure the alignment of the link list is consistent on the page this change will be behind the same feature flag as payment info changes for the health care section when there are no unread messages and no upcoming appointments the link list should align to the left side underneath the message you have no appointments scheduled in the next days tasks update design sketch file to include a mockup of the alignment update update the code to align the link list in the event of no unread messages and no upcoming appointments acceptance criteria health care link list will be aligned appropriately depending on whether there are unread messages and or upcoming appointments,1 105853,13224077252.0,IssuesEvent,2020-08-17 18:26:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Discovery - Iteration of appointments homepage,design discovery vaos,"There is some confusion associated with what's what on the appointments homepage between confirmed appointments and requests. Also in the near future we need to enable printing individual appointments with appropriate details about upcoming appointments. ",1.0,"Discovery - Iteration of appointments homepage - There is some confusion associated with what's what on the appointments homepage between confirmed appointments and requests. Also in the near future we need to enable printing individual appointments with appropriate details about upcoming appointments. ",1,discovery iteration of appointments homepage there is some confusion associated with what s what on the appointments homepage between confirmed appointments and requests also in the near future we need to enable printing individual appointments with appropriate details about upcoming appointments ,1 130679,18105958847.0,IssuesEvent,2021-09-22 19:10:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Find a VA Form: Mock up accessible PDF alert,design vsa needs-grooming vsa-decision-tools dt-find-va-form,"## Issue Description We will implement a modal that users must acknowledge before downloading a PDF form. The workflow would be as follows: 1. I search for a form 2. I get search results 3. I find the form I'm searching for 4. I want the PDF vs. online tool 5. I click Download PDF 6. The modal is triggered - see design system https://design.va.gov/storybook/?path=/docs/components-modal--default 7. Modal title says ""**Adobe Reader DC Required**"" (final copy TBD by Content team) 8. Modal text says ""All PDF forms do not function fully in a web browser or other PDF viewer. Please download the form and use Adobe Acrobat Reader DC to fill out. For specific instructions about working with PDFs, [please read our Resources and Support article](https://www.va.gov/resources/how-to-download-and-open-a-vagov-pdf-form)"" (final copy TBD by Content team) 9. There are three options below that: - [Get Adobe Reader](https://get.adobe.com/reader/) - Download VA Form 10-10EZ - Cancel button to close the modal ## Tasks - [x] Mock up modal as described above - [x] Provide Sketch link to mockup in comment in this ticket ## Acceptance Criteria - [x] We will have modal mockup that we can use for context when requesting content tweaks and for Zach to follow when building --- ",1.0,"Find a VA Form: Mock up accessible PDF alert - ## Issue Description We will implement a modal that users must acknowledge before downloading a PDF form. The workflow would be as follows: 1. I search for a form 2. I get search results 3. I find the form I'm searching for 4. I want the PDF vs. online tool 5. I click Download PDF 6. The modal is triggered - see design system https://design.va.gov/storybook/?path=/docs/components-modal--default 7. Modal title says ""**Adobe Reader DC Required**"" (final copy TBD by Content team) 8. Modal text says ""All PDF forms do not function fully in a web browser or other PDF viewer. Please download the form and use Adobe Acrobat Reader DC to fill out. For specific instructions about working with PDFs, [please read our Resources and Support article](https://www.va.gov/resources/how-to-download-and-open-a-vagov-pdf-form)"" (final copy TBD by Content team) 9. There are three options below that: - [Get Adobe Reader](https://get.adobe.com/reader/) - Download VA Form 10-10EZ - Cancel button to close the modal ## Tasks - [x] Mock up modal as described above - [x] Provide Sketch link to mockup in comment in this ticket ## Acceptance Criteria - [x] We will have modal mockup that we can use for context when requesting content tweaks and for Zach to follow when building --- ",1,find a va form mock up accessible pdf alert issue description we will implement a modal that users must acknowledge before downloading a pdf form the workflow would be as follows i search for a form i get search results i find the form i m searching for i want the pdf vs online tool i click download pdf the modal is triggered see design system modal title says adobe reader dc required final copy tbd by content team modal text says all pdf forms do not function fully in a web browser or other pdf viewer please download the form and use adobe acrobat reader dc to fill out for specific instructions about working with pdfs final copy tbd by content team there are three options below that download va form cancel button to close the modal tasks mock up modal as described above provide sketch link to mockup in comment in this ticket acceptance criteria we will have modal mockup that we can use for context when requesting content tweaks and for zach to follow when building ,1 136276,19730594129.0,IssuesEvent,2022-01-14 01:33:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Standardize design system component usage measurements,vsp-design-system-team,"## Description Currently, our component usage report measures the usage of our React components and our web components differently. - React components are measured by import because sometimes teams use the same name as a Design System component for their own component, which makes it difficult to measure actual usage. - Web components are measured by usage, so we search for the name of the component in the code. In order to get a more accurate picture of design system component usage, we need to be measuring these two types of components in the same way. We would like to update the React component measurement so that it measures component usage rather than imports. ## Details This is going to be a little tricky. I would recommend altering the code so that it looks for the import first and then measures how many times a component is used within that file. I have not dug into this code myself, though, so there may be a better way to do this. Alternatively, this may be harder than it seems at first glance as well. We just want to be careful to only measure design system component usage and not other components that are named the same. The component usage report code is contained in the [design-system-dashboard-cli](https://github.com/department-of-veterans-affairs/design-system-dashboard-cli) repo. ## Acceptance Criteria - [ ] React components are measured by usage rather than import - [ ] Our measurement is not capturing components with the same name as a design system component",1.0,"Standardize design system component usage measurements - ## Description Currently, our component usage report measures the usage of our React components and our web components differently. - React components are measured by import because sometimes teams use the same name as a Design System component for their own component, which makes it difficult to measure actual usage. - Web components are measured by usage, so we search for the name of the component in the code. In order to get a more accurate picture of design system component usage, we need to be measuring these two types of components in the same way. We would like to update the React component measurement so that it measures component usage rather than imports. ## Details This is going to be a little tricky. I would recommend altering the code so that it looks for the import first and then measures how many times a component is used within that file. I have not dug into this code myself, though, so there may be a better way to do this. Alternatively, this may be harder than it seems at first glance as well. We just want to be careful to only measure design system component usage and not other components that are named the same. The component usage report code is contained in the [design-system-dashboard-cli](https://github.com/department-of-veterans-affairs/design-system-dashboard-cli) repo. ## Acceptance Criteria - [ ] React components are measured by usage rather than import - [ ] Our measurement is not capturing components with the same name as a design system component",1,standardize design system component usage measurements description currently our component usage report measures the usage of our react components and our web components differently react components are measured by import because sometimes teams use the same name as a design system component for their own component which makes it difficult to measure actual usage web components are measured by usage so we search for the name of the component in the code in order to get a more accurate picture of design system component usage we need to be measuring these two types of components in the same way we would like to update the react component measurement so that it measures component usage rather than imports details this is going to be a little tricky i would recommend altering the code so that it looks for the import first and then measures how many times a component is used within that file i have not dug into this code myself though so there may be a better way to do this alternatively this may be harder than it seems at first glance as well we just want to be careful to only measure design system component usage and not other components that are named the same the component usage report code is contained in the repo acceptance criteria react components are measured by usage rather than import our measurement is not capturing components with the same name as a design system component,1 175512,27870788177.0,IssuesEvent,2023-03-21 13:20:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Remove dupes and organize symbols in unified experience sketch file ,design ux HCE-Checkin,"## Description Remove dupes and organize symbols in sketch file in order to be able to document design, functional or other specifications on specific symbols to engineers, designers, product owners and other stakeholders. ## Tasks - [ ] Meet with Christina and Ben to talk through organization of sketch file - [ ] Discuss how to manage this task while sitewide content is reviewing the sketch file. For example, should we create another page? - [ ] Remove dupes and organize symbols ## AC - [ ] Work is validated. E.g., dupes are removed and symbols are organized. ",1.0,"[Design] Remove dupes and organize symbols in unified experience sketch file - ## Description Remove dupes and organize symbols in sketch file in order to be able to document design, functional or other specifications on specific symbols to engineers, designers, product owners and other stakeholders. ## Tasks - [ ] Meet with Christina and Ben to talk through organization of sketch file - [ ] Discuss how to manage this task while sitewide content is reviewing the sketch file. For example, should we create another page? - [ ] Remove dupes and organize symbols ## AC - [ ] Work is validated. E.g., dupes are removed and symbols are organized. ",1, remove dupes and organize symbols in unified experience sketch file description remove dupes and organize symbols in sketch file in order to be able to document design functional or other specifications on specific symbols to engineers designers product owners and other stakeholders tasks meet with christina and ben to talk through organization of sketch file discuss how to manage this task while sitewide content is reviewing the sketch file for example should we create another page remove dupes and organize symbols ac work is validated e g dupes are removed and symbols are organized ,1 88959,11184066458.0,IssuesEvent,2019-12-31 16:15:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Discovery: Create Discovery Readout Documents,design discovery documentation research vsa vsa-benefits-2,"## User Story or Problem Statement As a UX designer participating in a discovery sprint, I need to create a discovery readout so I can the team, team leads, and future teams can learn about the completed work, concerns, opportunities, findings, and recommendations. ## Tasks (Hours) - [x] Create markdown outline and content for GH (2 days) - [x] Fill out the discovery sprint readout [template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/discovery-sprints/End%20of%20Discovery%20Readout%20Template.pptx) with the findings from the user interview sessions (2 days) ## Acceptance Criteria - [x] Discovery findings markdown document completed - [x] Discovery sprint readout completed ## Next Steps - Presenting our findings to the team and team leads - Influences ideation/whiteboarding sessions and the form flow",1.0,"Discovery: Create Discovery Readout Documents - ## User Story or Problem Statement As a UX designer participating in a discovery sprint, I need to create a discovery readout so I can the team, team leads, and future teams can learn about the completed work, concerns, opportunities, findings, and recommendations. ## Tasks (Hours) - [x] Create markdown outline and content for GH (2 days) - [x] Fill out the discovery sprint readout [template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/discovery-sprints/End%20of%20Discovery%20Readout%20Template.pptx) with the findings from the user interview sessions (2 days) ## Acceptance Criteria - [x] Discovery findings markdown document completed - [x] Discovery sprint readout completed ## Next Steps - Presenting our findings to the team and team leads - Influences ideation/whiteboarding sessions and the form flow",1,discovery create discovery readout documents user story or problem statement as a ux designer participating in a discovery sprint i need to create a discovery readout so i can the team team leads and future teams can learn about the completed work concerns opportunities findings and recommendations tasks hours create markdown outline and content for gh days fill out the discovery sprint readout with the findings from the user interview sessions days acceptance criteria discovery findings markdown document completed discovery sprint readout completed next steps presenting our findings to the team and team leads influences ideation whiteboarding sessions and the form flow,1 134600,19278860033.0,IssuesEvent,2021-12-10 14:59:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Overall user experience] Design component or pattern in use isn't considered a best practice. (01.01.2),design ia Identity collab-cycle-feedback Identity-Frontend Staging CCIssue01.01 CC-Dashboard,"### General Information #### VFS team name Identity #### VFS product name Sign-in modal #### Point of Contact/Reviewers Ryan Thurlwell (@rtwell) - OCTO Design Lead --- ### Platform Issue Design component or pattern in use isn't considered a best practice. ### Issue Details Not enough space between ""My HealthVet"" button and ""Create and account"" title. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 01, Issue Number 01](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References --- ### Platform Recommendation Space between ""My HealthVet"" button and “Create an account” title should be 24px. ### VFS Team Tasks to Complete - [x] Comment on the ticket if there are questions or concerns - [x] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. ",1.0,"[Overall user experience] Design component or pattern in use isn't considered a best practice. (01.01.2) - ### General Information #### VFS team name Identity #### VFS product name Sign-in modal #### Point of Contact/Reviewers Ryan Thurlwell (@rtwell) - OCTO Design Lead --- ### Platform Issue Design component or pattern in use isn't considered a best practice. ### Issue Details Not enough space between ""My HealthVet"" button and ""Create and account"" title. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 01, Issue Number 01](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References --- ### Platform Recommendation Space between ""My HealthVet"" button and “Create an account” title should be 24px. ### VFS Team Tasks to Complete - [x] Comment on the ticket if there are questions or concerns - [x] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. ",1, design component or pattern in use isn t considered a best practice general information vfs team name identity vfs product name sign in modal point of contact reviewers ryan thurlwell rtwell octo design lead platform issue design component or pattern in use isn t considered a best practice issue details not enough space between my healthvet button and create and account title link screenshot or steps to recreate va gov experience standard other references platform recommendation space between my healthvet button and “create an account” title should be vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 175509,27869974464.0,IssuesEvent,2023-03-21 12:53:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Content Review - Appointment Modality/Appointment Details Page from VAOS - VA Online Scheduling,ux vaos-product-design sitewide content sitewide content-product support November sitewide CAIA,"## What does your team need support for? Check all that apply. - [ ] Launching one or more new unauthenticated (static) VA.gov pages - [ ] Making revisions to one or more existing unauthenticated (static) VA.gov page - [ ] Launching a new online form, app, or tool on VA.gov - [X] Making revisions to an existing online form, app, or tool on VA.gov - [ ] Something else (please add details in the next question) ## What do you need help with? - [X] Content support - [ ] IA support *Please describe your need and provide any additional documents and/or links that will help us help you. If we need to add a react widget to a page, be sure to provide the code here.* ## Will this new product be released incrementally (for instance 25% of users initially)? - [ ] Yes - [X] No **Note:** If you checked yes, we'll reach out to discuss details about the content in the react widget. ## When do you expect to launch your product to 100% of users? *Please provide an estimated date so our team can create other relevant tickets.* ## Supporting artifacts *Please provide supporting artifacts as available.* - Link to product outline: - Link to or attach user flows: - Link to prototype or mockups: - [Modality Structure](https://www.figma.com/file/JpGM8LGBCqAlL8qh3DmFk8/Home-Page-Redesign?node-id=1194%3A66663) - [Pending Appt description](https://www.figma.com/file/JpGM8LGBCqAlL8qh3DmFk8/Home-Page-Redesign?node-id=2362%3A65832) - [Details Page Join Instructions](https://www.figma.com/file/JpGM8LGBCqAlL8qh3DmFk8/Home-Page-Redesign?node-id=1808%3A68061) - Link to any epics/issues that may be helpful: ## Will this work be going through the Collaboration Cycle? - [X] Yes - [ ] No ## When does this work need to be done? - Estimated launch date: February 2023 - Estimated staging review date: January 2023 - Content and IA work needed by: December 2022 ## Do you plan to bring this to an upcoming content office hours session? - [ ] Yes, benefit content office hours (Thursdays, 3:00 p.m. to 3:45 p.m. ET) - [ ] Yes, health content office hours (Thursdays, 11:00 a.m. to 11:30 a.m. ET) - [ ] Yes, unauth office hours (Mondays, 11:00 a.m. to 11:30 a.m. ET) - [ ] No, but I'd like to schedule time to talk about this request - [x] No, let's work asynchronously and meet if needed **Note:** If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet. ## About your team - Team name: VAOS, VA Online Scheduling - OCTO-DE product owner: Lauren Alexanderson, Katherine Lawyer, Stephen Barrs, Patrick Bateman, Mark Dewey - Product manager: Leah De La Costa & Jeff Roof - Designer: Peter Russo & Ciera Maddox - FE engineer: Simi Adebowale - Product/team Slack channel: #vaos ## Next steps **Once you’ve submitted this ticket, please post a link to this issue in the [#sitewide-content-ia](https://dsva.slack.com/channels/sitewide-content-ia) Slack channel and tag Randi Hecht.** If you also need engineering support from the Public Websites team, fill out their [intake request form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E). If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a [Redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=mnorthuis&labels=ia&template=redirect-request.md&title=Redirect+Request) ",1.0,"Content Review - Appointment Modality/Appointment Details Page from VAOS - VA Online Scheduling - ## What does your team need support for? Check all that apply. - [ ] Launching one or more new unauthenticated (static) VA.gov pages - [ ] Making revisions to one or more existing unauthenticated (static) VA.gov page - [ ] Launching a new online form, app, or tool on VA.gov - [X] Making revisions to an existing online form, app, or tool on VA.gov - [ ] Something else (please add details in the next question) ## What do you need help with? - [X] Content support - [ ] IA support *Please describe your need and provide any additional documents and/or links that will help us help you. If we need to add a react widget to a page, be sure to provide the code here.* ## Will this new product be released incrementally (for instance 25% of users initially)? - [ ] Yes - [X] No **Note:** If you checked yes, we'll reach out to discuss details about the content in the react widget. ## When do you expect to launch your product to 100% of users? *Please provide an estimated date so our team can create other relevant tickets.* ## Supporting artifacts *Please provide supporting artifacts as available.* - Link to product outline: - Link to or attach user flows: - Link to prototype or mockups: - [Modality Structure](https://www.figma.com/file/JpGM8LGBCqAlL8qh3DmFk8/Home-Page-Redesign?node-id=1194%3A66663) - [Pending Appt description](https://www.figma.com/file/JpGM8LGBCqAlL8qh3DmFk8/Home-Page-Redesign?node-id=2362%3A65832) - [Details Page Join Instructions](https://www.figma.com/file/JpGM8LGBCqAlL8qh3DmFk8/Home-Page-Redesign?node-id=1808%3A68061) - Link to any epics/issues that may be helpful: ## Will this work be going through the Collaboration Cycle? - [X] Yes - [ ] No ## When does this work need to be done? - Estimated launch date: February 2023 - Estimated staging review date: January 2023 - Content and IA work needed by: December 2022 ## Do you plan to bring this to an upcoming content office hours session? - [ ] Yes, benefit content office hours (Thursdays, 3:00 p.m. to 3:45 p.m. ET) - [ ] Yes, health content office hours (Thursdays, 11:00 a.m. to 11:30 a.m. ET) - [ ] Yes, unauth office hours (Mondays, 11:00 a.m. to 11:30 a.m. ET) - [ ] No, but I'd like to schedule time to talk about this request - [x] No, let's work asynchronously and meet if needed **Note:** If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet. ## About your team - Team name: VAOS, VA Online Scheduling - OCTO-DE product owner: Lauren Alexanderson, Katherine Lawyer, Stephen Barrs, Patrick Bateman, Mark Dewey - Product manager: Leah De La Costa & Jeff Roof - Designer: Peter Russo & Ciera Maddox - FE engineer: Simi Adebowale - Product/team Slack channel: #vaos ## Next steps **Once you’ve submitted this ticket, please post a link to this issue in the [#sitewide-content-ia](https://dsva.slack.com/channels/sitewide-content-ia) Slack channel and tag Randi Hecht.** If you also need engineering support from the Public Websites team, fill out their [intake request form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E). If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a [Redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=mnorthuis&labels=ia&template=redirect-request.md&title=Redirect+Request) ",1,content review appointment modality appointment details page from vaos va online scheduling what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with content support ia support please describe your need and provide any additional documents and or links that will help us help you if we need to add a react widget to a page be sure to provide the code here will this new product be released incrementally for instance of users initially yes no note if you checked yes we ll reach out to discuss details about the content in the react widget when do you expect to launch your product to of users please provide an estimated date so our team can create other relevant tickets supporting artifacts please provide supporting artifacts as available link to product outline link to or attach user flows link to prototype or mockups link to any epics issues that may be helpful will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date february estimated staging review date january content and ia work needed by december do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name vaos va online scheduling octo de product owner lauren alexanderson katherine lawyer stephen barrs patrick bateman mark dewey product manager leah de la costa jeff roof designer peter russo ciera maddox fe engineer simi adebowale product team slack channel vaos next steps once you’ve submitted this ticket please post a link to this issue in the  slack channel and tag randi hecht if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 93120,11740955621.0,IssuesEvent,2020-03-11 20:40:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"MDT- Review order page - edit selected products, v1",design vsa vsa-benefits-2," As a veteran, I need be able to change my selected items if I have made an ordering error so that I can make corrections before submitting my order ## Tasks - Create high fidelity mockups for editing selected products from the review order page - Upload to Invision with a comment to highlight initial focus state ## Acceptance Criteria: - [ ] Mockup aligns with VA.gov’s design system - [ ] Include a way for Veterans to change their selected product(s) - [ ] Initial focus point documented in Invision - [ ] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Step ## Dep/Blockers",1.0,"MDT- Review order page - edit selected products, v1 - As a veteran, I need be able to change my selected items if I have made an ordering error so that I can make corrections before submitting my order ## Tasks - Create high fidelity mockups for editing selected products from the review order page - Upload to Invision with a comment to highlight initial focus state ## Acceptance Criteria: - [ ] Mockup aligns with VA.gov’s design system - [ ] Include a way for Veterans to change their selected product(s) - [ ] Initial focus point documented in Invision - [ ] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Step ## Dep/Blockers",1,mdt review order page edit selected products as a veteran i need be able to change my selected items if i have made an ordering error so that i can make corrections before submitting my order tasks create high fidelity mockups for editing selected products from the review order page upload to invision with a comment to highlight initial focus state acceptance criteria mockup aligns with va gov’s design system include a way for veterans to change their selected product s initial focus point documented in invision sketch artboards are uploaded to invision and linked in this ticket as a comment next step dep blockers,1 141019,21336465413.0,IssuesEvent,2022-04-18 15:07:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] - Auth Profile - Bad Address Indicator- Component Discovery/Incorporate Design Intent feedback,design vsa vsa-authenticated-exp profile bad-address-indicator,"## Background Following the Design Intent meeting, work with Content/IA/Accessibility on UI revisions based on feedback. @cgednalske - Linking to the feedback from the Design Intent review held yesterday. - [Design Intent Request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38727) - [Design Feedback](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38886) - [Accessibility Feedback](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38905) - [Content & IA Feedback](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38922) ## Tasks - [ ] Create Content request if needed - [x] Work with Content on updated copy - [x] Work with IA on adjustments to user flow - [x] Work with Accessibility on any issues that need to be addressed - [x] Update mockups based on above conversations ## Acceptance Criteria - [ ] Create Content request if needed - [x] Work with Content on updated copy - [x] Work with IA on adjustments to user flow - [x] Work with Accessibility on any issues that need to be addressed - [x] Update mockups based on above conversations ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1.0,"[Design] - Auth Profile - Bad Address Indicator- Component Discovery/Incorporate Design Intent feedback - ## Background Following the Design Intent meeting, work with Content/IA/Accessibility on UI revisions based on feedback. @cgednalske - Linking to the feedback from the Design Intent review held yesterday. - [Design Intent Request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38727) - [Design Feedback](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38886) - [Accessibility Feedback](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38905) - [Content & IA Feedback](https://github.com/department-of-veterans-affairs/va.gov-team/issues/38922) ## Tasks - [ ] Create Content request if needed - [x] Work with Content on updated copy - [x] Work with IA on adjustments to user flow - [x] Work with Accessibility on any issues that need to be addressed - [x] Update mockups based on above conversations ## Acceptance Criteria - [ ] Create Content request if needed - [x] Work with Content on updated copy - [x] Work with IA on adjustments to user flow - [x] Work with Accessibility on any issues that need to be addressed - [x] Update mockups based on above conversations ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1, auth profile bad address indicator component discovery incorporate design intent feedback background following the design intent meeting work with content ia accessibility on ui revisions based on feedback cgednalske linking to the feedback from the design intent review held yesterday tasks create content request if needed work with content on updated copy work with ia on adjustments to user flow work with accessibility on any issues that need to be addressed update mockups based on above conversations acceptance criteria create content request if needed work with content on updated copy work with ia on adjustments to user flow work with accessibility on any issues that need to be addressed update mockups based on above conversations how to configure this issue include practice area in title e g include project initiative name e g auth profile address change messaging add label for practice area frontend backend design add label for project if applicable assign to a profile team member associate with an epic if applicable if creating for yourself estimate work if enough info exists to do so ,1 88979,11184767694.0,IssuesEvent,2019-12-31 20:05:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Facility Locator UX Redesign,Epic backend design frontend vsa vsa-facilities vsa-qa,"This Epic will track the work and process for the Facility Locator UX Redesign ## Discovery - [ ] [Review the Discovery How-to Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/discovery-sprints/how-to-run-discovery-sprint.md) as well as the [Discovery Toolkit](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Practice%20Areas/Research/Discovery/readme.md) - [ ] Schedule and attend an orientation of the new feature - [ ] List endpoints or questions about endpoints ## Design ### Research Plan - [ ] Establish process for user interviews ([great resource](https://docs.google.com/document/d/1d2PJ6saIhzbWneevUs4rc153LTcbGxN-IJ9cXT51g1A/edit#heading=h.mfojcojhlwfx)) - [ ] Create a Conversation Guide (sample [Conversation Guide](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Identity/Personalization/Profile/Direct%20Deposit/Discovery%20%26%20Research/Research/Usability%20testing/Conversation%20Guide.md)) ### UX - [ ] Develop thumbnail map of feature - [ ] Develop wireframes - [ ] Seek applicable feedback, obtain understanding from team - [ ] Develop mockups - [ ] Seek applicable feedback, obtain understanding from team ### Review Process - [ ] **Internal** - [ ] Review the [Web Brand Consolidation documentation](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/VA.gov%20Relaunch%202018/new-vagov-strategy/The-new-VA.gov-briefing-2019-07.pdf) - [ ] Review the [VA.gov Design System](https://design.va.gov/) - [ ] Team and DSVA: share mockups, discuss alternates/options in a team meeting - [ ] Review the [Design QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/ebenefits/design/design-review-checklist.md) docuementation - [ ] **External** - [ ] Review [Design Workflow](https://docs.google.com/document/d/1BtIHL5KRl9ln20FONWpBjQzTDveU_wyKqWCL5R-6MB8/edit?ts=5d9507d5#heading=h.bu00ebtvll88) - [ ] Shawna (`@shawna` in Slack): Design presentation of mockups (might be in a weekly meeting) - Iterate on Shawna's feedback - [ ] Other Teams: Authenticated Experience, Global UX, etc - [ ] VFS-platform-support - Emily: Design - Peggy: Content - Mikki: IA - Jennifer: Usability - Trevor: 508 - Iterate on other team's feedback - [ ] **As soon as feasible and iteration is finished,** request a [Design QA Review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-design-qa.md) ### Content/IA _Share as soon as you have content - this is usually after mockups are created. Get IA review after thumbnails (in case IA informs of a change, get Content review after mockups (provide as much final content to FE for implementation)_ - [ ] Discovery and reference the [VA.gov content style guide](https://design.va.gov/content-style-guide/) - [ ] Reference the [Content/IA best practices](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/content/content-review-process.md) - [ ] Reference the [Content/IA Messaging Dictionary](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Platform/Design%20System/Guidelines/Error%20handling/Dictionary.md) - [ ] Reference the [Error Handling Content Style Guide](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Platform/Design%20System/Guidelines/Error%20handling/Content%20Style%20Guide.md) - [ ] Engage with the Content/IA team as soon as feasible - [ ] Present text/verbiage that is beyond the boilerplate language - [ ] Outline links (hub and spoke), urls, navigation hierarchy, crosslinks/redirects, SEO - [ ] Discuss what parts of the site are templated - [ ] Solicit feedback from Content/IA Team - [ ] Confirm that wayfinding is appropriate - [ ] [Request IA Review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ia-review.md) & [Request a Content Review](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/content/content-review-process.md#how-to-request-content-review) _These links/reviews may end up being consolidated, stay tuned._ - [ ] Before launch, circle back with Content/IA about further impact and feedback ### Usability - [ ] Create a [test plan](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Identity/Personalization/Profile/Direct%20Deposit/Discovery%20&%20Research/Research/Usability%20testing/Research%20Plan.md) - [ ] Is the entry point established? - [ ] Is there a better entry point? - [ ] 508 Compliance - [ ] Review [508 Checklist](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/ebenefits/508-checklist-wip.md) - [ ] [Request 508 Audit](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/508-request-prelaunch-review.md) - [ ] Ensure the feature is tracked within the [508 Product Sheet](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/508-product-review-list.md) ## Development _Do we need to merge the FE and BE tasks?_ ### General Engineering Tasks - [ ] Documentation for quickly addressing when things go wrong - [ ] Establish contacts for oncall support: who do we contact if the application is failing? What kinds of failure modes are likely? ### Backend Tasks - [ ] Investigation of applicable services - [ ] Which API service does this feature use? - [ ] Collaborate with Frontend on Error Handling - [ ] Investigate the common area for error types - [ ] Define or reference a known resource - [ ] For PRs: first review internally with BE or another engineer before the BE Team - [ ] Once internally reviewed, share with the BE Review Team at the VSP (team name?) - [ ] Ensure that [feature flags](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/platform/tools/feature-flags/) are set appropriately to be [toggled](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/engineering/feature-toggles.md) - [ ] Documentation and points of contact for any new backend dependencies - [ ] Links to important dashboards for investigating relevant issues ### Frontend Tasks - [ ] Investigation - [ ] What will be involved in using the API service to pull and display data? - [ ] List and define what the main components will be for the feature to function properly - [ ] Collaborate with Backend on Error Handling - [ ] Investigate the common area for error types - [ ] Define or reference a known resource - [ ] For PRs: first review internally with FE or another engineer before the FE Team - [ ] Once internally reviewed, share with the FE Review Team at the VSP (team name?) - [ ] Ensure that [feature flags](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/platform/tools/feature-flags/) are set appropriately to be [toggled](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/engineering/feature-toggles.md) - [ ] Entrance pages (i.e. supporting static content) in place ### Security/ATO - [ ] Establish who among VSP we should talk to about Security Reviews - [ ] What is the review process? - [ ] Review the [ATO Procedures](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ato-reviews.md) - [ ] Request a [preliminary ATO review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ato-reviews.md#request-a-preliminary-ato-review) - [ ] Request a [pre-launch ATO review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ato-reviews.md#request-a-pre-launch-ato-review) ### QA - [ ] [Documentation](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/quality-assurance) from platform ### Testing - [ ] Create a test plan from an overall engineering perspective - [ ] Build, test, audits (508, content, security, load, CI/CD, passing on all browsers, etc) in a feedback loop - [ ] Code coverage requirements - [ ] Develop testing infrastructure, refer to established documentation - [ ] Define threshold or definition of high-severity bugs - [ ] Document any high-severity bugs for future reference - [ ] Establish contacts for errors to be reported to - [ ] Errors get sent directly to the team - [ ] Establish steps to take to move feature into [staging](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/accessing-staging.md) or within - [ ] Tested in prod with back-of-house people and systems ## Analytics - [ ] Confirm that the new feature/product is stable and visible in staging.va.gov - [ ] Engage with the Analytics Team about what is to be launched - [ ] Review [KPI/metrics spreadsheet](https://docs.google.com/spreadsheets/d/1e9bqzjBnibiCWXWNMcK-fJOw7cjXVdx5M6gmC4phlfg/edit#gid=1554481611) ## Support - [ ] Does the Call Center have documentation? - [ ] Have they asked for anything else? - [ ] What else should we say about ## Pre-release - [ ] Call Center is prepared for launch with updated scripts/documentation as needed - [ ] VA web comms team is aware of this launch and has accurate messaging - [ ] Product Outline is updated - [ ] Downtime UX and error messaging documentation complete - [ ] ""Learn and Improve"" plan written: KPI measurements, analytics reporting, next phase of features to build ## Release Plan - [ ] Refer to in-depth [Release Plan Template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/release-plan-template.md) ## Consider Deliverables and Artifacts - [ ] Ensure that these are noted and stored for easy access - [ ] Include contact information in case further discussion is required ## Launch - [ ] Go/No-go from each team member - [ ] Define what is being tracked - [ ] Define other last minute items - [ ] Review the [Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/release-plan-template.md) ## Post-Mortem - [ ] List and define any issues that impeded the process - [ ] Create post-launch coordination plan including calls with stakeholders and call center - [ ] Coordinate with Call Center to monitor calls - [ ] Ensure monitoring and resolve issues in 24 hours - [ ] Collect and report metrics from Google Analytics - [ ] Schedule regression testing ",1.0,"Facility Locator UX Redesign - This Epic will track the work and process for the Facility Locator UX Redesign ## Discovery - [ ] [Review the Discovery How-to Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/discovery-sprints/how-to-run-discovery-sprint.md) as well as the [Discovery Toolkit](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Practice%20Areas/Research/Discovery/readme.md) - [ ] Schedule and attend an orientation of the new feature - [ ] List endpoints or questions about endpoints ## Design ### Research Plan - [ ] Establish process for user interviews ([great resource](https://docs.google.com/document/d/1d2PJ6saIhzbWneevUs4rc153LTcbGxN-IJ9cXT51g1A/edit#heading=h.mfojcojhlwfx)) - [ ] Create a Conversation Guide (sample [Conversation Guide](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Identity/Personalization/Profile/Direct%20Deposit/Discovery%20%26%20Research/Research/Usability%20testing/Conversation%20Guide.md)) ### UX - [ ] Develop thumbnail map of feature - [ ] Develop wireframes - [ ] Seek applicable feedback, obtain understanding from team - [ ] Develop mockups - [ ] Seek applicable feedback, obtain understanding from team ### Review Process - [ ] **Internal** - [ ] Review the [Web Brand Consolidation documentation](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/VA.gov%20Relaunch%202018/new-vagov-strategy/The-new-VA.gov-briefing-2019-07.pdf) - [ ] Review the [VA.gov Design System](https://design.va.gov/) - [ ] Team and DSVA: share mockups, discuss alternates/options in a team meeting - [ ] Review the [Design QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/ebenefits/design/design-review-checklist.md) docuementation - [ ] **External** - [ ] Review [Design Workflow](https://docs.google.com/document/d/1BtIHL5KRl9ln20FONWpBjQzTDveU_wyKqWCL5R-6MB8/edit?ts=5d9507d5#heading=h.bu00ebtvll88) - [ ] Shawna (`@shawna` in Slack): Design presentation of mockups (might be in a weekly meeting) - Iterate on Shawna's feedback - [ ] Other Teams: Authenticated Experience, Global UX, etc - [ ] VFS-platform-support - Emily: Design - Peggy: Content - Mikki: IA - Jennifer: Usability - Trevor: 508 - Iterate on other team's feedback - [ ] **As soon as feasible and iteration is finished,** request a [Design QA Review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-design-qa.md) ### Content/IA _Share as soon as you have content - this is usually after mockups are created. Get IA review after thumbnails (in case IA informs of a change, get Content review after mockups (provide as much final content to FE for implementation)_ - [ ] Discovery and reference the [VA.gov content style guide](https://design.va.gov/content-style-guide/) - [ ] Reference the [Content/IA best practices](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/content/content-review-process.md) - [ ] Reference the [Content/IA Messaging Dictionary](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Platform/Design%20System/Guidelines/Error%20handling/Dictionary.md) - [ ] Reference the [Error Handling Content Style Guide](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Platform/Design%20System/Guidelines/Error%20handling/Content%20Style%20Guide.md) - [ ] Engage with the Content/IA team as soon as feasible - [ ] Present text/verbiage that is beyond the boilerplate language - [ ] Outline links (hub and spoke), urls, navigation hierarchy, crosslinks/redirects, SEO - [ ] Discuss what parts of the site are templated - [ ] Solicit feedback from Content/IA Team - [ ] Confirm that wayfinding is appropriate - [ ] [Request IA Review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ia-review.md) & [Request a Content Review](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/content/content-review-process.md#how-to-request-content-review) _These links/reviews may end up being consolidated, stay tuned._ - [ ] Before launch, circle back with Content/IA about further impact and feedback ### Usability - [ ] Create a [test plan](https://github.com/department-of-veterans-affairs/vets.gov-team/blob/master/Products/Identity/Personalization/Profile/Direct%20Deposit/Discovery%20&%20Research/Research/Usability%20testing/Research%20Plan.md) - [ ] Is the entry point established? - [ ] Is there a better entry point? - [ ] 508 Compliance - [ ] Review [508 Checklist](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/ebenefits/508-checklist-wip.md) - [ ] [Request 508 Audit](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/508-request-prelaunch-review.md) - [ ] Ensure the feature is tracked within the [508 Product Sheet](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/508-product-review-list.md) ## Development _Do we need to merge the FE and BE tasks?_ ### General Engineering Tasks - [ ] Documentation for quickly addressing when things go wrong - [ ] Establish contacts for oncall support: who do we contact if the application is failing? What kinds of failure modes are likely? ### Backend Tasks - [ ] Investigation of applicable services - [ ] Which API service does this feature use? - [ ] Collaborate with Frontend on Error Handling - [ ] Investigate the common area for error types - [ ] Define or reference a known resource - [ ] For PRs: first review internally with BE or another engineer before the BE Team - [ ] Once internally reviewed, share with the BE Review Team at the VSP (team name?) - [ ] Ensure that [feature flags](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/platform/tools/feature-flags/) are set appropriately to be [toggled](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/engineering/feature-toggles.md) - [ ] Documentation and points of contact for any new backend dependencies - [ ] Links to important dashboards for investigating relevant issues ### Frontend Tasks - [ ] Investigation - [ ] What will be involved in using the API service to pull and display data? - [ ] List and define what the main components will be for the feature to function properly - [ ] Collaborate with Backend on Error Handling - [ ] Investigate the common area for error types - [ ] Define or reference a known resource - [ ] For PRs: first review internally with FE or another engineer before the FE Team - [ ] Once internally reviewed, share with the FE Review Team at the VSP (team name?) - [ ] Ensure that [feature flags](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/platform/tools/feature-flags/) are set appropriately to be [toggled](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/engineering/feature-toggles.md) - [ ] Entrance pages (i.e. supporting static content) in place ### Security/ATO - [ ] Establish who among VSP we should talk to about Security Reviews - [ ] What is the review process? - [ ] Review the [ATO Procedures](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ato-reviews.md) - [ ] Request a [preliminary ATO review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ato-reviews.md#request-a-preliminary-ato-review) - [ ] Request a [pre-launch ATO review](https://github.com/department-of-veterans-affairs/va.gov-vfs-teams/blob/master/Request-Reviews/request-ato-reviews.md#request-a-pre-launch-ato-review) ### QA - [ ] [Documentation](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/quality-assurance) from platform ### Testing - [ ] Create a test plan from an overall engineering perspective - [ ] Build, test, audits (508, content, security, load, CI/CD, passing on all browsers, etc) in a feedback loop - [ ] Code coverage requirements - [ ] Develop testing infrastructure, refer to established documentation - [ ] Define threshold or definition of high-severity bugs - [ ] Document any high-severity bugs for future reference - [ ] Establish contacts for errors to be reported to - [ ] Errors get sent directly to the team - [ ] Establish steps to take to move feature into [staging](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/accessing-staging.md) or within - [ ] Tested in prod with back-of-house people and systems ## Analytics - [ ] Confirm that the new feature/product is stable and visible in staging.va.gov - [ ] Engage with the Analytics Team about what is to be launched - [ ] Review [KPI/metrics spreadsheet](https://docs.google.com/spreadsheets/d/1e9bqzjBnibiCWXWNMcK-fJOw7cjXVdx5M6gmC4phlfg/edit#gid=1554481611) ## Support - [ ] Does the Call Center have documentation? - [ ] Have they asked for anything else? - [ ] What else should we say about ## Pre-release - [ ] Call Center is prepared for launch with updated scripts/documentation as needed - [ ] VA web comms team is aware of this launch and has accurate messaging - [ ] Product Outline is updated - [ ] Downtime UX and error messaging documentation complete - [ ] ""Learn and Improve"" plan written: KPI measurements, analytics reporting, next phase of features to build ## Release Plan - [ ] Refer to in-depth [Release Plan Template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/release-plan-template.md) ## Consider Deliverables and Artifacts - [ ] Ensure that these are noted and stored for easy access - [ ] Include contact information in case further discussion is required ## Launch - [ ] Go/No-go from each team member - [ ] Define what is being tracked - [ ] Define other last minute items - [ ] Review the [Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/release-plan-template.md) ## Post-Mortem - [ ] List and define any issues that impeded the process - [ ] Create post-launch coordination plan including calls with stakeholders and call center - [ ] Coordinate with Call Center to monitor calls - [ ] Ensure monitoring and resolve issues in 24 hours - [ ] Collect and report metrics from Google Analytics - [ ] Schedule regression testing ",1,facility locator ux redesign this epic will track the work and process for the facility locator ux redesign discovery as well as the schedule and attend an orientation of the new feature list endpoints or questions about endpoints design research plan establish process for user interviews create a conversation guide sample ux develop thumbnail map of feature develop wireframes seek applicable feedback obtain understanding from team develop mockups seek applicable feedback obtain understanding from team review process internal review the review the team and dsva share mockups discuss alternates options in a team meeting review the docuementation external review shawna shawna in slack design presentation of mockups might be in a weekly meeting iterate on shawna s feedback other teams authenticated experience global ux etc vfs platform support emily design peggy content mikki ia jennifer usability trevor iterate on other team s feedback as soon as feasible and iteration is finished request a content ia share as soon as you have content this is usually after mockups are created get ia review after thumbnails in case ia informs of a change get content review after mockups provide as much final content to fe for implementation discovery and reference the reference the reference the reference the engage with the content ia team as soon as feasible present text verbiage that is beyond the boilerplate language outline links hub and spoke urls navigation hierarchy crosslinks redirects seo discuss what parts of the site are templated solicit feedback from content ia team confirm that wayfinding is appropriate these links reviews may end up being consolidated stay tuned before launch circle back with content ia about further impact and feedback usability create a is the entry point established is there a better entry point compliance review ensure the feature is tracked within the development do we need to merge the fe and be tasks general engineering tasks documentation for quickly addressing when things go wrong establish contacts for oncall support who do we contact if the application is failing what kinds of failure modes are likely backend tasks investigation of applicable services which api service does this feature use collaborate with frontend on error handling investigate the common area for error types define or reference a known resource for prs first review internally with be or another engineer before the be team once internally reviewed share with the be review team at the vsp team name ensure that are set appropriately to be documentation and points of contact for any new backend dependencies links to important dashboards for investigating relevant issues frontend tasks investigation what will be involved in using the api service to pull and display data list and define what the main components will be for the feature to function properly collaborate with backend on error handling investigate the common area for error types define or reference a known resource for prs first review internally with fe or another engineer before the fe team once internally reviewed share with the fe review team at the vsp team name ensure that are set appropriately to be entrance pages i e supporting static content in place security ato establish who among vsp we should talk to about security reviews what is the review process review the request a request a qa from platform testing create a test plan from an overall engineering perspective build test audits content security load ci cd passing on all browsers etc in a feedback loop code coverage requirements develop testing infrastructure refer to established documentation define threshold or definition of high severity bugs document any high severity bugs for future reference establish contacts for errors to be reported to errors get sent directly to the team establish steps to take to move feature into or within tested in prod with back of house people and systems analytics confirm that the new feature product is stable and visible in staging va gov engage with the analytics team about what is to be launched review support does the call center have documentation have they asked for anything else what else should we say about pre release call center is prepared for launch with updated scripts documentation as needed va web comms team is aware of this launch and has accurate messaging product outline is updated downtime ux and error messaging documentation complete learn and improve plan written kpi measurements analytics reporting next phase of features to build release plan refer to in depth consider deliverables and artifacts ensure that these are noted and stored for easy access include contact information in case further discussion is required launch go no go from each team member define what is being tracked define other last minute items review the post mortem list and define any issues that impeded the process create post launch coordination plan including calls with stakeholders and call center coordinate with call center to monitor calls ensure monitoring and resolve issues in hours collect and report metrics from google analytics schedule regression testing ,1 168894,26710041901.0,IssuesEvent,2023-01-27 22:24:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.3),content design 508/Accessibility ia collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard my-education-benefits enrollment-verification,"### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name Enrollment verification #### VFS feature name #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details You are using the blue address block on dates that are not related to locations. ### Link, screenshot or steps to recreate https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/50480_Allison_040703.png ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Remove the blue left border and indent (address block) throughout the all the page. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.3) - ### General Information #### VFS team name DGIB - My Education Benefits #### VFS product name Enrollment verification #### VFS feature name #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details You are using the blue address block on dates that are not related to locations. ### Link, screenshot or steps to recreate https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/50480_Allison_040703.png ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Remove the blue left border and indent (address block) throughout the all the page. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, design components or patterns don t align with design system guidelines general information vfs team name dgib my education benefits vfs product name enrollment verification vfs feature name point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details you are using the blue address block on dates that are not related to locations link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation remove the blue left border and indent address block throughout the all the page vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 131525,18296125322.0,IssuesEvent,2021-10-05 20:38:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Update COE Mockups to Account for New Doc Visuals,design vsa vsa-ebenefits LGY,"## Description As a user, I want visual confirmation that my documents have been successfully uploaded to LGY, or, I want to be notified that the upload failed and I need to retry. ## Considerations - Though the UI for the document upload feature is complete as of [this pr](https://github.com/department-of-veterans-affairs/vets-website/pull/18558), work to connect to vets-api still needs to be completed. This needs to include making an API call to an endpoint in vets-api that can accept a list of documents. - Existing endpoints (`/v0/claims_attachements` and I think one other?) may not work because they rely on an existing claim ID to associate documents with. - [Current mockups](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/141541271/simulate/sitemap) need to be updated to include visual feedback for when a user clicks `Submit uploaded documents`. Similar to form submission feedback, like direct deposit, with success/failure banners - This can probably be divided into three tickets - Design, FE, and BE, since it's a task that encompasses all three disciplines. ## Tasks - [x] Update existing mockups ## Acceptance Criteria - [x] Mockups have been updated and shared with Team",1.0,"Update COE Mockups to Account for New Doc Visuals - ## Description As a user, I want visual confirmation that my documents have been successfully uploaded to LGY, or, I want to be notified that the upload failed and I need to retry. ## Considerations - Though the UI for the document upload feature is complete as of [this pr](https://github.com/department-of-veterans-affairs/vets-website/pull/18558), work to connect to vets-api still needs to be completed. This needs to include making an API call to an endpoint in vets-api that can accept a list of documents. - Existing endpoints (`/v0/claims_attachements` and I think one other?) may not work because they rely on an existing claim ID to associate documents with. - [Current mockups](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/141541271/simulate/sitemap) need to be updated to include visual feedback for when a user clicks `Submit uploaded documents`. Similar to form submission feedback, like direct deposit, with success/failure banners - This can probably be divided into three tickets - Design, FE, and BE, since it's a task that encompasses all three disciplines. ## Tasks - [x] Update existing mockups ## Acceptance Criteria - [x] Mockups have been updated and shared with Team",1,update coe mockups to account for new doc visuals description as a user i want visual confirmation that my documents have been successfully uploaded to lgy or i want to be notified that the upload failed and i need to retry considerations though the ui for the document upload feature is complete as of work to connect to vets api still needs to be completed this needs to include making an api call to an endpoint in vets api that can accept a list of documents existing endpoints claims attachements and i think one other may not work because they rely on an existing claim id to associate documents with need to be updated to include visual feedback for when a user clicks submit uploaded documents similar to form submission feedback like direct deposit with success failure banners this can probably be divided into three tickets design fe and be since it s a task that encompasses all three disciplines tasks update existing mockups acceptance criteria mockups have been updated and shared with team,1 174106,27578641753.0,IssuesEvent,2023-03-08 14:46:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Finish initial wireframes ,content design ux HCE-Checkin,"## Description Finish remaining tasks for the initial set of wireframes for the unified experience. ## Tasks ### Priorities - [ ] Relocate all wireframes and components that aren't being used (Christina) - [ ] Add the ""you have other appointments to review"" component (4 different variations of content) to the four wireframes (Zach) - [ ] Swap out all the action links and alerts with the work that Ya-ching did (Christina) https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/zx92Zoe?annotation=bc467411-6d8a-4e81-95fb-c4a00ae90b8a ### Other tasks - [ ] Review all spacing and convert components to symbols (Zach) - [ ] Address spacing when there's no cards or alerts - https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/m1ZqWLJ?annotation=df3422f7-a6e2-4d8d-ab8c-9c6759433451 - [ ] Some wires still need to be updated to use upcoming and past links - [ ] Review with accessibility (Christina) - [ ] Action link location on appointment details page - https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/Om9P834?annotation=b0470109-643e-433c-a418-c5d68e2ae404 - [ ] Heading for the no appointments wireframe - [ ] Content on the pre check in introduction page (Ben & Kelly) - [ ] Are we reordering components on our confirmation pages based on the decisions and discussions that have or are happening with Zach, Kelly and Ya-ching about the travel reimbursement confirmation pages? https://staging.va.gov/health-care/appointment-check-in/error?error=refresh-on-details - [ ] Finish the phone appointment confirmation page (Zach) https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/ZVMMD93?annotation=84f3bfec-ed6f-498e-afd1-de251263f8fb - [ ] Review content on check in confirmation about way finding at the clinic (Ben) - https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/PGgw5vx?annotation=b7b48660-5164-4e2a-8edf-fb845fbafe24 - [ ] Provide annotations, where needed, for site wide content and IA and engineers. For example, notification that uses singular vs plural, variations of footer, etc. (Ben) - [ ] Final walk through with Kelly to review from a content perspective ### Lowest priorities - [ ] Ask Peter and Ciera about the heading for the no appointments wireframe - [ ] Remove timezone (ET) from all appointments (talk to Zach and Christina in case they're converting appointments to symbols) ",1.0,"Finish initial wireframes - ## Description Finish remaining tasks for the initial set of wireframes for the unified experience. ## Tasks ### Priorities - [ ] Relocate all wireframes and components that aren't being used (Christina) - [ ] Add the ""you have other appointments to review"" component (4 different variations of content) to the four wireframes (Zach) - [ ] Swap out all the action links and alerts with the work that Ya-ching did (Christina) https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/zx92Zoe?annotation=bc467411-6d8a-4e81-95fb-c4a00ae90b8a ### Other tasks - [ ] Review all spacing and convert components to symbols (Zach) - [ ] Address spacing when there's no cards or alerts - https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/m1ZqWLJ?annotation=df3422f7-a6e2-4d8d-ab8c-9c6759433451 - [ ] Some wires still need to be updated to use upcoming and past links - [ ] Review with accessibility (Christina) - [ ] Action link location on appointment details page - https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/Om9P834?annotation=b0470109-643e-433c-a418-c5d68e2ae404 - [ ] Heading for the no appointments wireframe - [ ] Content on the pre check in introduction page (Ben & Kelly) - [ ] Are we reordering components on our confirmation pages based on the decisions and discussions that have or are happening with Zach, Kelly and Ya-ching about the travel reimbursement confirmation pages? https://staging.va.gov/health-care/appointment-check-in/error?error=refresh-on-details - [ ] Finish the phone appointment confirmation page (Zach) https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/ZVMMD93?annotation=84f3bfec-ed6f-498e-afd1-de251263f8fb - [ ] Review content on check in confirmation about way finding at the clinic (Ben) - https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/PGgw5vx?annotation=b7b48660-5164-4e2a-8edf-fb845fbafe24 - [ ] Provide annotations, where needed, for site wide content and IA and engineers. For example, notification that uses singular vs plural, variations of footer, etc. (Ben) - [ ] Final walk through with Kelly to review from a content perspective ### Lowest priorities - [ ] Ask Peter and Ciera about the heading for the no appointments wireframe - [ ] Remove timezone (ET) from all appointments (talk to Zach and Christina in case they're converting appointments to symbols) ",1,finish initial wireframes description finish remaining tasks for the initial set of wireframes for the unified experience tasks priorities relocate all wireframes and components that aren t being used christina add the you have other appointments to review component different variations of content to the four wireframes zach swap out all the action links and alerts with the work that ya ching did christina other tasks review all spacing and convert components to symbols zach address spacing when there s no cards or alerts some wires still need to be updated to use upcoming and past links review with accessibility christina action link location on appointment details page heading for the no appointments wireframe content on the pre check in introduction page ben kelly are we reordering components on our confirmation pages based on the decisions and discussions that have or are happening with zach kelly and ya ching about the travel reimbursement confirmation pages finish the phone appointment confirmation page zach review content on check in confirmation about way finding at the clinic ben provide annotations where needed for site wide content and ia and engineers for example notification that uses singular vs plural variations of footer etc ben final walk through with kelly to review from a content perspective lowest priorities ask peter and ciera about the heading for the no appointments wireframe remove timezone et from all appointments talk to zach and christina in case they re converting appointments to symbols ,1 108341,13617136029.0,IssuesEvent,2020-09-23 16:33:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[FE] ""Invalid date"" on Military History period of service",Blocked by Design frontend needs-grooming profile vsa-authenticated-exp,"## Background ""invalid date"" was displayed in the on the period of service date section of Military information. This could be due to the fact that Veteran was still currently active in the military. https://dsva.slack.com/archives/C909ZG2BB/p1599062697061300 ![image.png](https://images.zenhubusercontent.com/5e41b49969d880e9f4f122b1/3f67744b-5613-466a-83d9-7c30be1d3912) ## Tasks - [ ] Update the ""invalid date"" bug",1.0,"[FE] ""Invalid date"" on Military History period of service - ## Background ""invalid date"" was displayed in the on the period of service date section of Military information. This could be due to the fact that Veteran was still currently active in the military. https://dsva.slack.com/archives/C909ZG2BB/p1599062697061300 ![image.png](https://images.zenhubusercontent.com/5e41b49969d880e9f4f122b1/3f67744b-5613-466a-83d9-7c30be1d3912) ## Tasks - [ ] Update the ""invalid date"" bug",1, invalid date on military history period of service background invalid date was displayed in the on the period of service date section of military information this could be due to the fact that veteran was still currently active in the military tasks update the invalid date bug,1 108647,13644980951.0,IssuesEvent,2020-09-25 19:54:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[FE] Build error alert for when Veterans are not being reported as Veterans ,Blocked by Design frontend profile vsa-authenticated-exp,"## Background See Design ticket: [Design] Error alert when we cant verify a person is a veteran/info is not available #13224 See Slack convo:: https://dsva.slack.com/archives/C909ZG2BB/p1599156467141700 During UAT a Veteran did not show up in the system as being a Veteran with Military Information. We should tell users when they aren't reported as being a veteran. We should let users know so they can fix it if they want to. ## Tasks - [ ] Build updated error alert",1.0,"[FE] Build error alert for when Veterans are not being reported as Veterans - ## Background See Design ticket: [Design] Error alert when we cant verify a person is a veteran/info is not available #13224 See Slack convo:: https://dsva.slack.com/archives/C909ZG2BB/p1599156467141700 During UAT a Veteran did not show up in the system as being a Veteran with Military Information. We should tell users when they aren't reported as being a veteran. We should let users know so they can fix it if they want to. ## Tasks - [ ] Build updated error alert",1, build error alert for when veterans are not being reported as veterans background see design ticket error alert when we cant verify a person is a veteran info is not available see slack convo during uat a veteran did not show up in the system as being a veteran with military information we should tell users when they aren t reported as being a veteran we should let users know so they can fix it if they want to tasks build updated error alert,1 165222,26125468479.0,IssuesEvent,2022-12-28 17:52:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Research NPS utility, pros, cons for our purposes",service-design,"## Issue Description We're considering how and if to continue with an NPS as it currently exists in the Qtrly Satisfaction Survey. This could take the form of multiple questions about areas/spaces/tasks. What are the pros to NPS? Cons? Is it relevant given the fixed audience of the Platform? ## Tasks - [ ] Research topic - [ ] Generate Confluence page with key learnings ## Acceptance Criteria - [ ] Confluence page reflects actionable takeaways",1.0,"Research NPS utility, pros, cons for our purposes - ## Issue Description We're considering how and if to continue with an NPS as it currently exists in the Qtrly Satisfaction Survey. This could take the form of multiple questions about areas/spaces/tasks. What are the pros to NPS? Cons? Is it relevant given the fixed audience of the Platform? ## Tasks - [ ] Research topic - [ ] Generate Confluence page with key learnings ## Acceptance Criteria - [ ] Confluence page reflects actionable takeaways",1,research nps utility pros cons for our purposes issue description we re considering how and if to continue with an nps as it currently exists in the qtrly satisfaction survey this could take the form of multiple questions about areas spaces tasks what are the pros to nps cons is it relevant given the fixed audience of the platform tasks research topic generate confluence page with key learnings acceptance criteria confluence page reflects actionable takeaways,1 108954,13696756197.0,IssuesEvent,2020-10-01 01:00:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Design - 10-10CG Improvements post launch ,design,"## Issue Description --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Design - 10-10CG Improvements post launch - ## Issue Description --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,design improvements post launch issue description tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 181335,30669599280.0,IssuesEvent,2023-07-25 21:09:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[SPIKE] Retry new idea for appt statuses,design ux HCE-Checkin,"## Description At design system meeting, Matt gave some feedback: * Status: has 4 variations (you checked in at, you can check in at, [confirmed, it's been reviewed](https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/nQDYAdl)) * But, we can also try ""You checked in at 8:55am"" with a checkmark to make that one distinct. * And, then we need to make these updates on the detail pages too. https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1889 In the future: we could add more statuses, e.g., ""you can't check in any longer"" ## Tasks - [ ] Create wires with no status idea(s) - [ ] Create artboards for each time of day (so they can user flow of the statuses) - [ ] Represent to DS platform team (try to attend first Tuesday meeting) ## AC - [ ] Create wires with no status idea(s) - [ ] Create artboards for each time of day (so they can user flow of the statuses) - [ ] Represent to DS platform team - ",1.0,"[SPIKE] Retry new idea for appt statuses - ## Description At design system meeting, Matt gave some feedback: * Status: has 4 variations (you checked in at, you can check in at, [confirmed, it's been reviewed](https://www.sketch.com/s/0e890de3-2530-4ee0-986e-cf0314334aec/a/nQDYAdl)) * But, we can also try ""You checked in at 8:55am"" with a checkmark to make that one distinct. * And, then we need to make these updates on the detail pages too. https://github.com/department-of-veterans-affairs/vets-design-system-documentation/issues/1889 In the future: we could add more statuses, e.g., ""you can't check in any longer"" ## Tasks - [ ] Create wires with no status idea(s) - [ ] Create artboards for each time of day (so they can user flow of the statuses) - [ ] Represent to DS platform team (try to attend first Tuesday meeting) ## AC - [ ] Create wires with no status idea(s) - [ ] Create artboards for each time of day (so they can user flow of the statuses) - [ ] Represent to DS platform team - ",1, retry new idea for appt statuses description at design system meeting matt gave some feedback status has variations you checked in at you can check in at but we can also try you checked in at with a checkmark to make that one distinct and then we need to make these updates on the detail pages too in the future we could add more statuses e g you can t check in any longer tasks create wires with no status idea s create artboards for each time of day so they can user flow of the statuses represent to ds platform team try to attend first tuesday meeting ac create wires with no status idea s create artboards for each time of day so they can user flow of the statuses represent to ds platform team ,1 165757,26222192488.0,IssuesEvent,2023-01-04 15:39:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Work to match Project Intake Funnels to Current+Desired State,service-design,"## Issue Description Continued work to match our workflow to the shared understanding of Octo and Leadership ## Preliminary Work Lucidchart [workflow](https://lucid.app/lucidchart/e2d771f0-6d82-4f13-8411-9e983ec0687d/edit?invitationId=inv_fc1e26fe-e5c7-4a42-902d-2999a568b8b6&page=0_0#) to capture existing process along with clarifications/simplifications ## Tasks - [x] Work to get accurate representation of Intake funnels ## Outcome Currently representing an ""Other"" intake funnel on the map since the methodology isn't fully refined yet on the part of Leadership.",1.0,"Work to match Project Intake Funnels to Current+Desired State - ## Issue Description Continued work to match our workflow to the shared understanding of Octo and Leadership ## Preliminary Work Lucidchart [workflow](https://lucid.app/lucidchart/e2d771f0-6d82-4f13-8411-9e983ec0687d/edit?invitationId=inv_fc1e26fe-e5c7-4a42-902d-2999a568b8b6&page=0_0#) to capture existing process along with clarifications/simplifications ## Tasks - [x] Work to get accurate representation of Intake funnels ## Outcome Currently representing an ""Other"" intake funnel on the map since the methodology isn't fully refined yet on the part of Leadership.",1,work to match project intake funnels to current desired state issue description continued work to match our workflow to the shared understanding of octo and leadership preliminary work lucidchart to capture existing process along with clarifications simplifications tasks work to get accurate representation of intake funnels outcome currently representing an other intake funnel on the map since the methodology isn t fully refined yet on the part of leadership ,1 160448,25165356632.0,IssuesEvent,2022-11-10 20:19:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My VA Audit UX Improvements: Update LOA1 State Designs,design my-va-dashboard authenticated-experience my-va-audit,"## Background During Midpoint Review we received feedback around our design of the LOA1 state on My VA. Feedback is documented [here](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2022-audit/MidpointReview.md). This ticket is to update the designs for LOA1 based on content feedback. Feedback on this topic can be found in these tickets: * #48624 -- Must feedback * #48655 -- Must feedback ## Tasks - [x] Use em dash instead of plain dash in this sentence “We need to make sure you're you—and not someone pretending to be you—before we can give you access to your personal and health-related information.” (longer dash, this – vs - ) - [x] Update Sketch files and FE Documentation - [ ] PM to check FE tickets and update accordingly ## Acceptance Criteria - [ ] New designs for LOA1 State are complete ",1.0,"[Design] My VA Audit UX Improvements: Update LOA1 State Designs - ## Background During Midpoint Review we received feedback around our design of the LOA1 state on My VA. Feedback is documented [here](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2022-audit/MidpointReview.md). This ticket is to update the designs for LOA1 based on content feedback. Feedback on this topic can be found in these tickets: * #48624 -- Must feedback * #48655 -- Must feedback ## Tasks - [x] Use em dash instead of plain dash in this sentence “We need to make sure you're you—and not someone pretending to be you—before we can give you access to your personal and health-related information.” (longer dash, this – vs - ) - [x] Update Sketch files and FE Documentation - [ ] PM to check FE tickets and update accordingly ## Acceptance Criteria - [ ] New designs for LOA1 State are complete ",1, my va audit ux improvements update state designs background during midpoint review we received feedback around our design of the state on my va feedback is documented this ticket is to update the designs for based on content feedback feedback on this topic can be found in these tickets must feedback must feedback tasks use em dash instead of plain dash in this sentence “we need to make sure you re you—and not someone pretending to be you—before we can give you access to your personal and health related information ” longer dash this – vs update sketch files and fe documentation pm to check fe tickets and update accordingly acceptance criteria new designs for state are complete ,1 116487,14969672292.0,IssuesEvent,2021-01-27 18:28:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Display or Provide Link to Decision Letter,Letters design vsa vsa-benefits,"## User Story As a veteran, I want Kevin to provide the best experience possible when viewing my decision letters. ## Expected Behavior Take another look at the design (and accessibility) for the #13405 ticket. ## Acceptance Criteria - [ ] TBD",1.0,"Display or Provide Link to Decision Letter - ## User Story As a veteran, I want Kevin to provide the best experience possible when viewing my decision letters. ## Expected Behavior Take another look at the design (and accessibility) for the #13405 ticket. ## Acceptance Criteria - [ ] TBD",1,display or provide link to decision letter user story as a veteran i want kevin to provide the best experience possible when viewing my decision letters expected behavior take another look at the design and accessibility for the ticket acceptance criteria tbd,1 117748,15170178906.0,IssuesEvent,2021-02-12 22:39:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Remove moment from component-library,components frontend vsp-design-system-team,"## Issue Description The `moment` dependency is in [maintenance-only mode](https://momentjs.com/docs/#/-project-status/). This, combined with the fact that `moment` contributes to a significantly larger bundle size, are good reasons why we should switch to `date-fns` in the `component-library`. This transition has already begun: https://github.com/department-of-veterans-affairs/component-library/pull/33 --- ## Acceptance Criteria - [ ] Unused functions in `validations.js` file which rely on moment are removed - [ ] Components which import `moment` (``, ``) are refactored to use `date-fns` and the standard Date object) - [ ] `moment` is no longer a dependency in `component-library` ",1.0,"Remove moment from component-library - ## Issue Description The `moment` dependency is in [maintenance-only mode](https://momentjs.com/docs/#/-project-status/). This, combined with the fact that `moment` contributes to a significantly larger bundle size, are good reasons why we should switch to `date-fns` in the `component-library`. This transition has already begun: https://github.com/department-of-veterans-affairs/component-library/pull/33 --- ## Acceptance Criteria - [ ] Unused functions in `validations.js` file which rely on moment are removed - [ ] Components which import `moment` (``, ``) are refactored to use `date-fns` and the standard Date object) - [ ] `moment` is no longer a dependency in `component-library` ",1,remove moment from component library issue description the moment dependency is in this combined with the fact that moment contributes to a significantly larger bundle size are good reasons why we should switch to date fns in the component library this transition has already begun acceptance criteria unused functions in validations js file which rely on moment are removed components which import moment are refactored to use date fns and the standard date object moment is no longer a dependency in component library ,1 121520,15954753677.0,IssuesEvent,2021-04-15 13:55:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Documentation request for On this page component,content-ia-team design-system-update documentation-support vsp-design-system-team,"### What is your documentation request, question, comment, or issue? The design system team needs assistance with checking a piece of documentation for the ""On this page"" component: https://design.va.gov/components/on-this-page-jump-links I'm writing documentation for the sections: ""Usability guidance: how to"" and ""Accessibility"" I spoke with VFS designers, product owners, and accessibility specialists to gather information. I followed the format of the USWDS documentation for their design system components. Ex: https://designsystem.digital.gov/components/card/ Note: I based the first accessibility point after this ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/7877 Here is the current draft: **Usability Guidance** - **Make sure to keep the first link and its corresponding heading close together.** Keeping the links and headings in close proximity helps users make the connection that the links correspond to sections on the page - **For content pages, have a minimum of 2 H2 sections.** The article will have to have a minimum of 2 H2 sections in order to display the On this page component links. - **Do not use components for very short sections if we can display sections on one screen.** If using this component for 2 sections, do not use component if sections are very short. **Accessibility** - **Heading levels should only increase by one.** Proper order of heading levels convey the structure of the page for users who use screen readers. When heading elements are applied correctly, the page becomes much easier to navigate for screen reader users and sighted users alike. - **Focus should be on the destination.** When a user clicks an item in on this page component, focus should move to the heading that it’s linked to. - **Allow enough spacing between components.** Space should be 1.5 rem (36px) from the bottom of the descender to the top of the ascender ",2.0,"Documentation request for On this page component - ### What is your documentation request, question, comment, or issue? The design system team needs assistance with checking a piece of documentation for the ""On this page"" component: https://design.va.gov/components/on-this-page-jump-links I'm writing documentation for the sections: ""Usability guidance: how to"" and ""Accessibility"" I spoke with VFS designers, product owners, and accessibility specialists to gather information. I followed the format of the USWDS documentation for their design system components. Ex: https://designsystem.digital.gov/components/card/ Note: I based the first accessibility point after this ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/7877 Here is the current draft: **Usability Guidance** - **Make sure to keep the first link and its corresponding heading close together.** Keeping the links and headings in close proximity helps users make the connection that the links correspond to sections on the page - **For content pages, have a minimum of 2 H2 sections.** The article will have to have a minimum of 2 H2 sections in order to display the On this page component links. - **Do not use components for very short sections if we can display sections on one screen.** If using this component for 2 sections, do not use component if sections are very short. **Accessibility** - **Heading levels should only increase by one.** Proper order of heading levels convey the structure of the page for users who use screen readers. When heading elements are applied correctly, the page becomes much easier to navigate for screen reader users and sighted users alike. - **Focus should be on the destination.** When a user clicks an item in on this page component, focus should move to the heading that it’s linked to. - **Allow enough spacing between components.** Space should be 1.5 rem (36px) from the bottom of the descender to the top of the ascender ",1,documentation request for on this page component what is your documentation request question comment or issue the design system team needs assistance with checking a piece of documentation for the on this page component i m writing documentation for the sections usability guidance how to and accessibility i spoke with vfs designers product owners and accessibility specialists to gather information i followed the format of the uswds documentation for their design system components ex note i based the first accessibility point after this ticket here is the current draft usability guidance make sure to keep the first link and its corresponding heading close together keeping the links and headings in close proximity helps users make the connection that the links correspond to sections on the page for content pages have a minimum of sections the article will have to have a minimum of sections in order to display the on this page component links do not use components for very short sections if we can display sections on one screen if using this component for sections do not use component if sections are very short accessibility heading levels should only increase by one proper order of heading levels convey the structure of the page for users who use screen readers when heading elements are applied correctly the page becomes much easier to navigate for screen reader users and sighted users alike focus should be on the destination when a user clicks an item in on this page component focus should move to the heading that it’s linked to allow enough spacing between components space should be rem from the bottom of the descender to the top of the ascender ,1 142891,21902861936.0,IssuesEvent,2022-05-20 14:58:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Determine the updated Scope and Purpose of Service Design Team,Epic service-design platform-initiative crew-platform team-platform-service-design FY22-Q2,"## Confluence Space [Mission](https://vfs.atlassian.net/wiki/spaces/SDT/overview) ## High Level User Stories As a member of the Service Design Team, I need to know what my team is responsible for so that I can stay within my boundaries and provide value where it's needed. As Platform leadership or a team member, I want to understand the team's purpose so I know how or when to utilize the SDT or their offerings. ## Hypothesis or Bet **If** we dedicate time to clearly define the Scope of the Service Design Team **then** then we can ensure the team will be able to better understand and pursue its mission to best support the Platform_. By clearly defining the Scope of the SDT, Platform team members will better understand when to engage with the SDT or its offerings. ## Definition of done **The SDT mission statement and product/service offerings will be updated to better support the Platform's mission via the lens of Service Design.** - [x] The team's updated [mission statement](https://vfs.atlassian.net/wiki/spaces/SDT/overview#Mission) is documented. - [x] The team's [current product offerings](https://vfs.atlassian.net/wiki/spaces/SDT/overview#Tools-%26-Services) are documented. ",2.0,"Determine the updated Scope and Purpose of Service Design Team - ## Confluence Space [Mission](https://vfs.atlassian.net/wiki/spaces/SDT/overview) ## High Level User Stories As a member of the Service Design Team, I need to know what my team is responsible for so that I can stay within my boundaries and provide value where it's needed. As Platform leadership or a team member, I want to understand the team's purpose so I know how or when to utilize the SDT or their offerings. ## Hypothesis or Bet **If** we dedicate time to clearly define the Scope of the Service Design Team **then** then we can ensure the team will be able to better understand and pursue its mission to best support the Platform_. By clearly defining the Scope of the SDT, Platform team members will better understand when to engage with the SDT or its offerings. ## Definition of done **The SDT mission statement and product/service offerings will be updated to better support the Platform's mission via the lens of Service Design.** - [x] The team's updated [mission statement](https://vfs.atlassian.net/wiki/spaces/SDT/overview#Mission) is documented. - [x] The team's [current product offerings](https://vfs.atlassian.net/wiki/spaces/SDT/overview#Tools-%26-Services) are documented. ",1,determine the updated scope and purpose of service design team confluence space high level user stories as a member of the service design team i need to know what my team is responsible for so that i can stay within my boundaries and provide value where it s needed as platform leadership or a team member i want to understand the team s purpose so i know how or when to utilize the sdt or their offerings hypothesis or bet if we dedicate time to clearly define the scope of the service design team then then we can ensure the team will be able to better understand and pursue its mission to best support the platform by clearly defining the scope of the sdt platform team members will better understand when to engage with the sdt or its offerings definition of done the sdt mission statement and product service offerings will be updated to better support the platform s mission via the lens of service design the team s updated is documented the team s are documented ,1 142316,21715128409.0,IssuesEvent,2022-05-10 17:07:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Review of upcoming RT team Communication Plan,service-design,"## Issue Description Meet w/ team PM to discuss Comm plan for a feature change. --- ## Tasks - [ ] Review plan - [ ] Discuss in workshop w/ RT team PM ## Acceptance Criteria - [ ] Questions and discussion [documented](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2184937681/Communication+Plan+review+w+Release+Tools).",1.0,"Review of upcoming RT team Communication Plan - ## Issue Description Meet w/ team PM to discuss Comm plan for a feature change. --- ## Tasks - [ ] Review plan - [ ] Discuss in workshop w/ RT team PM ## Acceptance Criteria - [ ] Questions and discussion [documented](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2184937681/Communication+Plan+review+w+Release+Tools).",1,review of upcoming rt team communication plan issue description meet w team pm to discuss comm plan for a feature change tasks review plan discuss in workshop w rt team pm acceptance criteria questions and discussion ,1 322190,23896166410.0,IssuesEvent,2022-09-08 14:55:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Q3 2022 IET - Create Microservices Deploy Playbook,Epic documentation platform-initiative integration-experience crew-platform PO Endorsed platform-okrs FY22-Q3,"## Overview This Epic will provide a “How to create microservices” guide (playbook) that will include a reference to each of the tools an Engineering Development Team will need to support a microservice architecture in Vets-API and the process by which a service can be extracted from the Vet-API monolith application that includes a large number of services. ## Problem Statement The current Vets-API is in the form of a monolith code base that is large and complicated without a clear separation of boundaries between services, which makes it difficult to support ZTA (Zero Trust Architecture). A shift to creating microservices will help create an architecture that will enforce boundaries, reduce complexity and make it much easier to support. IET has been investigating the feasibility of this architectural shift and will provide a summary of recommendations for future microservices development. IET also wants to consolidate what they have learned in a form that can easily be consumed by other development engineers who wish to create their own microservices. ## Hypothesis or Bet Documenting how to extract services from the Vet-API monolith application to create microservices will make it easier for us to further our goal of enabling other engineering development teams to extract and build microservices. ## Definition of Done - A completed ""how to"" microservices playbook that is readily available for other engineering development teams to consume. ## Desired Business Outcomes - IET will have produced a microservices playbook that can be easily consumed and understood by other development engineers. - Engineers will use this microservices playbook as a guide to successfully extract services from the Vet-API monolith application and build out microservices. ## Undesired Business Outcomes - Development engineers have trouble following the microservices playbook and are unable to successfully create microservices from the Vets-API monolith application. - The microservices playbook is not used and microservices work is put on a shelf and never revisited. --- ## Measuring Success ### Objectives and Key results (OKRs) - Objective: - Key result: IET will produce a microservices playbook by Sept 11, 2022. - Key result: IET will drive the Sidekig UI service from the development environment to the Production Environment in Q3. The knowledge gained during this process will create basis for the Microservices playbook. - Key result: IET will produce a microservices playbook that is considered to be easily consumed and understood by other development engineers as verified by pre-selected development engineers who will review the microservices playbook. NOTE: This Epic refers to a playbooks document that will provide guidance for how to take a microservice through the various development stages including: Development, Staging and Production. Driving Sidekiq UI to Production is covered in another Epic #40061 and will be transitioned to the Console Services Team as part of that Epic. --- ## Assumptions - Information will be readily available to completely understand the Vet-API monolith application architecture. - IET understands the Vets-API monolith well enough to successfully document how to extract services and create microservices. - There will be enough time in Q3 2022 for IET to complete the microservices playbook. - Risks: - The Vets-API is built using the Ruby coding language and IET has one resource with Ruby experience (Emily W.) - IET will find something in the Vets-API architecture that is challenging to interpret and make it difficult to document extracting a service. - IET runs out of time in Q3 2022 to complete the microservices playbook. ## Solution Approach - The microservices playbook will be designed to provide guidance on the necessary steps for extracting services and creating microservices from the current Vets-API monolith application. In brief, the microservices playbook will include but not be limited to things such as: - A checklist for items needed for deployment - Vets-API architecture - Microservice design - Continuous Integration/Continuous Deployment (CI/CD) build process - Logging & monitoring to ensure things are operating properly - How to deprecate a Vets-API service - Reference documentation --- ## Go-to-market Strategy - The microservices playbook is an internal document to be made available to development engineers. The playbook will be placed in locations where these engineers would normally consume documentation. - For example the microservices playbook will be placed on Confluence, Github and other locations deemed appropriate. --- ### Current Status - In-Progress ### Key Decision(s) - Do we understand the Vets-API monolith application well enough to document how to extract a service and create a microservice. --- #### Communications
- Team Name: IET - GitHub Label: Integration-Experience - Slack channel: PST-Integration-Experience - Product POCs: Frank Hiatt (PM), Emily Wilson (TL), Thomas Delrue (PO) - Stakeholders:
#### Team Members
- DEPO Lead: - PM: Frank Hiatt - Engineering: Emily Wilson, Igor Yegorov, Salvadore Gutierrez, Will Huang - Research/Design:
#### Stakeholders - Platform leadership - Platform Teams
_What offices/departments are critical to make this initiative successful?_
",1.0,"Q3 2022 IET - Create Microservices Deploy Playbook - ## Overview This Epic will provide a “How to create microservices” guide (playbook) that will include a reference to each of the tools an Engineering Development Team will need to support a microservice architecture in Vets-API and the process by which a service can be extracted from the Vet-API monolith application that includes a large number of services. ## Problem Statement The current Vets-API is in the form of a monolith code base that is large and complicated without a clear separation of boundaries between services, which makes it difficult to support ZTA (Zero Trust Architecture). A shift to creating microservices will help create an architecture that will enforce boundaries, reduce complexity and make it much easier to support. IET has been investigating the feasibility of this architectural shift and will provide a summary of recommendations for future microservices development. IET also wants to consolidate what they have learned in a form that can easily be consumed by other development engineers who wish to create their own microservices. ## Hypothesis or Bet Documenting how to extract services from the Vet-API monolith application to create microservices will make it easier for us to further our goal of enabling other engineering development teams to extract and build microservices. ## Definition of Done - A completed ""how to"" microservices playbook that is readily available for other engineering development teams to consume. ## Desired Business Outcomes - IET will have produced a microservices playbook that can be easily consumed and understood by other development engineers. - Engineers will use this microservices playbook as a guide to successfully extract services from the Vet-API monolith application and build out microservices. ## Undesired Business Outcomes - Development engineers have trouble following the microservices playbook and are unable to successfully create microservices from the Vets-API monolith application. - The microservices playbook is not used and microservices work is put on a shelf and never revisited. --- ## Measuring Success ### Objectives and Key results (OKRs) - Objective: - Key result: IET will produce a microservices playbook by Sept 11, 2022. - Key result: IET will drive the Sidekig UI service from the development environment to the Production Environment in Q3. The knowledge gained during this process will create basis for the Microservices playbook. - Key result: IET will produce a microservices playbook that is considered to be easily consumed and understood by other development engineers as verified by pre-selected development engineers who will review the microservices playbook. NOTE: This Epic refers to a playbooks document that will provide guidance for how to take a microservice through the various development stages including: Development, Staging and Production. Driving Sidekiq UI to Production is covered in another Epic #40061 and will be transitioned to the Console Services Team as part of that Epic. --- ## Assumptions - Information will be readily available to completely understand the Vet-API monolith application architecture. - IET understands the Vets-API monolith well enough to successfully document how to extract services and create microservices. - There will be enough time in Q3 2022 for IET to complete the microservices playbook. - Risks: - The Vets-API is built using the Ruby coding language and IET has one resource with Ruby experience (Emily W.) - IET will find something in the Vets-API architecture that is challenging to interpret and make it difficult to document extracting a service. - IET runs out of time in Q3 2022 to complete the microservices playbook. ## Solution Approach - The microservices playbook will be designed to provide guidance on the necessary steps for extracting services and creating microservices from the current Vets-API monolith application. In brief, the microservices playbook will include but not be limited to things such as: - A checklist for items needed for deployment - Vets-API architecture - Microservice design - Continuous Integration/Continuous Deployment (CI/CD) build process - Logging & monitoring to ensure things are operating properly - How to deprecate a Vets-API service - Reference documentation --- ## Go-to-market Strategy - The microservices playbook is an internal document to be made available to development engineers. The playbook will be placed in locations where these engineers would normally consume documentation. - For example the microservices playbook will be placed on Confluence, Github and other locations deemed appropriate. --- ### Current Status - In-Progress ### Key Decision(s) - Do we understand the Vets-API monolith application well enough to document how to extract a service and create a microservice. --- #### Communications
- Team Name: IET - GitHub Label: Integration-Experience - Slack channel: PST-Integration-Experience - Product POCs: Frank Hiatt (PM), Emily Wilson (TL), Thomas Delrue (PO) - Stakeholders:
#### Team Members
- DEPO Lead: - PM: Frank Hiatt - Engineering: Emily Wilson, Igor Yegorov, Salvadore Gutierrez, Will Huang - Research/Design:
#### Stakeholders - Platform leadership - Platform Teams
_What offices/departments are critical to make this initiative successful?_
",0, iet create microservices deploy playbook overview this epic will provide a “how to create microservices” guide playbook that will include a reference to each of the tools an engineering development team will need to support a microservice architecture in vets api and the process by which a service can be extracted from the vet api monolith application that includes a large number of services problem statement the current vets api is in the form of a monolith code base that is large and complicated without a clear separation of boundaries between services which makes it difficult to support zta zero trust architecture a shift to creating microservices will help create an architecture that will enforce boundaries reduce complexity and make it much easier to support iet has been investigating the feasibility of this architectural shift and will provide a summary of recommendations for future microservices development iet also wants to consolidate what they have learned in a form that can easily be consumed by other development engineers who wish to create their own microservices hypothesis or bet documenting how to extract services from the vet api monolith application to create microservices will make it easier for us to further our goal of enabling other engineering development teams to extract and build microservices definition of done a completed how to microservices playbook that is readily available for other engineering development teams to consume desired business outcomes iet will have produced a microservices playbook that can be easily consumed and understood by other development engineers engineers will use this microservices playbook as a guide to successfully extract services from the vet api monolith application and build out microservices undesired business outcomes development engineers have trouble following the microservices playbook and are unable to successfully create microservices from the vets api monolith application the microservices playbook is not used and microservices work is put on a shelf and never revisited measuring success objectives and key results okrs objective key result iet will produce a microservices playbook by sept key result iet will drive the sidekig ui service from the development environment to the production environment in the knowledge gained during this process will create basis for the microservices playbook key result iet will produce a microservices playbook that is considered to be easily consumed and understood by other development engineers as verified by pre selected development engineers who will review the microservices playbook note this epic refers to a playbooks document that will provide guidance for how to take a microservice through the various development stages including development staging and production driving sidekiq ui to production is covered in another epic and will be transitioned to the console services team as part of that epic assumptions information will be readily available to completely understand the vet api monolith application architecture iet understands the vets api monolith well enough to successfully document how to extract services and create microservices there will be enough time in for iet to complete the microservices playbook risks the vets api is built using the ruby coding language and iet has one resource with ruby experience emily w iet will find something in the vets api architecture that is challenging to interpret and make it difficult to document extracting a service iet runs out of time in to complete the microservices playbook solution approach the microservices playbook will be designed to provide guidance on the necessary steps for extracting services and creating microservices from the current vets api monolith application in brief the microservices playbook will include but not be limited to things such as a checklist for items needed for deployment vets api architecture microservice design continuous integration continuous deployment ci cd build process logging monitoring to ensure things are operating properly how to deprecate a vets api service reference documentation go to market strategy the microservices playbook is an internal document to be made available to development engineers the playbook will be placed in locations where these engineers would normally consume documentation for example the microservices playbook will be placed on confluence github and other locations deemed appropriate current status in progress key decision s do we understand the vets api monolith application well enough to document how to extract a service and create a microservice communications team name iet github label integration experience slack channel pst integration experience product pocs frank hiatt pm emily wilson tl thomas delrue po stakeholders team members depo lead pm frank hiatt engineering emily wilson igor yegorov salvadore gutierrez will huang research design stakeholders platform leadership platform teams what offices departments are critical to make this initiative successful ,0 134264,19102240584.0,IssuesEvent,2021-11-30 00:33:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Appointments help content from VAOS,vaos-product-design sitewide content sitewide content-product support,"## What does your team need support for? Check all that apply. - [ ] Launching one or more new unauthenticated (static) VA.gov pages - [x] Making revisions to one or more existing unauthenticated (static) VA.gov page - [ ] Launching a new online form, app, or tool on VA.gov - [x] Making revisions to an existing online form, app, or tool on VA.gov - [ ] Something else (please add details in the next question) ## What do you need help with? - [x] Content support - [ ] IA support *Please describe your need and provide any additional documents and/or links that will help us help you. If we need to add a react widget to a page, be sure to provide the code here.* As part of the Health Apartment work to move appointments from MHV to VAOS/VA.gov, we'd like consultation on possible options if we were to include similar help content. Considerations: - Edits to appointment static landing page (`/health-care/schedule-view-va-appointments/`) - New unauth content pages MHV currently has different links to help content. Reviewable artifacts are linked in the next section. ![Screen Shot 2021-11-29 help content links](https://user-images.githubusercontent.com/72046525/143962775-30ae39cd-49d3-46d5-a7f2-c57a18ccbf57.jpg) ## Supporting Artifacts *Please provide supporting artifacts as available.* - [Screenshots](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/health-care/appointments/va-online-scheduling/initiatives/health-apartment) - Downloadable [user guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/appointments/va-online-scheduling/initiatives/health-apartment/MHV%20Content%20Review_MHV%20AppointmentsUserGuide.pdf) - Link to product outline: [WIP Initiative Brief](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/appointments/va-online-scheduling/initiatives/health-apartment/mhv-vaos-appointments-initiative-brief.md) - Link to or attach user flows: - Link to prototype or mockups: - Link to any epics/issues that may be helpful: #33100 ## Will this work be going through the Collaboration Cycle? - [ ] Yes - [x] No ## When does this work need to be done? - Estimated launch date: Calendar year Q1 2022 - Estimated staging review date: Calendar year Q1 2022 - Content and IA work needed by: EOY 2021 ## Do you plan to bring this to an upcoming content office hours session? - [ ] Yes, benefit content office hours (Thursdays, 3:00 p.m. to 3:45 p.m. ET) - [ ] Yes, health content office hours (Thursdays, 11:00 a.m. to 11:30 a.m. ET) - [ ] Yes, unauth office hours (Mondays, 11:00 a.m. to 11:30 a.m. ET) - [x] No, but I'd like to schedule time to talk about this request - [ ] No, let's work asynchronously and meet if needed **Note:** If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet. ## About your team - Team name: - OCTO-DE product owner: Lauren Alexanderson - Product manager: Lauren Ernest - Designer: Peter Russo - FE engineer: - Product/team Slack channel: vaos-team ## Next steps **Once you’ve submitted this ticket, please post a link to this issue in the [#va-sitewide-content](https://dsva.slack.com/channels/va-sitewide-content) Slack channel and tag @RLHecht.** If you also need engineering support from the Public Websites team, fill out their [intake request form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E). If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a [Redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=mnorthuis&labels=ia&template=redirect-request.md&title=Redirect+Request) ",1.0,"Appointments help content from VAOS - ## What does your team need support for? Check all that apply. - [ ] Launching one or more new unauthenticated (static) VA.gov pages - [x] Making revisions to one or more existing unauthenticated (static) VA.gov page - [ ] Launching a new online form, app, or tool on VA.gov - [x] Making revisions to an existing online form, app, or tool on VA.gov - [ ] Something else (please add details in the next question) ## What do you need help with? - [x] Content support - [ ] IA support *Please describe your need and provide any additional documents and/or links that will help us help you. If we need to add a react widget to a page, be sure to provide the code here.* As part of the Health Apartment work to move appointments from MHV to VAOS/VA.gov, we'd like consultation on possible options if we were to include similar help content. Considerations: - Edits to appointment static landing page (`/health-care/schedule-view-va-appointments/`) - New unauth content pages MHV currently has different links to help content. Reviewable artifacts are linked in the next section. ![Screen Shot 2021-11-29 help content links](https://user-images.githubusercontent.com/72046525/143962775-30ae39cd-49d3-46d5-a7f2-c57a18ccbf57.jpg) ## Supporting Artifacts *Please provide supporting artifacts as available.* - [Screenshots](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/health-care/appointments/va-online-scheduling/initiatives/health-apartment) - Downloadable [user guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/appointments/va-online-scheduling/initiatives/health-apartment/MHV%20Content%20Review_MHV%20AppointmentsUserGuide.pdf) - Link to product outline: [WIP Initiative Brief](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/appointments/va-online-scheduling/initiatives/health-apartment/mhv-vaos-appointments-initiative-brief.md) - Link to or attach user flows: - Link to prototype or mockups: - Link to any epics/issues that may be helpful: #33100 ## Will this work be going through the Collaboration Cycle? - [ ] Yes - [x] No ## When does this work need to be done? - Estimated launch date: Calendar year Q1 2022 - Estimated staging review date: Calendar year Q1 2022 - Content and IA work needed by: EOY 2021 ## Do you plan to bring this to an upcoming content office hours session? - [ ] Yes, benefit content office hours (Thursdays, 3:00 p.m. to 3:45 p.m. ET) - [ ] Yes, health content office hours (Thursdays, 11:00 a.m. to 11:30 a.m. ET) - [ ] Yes, unauth office hours (Mondays, 11:00 a.m. to 11:30 a.m. ET) - [x] No, but I'd like to schedule time to talk about this request - [ ] No, let's work asynchronously and meet if needed **Note:** If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet. ## About your team - Team name: - OCTO-DE product owner: Lauren Alexanderson - Product manager: Lauren Ernest - Designer: Peter Russo - FE engineer: - Product/team Slack channel: vaos-team ## Next steps **Once you’ve submitted this ticket, please post a link to this issue in the [#va-sitewide-content](https://dsva.slack.com/channels/va-sitewide-content) Slack channel and tag @RLHecht.** If you also need engineering support from the Public Websites team, fill out their [intake request form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E). If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a [Redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=mnorthuis&labels=ia&template=redirect-request.md&title=Redirect+Request) ",1,appointments help content from vaos what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with content support ia support please describe your need and provide any additional documents and or links that will help us help you if we need to add a react widget to a page be sure to provide the code here as part of the health apartment work to move appointments from mhv to vaos va gov we d like consultation on possible options if we were to include similar help content considerations edits to appointment static landing page health care schedule view va appointments new unauth content pages mhv currently has different links to help content reviewable artifacts are linked in the next section supporting artifacts please provide supporting artifacts as available downloadable link to product outline link to or attach user flows link to prototype or mockups link to any epics issues that may be helpful will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date calendar year estimated staging review date calendar year content and ia work needed by eoy do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name octo de product owner lauren alexanderson product manager lauren ernest designer peter russo fe engineer product team slack channel vaos team next steps once you’ve submitted this ticket please post a link to this issue in the  slack channel and tag rlhecht if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 80458,10014306727.0,IssuesEvent,2019-07-15 17:11:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Define the post-onboarding meeting team interactions,508/Accessibility backend design frontend product product support,"## Goal After the initial onboarding meetings, local env setup, and strategy meetings, what will the remainder of the week look like? What will the weeks that follow look like? The goal of this ticket is to define what that initial post-onboarding interaction looks like. Will there be any recurring (role?) meetings? Office hours? A VSP liaison assigned to the VFS team? Things of this nature. ## Acceptance Criteria - [ ] Collaborate with support and leadership members on the initial draft of this plan - [ ] A description of what the remainder of the week 1 interactions are, including personnel (roles), duration, cadence, etc. - [ ] A description of what the post-week 1 interactions are, including personnel (roles), duration, cadence, etc. - [ ] Integration of these interactions into the [MVP onboarding schedule template](https://github.com/department-of-veterans-affairs/va.gov-team/issues/425) ## Definition of Done - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Define the post-onboarding meeting team interactions - ## Goal After the initial onboarding meetings, local env setup, and strategy meetings, what will the remainder of the week look like? What will the weeks that follow look like? The goal of this ticket is to define what that initial post-onboarding interaction looks like. Will there be any recurring (role?) meetings? Office hours? A VSP liaison assigned to the VFS team? Things of this nature. ## Acceptance Criteria - [ ] Collaborate with support and leadership members on the initial draft of this plan - [ ] A description of what the remainder of the week 1 interactions are, including personnel (roles), duration, cadence, etc. - [ ] A description of what the post-week 1 interactions are, including personnel (roles), duration, cadence, etc. - [ ] Integration of these interactions into the [MVP onboarding schedule template](https://github.com/department-of-veterans-affairs/va.gov-team/issues/425) ## Definition of Done - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,define the post onboarding meeting team interactions goal after the initial onboarding meetings local env setup and strategy meetings what will the remainder of the week look like what will the weeks that follow look like the goal of this ticket is to define what that initial post onboarding interaction looks like will there be any recurring role meetings office hours a vsp liaison assigned to the vfs team things of this nature acceptance criteria collaborate with support and leadership members on the initial draft of this plan a description of what the remainder of the week interactions are including personnel roles duration cadence etc a description of what the post week interactions are including personnel roles duration cadence etc integration of these interactions into the definition of done attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 83953,10454245044.0,IssuesEvent,2019-09-19 18:25:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Discovery] Create research plan,design discovery vsa-benefits vsa-decision-reviews,"## Goal Create a research plan to learn how Veterans are using the claim status tool to upload Decision Review forms. ## Acceptance Criteria - [x] Research plan has been reviewed with the team - [x] Recruiting ticket (with research plan attached)has been created and shared with Lauren Alexanderson - [x] Link to research plan has been added to this ticket",1.0,"[Discovery] Create research plan - ## Goal Create a research plan to learn how Veterans are using the claim status tool to upload Decision Review forms. ## Acceptance Criteria - [x] Research plan has been reviewed with the team - [x] Recruiting ticket (with research plan attached)has been created and shared with Lauren Alexanderson - [x] Link to research plan has been added to this ticket",1, create research plan goal create a research plan to learn how veterans are using the claim status tool to upload decision review forms acceptance criteria research plan has been reviewed with the team recruiting ticket with research plan attached has been created and shared with lauren alexanderson link to research plan has been added to this ticket,1 148859,23391636990.0,IssuesEvent,2022-08-11 18:26:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,UX research and design process documentation,design documentation vsa Facilities,"## Issue description VSA UX transition document was created in #38025 as part of the documentation on the status of our products to ensure continuity of work. This issue continues that effort. ## Tasks - [ ] Complete [Our UX research and design process section](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/facility-locator/product-transition-doc/vsa-ux-transition-doc.md#our-ux-researchdesign-process) of VSA UX Transition document - [ ] Review and edit other sections of VSA UX Transition document as needed ## Acceptance Criteria - [ ] Transition document provides a central starting point for links to UX research and design work products produced during design and development. ",1.0,"UX research and design process documentation - ## Issue description VSA UX transition document was created in #38025 as part of the documentation on the status of our products to ensure continuity of work. This issue continues that effort. ## Tasks - [ ] Complete [Our UX research and design process section](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsa/teams/facility-locator/product-transition-doc/vsa-ux-transition-doc.md#our-ux-researchdesign-process) of VSA UX Transition document - [ ] Review and edit other sections of VSA UX Transition document as needed ## Acceptance Criteria - [ ] Transition document provides a central starting point for links to UX research and design work products produced during design and development. ",1,ux research and design process documentation issue description vsa ux transition document was created in as part of the documentation on the status of our products to ensure continuity of work this issue continues that effort tasks complete of vsa ux transition document review and edit other sections of vsa ux transition document as needed acceptance criteria transition document provides a central starting point for links to ux research and design work products produced during design and development ,1 89414,11221703355.0,IssuesEvent,2020-01-07 18:27:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[OBE] Identify Legacy Issues on Submission Review Screen,HLR blocked design vsa-benefits vsa-decision-reviews,"## User Story As a Veteran, I need to view all my legacy issues when completing my Higher Level Review form so that I can select individual ones in order to be able to ""Opt Out"" of the legacy process. ## Goal _Display legacy issues so that user can select them_ ## Objectives or Key Results this is meant to further - Create a way for Veterans to opt out of individual legacy issues ## Acceptance Criteria - [ ] Design has been created that displays legacy issues that can be opted out of - [ ] Tagged Peggy in Content Review ticket #3866 - [ ] Tagged design team in Design Review ticket #3868 ",1.0,"[OBE] Identify Legacy Issues on Submission Review Screen - ## User Story As a Veteran, I need to view all my legacy issues when completing my Higher Level Review form so that I can select individual ones in order to be able to ""Opt Out"" of the legacy process. ## Goal _Display legacy issues so that user can select them_ ## Objectives or Key Results this is meant to further - Create a way for Veterans to opt out of individual legacy issues ## Acceptance Criteria - [ ] Design has been created that displays legacy issues that can be opted out of - [ ] Tagged Peggy in Content Review ticket #3866 - [ ] Tagged design team in Design Review ticket #3868 ",1, identify legacy issues on submission review screen user story as a veteran i need to view all my legacy issues when completing my higher level review form so that i can select individual ones in order to be able to opt out of the legacy process goal display legacy issues so that user can select them objectives or key results this is meant to further create a way for veterans to opt out of individual legacy issues acceptance criteria design has been created that displays legacy issues that can be opted out of tagged peggy in content review ticket tagged design team in design review ticket ,1 148868,23392529691.0,IssuesEvent,2022-08-11 19:20:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Accordion design inconsistency (Vet Centers),design vsa Facilities vet-center,"## Issue Description As result of the work to standardize accordions (#24636), the accordions are visually inconsistent on Vet Center pages. - The FAQs at the bottom of the page _do not_ have a border around the content when open. - Service accordions _do_ have a border around the content when open. This is likely occurring in other locations across VA.gov but is immediately evident on Vet Center pages due to the proximity of the two accordion types. --- ## Tasks - [ ] Determine expected style, based on design system and other factors ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ ",1.0,"Accordion design inconsistency (Vet Centers) - ## Issue Description As result of the work to standardize accordions (#24636), the accordions are visually inconsistent on Vet Center pages. - The FAQs at the bottom of the page _do not_ have a border around the content when open. - Service accordions _do_ have a border around the content when open. This is likely occurring in other locations across VA.gov but is immediately evident on Vet Center pages due to the proximity of the two accordion types. --- ## Tasks - [ ] Determine expected style, based on design system and other factors ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ ",1,accordion design inconsistency vet centers issue description as result of the work to standardize accordions the accordions are visually inconsistent on vet center pages the faqs at the bottom of the page do not have a border around the content when open service accordions do have a border around the content when open this is likely occurring in other locations across va gov but is immediately evident on vet center pages due to the proximity of the two accordion types tasks determine expected style based on design system and other factors acceptance criteria what will be created or happen as a result of this story ,1 133928,19006727890.0,IssuesEvent,2021-11-23 01:32:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Update Documentation on Radio Buttons, Checkbox, and Checkbox Groups",vsp-design-system-team,"Linked Tickets: * https://app.zenhub.com/workspaces/vsp-design-system-5f8de67192551b0012ebb802/issues/department-of-veterans-affairs/va.gov-team/33177 * https://app.zenhub.com/workspaces/vsp-design-system-5f8de67192551b0012ebb802/issues/department-of-veterans-affairs/va.gov-team/33114 Task: * Documentation on https://design.va.gov/ will need to be updated to reflect the changes made in the linked tickets Goal: Provide a straight forward guideline of: * Why we are moving to web components from react components * How to use the web component instead of the react component * The issues that are being solved now by the web component ",1.0,"Update Documentation on Radio Buttons, Checkbox, and Checkbox Groups - Linked Tickets: * https://app.zenhub.com/workspaces/vsp-design-system-5f8de67192551b0012ebb802/issues/department-of-veterans-affairs/va.gov-team/33177 * https://app.zenhub.com/workspaces/vsp-design-system-5f8de67192551b0012ebb802/issues/department-of-veterans-affairs/va.gov-team/33114 Task: * Documentation on https://design.va.gov/ will need to be updated to reflect the changes made in the linked tickets Goal: Provide a straight forward guideline of: * Why we are moving to web components from react components * How to use the web component instead of the react component * The issues that are being solved now by the web component ",1,update documentation on radio buttons checkbox and checkbox groups linked tickets task documentation on will need to be updated to reflect the changes made in the linked tickets goal provide a straight forward guideline of why we are moving to web components from react components how to use the web component instead of the react component the issues that are being solved now by the web component ,1 87493,10919779139.0,IssuesEvent,2019-11-21 19:46:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Prevent rendering empty content on review page,HLR bug design forms frontend vsa-benefits vsa-decision-reviews,"## User Story or Problem Statement After opening a review accordion on a form's review page, content that was presented to the veteran to review, but not editable takes up space in the review accordion. This PR prevents rendering of those empty elements since their class also includes a substantial bottom margin This gap can be seen in both form 526 & 996 (HLR) ![](https://user-images.githubusercontent.com/136959/69259547-0d99e700-0b84-11ea-832c-c9ff97820a22.png) Elements within other accordions do not have this margin ![](https://user-images.githubusercontent.com/136959/69259673-391cd180-0b84-11ea-9871-aedd16fd1967.png) ## Goal Prevent rendering of empty components ## Acceptance Criteria - [ ] Empty components are not rendered, so there is no additional 5rem margin above, or between other components ",1.0,"Prevent rendering empty content on review page - ## User Story or Problem Statement After opening a review accordion on a form's review page, content that was presented to the veteran to review, but not editable takes up space in the review accordion. This PR prevents rendering of those empty elements since their class also includes a substantial bottom margin This gap can be seen in both form 526 & 996 (HLR) ![](https://user-images.githubusercontent.com/136959/69259547-0d99e700-0b84-11ea-832c-c9ff97820a22.png) Elements within other accordions do not have this margin ![](https://user-images.githubusercontent.com/136959/69259673-391cd180-0b84-11ea-9871-aedd16fd1967.png) ## Goal Prevent rendering of empty components ## Acceptance Criteria - [ ] Empty components are not rendered, so there is no additional 5rem margin above, or between other components ",1,prevent rendering empty content on review page user story or problem statement after opening a review accordion on a form s review page content that was presented to the veteran to review but not editable takes up space in the review accordion this pr prevents rendering of those empty elements since their class also includes a substantial bottom margin this gap can be seen in both form hlr elements within other accordions do not have this margin goal prevent rendering of empty components acceptance criteria empty components are not rendered so there is no additional margin above or between other components ,1 174156,27585905180.0,IssuesEvent,2023-03-08 19:45:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Supplemental Claims | Accept submissions without evidence,frontend design Lighthouse benefits-team-1 squad-2,"## Value Statement **_As a_** Veteran **_I want to_** submit my claim without evidence **_So that_** I can quickly begin the review process without the burden of providing evidence. --- ## Background Context Due to the PACT Act, the VBA has changed it's process for reviewing all supplemental claims. As of January 1, 2023, claimants may submit supplemental claims without providing evidence. Claims processors will manually review all claims, regardless of PACT eligibility, to determine if evidence is needed. If so, they will reach out to the claimant directly for more information. The scope of this ticket is backend changes to the current endpoint. ## Acceptance Criteria - [ ] User may submit their claim without evidence - [ ] User receives a notice for unsuccessful submissions - [ ] Unit tests complete (90% coverage) - [ ] E2E tests complete - [ ] Accessibility testing complete - [ ] Reviewed and approved by product and/or design ## Designs and Build Notes - [Design (NOT APPROVED)](https://www.sketch.com/s/d2416db4-9a4f-4919-abe4-20ba4bdcfd89/a/agLe8Aq) - [COPY](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/design/sourceofcontenttruth.md#pact-act-copy-changes) ## Tasks - [ ] Update endpoint to accept submissions without evidence - [ ] Test load handling to determine evidence threshold ## Definition of Ready - [ ] _Clear value description_ - [ ] _Testable acceptance criteria_ - [ ] _Accessibility added to acceptance criteria_ - [ ] _Approved designs attached_ - [ ] _Sample data provided where appropriate_ - [ ] _Estimated to fit within the sprint_ - [ ] _Dependencies and blockers linked_ ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design",1.0,"Supplemental Claims | Accept submissions without evidence - ## Value Statement **_As a_** Veteran **_I want to_** submit my claim without evidence **_So that_** I can quickly begin the review process without the burden of providing evidence. --- ## Background Context Due to the PACT Act, the VBA has changed it's process for reviewing all supplemental claims. As of January 1, 2023, claimants may submit supplemental claims without providing evidence. Claims processors will manually review all claims, regardless of PACT eligibility, to determine if evidence is needed. If so, they will reach out to the claimant directly for more information. The scope of this ticket is backend changes to the current endpoint. ## Acceptance Criteria - [ ] User may submit their claim without evidence - [ ] User receives a notice for unsuccessful submissions - [ ] Unit tests complete (90% coverage) - [ ] E2E tests complete - [ ] Accessibility testing complete - [ ] Reviewed and approved by product and/or design ## Designs and Build Notes - [Design (NOT APPROVED)](https://www.sketch.com/s/d2416db4-9a4f-4919-abe4-20ba4bdcfd89/a/agLe8Aq) - [COPY](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/design/sourceofcontenttruth.md#pact-act-copy-changes) ## Tasks - [ ] Update endpoint to accept submissions without evidence - [ ] Test load handling to determine evidence threshold ## Definition of Ready - [ ] _Clear value description_ - [ ] _Testable acceptance criteria_ - [ ] _Accessibility added to acceptance criteria_ - [ ] _Approved designs attached_ - [ ] _Sample data provided where appropriate_ - [ ] _Estimated to fit within the sprint_ - [ ] _Dependencies and blockers linked_ ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design",1,supplemental claims accept submissions without evidence value statement as a veteran i want to submit my claim without evidence so that i can quickly begin the review process without the burden of providing evidence background context due to the pact act the vba has changed it s process for reviewing all supplemental claims as of january claimants may submit supplemental claims without providing evidence claims processors will manually review all claims regardless of pact eligibility to determine if evidence is needed if so they will reach out to the claimant directly for more information the scope of this ticket is backend changes to the current endpoint acceptance criteria user may submit their claim without evidence user receives a notice for unsuccessful submissions unit tests complete coverage tests complete accessibility testing complete reviewed and approved by product and or design designs and build notes tasks update endpoint to accept submissions without evidence test load handling to determine evidence threshold definition of ready clear value description testable acceptance criteria accessibility added to acceptance criteria approved designs attached sample data provided where appropriate estimated to fit within the sprint dependencies and blockers linked definition of done meets acceptance criteria passed testing coverage passed unit testing coverage passed integration testing if applicable code reviewed internal submitted to staging reviewed and approved by product and or design,1 111923,14172505898.0,IssuesEvent,2020-11-12 17:02:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Write stories for ErrorableRadioButtons,design-system-team frontend,"## Issue Description Using the documentation found in [the markdown file for `ErrorableRadioButtons`](https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/tree/master/packages/formation-react/src/components/ErrorableRadioButtons/ErrorableRadioButtons.mdx), write Storybook stories for the component. ## Acceptance Criteria - [ ] All the ""stories"" found in `ErrorableRadioButtons.mdx` are written as Storybook stories - [ ] These stories are found in `packages/formation-react/src/components/ErrorableRadioButtons/ErrorableRadioButtons.stories.jsx`",1.0,"Write stories for ErrorableRadioButtons - ## Issue Description Using the documentation found in [the markdown file for `ErrorableRadioButtons`](https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/tree/master/packages/formation-react/src/components/ErrorableRadioButtons/ErrorableRadioButtons.mdx), write Storybook stories for the component. ## Acceptance Criteria - [ ] All the ""stories"" found in `ErrorableRadioButtons.mdx` are written as Storybook stories - [ ] These stories are found in `packages/formation-react/src/components/ErrorableRadioButtons/ErrorableRadioButtons.stories.jsx`",1,write stories for errorableradiobuttons issue description using the documentation found in write storybook stories for the component acceptance criteria all the stories found in errorableradiobuttons mdx are written as storybook stories these stories are found in packages formation react src components errorableradiobuttons errorableradiobuttons stories jsx ,1 180731,30558752370.0,IssuesEvent,2023-07-20 13:23:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Meet w/ 10-10ezr team to discuss their Dig. experience,service-design,"## Purpose Jessica Stump works on this team and mentioned that they've begun discovery work on digitizing this form. May want to reach out and get their take at this stage. [10-10EZR form](https://www.va.gov/health-care/update-health-information/) ## Tasks - [x] Conduct session - [x] capture [notes](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2703949875/Notes+from+10-10+workshop) ## Acceptance Criteria - [x] Notes documented ",1.0,"Meet w/ 10-10ezr team to discuss their Dig. experience - ## Purpose Jessica Stump works on this team and mentioned that they've begun discovery work on digitizing this form. May want to reach out and get their take at this stage. [10-10EZR form](https://www.va.gov/health-care/update-health-information/) ## Tasks - [x] Conduct session - [x] capture [notes](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2703949875/Notes+from+10-10+workshop) ## Acceptance Criteria - [x] Notes documented ",1,meet w team to discuss their dig experience purpose jessica stump works on this team and mentioned that they ve begun discovery work on digitizing this form may want to reach out and get their take at this stage tasks conduct session capture acceptance criteria notes documented ,1 168336,26631989172.0,IssuesEvent,2023-01-24 18:36:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create wireframes and content for app with appointments list ,content design ux HCE-Checkin,"## Description How might we... 1. Make pre-check-in and check-in look like one app? 2. While still focusing on highlighting any primary actions that Veterans need to be complete 3. And, allow Veterans to view all of their appointments (like VAOS does with their appointments list), including future and past ## Tasks - [ ] Create wireframes and content for selected user flow option. Create for happy path(s). - [ ] Review with UX team - [ ] Review with CIE team ## AC - [ ] Wireframes complete and abstract branch created - [ ] Reviewed with UX team - [ ] Reviewed with CIE team ",1.0,"Create wireframes and content for app with appointments list - ## Description How might we... 1. Make pre-check-in and check-in look like one app? 2. While still focusing on highlighting any primary actions that Veterans need to be complete 3. And, allow Veterans to view all of their appointments (like VAOS does with their appointments list), including future and past ## Tasks - [ ] Create wireframes and content for selected user flow option. Create for happy path(s). - [ ] Review with UX team - [ ] Review with CIE team ## AC - [ ] Wireframes complete and abstract branch created - [ ] Reviewed with UX team - [ ] Reviewed with CIE team ",1,create wireframes and content for app with appointments list description how might we make pre check in and check in look like one app while still focusing on highlighting any primary actions that veterans need to be complete and allow veterans to view all of their appointments like vaos does with their appointments list including future and past tasks create wireframes and content for selected user flow option create for happy path s review with ux team review with cie team ac wireframes complete and abstract branch created reviewed with ux team reviewed with cie team ,1 90391,11388113020.0,IssuesEvent,2020-01-29 16:08:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Profile 2.0: Create mockups of the Contact Information screen,design personalization-2.0 profile vsa-authenticated-exp,"## User story As a user, I need to be able to easily find and and update my contact information so the VA can reach me at the right places. ## Additional background Epic #5092 ## Tasks - [ ] Create desktop mockups of the Contact information screen. - [ ] Create mobile mockups of the Contact information screen. ## Acceptance Criteria - [ ] All mockups have been produced",1.0,"[Design] Profile 2.0: Create mockups of the Contact Information screen - ## User story As a user, I need to be able to easily find and and update my contact information so the VA can reach me at the right places. ## Additional background Epic #5092 ## Tasks - [ ] Create desktop mockups of the Contact information screen. - [ ] Create mobile mockups of the Contact information screen. ## Acceptance Criteria - [ ] All mockups have been produced",1, profile create mockups of the contact information screen user story as a user i need to be able to easily find and and update my contact information so the va can reach me at the right places additional background epic tasks create desktop mockups of the contact information screen create mobile mockups of the contact information screen acceptance criteria all mockups have been produced,1 173490,27452786201.0,IssuesEvent,2023-03-02 18:42:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Discuss applicable learnings from Discovery Research assist of TT2,service-design,"## Purpose What did we learn? What might we change in our offerings? How might we communicate that? Should we include a mapping of some sort in our Research-adjacent work w/ a team? ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ ",1.0,"Discuss applicable learnings from Discovery Research assist of TT2 - ## Purpose What did we learn? What might we change in our offerings? How might we communicate that? Should we include a mapping of some sort in our Research-adjacent work w/ a team? ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ ",1,discuss applicable learnings from discovery research assist of purpose what did we learn what might we change in our offerings how might we communicate that should we include a mapping of some sort in our research adjacent work w a team tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story ,1 135858,19677929883.0,IssuesEvent,2022-01-11 14:13:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,ProcessList web component: migration script,vsp-design-system-team,"## Description Dependent on #35073 Write the migration script for the ProcessList web component. ## Acceptance Criteria - [ ] write migration script - [ ] test migration script",1.0,"ProcessList web component: migration script - ## Description Dependent on #35073 Write the migration script for the ProcessList web component. ## Acceptance Criteria - [ ] write migration script - [ ] test migration script",1,processlist web component migration script description dependent on write the migration script for the processlist web component acceptance criteria write migration script test migration script,1 152717,24008967619.0,IssuesEvent,2022-09-14 17:01:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Synthesize learnings from Meetings,service-design,"## Issue Description Meet w/ Platform teams to learn remaining information about their Tools/Services. Use the developed script and Data Repository. ## User Story As an SDT member, I want to meet w/ Platform teams so that I can capture the needed information for mapping their Tools and Services ## Additional questions: -What do you consider to be the most critical/essential services you offer? ## Tasks - [ ] Synthesize captured data - [ ] Evaluate data, make decisions on what to incorporate ## Acceptance Criteria - [ ] data is synthesized",1.0,"Synthesize learnings from Meetings - ## Issue Description Meet w/ Platform teams to learn remaining information about their Tools/Services. Use the developed script and Data Repository. ## User Story As an SDT member, I want to meet w/ Platform teams so that I can capture the needed information for mapping their Tools and Services ## Additional questions: -What do you consider to be the most critical/essential services you offer? ## Tasks - [ ] Synthesize captured data - [ ] Evaluate data, make decisions on what to incorporate ## Acceptance Criteria - [ ] data is synthesized",1,synthesize learnings from meetings issue description meet w platform teams to learn remaining information about their tools services use the developed script and data repository user story as an sdt member i want to meet w platform teams so that i can capture the needed information for mapping their tools and services additional questions what do you consider to be the most critical essential services you offer tasks synthesize captured data evaluate data make decisions on what to incorporate acceptance criteria data is synthesized,1 149801,23533328039.0,IssuesEvent,2022-08-19 17:38:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design] MyHealth - Secure Messaging - Design ""rename folder"" desktop and mobile pages",design my-health my-health-SM-CORE mhv-to-va.gov-SM,"## Issue Description As a secure messaging user, I need a way to rename secure messages folders I have created. --- ## Tasks - [x] Design ""rename folder"" page for desktop - [x] Design ""rename folder"" page for mobile - [x] Drop link to mockups into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Mobile and desktop initial designs will be complete and ready for review by PO. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1.0,"[Design] MyHealth - Secure Messaging - Design ""rename folder"" desktop and mobile pages - ## Issue Description As a secure messaging user, I need a way to rename secure messages folders I have created. --- ## Tasks - [x] Design ""rename folder"" page for desktop - [x] Design ""rename folder"" page for mobile - [x] Drop link to mockups into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Mobile and desktop initial designs will be complete and ready for review by PO. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1, myhealth secure messaging design rename folder desktop and mobile pages issue description as a secure messaging user i need a way to rename secure messages folders i have created tasks design rename folder page for desktop design rename folder page for mobile drop link to mockups into a comment on this ticket drop a note into mhv on vagov in slack when you are ready for tracey to review acceptance criteria mobile and desktop initial designs will be complete and ready for review by po how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 179599,30272746853.0,IssuesEvent,2023-07-07 16:43:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Update Product Artifacts for Release,design ux HCE-Checkin,"## Background Base on [this minor change]([FE] Change alert content shown when Veteran is too early to check in within check in app) to content, we need to update the appropriate design artifacts. This is already in production. ## Description Update various product artifacts, as necessary, based on the feature release. ## Tasks - [x] Update the Pre-Check-in Product Guide, including content and screenshots, if necessary - [x] Update the eCheck-in Product Guide, including content and screenshots, if necessary - [x] Update user flow diagrams, if necessary - [x] Send updated screenshots to Danielle Thierry for the Resources & Support (R&S) articles in VA.gov, if necessary ## Acceptance Criteria - [x] Product Guides are up-to-date and ready to be published to Git - [x] ALL screenshots are of the highest quality possible - [x] [User flow diagrams are up-to-date](https://www.sketch.com/s/e79a827e-42cf-4a82-b554-874c75b5c70e/a/3Op54Vm) and ready to be merged in Abstract and pushed to sketch cloud - [x] R&D articles are up-to-date (or scheduled for publishing) ",1.0,"Update Product Artifacts for Release - ## Background Base on [this minor change]([FE] Change alert content shown when Veteran is too early to check in within check in app) to content, we need to update the appropriate design artifacts. This is already in production. ## Description Update various product artifacts, as necessary, based on the feature release. ## Tasks - [x] Update the Pre-Check-in Product Guide, including content and screenshots, if necessary - [x] Update the eCheck-in Product Guide, including content and screenshots, if necessary - [x] Update user flow diagrams, if necessary - [x] Send updated screenshots to Danielle Thierry for the Resources & Support (R&S) articles in VA.gov, if necessary ## Acceptance Criteria - [x] Product Guides are up-to-date and ready to be published to Git - [x] ALL screenshots are of the highest quality possible - [x] [User flow diagrams are up-to-date](https://www.sketch.com/s/e79a827e-42cf-4a82-b554-874c75b5c70e/a/3Op54Vm) and ready to be merged in Abstract and pushed to sketch cloud - [x] R&D articles are up-to-date (or scheduled for publishing) ",1,update product artifacts for release background base on change alert content shown when veteran is too early to check in within check in app to content we need to update the appropriate design artifacts this is already in production description update various product artifacts as necessary based on the feature release tasks update the pre check in product guide including content and screenshots if necessary update the echeck in product guide including content and screenshots if necessary update user flow diagrams if necessary send updated screenshots to danielle thierry for the resources support r s articles in va gov if necessary acceptance criteria product guides are up to date and ready to be published to git all screenshots are of the highest quality possible and ready to be merged in abstract and pushed to sketch cloud r d articles are up to date or scheduled for publishing ,1 151988,23901196779.0,IssuesEvent,2022-09-08 18:57:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Ongoing Service] 2022 Q3 - Provide Customer Insights to Platform teams,Epic service-design VSP-Ongoing-Service team-platform-service-design PO Endorsed platform-okrs,"### **Problem Statement** ### VSP does not have a consolidated repository of customer research and feedback. _How might we consolidate customer research and feedback for holistic analysis and synthesis on an ongoing basis?_ ### **Measuring Success** ### Increase in customer NPS ### **Additional Information** ### Continuous customer feedback loop solution approach (WIP): https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1580853363126/ef5036613c38f1afeffbc082f28d2d8016c66a4a Typical research sources: - Quarterly VFS Satisfaction survey - Collaboration cycle surveys - Onboarding surveys - KPI workshops - Feedback on new tools and services ",2.0,"[Ongoing Service] 2022 Q3 - Provide Customer Insights to Platform teams - ### **Problem Statement** ### VSP does not have a consolidated repository of customer research and feedback. _How might we consolidate customer research and feedback for holistic analysis and synthesis on an ongoing basis?_ ### **Measuring Success** ### Increase in customer NPS ### **Additional Information** ### Continuous customer feedback loop solution approach (WIP): https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1580853363126/ef5036613c38f1afeffbc082f28d2d8016c66a4a Typical research sources: - Quarterly VFS Satisfaction survey - Collaboration cycle surveys - Onboarding surveys - KPI workshops - Feedback on new tools and services ",1, provide customer insights to platform teams problem statement vsp does not have a consolidated repository of customer research and feedback how might we consolidate customer research and feedback for holistic analysis and synthesis on an ongoing basis measuring success increase in customer nps additional information continuous customer feedback loop solution approach wip typical research sources quarterly vfs satisfaction survey collaboration cycle surveys onboarding surveys kpi workshops feedback on new tools and services ,1 118753,15362503139.0,IssuesEvent,2021-03-01 19:34:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create On this page Web component ,vsp-design-system-team,"## Issue Description Build On this page web component. --- ## Tasks - [ ] Development of on this page component - [ ] Testing - basic accessibility testing for staging review prep - [ ] Put on staging for staging review - [ ] Add to Storybook - [ ] Put together guidance for CMS team to use web component ## Acceptance Criteria - [ ] Accessible on staging for testing - [ ] On this page component added to Storybook --- ",1.0,"Create On this page Web component - ## Issue Description Build On this page web component. --- ## Tasks - [ ] Development of on this page component - [ ] Testing - basic accessibility testing for staging review prep - [ ] Put on staging for staging review - [ ] Add to Storybook - [ ] Put together guidance for CMS team to use web component ## Acceptance Criteria - [ ] Accessible on staging for testing - [ ] On this page component added to Storybook --- ",1,create on this page web component issue description build on this page web component tasks development of on this page component testing basic accessibility testing for staging review prep put on staging for staging review add to storybook put together guidance for cms team to use web component acceptance criteria accessible on staging for testing on this page component added to storybook ,1 149223,23445324338.0,IssuesEvent,2022-08-15 19:00:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Review VAOS user flows with Dev,design ux vaos-product-design,"## Background * We updated the [VAOS user flows](https://www.figma.com/file/xRs9s6QWoBPRhpdYCGc3cV/User-Flow?node-id=0%3A1) * Some questions remain that require engineering support to answer * We'll ask engineers to review the flow, answer questions, and surface any missing screens/flows. ## Questions ",2.0,"Review VAOS user flows with Dev - ## Background * We updated the [VAOS user flows](https://www.figma.com/file/xRs9s6QWoBPRhpdYCGc3cV/User-Flow?node-id=0%3A1) * Some questions remain that require engineering support to answer * We'll ask engineers to review the flow, answer questions, and surface any missing screens/flows. ## Questions ",1,review vaos user flows with dev background we updated the some questions remain that require engineering support to answer we ll ask engineers to review the flow answer questions and surface any missing screens flows questions ,1 165782,26225163744.0,IssuesEvent,2023-01-04 17:59:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Run internal provider-based, multi-modality scheduling discovery",discovery ux vaos-product-design,"## Task Description Run a discovery session to surface stakeholder and team questions, assumptions and ideas around provider-based, multi-modality scheduling ## References * None ## Acceptance Criteria - [x] List of questions, assumptions, and ideas exists",1.0,"Run internal provider-based, multi-modality scheduling discovery - ## Task Description Run a discovery session to surface stakeholder and team questions, assumptions and ideas around provider-based, multi-modality scheduling ## References * None ## Acceptance Criteria - [x] List of questions, assumptions, and ideas exists",1,run internal provider based multi modality scheduling discovery task description run a discovery session to surface stakeholder and team questions assumptions and ideas around provider based multi modality scheduling references none acceptance criteria list of questions assumptions and ideas exists,1 144467,22356922857.0,IssuesEvent,2022-06-15 16:26:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Update components using consistency audit tickets,Epic platform-initiative vsp-design-system-team,"## Problem Statement Product support team did a consistency audit to identify the components/patterns that are outdated or inconsistent that leads to support and inconsistency. How might we ensure that both engineers and designers are able to find and implement the correct components and patterns for their features/products. ## Hypothesis or Bet *How will this initiative impact the quality of VFS or VSP teams' work?* *How will this initiative be easy for VFS or VSP teams? Or how will it be easier than what they did before?* If we have more robust documentation of established components and patterns, VSP will be giving less support to VFS teams. If we have more robust documentation, VFS teams will be able to identify the correct component or pattern to use right away. ## We will know we're done when... (""Definition of Done"") *What requirements does this project need to meet for you to finish this initiative?* - [ ] Updated documentation of established components and form patterns - [ ] Closing consistency audit tickets - [ ] VFS team is using component and pattern documentation to identify the form to use ## Launch Checklist ### Is this service / tool / feature... Tool ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1.0,"Update components using consistency audit tickets - ## Problem Statement Product support team did a consistency audit to identify the components/patterns that are outdated or inconsistent that leads to support and inconsistency. How might we ensure that both engineers and designers are able to find and implement the correct components and patterns for their features/products. ## Hypothesis or Bet *How will this initiative impact the quality of VFS or VSP teams' work?* *How will this initiative be easy for VFS or VSP teams? Or how will it be easier than what they did before?* If we have more robust documentation of established components and patterns, VSP will be giving less support to VFS teams. If we have more robust documentation, VFS teams will be able to identify the correct component or pattern to use right away. ## We will know we're done when... (""Definition of Done"") *What requirements does this project need to meet for you to finish this initiative?* - [ ] Updated documentation of established components and form patterns - [ ] Closing consistency audit tickets - [ ] VFS team is using component and pattern documentation to identify the form to use ## Launch Checklist ### Is this service / tool / feature... Tool ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1,update components using consistency audit tickets problem statement product support team did a consistency audit to identify the components patterns that are outdated or inconsistent that leads to support and inconsistency how might we ensure that both engineers and designers are able to find and implement the correct components and patterns for their features products hypothesis or bet how will this initiative impact the quality of vfs or vsp teams work how will this initiative be easy for vfs or vsp teams or how will it be easier than what they did before if we have more robust documentation of established components and patterns vsp will be giving less support to vfs teams if we have more robust documentation vfs teams will be able to identify the correct component or pattern to use right away we will know we re done when definition of done what requirements does this project need to meet for you to finish this initiative updated documentation of established components and form patterns closing consistency audit tickets vfs team is using component and pattern documentation to identify the form to use launch checklist is this service tool feature tool tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a checked into note the product directory name should match with the list of vsp products external facing a exists for this product feature tool and should be located at platform product name readme md external facing a exists for this product feature tool and is updated for changes from this initiative and should be linked from the vfs facing readme for your product and should be located within platform product name unless you already have another location for it if applicable and post to about whether this should be added to the if applicable post to for external communication about this change e g vsp newsletter customer facing meetings measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying required artifacts documentation product name directory name used for your product documentation product outline link to product outline readme link to vfs facing readme for your product user guide link to user guide testing usability test link to github issue or provide reason for skipping manual qa link to github issue or documented results automated tests link to tests or n a measurement success metrics link to where success metrics are measured or where they re defined product outline is ok or provide reason for skipping release plan link to release plan ticket todos convert this issue to an epic add your team s label to this epic ,1 137533,20158972809.0,IssuesEvent,2022-02-09 19:19:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,526 Failed Submissions Email Templates for Additional Error Conditions,design vsa vsa-claims-appeals 526 benefits-crew,"## Issue Description As a Veteran, when my claim fails, I'd like to understand why, so that I can resubmit properly. --- ## Tasks - [ ] Continue to build on our initial email notification, developing language to fit PIF in Use and additional error conditions. [Backend Ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/36702). ## Acceptance Criteria - [ ] Language developed for error conditions and shared with backend. --- ",1.0,"526 Failed Submissions Email Templates for Additional Error Conditions - ## Issue Description As a Veteran, when my claim fails, I'd like to understand why, so that I can resubmit properly. --- ## Tasks - [ ] Continue to build on our initial email notification, developing language to fit PIF in Use and additional error conditions. [Backend Ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/36702). ## Acceptance Criteria - [ ] Language developed for error conditions and shared with backend. --- ",1, failed submissions email templates for additional error conditions issue description as a veteran when my claim fails i d like to understand why so that i can resubmit properly tasks continue to build on our initial email notification developing language to fit pif in use and additional error conditions acceptance criteria language developed for error conditions and shared with backend ,1 122449,16117213795.0,IssuesEvent,2021-04-28 08:53:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Notification Preferences: Determine naming conventions + organization for notifications and groups,design notifications-preferences profile unplanned-work vsa-authenticated-exp,"## Background As part of the Notification Preferences work we need to define name for the communication items as well as the names of the groups that we'll categorize those communication items into. We'll need to collaborate with our partners on VANotify and VEText. ## Tasks - [x] Define communication items - [x] Define group names and groupings for communication items to fit into - [x] Send to Danielle for content review ## MVP notification worksheet [Communication-Permissions-Configuration-Data-Worksheet_4.20.21-edits.xlsx](https://github.com/department-of-veterans-affairs/va.gov-team/files/6367737/Communication-Permissions-Configuration-Data-Worksheet_4.20.21-edits.xlsx) ",1.0,"[Design] Notification Preferences: Determine naming conventions + organization for notifications and groups - ## Background As part of the Notification Preferences work we need to define name for the communication items as well as the names of the groups that we'll categorize those communication items into. We'll need to collaborate with our partners on VANotify and VEText. ## Tasks - [x] Define communication items - [x] Define group names and groupings for communication items to fit into - [x] Send to Danielle for content review ## MVP notification worksheet [Communication-Permissions-Configuration-Data-Worksheet_4.20.21-edits.xlsx](https://github.com/department-of-veterans-affairs/va.gov-team/files/6367737/Communication-Permissions-Configuration-Data-Worksheet_4.20.21-edits.xlsx) ",1, notification preferences determine naming conventions organization for notifications and groups background as part of the notification preferences work we need to define name for the communication items as well as the names of the groups that we ll categorize those communication items into we ll need to collaborate with our partners on vanotify and vetext tasks define communication items define group names and groupings for communication items to fit into send to danielle for content review mvp notification worksheet ,1 145536,22708366569.0,IssuesEvent,2022-07-05 16:37:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] My Health - Design list of message drafts for desktop and mobile,design myhealth myhealth-groundwork myhealth-secure-messaging,"## Issue Description As a secure messaging user, I need an inbox that lists my secure messages on desktop and mobile. --- ## Tasks - [x] Design inbox message list for desktop - [x] Design Inbox message list for mobile - [x] Drop link to prototypes into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Mobile and desktop initial designs will be complete and ready for a design review with the remaining secure messaging screens. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] My Health - Design list of message drafts for desktop and mobile - ## Issue Description As a secure messaging user, I need an inbox that lists my secure messages on desktop and mobile. --- ## Tasks - [x] Design inbox message list for desktop - [x] Design Inbox message list for mobile - [x] Drop link to prototypes into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Mobile and desktop initial designs will be complete and ready for a design review with the remaining secure messaging screens. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, my health design list of message drafts for desktop and mobile issue description as a secure messaging user i need an inbox that lists my secure messages on desktop and mobile tasks design inbox message list for desktop design inbox message list for mobile drop link to prototypes into a comment on this ticket drop a note into mhv on vagov in slack when you are ready for tracey to review acceptance criteria mobile and desktop initial designs will be complete and ready for a design review with the remaining secure messaging screens how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 179888,30318664288.0,IssuesEvent,2023-07-10 17:26:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[AFTER RESEARCH] Decision on default warning alert,content design ux HCE-Checkin,"## Description Zach worked on this [related ticket ](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/gh/department-of-veterans-affairs/va.gov-team/59007), and pointed out that the default warning alert includes a heading, which we currently haven't written content for. So, question is, do we think we should write headings? Or, do we want to consider a different component? ## AC - [ ] Decision documented in ticket - [ ] Create f/u ticket for the work ",1.0,"[AFTER RESEARCH] Decision on default warning alert - ## Description Zach worked on this [related ticket ](https://app.zenhub.com/workspaces/check-in-experience-61fc23a2cb8a14001132e102/issues/gh/department-of-veterans-affairs/va.gov-team/59007), and pointed out that the default warning alert includes a heading, which we currently haven't written content for. So, question is, do we think we should write headings? Or, do we want to consider a different component? ## AC - [ ] Decision documented in ticket - [ ] Create f/u ticket for the work ",1, decision on default warning alert description zach worked on this and pointed out that the default warning alert includes a heading which we currently haven t written content for so question is do we think we should write headings or do we want to consider a different component ac decision documented in ticket create f u ticket for the work ,1 121687,16015352955.0,IssuesEvent,2021-04-20 15:23:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Mock up of Decision Review entry points flow,blocked design needs-grooming vsa-claims-appeals vsa-decision-reviews,"## User Story or Problem Statement As a designer, I need to create visual representation of the Decision Review entry point flow so I can test the proposed solution during Veteran sessions ## Goal _What outcome(s) do we want to see?_ We want to get a visualization of how the user will navigate to the Decision Review 'vertical' of the website (a section of content related to Decision Reviews and contains all pages for decision review lanes). ## Objectives or Key Results this is meant to further - _This will allow the veteran a clearer and simpler means of navigating to the Decision Review section of the website with the intent to funnel them to the proper content, assisting them in understanding which Decision Review lane is appropriate for their needs._ ## Acceptance Criteria - [ ] Flow diagram that shows the points of entry that a user will navigate to the decision reviews section of the website (va.gov/decision-reviews) ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] Mock up of Decision Review entry points flow - ## User Story or Problem Statement As a designer, I need to create visual representation of the Decision Review entry point flow so I can test the proposed solution during Veteran sessions ## Goal _What outcome(s) do we want to see?_ We want to get a visualization of how the user will navigate to the Decision Review 'vertical' of the website (a section of content related to Decision Reviews and contains all pages for decision review lanes). ## Objectives or Key Results this is meant to further - _This will allow the veteran a clearer and simpler means of navigating to the Decision Review section of the website with the intent to funnel them to the proper content, assisting them in understanding which Decision Review lane is appropriate for their needs._ ## Acceptance Criteria - [ ] Flow diagram that shows the points of entry that a user will navigate to the decision reviews section of the website (va.gov/decision-reviews) ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, mock up of decision review entry points flow user story or problem statement as a designer i need to create visual representation of the decision review entry point flow so i can test the proposed solution during veteran sessions goal what outcome s do we want to see we want to get a visualization of how the user will navigate to the decision review vertical of the website a section of content related to decision reviews and contains all pages for decision review lanes objectives or key results this is meant to further this will allow the veteran a clearer and simpler means of navigating to the decision review section of the website with the intent to funnel them to the proper content assisting them in understanding which decision review lane is appropriate for their needs acceptance criteria flow diagram that shows the points of entry that a user will navigate to the decision reviews section of the website va gov decision reviews how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 171565,27142179156.0,IssuesEvent,2023-02-16 17:05:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[discovery] Supplemental Claims | Learn how the Intent to File form/functionality works,design Supplemental Claims high priority benefits-team-1 squad-2,"## Value Statement **_As a_** Veteran **_I want to_** submit an Intent to File form as soon as I know I plan to file a supplemental claim **_So that_** I can have more time to collect information to support my claim, and protect the earliest possible effective date for any benefits resulting from my claim. --- ## Background Context Claimants can now submit an Intent to File for a supplemental claim. The VBA wants to include this functionality in support of the updated policy. ## What do we want to learn? 1. Is there a separate ITF for the supplemental claim form, or can we use the version that accompanies the 526ez? _VA Form 21-0966, Intent to File a Claim for Compensation and/or Pension, or Survivors Pension and/or DIC applies to all claims so yes, the version that accompanies the 526EZ may be used._ 2. Can one intent to file be used for multiple claims? _For example, can an Intent to File that was previously submitted for a 526ez be extended to a Supplemental claim form. An Intent to File only applies to the next received, qualifying claim. It would not extend to multiple claims._ 3. Does an Intent to File form stay on file for reuse? Or does the claimant have to submit an Intent to File for each new claim? _A new Intent to File would have to be submitted for each claim._ 4. When a claim is closed, does it close the Intent to File? _Yes, if the Intent to File was absorbed by a claim, it would not apply to another, subsequently received claim. The Intent to File is closed when a qualifying claim is received._ 5. Does VA policy require that only one ITF can be active at a time? Or can there be multiple? 6. How does ITF data for 526 submissions feed into VBMS? 7. Does the system (VBMS or otherwise) associate an ITF to a claim. 8. What does the claims processor view in the VBMS to decide how to associate a claim to an ITF? 9. How does HINES batch processing handle acknowledgement letters for ITFs? What’s the logic? 10. (EVSS) Are ITFs passed directly to VBMS or are they turned into a PDF and stored (or both)? 11. When a claim is completed, does the system (VBMS) associate the completed claim with an ITF? 12. How does mail automation come into this and what is the involvement? ## Definition of Done - [x] We understand how the functionality works in VA.gov and VBMS - [x] We've [documented how the functionality will work](https://app.mural.co/t/coforma8350/m/coforma8350/1675717991659/e02c9447f57eb2d4d4c1b4dac76aec3f3264a656?sender=u0d70ac6e87daa7c066838517) for supplemental claims and sent to VBA for review - [ ] Design understands how to guide the user experience to enable design - [x] We have approval from VBA to reuse functionality in VA.gov and VBMS",1.0,"[discovery] Supplemental Claims | Learn how the Intent to File form/functionality works - ## Value Statement **_As a_** Veteran **_I want to_** submit an Intent to File form as soon as I know I plan to file a supplemental claim **_So that_** I can have more time to collect information to support my claim, and protect the earliest possible effective date for any benefits resulting from my claim. --- ## Background Context Claimants can now submit an Intent to File for a supplemental claim. The VBA wants to include this functionality in support of the updated policy. ## What do we want to learn? 1. Is there a separate ITF for the supplemental claim form, or can we use the version that accompanies the 526ez? _VA Form 21-0966, Intent to File a Claim for Compensation and/or Pension, or Survivors Pension and/or DIC applies to all claims so yes, the version that accompanies the 526EZ may be used._ 2. Can one intent to file be used for multiple claims? _For example, can an Intent to File that was previously submitted for a 526ez be extended to a Supplemental claim form. An Intent to File only applies to the next received, qualifying claim. It would not extend to multiple claims._ 3. Does an Intent to File form stay on file for reuse? Or does the claimant have to submit an Intent to File for each new claim? _A new Intent to File would have to be submitted for each claim._ 4. When a claim is closed, does it close the Intent to File? _Yes, if the Intent to File was absorbed by a claim, it would not apply to another, subsequently received claim. The Intent to File is closed when a qualifying claim is received._ 5. Does VA policy require that only one ITF can be active at a time? Or can there be multiple? 6. How does ITF data for 526 submissions feed into VBMS? 7. Does the system (VBMS or otherwise) associate an ITF to a claim. 8. What does the claims processor view in the VBMS to decide how to associate a claim to an ITF? 9. How does HINES batch processing handle acknowledgement letters for ITFs? What’s the logic? 10. (EVSS) Are ITFs passed directly to VBMS or are they turned into a PDF and stored (or both)? 11. When a claim is completed, does the system (VBMS) associate the completed claim with an ITF? 12. How does mail automation come into this and what is the involvement? ## Definition of Done - [x] We understand how the functionality works in VA.gov and VBMS - [x] We've [documented how the functionality will work](https://app.mural.co/t/coforma8350/m/coforma8350/1675717991659/e02c9447f57eb2d4d4c1b4dac76aec3f3264a656?sender=u0d70ac6e87daa7c066838517) for supplemental claims and sent to VBA for review - [ ] Design understands how to guide the user experience to enable design - [x] We have approval from VBA to reuse functionality in VA.gov and VBMS",1, supplemental claims learn how the intent to file form functionality works value statement as a veteran i want to submit an intent to file form as soon as i know i plan to file a supplemental claim so that i can have more time to collect information to support my claim and protect the earliest possible effective date for any benefits resulting from my claim background context claimants can now submit an intent to file for a supplemental claim the vba wants to include this functionality in support of the updated policy what do we want to learn is there a separate itf for the supplemental claim form or can we use the version that accompanies the va form intent to file a claim for compensation and or pension or survivors pension and or dic applies to all claims so yes the version that accompanies the may be used can one intent to file be used for multiple claims for example can an intent to file that was previously submitted for a be extended to a supplemental claim form an intent to file only applies to the next received qualifying claim it would not extend to multiple claims does an intent to file form stay on file for reuse or does the claimant have to submit an intent to file for each new claim a new intent to file would have to be submitted for each claim when a claim is closed does it close the intent to file yes if the intent to file was absorbed by a claim it would not apply to another subsequently received claim the intent to file is closed when a qualifying claim is received does va policy require that only one itf can be active at a time or can there be multiple how does itf data for submissions feed into vbms does the system vbms or otherwise associate an itf to a claim what does the claims processor view in the vbms to decide how to associate a claim to an itf how does hines batch processing handle acknowledgement letters for itfs what’s the logic evss are itfs passed directly to vbms or are they turned into a pdf and stored or both when a claim is completed does the system vbms associate the completed claim with an itf how does mail automation come into this and what is the involvement definition of done we understand how the functionality works in va gov and vbms we ve for supplemental claims and sent to vba for review design understands how to guide the user experience to enable design we have approval from vba to reuse functionality in va gov and vbms,1 144892,22583806231.0,IssuesEvent,2022-06-28 13:47:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Platform SRE: Q2 Support Bot Enhancements and Redesign ,needs-grooming needs research platform-initiative needs-design platform-sre crew-platform FY22-Q2 team-platform-sre,"## Problem Statement How might we improve the support bot ? ## Projected Launch Date April 1. ### Measurement * **Success metrics**: [Platform SRE OKRs](https://vfs.atlassian.net/wiki/spaces/SRE/pages/2136539137/DRAFT+-+OKRs+-+Platform+SRE+Department+-+Q2+22+Tracking) * **Release plan**: _link to Release Plan ticket_ # Completed Work ## Items Completed in Q2 [Items Completed in Q2](https://github.com/department-of-veterans-affairs/va.gov-team/issues?q=assignee%3Apowellkerry+is%3Aopen+Slackbot) ## Items Rolling over to Q3 [Items Rolling over to Q3](https://github.com/department-of-veterans-affairs/va.gov-team/issues/43503) NOTE: This task is an ongoing task and will rollover into Q3 and Q4",1.0,"Platform SRE: Q2 Support Bot Enhancements and Redesign - ## Problem Statement How might we improve the support bot ? ## Projected Launch Date April 1. ### Measurement * **Success metrics**: [Platform SRE OKRs](https://vfs.atlassian.net/wiki/spaces/SRE/pages/2136539137/DRAFT+-+OKRs+-+Platform+SRE+Department+-+Q2+22+Tracking) * **Release plan**: _link to Release Plan ticket_ # Completed Work ## Items Completed in Q2 [Items Completed in Q2](https://github.com/department-of-veterans-affairs/va.gov-team/issues?q=assignee%3Apowellkerry+is%3Aopen+Slackbot) ## Items Rolling over to Q3 [Items Rolling over to Q3](https://github.com/department-of-veterans-affairs/va.gov-team/issues/43503) NOTE: This task is an ongoing task and will rollover into Q3 and Q4",1,platform sre support bot enhancements and redesign problem statement how might we improve the support bot projected launch date april measurement success metrics release plan link to release plan ticket completed work items completed in items rolling over to note this task is an ongoing task and will rollover into and ,1 159753,25040769570.0,IssuesEvent,2022-11-04 20:29:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Cancelation discovery,discovery ux vaos-product-design,"## Background VAOS displays both appointments canceled by the Veteran and facility. Questions often arise as to why we show these. Generally our answer is that Veterans need to understand when a facility cancels the appt, because notifications are lacking. The same answer applies to Veteran-canceled appts. Additionally, Veterans use the VAOS appts list to verify their appts, so it needs to be a complete source of truth. The goal of this discovery is to evaluate our assumptions and provide a clearer understanding of why Veterans may or may not need this information ## Todo - [ ] Desk research - collect comments and background on cancelation into mini-report: - @outerpress - [ ] Ask product for canceled metrics - [ ] Ask for requirements around canceled appts - [ ] Aggregate Veteran feedback (ask Kay) ",1.0,"Cancelation discovery - ## Background VAOS displays both appointments canceled by the Veteran and facility. Questions often arise as to why we show these. Generally our answer is that Veterans need to understand when a facility cancels the appt, because notifications are lacking. The same answer applies to Veteran-canceled appts. Additionally, Veterans use the VAOS appts list to verify their appts, so it needs to be a complete source of truth. The goal of this discovery is to evaluate our assumptions and provide a clearer understanding of why Veterans may or may not need this information ## Todo - [ ] Desk research - collect comments and background on cancelation into mini-report: - @outerpress - [ ] Ask product for canceled metrics - [ ] Ask for requirements around canceled appts - [ ] Aggregate Veteran feedback (ask Kay) ",1,cancelation discovery background vaos displays both appointments canceled by the veteran and facility questions often arise as to why we show these generally our answer is that veterans need to understand when a facility cancels the appt because notifications are lacking the same answer applies to veteran canceled appts additionally veterans use the vaos appts list to verify their appts so it needs to be a complete source of truth the goal of this discovery is to evaluate our assumptions and provide a clearer understanding of why veterans may or may not need this information todo desk research collect comments and background on cancelation into mini report outerpress ask product for canceled metrics ask for requirements around canceled appts aggregate veteran feedback ask kay ,1 100564,12534777421.0,IssuesEvent,2020-06-04 20:05:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Drive-time eligible community care Veterans,content design discovery frontend vaos,"As a veteran who may eligible for Community Care based on drive time, I want to be prompted to update my physical address so I can request a Community Care appointment if I am eligible. --- ## Tasks - [ ] Determine where in the scheduling flow a user would be prompted to update their physical address as part of community care eligibility consideration - [ ] Determine content/copy for how to direct users to update their VA profile ## Items to consider - [ ] VAOSR is using the CCE API to check for CC eligibility - [ ] the CCE API will soon check for 'drive time' as part of eligibility - [ ] the CCE API uses the physical address of a Veteran via the PSSG data - [ ] PSSG data only updates twice a day - so if a Veteran updates their address in VA profile, it could take a bit before this change is reflected in all of the system ## Acceptance Criteria - [ ] A user is prompted to update their physical address in VA.gov when the CCE call cannot find a physical address to us - [ ] A user can navigate to the VA profile to update address - [ ] A user is informed to ""try again tomorrow"" for CC eligibility for that appointment type",1.0,"Drive-time eligible community care Veterans - As a veteran who may eligible for Community Care based on drive time, I want to be prompted to update my physical address so I can request a Community Care appointment if I am eligible. --- ## Tasks - [ ] Determine where in the scheduling flow a user would be prompted to update their physical address as part of community care eligibility consideration - [ ] Determine content/copy for how to direct users to update their VA profile ## Items to consider - [ ] VAOSR is using the CCE API to check for CC eligibility - [ ] the CCE API will soon check for 'drive time' as part of eligibility - [ ] the CCE API uses the physical address of a Veteran via the PSSG data - [ ] PSSG data only updates twice a day - so if a Veteran updates their address in VA profile, it could take a bit before this change is reflected in all of the system ## Acceptance Criteria - [ ] A user is prompted to update their physical address in VA.gov when the CCE call cannot find a physical address to us - [ ] A user can navigate to the VA profile to update address - [ ] A user is informed to ""try again tomorrow"" for CC eligibility for that appointment type",1,drive time eligible community care veterans as a veteran who may eligible for community care based on drive time i want to be prompted to update my physical address so i can request a community care appointment if i am eligible tasks determine where in the scheduling flow a user would be prompted to update their physical address as part of community care eligibility consideration determine content copy for how to direct users to update their va profile items to consider vaosr is using the cce api to check for cc eligibility the cce api will soon check for drive time as part of eligibility the cce api uses the physical address of a veteran via the pssg data pssg data only updates twice a day so if a veteran updates their address in va profile it could take a bit before this change is reflected in all of the system acceptance criteria a user is prompted to update their physical address in va gov when the cce call cannot find a physical address to us a user can navigate to the va profile to update address a user is informed to try again tomorrow for cc eligibility for that appointment type,1 94292,11861775491.0,IssuesEvent,2020-03-25 16:51:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design] - ""Personal Contact Info"" : Modal to Edit-in-Place: Desktop",design profile vsa-authenticated-exp,"## Tasks - [x] Update design to be Edit-in-place vs Modal. ## Acceptance Criteria - [x] All fields have been updated ",1.0,"[Design] - ""Personal Contact Info"" : Modal to Edit-in-Place: Desktop - ## Tasks - [x] Update design to be Edit-in-place vs Modal. ## Acceptance Criteria - [x] All fields have been updated ",1, personal contact info modal to edit in place desktop tasks update design to be edit in place vs modal acceptance criteria all fields have been updated ,1 143626,22107367906.0,IssuesEvent,2022-06-01 18:05:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Wording explaining VAOS link,design ux HCE-Checkin,"# Description From Stephen Barrs, ""There was some confusion as to what the VAOS link was there for and if Veterans would know what to expect when tapping it. Suggestion was to add some shorty preamble text before the link. This is not a suggestion that we do that, but an ask for your expert thoughts around that idea, and if there has been any veteran feedback on the VAOS link. ([Original Slack message](https://dsva.slack.com/archives/C02GXKL8WM6/p1641844626048000)) # Tasks - [x] Determine if we need another wording - [x] Create wording options - [x] Review with content # Acceptance Criteria - [x] Updated Sketch with final wording - [x] Create FE ticket",1.0,"[Design] Wording explaining VAOS link - # Description From Stephen Barrs, ""There was some confusion as to what the VAOS link was there for and if Veterans would know what to expect when tapping it. Suggestion was to add some shorty preamble text before the link. This is not a suggestion that we do that, but an ask for your expert thoughts around that idea, and if there has been any veteran feedback on the VAOS link. ([Original Slack message](https://dsva.slack.com/archives/C02GXKL8WM6/p1641844626048000)) # Tasks - [x] Determine if we need another wording - [x] Create wording options - [x] Review with content # Acceptance Criteria - [x] Updated Sketch with final wording - [x] Create FE ticket",1, wording explaining vaos link description from stephen barrs there was some confusion as to what the vaos link was there for and if veterans would know what to expect when tapping it suggestion was to add some shorty preamble text before the link this is not a suggestion that we do that but an ask for your expert thoughts around that idea and if there has been any veteran feedback on the vaos link tasks determine if we need another wording create wording options review with content acceptance criteria updated sketch with final wording create fe ticket,1 86550,10761663571.0,IssuesEvent,2019-10-31 21:18:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Bad Address Indicator Additional UX design for APO/FPO/DPO flow,design vsa-authenticated-exp,"## User Story As an UX designer, I want to be able to create UX design to show the process of moving ""US COUNTRY"" to the a later part of the flow when a user inputs their address/APO/FPO/DPO information. ## Tasks Create UX mock up design to show this flow with clickable prototype ## Acceptance Criteria - [ ] Upload UX mock ups and design and share with team members and design team. - [ ] Any revisions made from feedback. - [ ] Approved to move forward with FE dev work ## Upload Screenshots Below: ",1.0,"[Design] Bad Address Indicator Additional UX design for APO/FPO/DPO flow - ## User Story As an UX designer, I want to be able to create UX design to show the process of moving ""US COUNTRY"" to the a later part of the flow when a user inputs their address/APO/FPO/DPO information. ## Tasks Create UX mock up design to show this flow with clickable prototype ## Acceptance Criteria - [ ] Upload UX mock ups and design and share with team members and design team. - [ ] Any revisions made from feedback. - [ ] Approved to move forward with FE dev work ## Upload Screenshots Below: ",1, bad address indicator additional ux design for apo fpo dpo flow user story as an ux designer i want to be able to create ux design to show the process of moving us country to the a later part of the flow when a user inputs their address apo fpo dpo information tasks create ux mock up design to show this flow with clickable prototype acceptance criteria upload ux mock ups and design and share with team members and design team any revisions made from feedback approved to move forward with fe dev work upload screenshots below ,1 148884,23393329742.0,IssuesEvent,2022-08-11 20:09:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Misalignment of error messages (FL),frontend design vsa Facilities Facility Locator,"## Issue Description When the user makes a Facility or Service type mistake, the error message causes a visual misalignment of the fields. ![image](https://user-images.githubusercontent.com/55411834/110543165-329eca00-80e7-11eb-991e-f4086a2c81db.png) --- ## Tasks - [ ] Identify options for visually aligned error handling (staying consistent with the design system) ## Acceptance Criteria - [ ] Error messages do not cause Facility Locator search fields to be visually misaligned. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Misalignment of error messages (FL) - ## Issue Description When the user makes a Facility or Service type mistake, the error message causes a visual misalignment of the fields. ![image](https://user-images.githubusercontent.com/55411834/110543165-329eca00-80e7-11eb-991e-f4086a2c81db.png) --- ## Tasks - [ ] Identify options for visually aligned error handling (staying consistent with the design system) ## Acceptance Criteria - [ ] Error messages do not cause Facility Locator search fields to be visually misaligned. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,misalignment of error messages fl issue description when the user makes a facility or service type mistake the error message causes a visual misalignment of the fields tasks identify options for visually aligned error handling staying consistent with the design system acceptance criteria error messages do not cause facility locator search fields to be visually misaligned how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 145533,22708363800.0,IssuesEvent,2022-07-05 16:37:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyHealth - Design list of deleted messages for desktop and mobile,design myhealth myhealth-groundwork myhealth-secure-messaging,"## Issue Description As a secure messaging user, I need an inbox that lists my secure messages on desktop and mobile. --- ## Tasks - [x] Design deleted message list for desktop - [x] Design deleted message list for mobile - [x] Drop link to prototypes into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Mobile and desktop initial designs will be complete and ready for a design review with the remaining secure messaging screens. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] MyHealth - Design list of deleted messages for desktop and mobile - ## Issue Description As a secure messaging user, I need an inbox that lists my secure messages on desktop and mobile. --- ## Tasks - [x] Design deleted message list for desktop - [x] Design deleted message list for mobile - [x] Drop link to prototypes into a comment on this ticket - [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review ## Acceptance Criteria - [ ] Mobile and desktop initial designs will be complete and ready for a design review with the remaining secure messaging screens. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, myhealth design list of deleted messages for desktop and mobile issue description as a secure messaging user i need an inbox that lists my secure messages on desktop and mobile tasks design deleted message list for desktop design deleted message list for mobile drop link to prototypes into a comment on this ticket drop a note into mhv on vagov in slack when you are ready for tracey to review acceptance criteria mobile and desktop initial designs will be complete and ready for a design review with the remaining secure messaging screens how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 93382,11777759086.0,IssuesEvent,2020-03-16 15:17:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Break Up Mockups into Workflow Specific Files,design vsa vsa-ebenefits,"## Goal Using one large mockup between Design and Frontend is starting to become cumbersome and it would be easier if they were more discrete and specific to each workflow. ## Tasks - Breakup the mockups into smaller files so that changes can be found quickly and clearly - A centralized hub has been created that acts as a table of contents for all the mockups ## Acceptance Criteria - [x] Links to the new workflow mockups are shared with the team",1.0,"Break Up Mockups into Workflow Specific Files - ## Goal Using one large mockup between Design and Frontend is starting to become cumbersome and it would be easier if they were more discrete and specific to each workflow. ## Tasks - Breakup the mockups into smaller files so that changes can be found quickly and clearly - A centralized hub has been created that acts as a table of contents for all the mockups ## Acceptance Criteria - [x] Links to the new workflow mockups are shared with the team",1,break up mockups into workflow specific files goal using one large mockup between design and frontend is starting to become cumbersome and it would be easier if they were more discrete and specific to each workflow tasks breakup the mockups into smaller files so that changes can be found quickly and clearly a centralized hub has been created that acts as a table of contents for all the mockups acceptance criteria links to the new workflow mockups are shared with the team,1 150850,23724305057.0,IssuesEvent,2022-08-30 18:04:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design] Profile: ""I live on a United States military base outside of the United States."" doesn't get checked and the form doesn't change if someone clicks ""Use my mailing address for my home address."" in the home address form",design vsa authenticated-experience profile,"## Background Updating original details with my comment below: If I check ""I live on a United States military base outside of the United States."" for mailing address and save my address.... ![image.png](https://images.zenhubusercontent.com/5a4e5e33a016c5b034bc0750/019f6be1-1dca-40fd-a5a1-057461a13708) When I go to home address and click ""Use my mailing address for my home address"", the address changes below, but it does not check the ""I live on a United States military base outside of the United States."" checkbox, nor does it change to the military address form. I actually think this is largely a frontend ticket, but some mockups for desired functionality could probably be helpful. Let me know if you have other questions. ![image.png](https://images.zenhubusercontent.com/5a4e5e33a016c5b034bc0750/8aa1e10a-5f63-43a8-b15d-4e6c68f936f7) ## Tasks - [ ] Determine if we need any design changes here - [ ] If not, create ticket and outline fix to be implemented by frontend - [ ] Determine if we need any documentation changes for contact info ## Acceptance Criteria - [ ] We have determined whether we need any design updates or not for this ticket - [ ] Next steps for FE are outlined and ticketed - [ ] If needed, a ticket for documentation updates has been created ",1.0,"[Design] Profile: ""I live on a United States military base outside of the United States."" doesn't get checked and the form doesn't change if someone clicks ""Use my mailing address for my home address."" in the home address form - ## Background Updating original details with my comment below: If I check ""I live on a United States military base outside of the United States."" for mailing address and save my address.... ![image.png](https://images.zenhubusercontent.com/5a4e5e33a016c5b034bc0750/019f6be1-1dca-40fd-a5a1-057461a13708) When I go to home address and click ""Use my mailing address for my home address"", the address changes below, but it does not check the ""I live on a United States military base outside of the United States."" checkbox, nor does it change to the military address form. I actually think this is largely a frontend ticket, but some mockups for desired functionality could probably be helpful. Let me know if you have other questions. ![image.png](https://images.zenhubusercontent.com/5a4e5e33a016c5b034bc0750/8aa1e10a-5f63-43a8-b15d-4e6c68f936f7) ## Tasks - [ ] Determine if we need any design changes here - [ ] If not, create ticket and outline fix to be implemented by frontend - [ ] Determine if we need any documentation changes for contact info ## Acceptance Criteria - [ ] We have determined whether we need any design updates or not for this ticket - [ ] Next steps for FE are outlined and ticketed - [ ] If needed, a ticket for documentation updates has been created ",1, profile i live on a united states military base outside of the united states doesn t get checked and the form doesn t change if someone clicks use my mailing address for my home address in the home address form background updating original details with my comment below if i check i live on a united states military base outside of the united states for mailing address and save my address when i go to home address and click use my mailing address for my home address the address changes below but it does not check the i live on a united states military base outside of the united states checkbox nor does it change to the military address form i actually think this is largely a frontend ticket but some mockups for desired functionality could probably be helpful let me know if you have other questions tasks determine if we need any design changes here if not create ticket and outline fix to be implemented by frontend determine if we need any documentation changes for contact info acceptance criteria we have determined whether we need any design updates or not for this ticket next steps for fe are outlined and ticketed if needed a ticket for documentation updates has been created ,1 137505,20156274957.0,IssuesEvent,2022-02-09 16:44:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,va-alert padding is too big,bug vsp-design-system-team,"## Issue Description The `va-alert` padding takes up more space than it should (compared to the old component). ![image](https://user-images.githubusercontent.com/12970166/131754494-ae107ff9-7c40-47c3-9ee3-c6095446e0b5.png) ## Acceptance Criteria - [ ] The padding is uniform and reasonably sized (matches the legacy component)",1.0,"va-alert padding is too big - ## Issue Description The `va-alert` padding takes up more space than it should (compared to the old component). ![image](https://user-images.githubusercontent.com/12970166/131754494-ae107ff9-7c40-47c3-9ee3-c6095446e0b5.png) ## Acceptance Criteria - [ ] The padding is uniform and reasonably sized (matches the legacy component)",1,va alert padding is too big issue description the va alert padding takes up more space than it should compared to the old component acceptance criteria the padding is uniform and reasonably sized matches the legacy component ,1 175555,27880020677.0,IssuesEvent,2023-03-21 18:38:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] 10-10CG Sketch File “Source of Truth” and Documentation ,design 1010-team 1010-cg story improvement,"### Background: Update the existing Sketch file to being a source of truth to match staging/production including all pages (both desktop and mobile versions), states, errors and annotations. Add a page to keep master templates. Add a page and create a wireflow of the entire application. #### Naming Conventions **Pages:** Create Pages named consistently with numbers/wording used on progress tracker in form. 1-VeteranInformation, 2-PrimaryCaregiver for placement of staging/production artboards. Keep existing pages in file as to not break any links in GH. In future: Name Pages with conventions: Common Name-EPIC or ISSUE number Example: FacilitiesRedesign-E12345 **Artboards:** CommonName-Size-{url}-State Examples: Demographics-Desktop-{vet-1}-STAGING or Demographics-Mobile-{vet-1}-Issue12345 _Don’t change names or delete old pages this will break any existing links out there in closed tickets or conversations._ ### User Story: As a designer/PM it is clear what file should be the master source of truth (what is approved and in staging) as well as a clear trail to follow to find references of past work. ### Tasks Ideas: - [x] Meet with a goal to revise these tasks, discuss questions, decide on conventions, etc. and adjust description of this ticket. - [x] Check design system Sketch file to copy out layout pages with grids (tip from orientation session) - [x] Create a Templates Page in the Sketch file and create desktop and mobile templates that include padding and vertical spacing details. Keep all components and type styles in the templates page linked to the master VA Design System file. - [x] Create a Wireframe Page, the overall map of product that will show the pages in the form, fields included and flow. - [x] Create new Pages by section of form (_Veteran Information_ for example) and create artboards for each page/state within that section that aligns with staging. Include mobile designs. ### Acceptance Criteria: The Sketch file is a reliable source of truth doc that includes pages that aligns with staging/production and the VA Design System. There are naming conventions and patterns established to add new design iterations and explorations to the file. ",1.0,"[DESIGN] 10-10CG Sketch File “Source of Truth” and Documentation - ### Background: Update the existing Sketch file to being a source of truth to match staging/production including all pages (both desktop and mobile versions), states, errors and annotations. Add a page to keep master templates. Add a page and create a wireflow of the entire application. #### Naming Conventions **Pages:** Create Pages named consistently with numbers/wording used on progress tracker in form. 1-VeteranInformation, 2-PrimaryCaregiver for placement of staging/production artboards. Keep existing pages in file as to not break any links in GH. In future: Name Pages with conventions: Common Name-EPIC or ISSUE number Example: FacilitiesRedesign-E12345 **Artboards:** CommonName-Size-{url}-State Examples: Demographics-Desktop-{vet-1}-STAGING or Demographics-Mobile-{vet-1}-Issue12345 _Don’t change names or delete old pages this will break any existing links out there in closed tickets or conversations._ ### User Story: As a designer/PM it is clear what file should be the master source of truth (what is approved and in staging) as well as a clear trail to follow to find references of past work. ### Tasks Ideas: - [x] Meet with a goal to revise these tasks, discuss questions, decide on conventions, etc. and adjust description of this ticket. - [x] Check design system Sketch file to copy out layout pages with grids (tip from orientation session) - [x] Create a Templates Page in the Sketch file and create desktop and mobile templates that include padding and vertical spacing details. Keep all components and type styles in the templates page linked to the master VA Design System file. - [x] Create a Wireframe Page, the overall map of product that will show the pages in the form, fields included and flow. - [x] Create new Pages by section of form (_Veteran Information_ for example) and create artboards for each page/state within that section that aligns with staging. Include mobile designs. ### Acceptance Criteria: The Sketch file is a reliable source of truth doc that includes pages that aligns with staging/production and the VA Design System. There are naming conventions and patterns established to add new design iterations and explorations to the file. ",1, sketch file “source of truth” and documentation background update the existing sketch file to being a source of truth to match staging production including all pages both desktop and mobile versions states errors and annotations add a page to keep master templates add a page and create a wireflow of the entire application naming conventions pages create pages named consistently with numbers wording used on progress tracker in form veteraninformation primarycaregiver for placement of staging production artboards keep existing pages in file as to not break any links in gh in future name pages with conventions common name epic or issue number example facilitiesredesign artboards commonname size url state examples demographics desktop vet staging or demographics mobile vet don’t change names or delete old pages this will break any existing links out there in closed tickets or conversations user story as a designer pm it is clear what file should be the master source of truth what is approved and in staging as well as a clear trail to follow to find references of past work tasks ideas meet with a goal to revise these tasks discuss questions decide on conventions etc and adjust description of this ticket check design system sketch file to copy out layout pages with grids tip from orientation session create a templates page in the sketch file and create desktop and mobile templates that include padding and vertical spacing details keep all components and type styles in the templates page linked to the master va design system file create a wireframe page the overall map of product that will show the pages in the form fields included and flow create new pages by section of form veteran information for example and create artboards for each page state within that section that aligns with staging include mobile designs acceptance criteria the sketch file is a reliable source of truth doc that includes pages that aligns with staging production and the va design system there are naming conventions and patterns established to add new design iterations and explorations to the file ,1 136104,19705006996.0,IssuesEvent,2022-01-12 20:51:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,ProcessList web component: migration,vsp-design-system-team,"## Description There are no uses of ProcessList in `vets-website`, so no need to perform the migration. But we do need to let teams know that it exists. Announce the component at least in the #vfs-frontend channel. Might be worth reaching out to the teams who work on the static page templates as well. ## Details Sample announcement: >:wave: The Design System has just published a new version of component-library which includes , as well as made it available in vets-website. The migration script is also capable of automatically migrating your directories to this new component. Why does this matter to me The new additional info Web Component has a number of enhancements/fixes: Keyboard control with space and ""Enter"" key Design fix for the blue border when expanded Improved colors for contrast & consistency The web component is already loaded into the site, so removing your old AdditionalInfo imports will reduce application bundle size and improve performance. How do I migrate First, make sure your branch is using the latest master, and run yarn install. We have a script that you can use to assist with this process. You pass it two arguments: --directory - the directory you wish to migrate --component - the name of the React component to find and transform into a web component For example, to run this migration in the platform directory, you would run: yarn migrate-component --dir src/platform --component AdditionalInfo --- *NOTE:* One change with is that it no longer exposes onClick for an external analytics event. There is still an internal component-library-analytics event that gets fired which includes the action (expand/collapse) and the trigger text. Just be aware of this so that you don't lose any tracking data that may be used in your dashboards. Reach out to us if you have any questions/concerns about this. ## Acceptance Criteria - [ ] Craft announcement and post in #vfs-frontend - [ ] Reach out to static templates teams directly",1.0,"ProcessList web component: migration - ## Description There are no uses of ProcessList in `vets-website`, so no need to perform the migration. But we do need to let teams know that it exists. Announce the component at least in the #vfs-frontend channel. Might be worth reaching out to the teams who work on the static page templates as well. ## Details Sample announcement: >:wave: The Design System has just published a new version of component-library which includes , as well as made it available in vets-website. The migration script is also capable of automatically migrating your directories to this new component. Why does this matter to me The new additional info Web Component has a number of enhancements/fixes: Keyboard control with space and ""Enter"" key Design fix for the blue border when expanded Improved colors for contrast & consistency The web component is already loaded into the site, so removing your old AdditionalInfo imports will reduce application bundle size and improve performance. How do I migrate First, make sure your branch is using the latest master, and run yarn install. We have a script that you can use to assist with this process. You pass it two arguments: --directory - the directory you wish to migrate --component - the name of the React component to find and transform into a web component For example, to run this migration in the platform directory, you would run: yarn migrate-component --dir src/platform --component AdditionalInfo --- *NOTE:* One change with is that it no longer exposes onClick for an external analytics event. There is still an internal component-library-analytics event that gets fired which includes the action (expand/collapse) and the trigger text. Just be aware of this so that you don't lose any tracking data that may be used in your dashboards. Reach out to us if you have any questions/concerns about this. ## Acceptance Criteria - [ ] Craft announcement and post in #vfs-frontend - [ ] Reach out to static templates teams directly",1,processlist web component migration description there are no uses of processlist in vets website so no need to perform the migration but we do need to let teams know that it exists announce the component at least in the vfs frontend channel might be worth reaching out to the teams who work on the static page templates as well details sample announcement wave the design system has just published a new version of component library which includes as well as made it available in vets website the migration script is also capable of automatically migrating your directories to this new component why does this matter to me the new additional info web component has a number of enhancements fixes keyboard control with space and enter key design fix for the blue border when expanded improved colors for contrast consistency the web component is already loaded into the site so removing your old additionalinfo imports will reduce application bundle size and improve performance how do i migrate first make sure your branch is using the latest master and run yarn install we have a script that you can use to assist with this process you pass it two arguments directory the directory you wish to migrate component the name of the react component to find and transform into a web component for example to run this migration in the platform directory you would run yarn migrate component dir src platform component additionalinfo note one change with is that it no longer exposes onclick for an external analytics event there is still an internal component library analytics event that gets fired which includes the action expand collapse and the trigger text just be aware of this so that you don t lose any tracking data that may be used in your dashboards reach out to us if you have any questions concerns about this acceptance criteria craft announcement and post in vfs frontend reach out to static templates teams directly,1 136941,20021533089.0,IssuesEvent,2022-02-01 16:49:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Discovery] Improvements to the migration script,vsp-design-system-team,"## Description As we use the migration script for migrating more and more React components to web components, we are discovering more and more weaknesses in the script. We'd like to take a little time and figure out if there are some ways we can improve it. ## Acceptance Criteria - [ ] Review the migration script and consider any improvements we might make - [ ] Document any necessary improvements in this ticket - [ ] Tag Katy and Carol for review",1.0,"[Discovery] Improvements to the migration script - ## Description As we use the migration script for migrating more and more React components to web components, we are discovering more and more weaknesses in the script. We'd like to take a little time and figure out if there are some ways we can improve it. ## Acceptance Criteria - [ ] Review the migration script and consider any improvements we might make - [ ] Document any necessary improvements in this ticket - [ ] Tag Katy and Carol for review",1, improvements to the migration script description as we use the migration script for migrating more and more react components to web components we are discovering more and more weaknesses in the script we d like to take a little time and figure out if there are some ways we can improve it acceptance criteria review the migration script and consider any improvements we might make document any necessary improvements in this ticket tag katy and carol for review,1 114308,14546015279.0,IssuesEvent,2020-12-15 20:33:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Schedule UAT for View Payment History,design view-payments vsa vsa-ebenefits,"## Background Conduct user acceptance testing (UAT) for View Payment history. ### Considerations UAT will supersede final usability testing. ### Tasks - [x] Create UAT plan - [x] Create conversation guide/acceptance punchlist - [x] Submit RP and CG for review - [x] Deliver RP and CP to Lauren A. - [x] Schedule and conduct UAT sessions ### Acceptance criteria - [x] UAT plan created - [x] Convo guide/punchlist created - [x] UAT sessions scheduled ",1.0,"Schedule UAT for View Payment History - ## Background Conduct user acceptance testing (UAT) for View Payment history. ### Considerations UAT will supersede final usability testing. ### Tasks - [x] Create UAT plan - [x] Create conversation guide/acceptance punchlist - [x] Submit RP and CG for review - [x] Deliver RP and CP to Lauren A. - [x] Schedule and conduct UAT sessions ### Acceptance criteria - [x] UAT plan created - [x] Convo guide/punchlist created - [x] UAT sessions scheduled ",1,schedule uat for view payment history background conduct user acceptance testing uat for view payment history considerations uat will supersede final usability testing tasks create uat plan create conversation guide acceptance punchlist submit rp and cg for review deliver rp and cp to lauren a schedule and conduct uat sessions acceptance criteria uat plan created convo guide punchlist created uat sessions scheduled ,1 117142,15056739409.0,IssuesEvent,2021-02-03 20:37:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Adding a link to example of component in prod.,vsp-design-system-team,"## Issue Description Based on user feedback, it would be helpful to add a link to an example of a component in production in the Design System. --- ## Tasks - [ ] Create list of components that are frequently used - [ ] Find examples of components on prod - [ ] Add a link to in SB to the production version of the component ## Acceptance Criteria - [ ] Most frequently used components have a link to an example of that component on production. --- ",1.0,"Adding a link to example of component in prod. - ## Issue Description Based on user feedback, it would be helpful to add a link to an example of a component in production in the Design System. --- ## Tasks - [ ] Create list of components that are frequently used - [ ] Find examples of components on prod - [ ] Add a link to in SB to the production version of the component ## Acceptance Criteria - [ ] Most frequently used components have a link to an example of that component on production. --- ",1,adding a link to example of component in prod issue description based on user feedback it would be helpful to add a link to an example of a component in production in the design system tasks create list of components that are frequently used find examples of components on prod add a link to in sb to the production version of the component acceptance criteria most frequently used components have a link to an example of that component on production ,1 118468,15301753905.0,IssuesEvent,2021-02-24 13:59:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyVA: Create clickable prototype for research,design my-va-dashboard vsa-authenticated-exp,"## Background In preparation for usability testing, we need to create clickable prototypes. https://vsateams.invisionapp.com/share/XNZWCYAYD45#/444774121_Home_Screen ## Tasks - [x] Create clickable prototype - [ ] Review with Matt/Samara",1.0,"[Design] MyVA: Create clickable prototype for research - ## Background In preparation for usability testing, we need to create clickable prototypes. https://vsateams.invisionapp.com/share/XNZWCYAYD45#/444774121_Home_Screen ## Tasks - [x] Create clickable prototype - [ ] Review with Matt/Samara",1, myva create clickable prototype for research background in preparation for usability testing we need to create clickable prototypes tasks create clickable prototype review with matt samara,1 140025,20999240152.0,IssuesEvent,2022-03-29 15:53:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,A11y documentation audit: Review Buttons component documentation,vsp-design-system-team,"## Description We want to audit our accessibility documentation on design.va.gov to make sure that it is up-to-date with current accessibility guidelines. For this ticket, we need to review the [accessibility guidelines for the Buttons component](https://design.va.gov/components/buttons#accessibility-considerations) on design.va.gov and provide any updates that need to be made to the existing documentation as a comment on this ticket. ## Details Just for reference, here are some useful links: [Platform accessibility standards](https://vfs.atlassian.net/wiki/spaces/pilot/pages/1777893393/WCAG+2.1+success+criteria+and+foundational+testing) [VFS Team accessibility responsibilities](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/roles-and-responsibilities/accessibility.md#accessibility) [VA.gov experience standards](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) VSP WCAG 2.1 Presentations: [VSP WCAG2.1 Foundational Testing Redux](https://app.zenhub.com/files/133843125/368da85e-7f1f-4332-8ccb-6808e52a8a51/download) [VSP WCAG2.1 New Success Criteria](https://app.zenhub.com/files/133843125/5475fd9b-9d2e-4a6a-901f-97682664eb33/download) ## Acceptance Criteria - [ ] Review accessibility guidelines on the following pages of design.va.gov: - [ ] https://design.va.gov/components/buttons#accessibility-considerations - [ ] Make sure accessibility guidelines match the performance of the component in Storybook - [ ] Add notes on any necessary updates as a comment on this ticket - [ ] Ping Katy, Carol, and Natalie for review",1.0,"A11y documentation audit: Review Buttons component documentation - ## Description We want to audit our accessibility documentation on design.va.gov to make sure that it is up-to-date with current accessibility guidelines. For this ticket, we need to review the [accessibility guidelines for the Buttons component](https://design.va.gov/components/buttons#accessibility-considerations) on design.va.gov and provide any updates that need to be made to the existing documentation as a comment on this ticket. ## Details Just for reference, here are some useful links: [Platform accessibility standards](https://vfs.atlassian.net/wiki/spaces/pilot/pages/1777893393/WCAG+2.1+success+criteria+and+foundational+testing) [VFS Team accessibility responsibilities](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/roles-and-responsibilities/accessibility.md#accessibility) [VA.gov experience standards](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) VSP WCAG 2.1 Presentations: [VSP WCAG2.1 Foundational Testing Redux](https://app.zenhub.com/files/133843125/368da85e-7f1f-4332-8ccb-6808e52a8a51/download) [VSP WCAG2.1 New Success Criteria](https://app.zenhub.com/files/133843125/5475fd9b-9d2e-4a6a-901f-97682664eb33/download) ## Acceptance Criteria - [ ] Review accessibility guidelines on the following pages of design.va.gov: - [ ] https://design.va.gov/components/buttons#accessibility-considerations - [ ] Make sure accessibility guidelines match the performance of the component in Storybook - [ ] Add notes on any necessary updates as a comment on this ticket - [ ] Ping Katy, Carol, and Natalie for review",1, documentation audit review buttons component documentation description we want to audit our accessibility documentation on design va gov to make sure that it is up to date with current accessibility guidelines for this ticket we need to review the on design va gov and provide any updates that need to be made to the existing documentation as a comment on this ticket details just for reference here are some useful links vsp wcag presentations acceptance criteria review accessibility guidelines on the following pages of design va gov make sure accessibility guidelines match the performance of the component in storybook add notes on any necessary updates as a comment on this ticket ping katy carol and natalie for review,1 88101,11032100848.0,IssuesEvent,2019-12-06 19:21:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Urgent Care PDF Research Synthesis,design research vsa vsa-facilities,"## User Story As the Facility Locator team, we need to understand how to provide information on urgent care eligibility and benefits in preparation for a visit. ## Tasks Synthesize information gleaned from Urgent Care PDF research sessions ## Acceptance Criteria [ ] Research readout summary which includes findings, recommendations, additional questions This follows [#3897]",1.0,"Urgent Care PDF Research Synthesis - ## User Story As the Facility Locator team, we need to understand how to provide information on urgent care eligibility and benefits in preparation for a visit. ## Tasks Synthesize information gleaned from Urgent Care PDF research sessions ## Acceptance Criteria [ ] Research readout summary which includes findings, recommendations, additional questions This follows [#3897]",1,urgent care pdf research synthesis user story as the facility locator team we need to understand how to provide information on urgent care eligibility and benefits in preparation for a visit tasks synthesize information gleaned from urgent care pdf research sessions acceptance criteria research readout summary which includes findings recommendations additional questions this follows ,1 100426,12521319632.0,IssuesEvent,2020-06-03 17:14:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"[Design] DL - Debt list, Current debts, default",design vsa vsa-benefits-2,"## Issue Description We need to create mockups of the debt list screen, showing debts populated under current debts: - Debt with no action taken (ex: pension debt with no benefits to withhold) - Debt with action taken (ex: compensation debt that is being repaid out of pocket) - Ch 35 triple debt (for illustration's sake) --- ## Tasks - [ ] Create mockups - [ ] Share with design team - [ ] Update [use case doc](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/debt-letters-mvp/use-cases.md) - [ ] Update this ticket ## Acceptance Criteria - [ ] Screen(s) created with each of the debt statuses above - [ ] [Use case doc updated](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/debt-letters-mvp/use-cases.md)",1.0,"[Design] DL - Debt list, Current debts, default - ## Issue Description We need to create mockups of the debt list screen, showing debts populated under current debts: - Debt with no action taken (ex: pension debt with no benefits to withhold) - Debt with action taken (ex: compensation debt that is being repaid out of pocket) - Ch 35 triple debt (for illustration's sake) --- ## Tasks - [ ] Create mockups - [ ] Share with design team - [ ] Update [use case doc](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/debt-letters-mvp/use-cases.md) - [ ] Update this ticket ## Acceptance Criteria - [ ] Screen(s) created with each of the debt statuses above - [ ] [Use case doc updated](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/debt-letters-mvp/use-cases.md)",1, dl debt list current debts default issue description we need to create mockups of the debt list screen showing debts populated under current debts debt with no action taken ex pension debt with no benefits to withhold debt with action taken ex compensation debt that is being repaid out of pocket ch triple debt for illustration s sake tasks create mockups share with design team update update this ticket acceptance criteria screen s created with each of the debt statuses above ,1 144111,22273763471.0,IssuesEvent,2022-06-10 14:39:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Add VAOS SLP widget Cerner logic in the tool,product needs-info vaos-product-design,"## Description Review and update Cerner offboarding links when not in the scheduling flow. ### Background The Public Websites team manages the authentication widget logic on the VAOS static landing page (/health-care/schedule-view-va-appointments/) This widget detects if a user is registered at a Cerner site and displays a link to the My VA Health portal. Code for this widget is here: - auth - https://github.com/department-of-veterans-affairs/vets-website/blob/5fca036932a6e9[…]edule-view-va-appointments-page/components/AuthContent/index.js - unauth - https://github.com/department-of-veterans-affairs/vets-website/blob/5fca036932a6e9[…]ule-view-va-appointments-page/components/UnauthContent/index.js ![slp cerner widget.png](https://images.zenhubusercontent.com/5f7dd2dad6b9a9301bbab94e/ed38fe8d-b601-499e-842c-6897e89c9f6e) Old behavior: - Given user is not signed in, When user goes directly to the VAOS homepage (`/health-care/schedule-view-va-appointments/appointments`), Then user is prompted to sign and redirected is to the static landing page (`/health-care/schedule-view-va-appointments/`) - Given user is signed in, When user goes directly to the VAOS homepage, Then VAOS homepage loads New behavior: - If user goes directly to the VAOS homepage, then page loads regardless of when they authenticated (i.e. no redirects back to static landing page) ### Business Requirements - Scheduling and appointments for Cerner sites are managed in the My VA Health portal - Veterans registered at Cerner sites and eligible for Community Care can use VAOS to request Community Care appointments",1.0,"Add VAOS SLP widget Cerner logic in the tool - ## Description Review and update Cerner offboarding links when not in the scheduling flow. ### Background The Public Websites team manages the authentication widget logic on the VAOS static landing page (/health-care/schedule-view-va-appointments/) This widget detects if a user is registered at a Cerner site and displays a link to the My VA Health portal. Code for this widget is here: - auth - https://github.com/department-of-veterans-affairs/vets-website/blob/5fca036932a6e9[…]edule-view-va-appointments-page/components/AuthContent/index.js - unauth - https://github.com/department-of-veterans-affairs/vets-website/blob/5fca036932a6e9[…]ule-view-va-appointments-page/components/UnauthContent/index.js ![slp cerner widget.png](https://images.zenhubusercontent.com/5f7dd2dad6b9a9301bbab94e/ed38fe8d-b601-499e-842c-6897e89c9f6e) Old behavior: - Given user is not signed in, When user goes directly to the VAOS homepage (`/health-care/schedule-view-va-appointments/appointments`), Then user is prompted to sign and redirected is to the static landing page (`/health-care/schedule-view-va-appointments/`) - Given user is signed in, When user goes directly to the VAOS homepage, Then VAOS homepage loads New behavior: - If user goes directly to the VAOS homepage, then page loads regardless of when they authenticated (i.e. no redirects back to static landing page) ### Business Requirements - Scheduling and appointments for Cerner sites are managed in the My VA Health portal - Veterans registered at Cerner sites and eligible for Community Care can use VAOS to request Community Care appointments",1,add vaos slp widget cerner logic in the tool description review and update cerner offboarding links when not in the scheduling flow background the public websites team manages the authentication widget logic on the vaos static landing page health care schedule view va appointments this widget detects if a user is registered at a cerner site and displays a link to the my va health portal code for this widget is here auth edule view va appointments page components authcontent index js unauth ule view va appointments page components unauthcontent index js old behavior given user is not signed in when user goes directly to the vaos homepage health care schedule view va appointments appointments then user is prompted to sign and redirected is to the static landing page health care schedule view va appointments given user is signed in when user goes directly to the vaos homepage then vaos homepage loads new behavior if user goes directly to the vaos homepage then page loads regardless of when they authenticated i e no redirects back to static landing page business requirements scheduling and appointments for cerner sites are managed in the my va health portal veterans registered at cerner sites and eligible for community care can use vaos to request community care appointments,1 87089,10866770657.0,IssuesEvent,2019-11-14 22:01:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Candidate Address Validation Design Work,content-ia-team design vsa-authenticated-exp,"*Historical reference of the first draft of this flow.* *- [11339] (https://app.zenhub.com/workspaces/vft-59c95ae5fda7577a9b3184f8/issues/department-of-veterans-affairs/vets.gov-team/11339)* ----------------------------------------------------------------------------------- @artistgreen will upload his UX documentation to this ticket. ## User Story As an UX designer, I need to create UX mock up so the copy team can validate/suggest any content changes needed to finalize the UX designs. ## Goal Have the content/copy team to validate or suggest verbiage to finalize the UX design mock ups. ....... ## Definition of Done - [x] Content team has reviewed the mock ups. - [x] Necessary changes/suggestions were made. - [ ] *This relates to epic ticket #1287 *Check the box below when this has been completed and comment ""done"". ",1.0,"Candidate Address Validation Design Work - *Historical reference of the first draft of this flow.* *- [11339] (https://app.zenhub.com/workspaces/vft-59c95ae5fda7577a9b3184f8/issues/department-of-veterans-affairs/vets.gov-team/11339)* ----------------------------------------------------------------------------------- @artistgreen will upload his UX documentation to this ticket. ## User Story As an UX designer, I need to create UX mock up so the copy team can validate/suggest any content changes needed to finalize the UX designs. ## Goal Have the content/copy team to validate or suggest verbiage to finalize the UX design mock ups. ....... ## Definition of Done - [x] Content team has reviewed the mock ups. - [x] Necessary changes/suggestions were made. - [ ] *This relates to epic ticket #1287 *Check the box below when this has been completed and comment ""done"". ",1,candidate address validation design work historical reference of the first draft of this flow artistgreen will upload his ux documentation to this ticket user story as an ux designer i need to create ux mock up so the copy team can validate suggest any content changes needed to finalize the ux designs goal have the content copy team to validate or suggest verbiage to finalize the ux design mock ups definition of done content team has reviewed the mock ups necessary changes suggestions were made this relates to epic ticket check the box below when this has been completed and comment done ,1 139146,20782380391.0,IssuesEvent,2022-03-16 15:48:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Public Websites: Sprint 39 Priorities ,vsa-public-websites frontend vsa planned-work Design -> Frontend,"## Priorities 1. Build out CLP FE Panel tickets - Panel 1 [#17636] & Panel 2 Epics [#17642] 2. Finalizing R&S functionality (post code freeze) - Remaining tickets from Sprint 38 3. Outstanding tickets from Sprint 38 not already included in the priorities listed above 4. Intake Requests for January, along with some applicable Tech Debt (508/a11y issues) 5. Transformer followup and close out of #16440 (Pending Platform comparison tool) 6. Follow up with CLP Content Nodes for FE. ### Campaign Landing Page MVP 1.0 **FE Transformer** - [x] [FE] Create CLP Template + graphql query [Transformers] #17514 - [ ] [FE] Create transformer/output/input for the CLP [Transformers] #17513 - [x] [Design/PM] Work with a11y to review mural design. 508/a11y Review #18756 **FE Panel 1 [#17636]** - [x] [FE] CLP Hero Banner Node Title, Header and Blurb H3 #17638 - [x] [FE] CLP Field Images (Hero, Field Image, Field Image Alt) #17640 - [x] [FE] CLP Primary CTA (Label, Link) #17641 **FE Panel 2 Epics [#17642]** - [x] [FE] CLP Field Title and Blurb H2 “Why this matters"" #17644 - [x] [FE] CLP ""Why this matters"" Field Secondary CTA (Label, Link) #17645 ### Resources and Support Priority R&S Breakdown: WIP [MVP 1.1 EPIC #15588] [Iterate EPIC #15584] **FE** - [x] [FE] PDF/Print Save Checklist - mobile and desktop - R&S 1.1 #18337 - [x] [FE] Browse by audience RS homepage FE update (WIP - Nick) #17276 `(BLOCKED)` - [x] [FE] Auto-expand accordion items if the URL hash matches the item ID #15798 ### Transformers - [x] [PM] Transformer followup and close out of #16440 - [x] [PM] Determine ETA on Platform CMS Transformer Comparison Tool ### Cerner Support Main objective: Acquire facility list to determine what facilities need to be set accordingly. ### Intake Request - Techical Debt **FE** - [x] [FE/Content] Analytics Implementation for COVID FAQ Accordion Embedded Links #13727 (WIP - Nick) ### Kanban Board _Please select a ticket and include [WIP - [NAME]] next to the ticket that is being worked._ Pick up tickets by priority on the `To Do ` section to begin and move ticket through kanban workflow until `Done`. Please include resolution steps on tickets along with instructions if for some reason you are unable to complete the ticket during this sprint. Please tag @brianalloyd on tickets when moved to **Done** section for validation and closeout. Please reach out if you have any questions or concerns in the interim. Welcome to **PW team** (for this sprint) we're excited to have the help.
TO DO
ON-GOING - [ ] [FE] Enhancement: RS mobile views, left margin is too smooshed to the edge and cutting off text #17470 (WIP Sandra)
DONE - [x] [FE] Link TTY: 711 number in footer and right rail of hub landing pages #18151 (Sandra) @brianalloyd - [x] [FE] [COGNITION]: Footer links are inconsistently styled and missing interactive cues #3179 (Sandra) @brianalloyd - [x] [FE] Main nav's ""Contact Us"" button can wrap when logged-in user has a long name #18412 (Sandra) @brianalloyd - [x] [FE] [COGNITION]: Multiple ambiguities with linked text in content block #3556 (Sandra) @brianalloyd - [x] [FE] Use redesigned ""In this section"" button for triggering sidebar on mobile devices across benefit pages #13325 (WIP Erik) - [x] [FE] VA.gov mobile nav bugs #8256 (WIP Erik) ",1.0,"Public Websites: Sprint 39 Priorities - ## Priorities 1. Build out CLP FE Panel tickets - Panel 1 [#17636] & Panel 2 Epics [#17642] 2. Finalizing R&S functionality (post code freeze) - Remaining tickets from Sprint 38 3. Outstanding tickets from Sprint 38 not already included in the priorities listed above 4. Intake Requests for January, along with some applicable Tech Debt (508/a11y issues) 5. Transformer followup and close out of #16440 (Pending Platform comparison tool) 6. Follow up with CLP Content Nodes for FE. ### Campaign Landing Page MVP 1.0 **FE Transformer** - [x] [FE] Create CLP Template + graphql query [Transformers] #17514 - [ ] [FE] Create transformer/output/input for the CLP [Transformers] #17513 - [x] [Design/PM] Work with a11y to review mural design. 508/a11y Review #18756 **FE Panel 1 [#17636]** - [x] [FE] CLP Hero Banner Node Title, Header and Blurb H3 #17638 - [x] [FE] CLP Field Images (Hero, Field Image, Field Image Alt) #17640 - [x] [FE] CLP Primary CTA (Label, Link) #17641 **FE Panel 2 Epics [#17642]** - [x] [FE] CLP Field Title and Blurb H2 “Why this matters"" #17644 - [x] [FE] CLP ""Why this matters"" Field Secondary CTA (Label, Link) #17645 ### Resources and Support Priority R&S Breakdown: WIP [MVP 1.1 EPIC #15588] [Iterate EPIC #15584] **FE** - [x] [FE] PDF/Print Save Checklist - mobile and desktop - R&S 1.1 #18337 - [x] [FE] Browse by audience RS homepage FE update (WIP - Nick) #17276 `(BLOCKED)` - [x] [FE] Auto-expand accordion items if the URL hash matches the item ID #15798 ### Transformers - [x] [PM] Transformer followup and close out of #16440 - [x] [PM] Determine ETA on Platform CMS Transformer Comparison Tool ### Cerner Support Main objective: Acquire facility list to determine what facilities need to be set accordingly. ### Intake Request - Techical Debt **FE** - [x] [FE/Content] Analytics Implementation for COVID FAQ Accordion Embedded Links #13727 (WIP - Nick) ### Kanban Board _Please select a ticket and include [WIP - [NAME]] next to the ticket that is being worked._ Pick up tickets by priority on the `To Do ` section to begin and move ticket through kanban workflow until `Done`. Please include resolution steps on tickets along with instructions if for some reason you are unable to complete the ticket during this sprint. Please tag @brianalloyd on tickets when moved to **Done** section for validation and closeout. Please reach out if you have any questions or concerns in the interim. Welcome to **PW team** (for this sprint) we're excited to have the help.
TO DO
ON-GOING - [ ] [FE] Enhancement: RS mobile views, left margin is too smooshed to the edge and cutting off text #17470 (WIP Sandra)
DONE - [x] [FE] Link TTY: 711 number in footer and right rail of hub landing pages #18151 (Sandra) @brianalloyd - [x] [FE] [COGNITION]: Footer links are inconsistently styled and missing interactive cues #3179 (Sandra) @brianalloyd - [x] [FE] Main nav's ""Contact Us"" button can wrap when logged-in user has a long name #18412 (Sandra) @brianalloyd - [x] [FE] [COGNITION]: Multiple ambiguities with linked text in content block #3556 (Sandra) @brianalloyd - [x] [FE] Use redesigned ""In this section"" button for triggering sidebar on mobile devices across benefit pages #13325 (WIP Erik) - [x] [FE] VA.gov mobile nav bugs #8256 (WIP Erik) ",1,public websites sprint priorities priorities build out clp fe panel tickets panel panel epics finalizing r s functionality post code freeze remaining tickets from sprint outstanding tickets from sprint not already included in the priorities listed above intake requests for january along with some applicable tech debt issues transformer followup and close out of pending platform comparison tool follow up with clp content nodes for fe campaign landing page mvp fe transformer create clp template graphql query create transformer output input for the clp work with to review mural design review fe panel clp hero banner node title header and blurb clp field images hero field image field image alt clp primary cta label link fe panel epics clp field title and blurb “why this matters clp why this matters field secondary cta label link resources and support priority r s breakdown wip fe pdf print save checklist mobile and desktop r s browse by audience rs homepage fe update wip nick blocked auto expand accordion items if the url hash matches the item id transformers transformer followup and close out of determine eta on platform cms transformer comparison tool cerner support main objective acquire facility list to determine what facilities need to be set accordingly intake request techical debt fe analytics implementation for covid faq accordion embedded links wip nick kanban board please select a ticket and include next to the ticket that is being worked pick up tickets by priority on the to do section to begin and move ticket through kanban workflow until done please include resolution steps on tickets along with instructions if for some reason you are unable to complete the ticket during this sprint please tag brianalloyd on tickets when moved to done section for validation and closeout please reach out if you have any questions or concerns in the interim welcome to pw team for this sprint we re excited to have the help to do on going enhancement rs mobile views left margin is too smooshed to the edge and cutting off text wip sandra done link tty number in footer and right rail of hub landing pages sandra brianalloyd footer links are inconsistently styled and missing interactive cues sandra brianalloyd main nav s contact us button can wrap when logged in user has a long name sandra brianalloyd multiple ambiguities with linked text in content block sandra brianalloyd use redesigned in this section button for triggering sidebar on mobile devices across benefit pages wip erik va gov mobile nav bugs wip erik ,1 108654,13645189550.0,IssuesEvent,2020-09-25 20:18:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Error alert for when Veterans are not showing up as Veterans with military information in the system,Design -> Frontend content-ia-team design profile vsa-authenticated-exp,"## Background See Slack convo:: https://dsva.slack.com/archives/C909ZG2BB/p1599156467141700 During UAT a Veteran did not show up in the system as being a Veteran with Military Information. We should tell users when they aren't reported as being a veteran. We should let users know so they can fix it if they want to. ## Tasks - [ ] Create updated error messaging ",2.0,"[Design] Error alert for when Veterans are not showing up as Veterans with military information in the system - ## Background See Slack convo:: https://dsva.slack.com/archives/C909ZG2BB/p1599156467141700 During UAT a Veteran did not show up in the system as being a Veteran with Military Information. We should tell users when they aren't reported as being a veteran. We should let users know so they can fix it if they want to. ## Tasks - [ ] Create updated error messaging ",1, error alert for when veterans are not showing up as veterans with military information in the system background see slack convo during uat a veteran did not show up in the system as being a veteran with military information we should tell users when they aren t reported as being a veteran we should let users know so they can fix it if they want to tasks create updated error messaging ,1 102898,12829311250.0,IssuesEvent,2020-07-06 22:34:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[FUNCTIONALITY]: Sortable Table - SHOULD have a base Table component with proper HTML structure,508/Accessibility design system,"**Feedback framework** - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Description Our [sortable table component](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/visual-design/components/sortabletable/) would benefit greatly from a basic `` component. This way we could build out more complex tables as extensions than completely new components. Thinking: * Tables with multiple heading rows * Tables with rows or columns that span multiple * Tables with sortable columns ## Related Issues * #9193 * #9194 ## Point of Contact **VFS Point of Contact:** _Trevor_ ## Acceptance Criteria - [ ] HTML validates with W3C validator or other HTML5 checker - [ ] No axe errors - [ ] Base component is used to create extended or enhanced table components - [ ] Visual styling does not change, except where noted by issue tickets ## Environment * https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/visual-design/components/sortabletable/ ## Possible Fixes (optional) This example uses proper `scope` attributes and a `
` for first table row element. This is the preferred means to create table structure, and is well-supported by assistive technology. ```diff + + + + + +
NameEmailMessage
Joe joe@joe.com Hello
Bob bob@bob.com Hola
Tom tom@tom.com What's Up
``` ## Screenshots or Trace Logs ![Screen Shot 2020-05-18 at 10 39 35 AM](https://user-images.githubusercontent.com/934879/82232397-32cd9f00-98f4-11ea-8ab3-91c24eaa434e.png) ",1.0,"[FUNCTIONALITY]: Sortable Table - SHOULD have a base Table component with proper HTML structure - **Feedback framework** - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Description Our [sortable table component](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/visual-design/components/sortabletable/) would benefit greatly from a basic `` component. This way we could build out more complex tables as extensions than completely new components. Thinking: * Tables with multiple heading rows * Tables with rows or columns that span multiple * Tables with sortable columns ## Related Issues * #9193 * #9194 ## Point of Contact **VFS Point of Contact:** _Trevor_ ## Acceptance Criteria - [ ] HTML validates with W3C validator or other HTML5 checker - [ ] No axe errors - [ ] Base component is used to create extended or enhanced table components - [ ] Visual styling does not change, except where noted by issue tickets ## Environment * https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/visual-design/components/sortabletable/ ## Possible Fixes (optional) This example uses proper `scope` attributes and a `
` for first table row element. This is the preferred means to create table structure, and is well-supported by assistive technology. ```diff + + + + + +
NameEmailMessage
Joe joe@joe.com Hello
Bob bob@bob.com Hola
Tom tom@tom.com What's Up
``` ## Screenshots or Trace Logs ![Screen Shot 2020-05-18 at 10 39 35 AM](https://user-images.githubusercontent.com/934879/82232397-32cd9f00-98f4-11ea-8ab3-91c24eaa434e.png) ",1, sortable table should have a base table component with proper html structure feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements description our would benefit greatly from a basic component this way we could build out more complex tables as extensions than completely new components thinking tables with multiple heading rows tables with rows or columns that span multiple tables with sortable columns related issues point of contact if this issue is being opened by a vfs team member please add a point of contact usually this is the same person who enters the issue ticket vfs point of contact trevor acceptance criteria html validates with validator or other checker no axe errors base component is used to create extended or enhanced table components visual styling does not change except where noted by issue tickets environment possible fixes optional this example uses proper scope attributes and a for first table row element this is the preferred means to create table structure and is well supported by assistive technology diff name email message joe joe joe com hello bob bob bob com hola tom tom tom com what s up screenshots or trace logs ,1 103668,12960936614.0,IssuesEvent,2020-07-20 15:00:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"[Design] A veteran is registered at one or more VAMC facilities, but only one facility has EC enabled",design discovery vaos,"Use case: A veteran is registered at one or more VAMC facilities, but only one facility has EC enabled and availability today. Example - Veteran is registered at both San Fransisco and Sacramento, but only EC is only offered at San Fransisco which is not the site that the Veteran goes to for care. Questions: - Do we indicate to Veterans which Facility this is with? - Do we ask Veteran to confirm they want to still request EC even though it's at a site they don't normally go to? - Consider asking user to confirm via question - ""Express care is a pilot feature currently available for Veterans [name child facility]. Is [name child facility] where you primarily receive your VA care? [Y/N] - If yes - continue user to EC flow - If no - ask Veteran to confirm they would still like to submit express care request with facility (or something to the effect) ## Acceptance criteria: - Walk through desired user flow for this scenario - Design mocks for handling this flow throughout EC flow - from homepage to submission",1.0,"[Design] A veteran is registered at one or more VAMC facilities, but only one facility has EC enabled - Use case: A veteran is registered at one or more VAMC facilities, but only one facility has EC enabled and availability today. Example - Veteran is registered at both San Fransisco and Sacramento, but only EC is only offered at San Fransisco which is not the site that the Veteran goes to for care. Questions: - Do we indicate to Veterans which Facility this is with? - Do we ask Veteran to confirm they want to still request EC even though it's at a site they don't normally go to? - Consider asking user to confirm via question - ""Express care is a pilot feature currently available for Veterans [name child facility]. Is [name child facility] where you primarily receive your VA care? [Y/N] - If yes - continue user to EC flow - If no - ask Veteran to confirm they would still like to submit express care request with facility (or something to the effect) ## Acceptance criteria: - Walk through desired user flow for this scenario - Design mocks for handling this flow throughout EC flow - from homepage to submission",1, a veteran is registered at one or more vamc facilities but only one facility has ec enabled use case a veteran is registered at one or more vamc facilities but only one facility has ec enabled and availability today example veteran is registered at both san fransisco and sacramento but only ec is only offered at san fransisco which is not the site that the veteran goes to for care questions do we indicate to veterans which facility this is with do we ask veteran to confirm they want to still request ec even though it s at a site they don t normally go to consider asking user to confirm via question express care is a pilot feature currently available for veterans is where you primarily receive your va care if yes continue user to ec flow if no ask veteran to confirm they would still like to submit express care request with facility or something to the effect acceptance criteria walk through desired user flow for this scenario design mocks for handling this flow throughout ec flow from homepage to submission,1 94151,11852561318.0,IssuesEvent,2020-03-24 20:11:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Establish Documentation for Content Collaboration,design vsa-caregiver,"## Problem Statement Given that @LinnJS needs an easy way to understand the front end requirements for the 10-10CG I want to create an easy system of collaboration between front-end, content, and design So that content and changes can be communicated effectively.",1.0,"Establish Documentation for Content Collaboration - ## Problem Statement Given that @LinnJS needs an easy way to understand the front end requirements for the 10-10CG I want to create an easy system of collaboration between front-end, content, and design So that content and changes can be communicated effectively.",1,establish documentation for content collaboration problem statement given that linnjs needs an easy way to understand the front end requirements for the i want to create an easy system of collaboration between front end content and design so that content and changes can be communicated effectively ,1 181450,30688034695.0,IssuesEvent,2023-07-26 13:34:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Update wireframes with confirmation status solution ,design ux HCE-Checkin,"## Tasks - [ ] Update wireframes with confirmation status solution - [ ] Update symbols and annotations, as needed ## AC - [ ] Update wireframes with confirmation status solution - [ ] Update symbols and annotations, as needed ",1.0,"Update wireframes with confirmation status solution - ## Tasks - [ ] Update wireframes with confirmation status solution - [ ] Update symbols and annotations, as needed ## AC - [ ] Update wireframes with confirmation status solution - [ ] Update symbols and annotations, as needed ",1,update wireframes with confirmation status solution tasks update wireframes with confirmation status solution update symbols and annotations as needed ac update wireframes with confirmation status solution update symbols and annotations as needed ,1 146207,23030917585.0,IssuesEvent,2022-07-22 13:50:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Forms library developer documentation update,Epic forms platform-content-team vsp-design-system-team,"## User Story As a VFS developer, I need to be able to find accurate information on the forms library, so that I can build forms on VA.gov efficiently and in an agile way. ## Problem Statement Forms library developer documentation currently is stored primarily on [""the Gatsby site""](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/forms). However, there is additional information scattered in other sources, and much of it is out of date. How might we overhaul forms library developer documentation to better meet the needs of VFS developers?",1.0,"Forms library developer documentation update - ## User Story As a VFS developer, I need to be able to find accurate information on the forms library, so that I can build forms on VA.gov efficiently and in an agile way. ## Problem Statement Forms library developer documentation currently is stored primarily on [""the Gatsby site""](https://department-of-veterans-affairs.github.io/veteran-facing-services-tools/forms). However, there is additional information scattered in other sources, and much of it is out of date. How might we overhaul forms library developer documentation to better meet the needs of VFS developers?",1,forms library developer documentation update user story as a vfs developer i need to be able to find accurate information on the forms library so that i can build forms on va gov efficiently and in an agile way problem statement forms library developer documentation currently is stored primarily on however there is additional information scattered in other sources and much of it is out of date how might we overhaul forms library developer documentation to better meet the needs of vfs developers ,1 94008,11841432267.0,IssuesEvent,2020-03-23 20:46:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Accessories page empty state,design vsa vsa-benefits-2,"## User Story or Problem Statement Problem description. How might we let the Veteran know that they do not have any currently-authorized accessories? ## Goal Show users a page state reflecting the absence of authorized accessories and instructions on what to do if there is a problem. ## Tasks - [ ] Create a mockup of this state - [ ] Upload to invision - [ ] Update GH documentation ## Acceptance Criteria - [ ] New state is reflected in GH",1.0,"[Design] Accessories page empty state - ## User Story or Problem Statement Problem description. How might we let the Veteran know that they do not have any currently-authorized accessories? ## Goal Show users a page state reflecting the absence of authorized accessories and instructions on what to do if there is a problem. ## Tasks - [ ] Create a mockup of this state - [ ] Upload to invision - [ ] Update GH documentation ## Acceptance Criteria - [ ] New state is reflected in GH",1, accessories page empty state user story or problem statement problem description how might we let the veteran know that they do not have any currently authorized accessories goal show users a page state reflecting the absence of authorized accessories and instructions on what to do if there is a problem tasks create a mockup of this state upload to invision update gh documentation acceptance criteria new state is reflected in gh,1 95052,11950986154.0,IssuesEvent,2020-04-03 16:05:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Bug] Un-checking worsened condition should remove that condition from treatment facility,526 bug design frontend vsa-benefits,"## What happened? Discovery issue: https://github.com/department-of-veterans-affairs/va.gov-team/issues/1536 526 forms were failing to submit for veterans due to an error from EVSS involving conditions being linked to treatment facilities without that condition actually being submitted in the veteran's list of disabilities. ## Steps to Reproduce - URL: https://staging.va.gov/disability/file-disability-claim-form-21-526ez/introduction - Test User: User 229 1. Start a new 526 form and navigate to the page below and select ""One or more of my rated conditions that have gotten worse"" ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/40a5dc74-8afb-40e4-ad85-f0fe497df87b) 2. Continue through the form to the page below and select one or more Rated Disabilities ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/516437af-9b7e-4e22-abf0-8ab76931774f) 3. At the step below, select ""Yes"" for the first prompt and select ""VA medical records"" for the second ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/f4249a89-ad4e-4b5c-b841-9f7b2095b887) 4. On the next page, fill out all required fields with any information and then select one or more of the previously selected conditions ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/f156bcbc-27bf-43ac-81c7-e6cb37391180) 5. Navigate to the review step and deselect one or more of the conditions that were selected for the facility in the previous step ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/2a478aa3-9779-433b-b6d1-da5b6885d3ef) Notice that under ""Supporting evidence"" and then under the ""VA medical records"" section will be the facility previously created, but the condition just removed will not be there. This is a false positive as the condition remains linked to this facility behind the scenes. ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/3f527439-1545-4230-b939-02a0c5bd664b) 6. Submit the application and the submission will fail ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/9a0a63ba-3620-48e6-a747-2907e5ca2a9c) Observing the submitted JSON to vets-api will reveal that the removed condition is in fact still linked to the treatment center: ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/83a17a42-2c83-494f-af1e-e7782ac47025) ## Desired behavior The removed conditions should also be removed from the linked treatment facilities and the submission should be successful. ## Acceptance Criteria - [ ] Conditions removed from being ""worsened"" are removed from linked treatment facilities - [ ] The form submits successfully under these conditions",1.0,"[Bug] Un-checking worsened condition should remove that condition from treatment facility - ## What happened? Discovery issue: https://github.com/department-of-veterans-affairs/va.gov-team/issues/1536 526 forms were failing to submit for veterans due to an error from EVSS involving conditions being linked to treatment facilities without that condition actually being submitted in the veteran's list of disabilities. ## Steps to Reproduce - URL: https://staging.va.gov/disability/file-disability-claim-form-21-526ez/introduction - Test User: User 229 1. Start a new 526 form and navigate to the page below and select ""One or more of my rated conditions that have gotten worse"" ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/40a5dc74-8afb-40e4-ad85-f0fe497df87b) 2. Continue through the form to the page below and select one or more Rated Disabilities ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/516437af-9b7e-4e22-abf0-8ab76931774f) 3. At the step below, select ""Yes"" for the first prompt and select ""VA medical records"" for the second ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/f4249a89-ad4e-4b5c-b841-9f7b2095b887) 4. On the next page, fill out all required fields with any information and then select one or more of the previously selected conditions ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/f156bcbc-27bf-43ac-81c7-e6cb37391180) 5. Navigate to the review step and deselect one or more of the conditions that were selected for the facility in the previous step ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/2a478aa3-9779-433b-b6d1-da5b6885d3ef) Notice that under ""Supporting evidence"" and then under the ""VA medical records"" section will be the facility previously created, but the condition just removed will not be there. This is a false positive as the condition remains linked to this facility behind the scenes. ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/3f527439-1545-4230-b939-02a0c5bd664b) 6. Submit the application and the submission will fail ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/9a0a63ba-3620-48e6-a747-2907e5ca2a9c) Observing the submitted JSON to vets-api will reveal that the removed condition is in fact still linked to the treatment center: ![image.png](https://images.zenhubusercontent.com/5d5ebd091325bafe068c37dc/83a17a42-2c83-494f-af1e-e7782ac47025) ## Desired behavior The removed conditions should also be removed from the linked treatment facilities and the submission should be successful. ## Acceptance Criteria - [ ] Conditions removed from being ""worsened"" are removed from linked treatment facilities - [ ] The form submits successfully under these conditions",1, un checking worsened condition should remove that condition from treatment facility what happened discovery issue forms were failing to submit for veterans due to an error from evss involving conditions being linked to treatment facilities without that condition actually being submitted in the veteran s list of disabilities steps to reproduce url test user user start a new form and navigate to the page below and select one or more of my rated conditions that have gotten worse continue through the form to the page below and select one or more rated disabilities at the step below select yes for the first prompt and select va medical records for the second on the next page fill out all required fields with any information and then select one or more of the previously selected conditions navigate to the review step and deselect one or more of the conditions that were selected for the facility in the previous step notice that under supporting evidence and then under the va medical records section will be the facility previously created but the condition just removed will not be there this is a false positive as the condition remains linked to this facility behind the scenes submit the application and the submission will fail observing the submitted json to vets api will reveal that the removed condition is in fact still linked to the treatment center desired behavior the removed conditions should also be removed from the linked treatment facilities and the submission should be successful acceptance criteria conditions removed from being worsened are removed from linked treatment facilities the form submits successfully under these conditions,1 176485,28101524634.0,IssuesEvent,2023-03-30 19:55:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Supplemental Claims | Match H1 to breadcrumb,Supplemental Claims needs-design benefits-team-1 squad-2,"### Background For this page: https://staging.va.gov/decision-reviews/supplemental-claim/file-supplemental-claim-form-20-0995/start ### Acceptance Criteria - [ ] The page reads with the following header structure: H1 File a Supplemental Claim H2 Is this the form I need? H2 What type of claim are you filing a Supplemental Claim for? ### Tasks - [ ] Add H1 that says 'File a Supplemental Claim' to match breadcrumb. - [ ] Change 'Is this the form I need?' to an H2 ### Design & Build Notes [DESIGN](https://www.sketch.com/s/d2416db4-9a4f-4919-abe4-20ba4bdcfd89/a/ZOGd21Z#Version) [COPY](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/design/sourceofcontenttruth.md#file-a-supplemental-claim) ",1.0,"Supplemental Claims | Match H1 to breadcrumb - ### Background For this page: https://staging.va.gov/decision-reviews/supplemental-claim/file-supplemental-claim-form-20-0995/start ### Acceptance Criteria - [ ] The page reads with the following header structure: H1 File a Supplemental Claim H2 Is this the form I need? H2 What type of claim are you filing a Supplemental Claim for? ### Tasks - [ ] Add H1 that says 'File a Supplemental Claim' to match breadcrumb. - [ ] Change 'Is this the form I need?' to an H2 ### Design & Build Notes [DESIGN](https://www.sketch.com/s/d2416db4-9a4f-4919-abe4-20ba4bdcfd89/a/ZOGd21Z#Version) [COPY](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/decision-reviews/Supplemental-Claims/design/sourceofcontenttruth.md#file-a-supplemental-claim) ",1,supplemental claims match to breadcrumb background for this page acceptance criteria the page reads with the following header structure file a supplemental claim is this the form i need what type of claim are you filing a supplemental claim for tasks add that says file a supplemental claim to match breadcrumb change is this the form i need to an design build notes ,1 147068,23161228096.0,IssuesEvent,2022-07-29 17:59:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Notification preferences: Initial 1095B preference mockup,design notification-settings vsa-authenticated-exp profile FY21Q2-priority 1095b-tax-form,"### Background We are working in partnership with the 1095B team, VANotify, and VA Profile to add a notification preference which will allow people to opt into and out of a mailed copy of their 1095B (proof of health care) tax form. If people opt out of the mailed copy of their 1095, they are opting into downloading a copy from VA.gov. **Requirements** - We must add a new preference for the 1095B to notification preferences. This preference must have two options that describe the following (this is not intended as exact copy): - Send me a copy of my 1095B by mail. - Do not mail me a copy of my 1095B. I will download a copy of it from VA.gov. I also understand I will receive an email yearly letting me know my 1095B is available. - We must make it clear that people can change this preference any time. [Being explicit about this seems to be a requirement from the 1095B team](https://dsva.slack.com/archives/C02TUH5U3HS/p1658933063191909?thread_ts=1658931650.076399&cid=C02TUH5U3HS). - We must make sure people have an email on file to change this preference since the digital download will have automated emails associated with it. - Every time someone changes this preference, we need to send them a confirmation email that acknowledges they have changed this preference. **Question for the 1095B team -- do we need to only send an email if someone opts out of mail? Or any time they change this setting?** **Other things to think about** - Should this go in the ""Your health care"" group, or does it need its own group? - We need to get this to the 1095B legal team ASAP so we can get feedback from them, so working with content as soon as we can would be great. - Speaking of legal, there are possibly other things they will ask us to mention in the UI, but the requirements above are all we are aware of as of now. ### Tasks - [ ] Create initial mockups - [ ] Review with team - [ ] Iterate as needed - [ ] Work with content",1.0,"[Design] Notification preferences: Initial 1095B preference mockup - ### Background We are working in partnership with the 1095B team, VANotify, and VA Profile to add a notification preference which will allow people to opt into and out of a mailed copy of their 1095B (proof of health care) tax form. If people opt out of the mailed copy of their 1095, they are opting into downloading a copy from VA.gov. **Requirements** - We must add a new preference for the 1095B to notification preferences. This preference must have two options that describe the following (this is not intended as exact copy): - Send me a copy of my 1095B by mail. - Do not mail me a copy of my 1095B. I will download a copy of it from VA.gov. I also understand I will receive an email yearly letting me know my 1095B is available. - We must make it clear that people can change this preference any time. [Being explicit about this seems to be a requirement from the 1095B team](https://dsva.slack.com/archives/C02TUH5U3HS/p1658933063191909?thread_ts=1658931650.076399&cid=C02TUH5U3HS). - We must make sure people have an email on file to change this preference since the digital download will have automated emails associated with it. - Every time someone changes this preference, we need to send them a confirmation email that acknowledges they have changed this preference. **Question for the 1095B team -- do we need to only send an email if someone opts out of mail? Or any time they change this setting?** **Other things to think about** - Should this go in the ""Your health care"" group, or does it need its own group? - We need to get this to the 1095B legal team ASAP so we can get feedback from them, so working with content as soon as we can would be great. - Speaking of legal, there are possibly other things they will ask us to mention in the UI, but the requirements above are all we are aware of as of now. ### Tasks - [ ] Create initial mockups - [ ] Review with team - [ ] Iterate as needed - [ ] Work with content",1, notification preferences initial preference mockup background we are working in partnership with the team vanotify and va profile to add a notification preference which will allow people to opt into and out of a mailed copy of their proof of health care tax form if people opt out of the mailed copy of their they are opting into downloading a copy from va gov requirements we must add a new preference for the to notification preferences this preference must have two options that describe the following this is not intended as exact copy send me a copy of my by mail do not mail me a copy of my i will download a copy of it from va gov i also understand i will receive an email yearly letting me know my is available we must make it clear that people can change this preference any time we must make sure people have an email on file to change this preference since the digital download will have automated emails associated with it every time someone changes this preference we need to send them a confirmation email that acknowledges they have changed this preference question for the team do we need to only send an email if someone opts out of mail or any time they change this setting other things to think about should this go in the your health care group or does it need its own group we need to get this to the legal team asap so we can get feedback from them so working with content as soon as we can would be great speaking of legal there are possibly other things they will ask us to mention in the ui but the requirements above are all we are aware of as of now tasks create initial mockups review with team iterate as needed work with content,1 88790,11149805662.0,IssuesEvent,2019-12-23 20:02:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] Content Adjustment for Rated Disabilities,design vsa vsa-ebenefits,"## Story As an end user of the Rated Disabilities Tool page, I want to have concise, clear and consistent language so that I can better understand what the tool page's information is trying to convey. ## Considerations These are comments from Peggy that will make the content consistent with the latest style changes. ## Tasks Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] Add a short intro to help users understand what they are reading (combined ratings vs. individual ratings), and update the titles to read: H1: **Your VA disability ratings** H2: **Your combined disability rating** *Note that H1 is plural, and H2 is not* ~~Add new intro copy: **""This is your rating for multiple conditions.""**~~ - [x] Update box copy (as we've heard in recent research that some people don't understand what ""pending"" means) to: **""This rating doesn’t include any disabilities for your claims that are still in process.""** - [x] Rewrite H2 head to say Individual ratings to tie in more closely with the H1. So this header would become: H2: **Your individual ratings** ~~New intro copy: **""This is your rating for a single condition.""**~~ - [x] In the right rail, update the last sentence under the header ""How did I get this rating?"" to: **""…and information from other sources, like federal agencies.""** - [x] In the right rail, under the header ""Learn about VA disability ratings,"" rewrite to make more active voice: **""To learn how we determined your combined VA disability rating, use our disability rating calculator and ratings table.""** - [x] The link ""About VA Disability ratings"" should be sentence-cased: **""About VA disability ratings""** Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] For the blue error message, just remove ""We're sorry."" from the beginning of the first sentence for the error message in the TCDR location. Title: **We don't have a disability rating on file for you** Message body copy would start: **""We can't find a disability rating for you...""** Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] For the red error message, please add **“the”** before VA.gov help desk in the body of the message The sentence should read: **""...please call the VA.gov help desk...""** Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] For the blue error message, just remove ""We're sorry."" from the beginning of the first sentence for the error message in the individual ratings location. Message body copy would simply start: **""We can't find a disability rating for you...""** ## Acceptance Criteria - [x] The Rated Disabilities mockup reflects these changes. ",1.0,"[DESIGN] Content Adjustment for Rated Disabilities - ## Story As an end user of the Rated Disabilities Tool page, I want to have concise, clear and consistent language so that I can better understand what the tool page's information is trying to convey. ## Considerations These are comments from Peggy that will make the content consistent with the latest style changes. ## Tasks Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] Add a short intro to help users understand what they are reading (combined ratings vs. individual ratings), and update the titles to read: H1: **Your VA disability ratings** H2: **Your combined disability rating** *Note that H1 is plural, and H2 is not* ~~Add new intro copy: **""This is your rating for multiple conditions.""**~~ - [x] Update box copy (as we've heard in recent research that some people don't understand what ""pending"" means) to: **""This rating doesn’t include any disabilities for your claims that are still in process.""** - [x] Rewrite H2 head to say Individual ratings to tie in more closely with the H1. So this header would become: H2: **Your individual ratings** ~~New intro copy: **""This is your rating for a single condition.""**~~ - [x] In the right rail, update the last sentence under the header ""How did I get this rating?"" to: **""…and information from other sources, like federal agencies.""** - [x] In the right rail, under the header ""Learn about VA disability ratings,"" rewrite to make more active voice: **""To learn how we determined your combined VA disability rating, use our disability rating calculator and ratings table.""** - [x] The link ""About VA Disability ratings"" should be sentence-cased: **""About VA disability ratings""** Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] For the blue error message, just remove ""We're sorry."" from the beginning of the first sentence for the error message in the TCDR location. Title: **We don't have a disability rating on file for you** Message body copy would start: **""We can't find a disability rating for you...""** Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] For the red error message, please add **“the”** before VA.gov help desk in the body of the message The sentence should read: **""...please call the VA.gov help desk...""** Referring to [Peggy's comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/4104): - [x] For the blue error message, just remove ""We're sorry."" from the beginning of the first sentence for the error message in the individual ratings location. Message body copy would simply start: **""We can't find a disability rating for you...""** ## Acceptance Criteria - [x] The Rated Disabilities mockup reflects these changes. ",1, content adjustment for rated disabilities story as an end user of the rated disabilities tool page i want to have concise clear and consistent language so that i can better understand what the tool page s information is trying to convey considerations these are comments from peggy that will make the content consistent with the latest style changes tasks referring to add a short intro to help users understand what they are reading combined ratings vs individual ratings and update the titles to read your va disability ratings your combined disability rating note that is plural and is not add new intro copy this is your rating for multiple conditions update box copy as we ve heard in recent research that some people don t understand what pending means to this rating doesn’t include any disabilities for your claims that are still in process rewrite head to say individual ratings to tie in more closely with the so this header would become your individual ratings new intro copy this is your rating for a single condition in the right rail update the last sentence under the header how did i get this rating to …and information from other sources like federal agencies in the right rail under the header learn about va disability ratings rewrite to make more active voice to learn how we determined your combined va disability rating use our disability rating calculator and ratings table the link about va disability ratings should be sentence cased about va disability ratings referring to for the blue error message just remove we re sorry from the beginning of the first sentence for the error message in the tcdr location title we don t have a disability rating on file for you message body copy would start we can t find a disability rating for you referring to for the red error message please add “the” before va gov help desk in the body of the message the sentence should read please call the va gov help desk referring to for the blue error message just remove we re sorry from the beginning of the first sentence for the error message in the individual ratings location message body copy would simply start we can t find a disability rating for you acceptance criteria the rated disabilities mockup reflects these changes ,1 139605,20917494508.0,IssuesEvent,2022-03-24 14:35:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,VAOS - Small Improvement Initiative ,Epic vaos-product-design,"## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/product-outline-template.md) ## High Level User Story/ies As a Veteran, I need to be able to manage and schedule health appointments online so I can have a seamless and positive experience. ## Hypothesis If VAOS continues to make improvements in the application, then we see more users using the application and receive positive feedback from the Veterans and the VA. ## OKR _Which Objective / Key Result does this epic push forward?_ ## Definition of done ### What must be true in order for you to consider this epic complete? *Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.* ",1.0,"VAOS - Small Improvement Initiative - ## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/product-outline-template.md) ## High Level User Story/ies As a Veteran, I need to be able to manage and schedule health appointments online so I can have a seamless and positive experience. ## Hypothesis If VAOS continues to make improvements in the application, then we see more users using the application and receive positive feedback from the Veterans and the VA. ## OKR _Which Objective / Key Result does this epic push forward?_ ## Definition of done ### What must be true in order for you to consider this epic complete? *Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.* ",1,vaos small improvement initiative product outline high level user story ies as a veteran i need to be able to manage and schedule health appointments online so i can have a seamless and positive experience hypothesis if vaos continues to make improvements in the application then we see more users using the application and receive positive feedback from the veterans and the va okr which objective key result does this epic push forward definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements ,1 96402,12126827270.0,IssuesEvent,2020-04-22 17:40:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Implement and Refine Feedback From Design Intent for PCPG,design vsa vsa-ebenefits,"## Goal After recieving feedback from the Design Intent Review, we need to implement those recommendations where they make sense ## Tasks - [ ] Make changes to the screens to align with recomendations. ## Acceptance Criteria - [ ] Changes have been made and team and interested parties have been notified",1.0,"Implement and Refine Feedback From Design Intent for PCPG - ## Goal After recieving feedback from the Design Intent Review, we need to implement those recommendations where they make sense ## Tasks - [ ] Make changes to the screens to align with recomendations. ## Acceptance Criteria - [ ] Changes have been made and team and interested parties have been notified",1,implement and refine feedback from design intent for pcpg goal after recieving feedback from the design intent review we need to implement those recommendations where they make sense tasks make changes to the screens to align with recomendations acceptance criteria changes have been made and team and interested parties have been notified,1 124267,16601759056.0,IssuesEvent,2021-06-01 20:32:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Write Questionnaire Job Aid for Clinic Staff,design vsa-healthcare-exp,"# Description Staff members within the Loma Linda pilot site need guidance on how to answer questions from Veterans about the new questionnaires # Tasks - [x] Find current write up about how to log into va.gov - [x] Write draft document # Acceptance Criteria - [x] Review with team (and content?) - [x] Send to Loma Linda",1.0,"Write Questionnaire Job Aid for Clinic Staff - # Description Staff members within the Loma Linda pilot site need guidance on how to answer questions from Veterans about the new questionnaires # Tasks - [x] Find current write up about how to log into va.gov - [x] Write draft document # Acceptance Criteria - [x] Review with team (and content?) - [x] Send to Loma Linda",1,write questionnaire job aid for clinic staff description staff members within the loma linda pilot site need guidance on how to answer questions from veterans about the new questionnaires tasks find current write up about how to log into va gov write draft document acceptance criteria review with team and content send to loma linda,1 146608,23094359018.0,IssuesEvent,2022-07-26 18:00:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Publicize the Q3 PS Survey,service-design,"## Issue Description Share survey's availability in Slack, ToT, and relevant group discussions every few days as needed to ensure participation. # Make sure Content has updated Platform before linking to page ## Tasks - [x] Share Survey in Slack - [x] Share Survey in ToT ## Acceptance Criteria - [x] Survey posted in Slack - [x] Survey posted in ToT slides for active period",1.0,"Publicize the Q3 PS Survey - ## Issue Description Share survey's availability in Slack, ToT, and relevant group discussions every few days as needed to ensure participation. # Make sure Content has updated Platform before linking to page ## Tasks - [x] Share Survey in Slack - [x] Share Survey in ToT ## Acceptance Criteria - [x] Survey posted in Slack - [x] Survey posted in ToT slides for active period",1,publicize the ps survey issue description share survey s availability in slack tot and relevant group discussions every few days as needed to ensure participation make sure content has updated platform before linking to page tasks share survey in slack share survey in tot acceptance criteria survey posted in slack survey posted in tot slides for active period,1 144918,22586109474.0,IssuesEvent,2022-06-28 15:22:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Where should the updated playbook live?,service-design,"## Issue Description Where should the updated playbook live? (who needs it and where makes the most sense) --- ## Tasks - [ ] Determine who the consumer will be - [ ] Determine where the playbook should reside ## Acceptance Criteria - [ ] Audience is determined - [ ] Location is determined",1.0,"Where should the updated playbook live? - ## Issue Description Where should the updated playbook live? (who needs it and where makes the most sense) --- ## Tasks - [ ] Determine who the consumer will be - [ ] Determine where the playbook should reside ## Acceptance Criteria - [ ] Audience is determined - [ ] Location is determined",1,where should the updated playbook live issue description where should the updated playbook live who needs it and where makes the most sense tasks determine who the consumer will be determine where the playbook should reside acceptance criteria audience is determined location is determined,1 117609,15144464207.0,IssuesEvent,2021-02-11 01:23:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Usability Testing Prep [Team Name, Feature Name]",collab-cycle-review collaboration-cycle content-ia-team vaos-product-design vsp-product-support,"## Steps to complete Usability Testing Prep: - [ ] VFS Product Manager: create this issue and fill in the team name and feature name in the title and other bolded information appropriately - [ ] VFS: Attach all artifacts before requesting the meeting - [ ] VFS: Link to this issue once created in [#vfs-platform-support](https://dsva.slack.com/channels/vfs-platform-support) in Slack; tag @ Shira Goodman and @ Andrea Hewitt - [ ] VSP: Schedule meeting with VSP reviewers and requesting team attendees (as listed below) - [ ] VFS: At least 2 days before scheduled meeting, you must complete list of artifacts below - [ ] VSP: Practice area reviewers create sub-issues attached to this one with feedback for your team - [ ] VFS: Completes attached feedback tickets based on acceptance included in each practice area feedback ticket - [ ] VSP: [Platform Collaboration Point Tracker](https://docs.google.com/spreadsheets/u/1/d/1d219oL1zCvCvnv1Bx-dI-GMzwgbarLv9_bzMSa3ULjA/edit#gid=1341642809) is updated ## Artifacts - _please provide the following artifacts at least 2 days before scheduled meeting_ - Link to product outline - [Product outline](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/vaos-for-distribution-initiative/vaos-for-distribution-initiative.md) - Link to or attach prototype or mockups - [Prototype](https://adhoc.invisionapp.com/share/GU1028Y9YDTX#/443560117_Home) - Link to or attach artifact with copy (if separate from prototypes/mockups) - Link to research plan - [Research plan](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/scheduling/research/feb-2021-vaos-vaccine-concept-test/research-plan.md) - [Conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/scheduling/research/feb-2021-vaos-vaccine-concept-test/conversation-guide.md) - Link to regression test plan - TBD, not sure if we'll have this documented in TestRail - Link to test cases/test plan in TestRail - TBD, not sure if we'll have this documented in TestRail ## Meeting attendees from **VAOS** - Product Manager (required): **Lauren Ernest** - DEPO product lead (required): **Lauren Alexanderson, Ryan Thurlwell** - Anyone else from your team who significantly contributed to the artifacts provided (required): **Peter Russo** - Other specialists: VSP will only invite those specified, so be sure to list your content, IA, accessibility and QA specialists, if applicable. ## Scheduling - Please reference the [VSP Collaboration Meetings Calendar](https://calendar.google.com/calendar/embed?src=adhocteam.us_4dn3o77gcm5e3vbiedlha96tc0%40group.calendar.google.com&ctz=America%2FNew_York) (times shown are ET) - Note an available time slot within a recurring ""[CALENDAR BLOCK] Review Group Office Hours"" slot that works for your team and is at least 2 business days from now - Write that preferred time slot here (on this ticket), and VSP will send you a meeting invite - _If no available time slots work for your team, write your availability and requirements here and Shira will reach out as needed_ ## Additional Notes: During this collaboration point, you will receive feedback from the following practice areas: design, accessibility, content, QA, and optional: information architecture (IA), product ",1.0,"Usability Testing Prep [Team Name, Feature Name] - ## Steps to complete Usability Testing Prep: - [ ] VFS Product Manager: create this issue and fill in the team name and feature name in the title and other bolded information appropriately - [ ] VFS: Attach all artifacts before requesting the meeting - [ ] VFS: Link to this issue once created in [#vfs-platform-support](https://dsva.slack.com/channels/vfs-platform-support) in Slack; tag @ Shira Goodman and @ Andrea Hewitt - [ ] VSP: Schedule meeting with VSP reviewers and requesting team attendees (as listed below) - [ ] VFS: At least 2 days before scheduled meeting, you must complete list of artifacts below - [ ] VSP: Practice area reviewers create sub-issues attached to this one with feedback for your team - [ ] VFS: Completes attached feedback tickets based on acceptance included in each practice area feedback ticket - [ ] VSP: [Platform Collaboration Point Tracker](https://docs.google.com/spreadsheets/u/1/d/1d219oL1zCvCvnv1Bx-dI-GMzwgbarLv9_bzMSa3ULjA/edit#gid=1341642809) is updated ## Artifacts - _please provide the following artifacts at least 2 days before scheduled meeting_ - Link to product outline - [Product outline](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/vaos-for-distribution-initiative/vaos-for-distribution-initiative.md) - Link to or attach prototype or mockups - [Prototype](https://adhoc.invisionapp.com/share/GU1028Y9YDTX#/443560117_Home) - Link to or attach artifact with copy (if separate from prototypes/mockups) - Link to research plan - [Research plan](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/scheduling/research/feb-2021-vaos-vaccine-concept-test/research-plan.md) - [Conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/scheduling/research/feb-2021-vaos-vaccine-concept-test/conversation-guide.md) - Link to regression test plan - TBD, not sure if we'll have this documented in TestRail - Link to test cases/test plan in TestRail - TBD, not sure if we'll have this documented in TestRail ## Meeting attendees from **VAOS** - Product Manager (required): **Lauren Ernest** - DEPO product lead (required): **Lauren Alexanderson, Ryan Thurlwell** - Anyone else from your team who significantly contributed to the artifacts provided (required): **Peter Russo** - Other specialists: VSP will only invite those specified, so be sure to list your content, IA, accessibility and QA specialists, if applicable. ## Scheduling - Please reference the [VSP Collaboration Meetings Calendar](https://calendar.google.com/calendar/embed?src=adhocteam.us_4dn3o77gcm5e3vbiedlha96tc0%40group.calendar.google.com&ctz=America%2FNew_York) (times shown are ET) - Note an available time slot within a recurring ""[CALENDAR BLOCK] Review Group Office Hours"" slot that works for your team and is at least 2 business days from now - Write that preferred time slot here (on this ticket), and VSP will send you a meeting invite - _If no available time slots work for your team, write your availability and requirements here and Shira will reach out as needed_ ## Additional Notes: During this collaboration point, you will receive feedback from the following practice areas: design, accessibility, content, QA, and optional: information architecture (IA), product ",1,usability testing prep steps to complete usability testing prep vfs product manager create this issue and fill in the team name and feature name in the title and other bolded information appropriately vfs attach all artifacts before requesting the meeting vfs link to this issue once created in in slack tag shira goodman and andrea hewitt vsp schedule meeting with vsp reviewers and requesting team attendees as listed below vfs at least days before scheduled meeting you must complete list of artifacts below vsp practice area reviewers create sub issues attached to this one with feedback for your team vfs completes attached feedback tickets based on acceptance included in each practice area feedback ticket vsp is updated artifacts please provide the following artifacts at least days before scheduled meeting link to product outline link to or attach prototype or mockups link to or attach artifact with copy if separate from prototypes mockups link to research plan link to regression test plan tbd not sure if we ll have this documented in testrail link to test cases test plan in testrail tbd not sure if we ll have this documented in testrail meeting attendees from vaos product manager required lauren ernest depo product lead required lauren alexanderson ryan thurlwell anyone else from your team who significantly contributed to the artifacts provided required peter russo other specialists vsp will only invite those specified so be sure to list your content ia accessibility and qa specialists if applicable scheduling please reference the times shown are et note an available time slot within a recurring review group office hours slot that works for your team and is at least business days from now write that preferred time slot here on this ticket and vsp will send you a meeting invite if no available time slots work for your team write your availability and requirements here and shira will reach out as needed additional notes during this collaboration point you will receive feedback from the following practice areas design accessibility content qa and optional information architecture ia product ,1 104698,13107994309.0,IssuesEvent,2020-08-04 16:05:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Tressa to introduce Cassandra to the LIH project,LIH design vsa-authenticated-exp,"## Background As part of Cassandra's onboarding process we would like to get her up to speed with LIH. ## Tasks - [x] Tressa to meet with Cassandra to get her up to speed and familiarize her with LIH work",1.0,"[Design] Tressa to introduce Cassandra to the LIH project - ## Background As part of Cassandra's onboarding process we would like to get her up to speed with LIH. ## Tasks - [x] Tressa to meet with Cassandra to get her up to speed and familiarize her with LIH work",1, tressa to introduce cassandra to the lih project background as part of cassandra s onboarding process we would like to get her up to speed with lih tasks tressa to meet with cassandra to get her up to speed and familiarize her with lih work,1 137706,20201019710.0,IssuesEvent,2022-02-11 15:16:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Table web component: accessibility review,vsp-design-system-team,"## Description We need to conduct a full accessibility review of the new Table web component. The component can be viewed in Storybook here: [insert Chromatic link] ## Acceptance Criteria - [ ] Full accessibility review of the Table component is completed - [ ] Add descriptions of any issues found to this ticket - [ ] If any problems are found, add screen recordings and/or screenshots to comments on this ticket that show the problem. - [ ] Alert Katy and the developer who built the component when the review is complete - [ ] Re-review any fixes the developer makes to the component",1.0,"Table web component: accessibility review - ## Description We need to conduct a full accessibility review of the new Table web component. The component can be viewed in Storybook here: [insert Chromatic link] ## Acceptance Criteria - [ ] Full accessibility review of the Table component is completed - [ ] Add descriptions of any issues found to this ticket - [ ] If any problems are found, add screen recordings and/or screenshots to comments on this ticket that show the problem. - [ ] Alert Katy and the developer who built the component when the review is complete - [ ] Re-review any fixes the developer makes to the component",1,table web component accessibility review description we need to conduct a full accessibility review of the new table web component the component can be viewed in storybook here acceptance criteria full accessibility review of the table component is completed add descriptions of any issues found to this ticket if any problems are found add screen recordings and or screenshots to comments on this ticket that show the problem alert katy and the developer who built the component when the review is complete re review any fixes the developer makes to the component,1 91255,11489796973.0,IssuesEvent,2020-02-11 16:03:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"MDT- Email step- Veteran contact details - add an email address, v1",design vsa vsa-benefits-2,"## User Story: As a veteran, I need to be able to add a new email address so that I can keep my information updated and current. ## Tasks - [x] Create a high fidelity mockup depicting how a veteran might add a new email address if one is not pre-populated - [x] Upload exports to Invision and indicate initial focus point as a comment ## Acceptance Criteria: Mockup aligns with VA.gov’s design system Veteran is able to add a new email address The screen’s initial focus is incorporated Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps ## Dep/Blockers",1.0,"MDT- Email step- Veteran contact details - add an email address, v1 - ## User Story: As a veteran, I need to be able to add a new email address so that I can keep my information updated and current. ## Tasks - [x] Create a high fidelity mockup depicting how a veteran might add a new email address if one is not pre-populated - [x] Upload exports to Invision and indicate initial focus point as a comment ## Acceptance Criteria: Mockup aligns with VA.gov’s design system Veteran is able to add a new email address The screen’s initial focus is incorporated Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps ## Dep/Blockers",1,mdt email step veteran contact details add an email address user story as a veteran i need to be able to add a new email address so that i can keep my information updated and current tasks create a high fidelity mockup depicting how a veteran might add a new email address if one is not pre populated upload exports to invision and indicate initial focus point as a comment acceptance criteria mockup aligns with va gov’s design system veteran is able to add a new email address the screen’s initial focus is incorporated sketch artboards are uploaded to invision and linked in this ticket as a comment next steps dep blockers,1 93700,11799235303.0,IssuesEvent,2020-03-18 15:35:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"Refine Mockups for ""View Payments""",design vsa vsa-ebenefits,"## Goal After receiving feedback from others (and possibly after Design Intent Review), we want to refine our mockups to reflect a closer approximation to a final version that can be built by engineers. ## Tasks - Address content and layout - Ensure functionality is still in place per the Epic ## Acceptance Criteria - [ ] All feedback has been addressed in the latest mockup and shared with the team",1.0,"Refine Mockups for ""View Payments"" - ## Goal After receiving feedback from others (and possibly after Design Intent Review), we want to refine our mockups to reflect a closer approximation to a final version that can be built by engineers. ## Tasks - Address content and layout - Ensure functionality is still in place per the Epic ## Acceptance Criteria - [ ] All feedback has been addressed in the latest mockup and shared with the team",1,refine mockups for view payments goal after receiving feedback from others and possibly after design intent review we want to refine our mockups to reflect a closer approximation to a final version that can be built by engineers tasks address content and layout ensure functionality is still in place per the epic acceptance criteria all feedback has been addressed in the latest mockup and shared with the team,1 98551,12338787988.0,IssuesEvent,2020-05-14 17:00:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,(Not Needed) [User Testing] Form Details Landing Pages: User Interview Conversation Guide,design research vsa-public-websites,"## User Story As a UX designer, I need to create a user testing conversation guide so I can ensure that all necessary questions are documented in one place and can be referenced during user interviews. ## Goal _A document to serve as a user interview conversation guide._ ## Objectives or Key Results this is meant to further - This furthers the discovery effort to understand more about the messaging being provided to users and identify needs and pain points. ## Tasks - [ ] _Create conversation guide (according to template if provided)_ - [ ] _Review conversation guide with design team & PM_ - [ ] _(Optional) Review conversation guide with content team, IA team for additional questions that could be beneficial_ - [ ] _Make edits to conversation guide if necessary_ ## Acceptance Criteria - [ ] Conversation guide has been completed ",1.0,"(Not Needed) [User Testing] Form Details Landing Pages: User Interview Conversation Guide - ## User Story As a UX designer, I need to create a user testing conversation guide so I can ensure that all necessary questions are documented in one place and can be referenced during user interviews. ## Goal _A document to serve as a user interview conversation guide._ ## Objectives or Key Results this is meant to further - This furthers the discovery effort to understand more about the messaging being provided to users and identify needs and pain points. ## Tasks - [ ] _Create conversation guide (according to template if provided)_ - [ ] _Review conversation guide with design team & PM_ - [ ] _(Optional) Review conversation guide with content team, IA team for additional questions that could be beneficial_ - [ ] _Make edits to conversation guide if necessary_ ## Acceptance Criteria - [ ] Conversation guide has been completed ",1, not needed form details landing pages user interview conversation guide user story as a ux designer i need to create a user testing conversation guide so i can ensure that all necessary questions are documented in one place and can be referenced during user interviews goal a document to serve as a user interview conversation guide objectives or key results this is meant to further this furthers the discovery effort to understand more about the messaging being provided to users and identify needs and pain points tasks create conversation guide according to template if provided review conversation guide with design team pm optional review conversation guide with content team ia team for additional questions that could be beneficial make edits to conversation guide if necessary acceptance criteria conversation guide has been completed ,1 124269,16601865981.0,IssuesEvent,2021-06-01 20:41:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Research] Notification Prefs - Refine deliverables for notification settings research,design notifications-preferences planned-work profile research vsa-authenticated-exp,"**Background** In sprint 46, we started the [research plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/notifications/notification-preferences/discovery-and-research/notifications-research-plan.md) and [conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/notifications/notification-preferences/discovery-and-research/notifications-conversation-guide.md) for our notification settings research. Now we need to update the prototype + documentation to prepare for a study in early/mid June. **Tasks** - [x] Update prototype (add contact info screens, ensure alignment between groups + notification items to tasks + MVP definition, remove ""note:..."" copy) - [x] Update plan + convo accordingly - [x] Review w/ team - [x] Ready for mid-point review",1.0,"[Research] Notification Prefs - Refine deliverables for notification settings research - **Background** In sprint 46, we started the [research plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/notifications/notification-preferences/discovery-and-research/notifications-research-plan.md) and [conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/notifications/notification-preferences/discovery-and-research/notifications-conversation-guide.md) for our notification settings research. Now we need to update the prototype + documentation to prepare for a study in early/mid June. **Tasks** - [x] Update prototype (add contact info screens, ensure alignment between groups + notification items to tasks + MVP definition, remove ""note:..."" copy) - [x] Update plan + convo accordingly - [x] Review w/ team - [x] Ready for mid-point review",1, notification prefs refine deliverables for notification settings research background in sprint we started the and for our notification settings research now we need to update the prototype documentation to prepare for a study in early mid june tasks update prototype add contact info screens ensure alignment between groups notification items to tasks mvp definition remove note copy update plan convo accordingly review w team ready for mid point review,1 126289,17016485578.0,IssuesEvent,2021-07-02 12:48:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[MCP] Usability study prep,MCP design research usability vsa-benefits-2,"## Issue Description _Prior to the usability study kicking off on July 1, we need to prep for note-taking and debriefing._ --- ## Tasks - [x] _Set up note-taking/synthesis spreadsheet_ - [x] _Schedule meetings for daily debrief sessions and set up Mural board as needed_ ## Acceptance Criteria - [x] _Note-taking/synthesis spreadsheet is linked in this ticket_ - [x] _Daily debrief sessions are scheduled and Mural board is linked_ ",1.0,"[MCP] Usability study prep - ## Issue Description _Prior to the usability study kicking off on July 1, we need to prep for note-taking and debriefing._ --- ## Tasks - [x] _Set up note-taking/synthesis spreadsheet_ - [x] _Schedule meetings for daily debrief sessions and set up Mural board as needed_ ## Acceptance Criteria - [x] _Note-taking/synthesis spreadsheet is linked in this ticket_ - [x] _Daily debrief sessions are scheduled and Mural board is linked_ ",1, usability study prep issue description prior to the usability study kicking off on july we need to prep for note taking and debriefing tasks set up note taking synthesis spreadsheet schedule meetings for daily debrief sessions and set up mural board as needed acceptance criteria note taking synthesis spreadsheet is linked in this ticket daily debrief sessions are scheduled and mural board is linked ,1 106956,13400566894.0,IssuesEvent,2020-09-03 16:00:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Public Websites [MVP learning center templates]: Back to top component,design needs-grooming ux vsa-public-websites,"This is a subtask of Accessibility feedback - Design intent collaboration - Public Websites [MVP learning center templates] #11386 ![image](https://user-images.githubusercontent.com/12564977/88180075-d12ef700-cbfa-11ea-9fbe-963189c12d33.png) 1. Jump links must not use smooth-scroll animated scroll. The setting must be 0. 2. “Back to top” should be a component. This would be a great opportunity for inter-op with the “On this page” component. Working in lock-step would be pretty cool! 3. Specification possibilities for Back to top link - Use for screens that are longer than 2400px (screens > 600px wide) or 1800px (screens < 600px wide) - Use when there are three or more h2 level headings (items in the jump links) Nielsen Norman (NN) recommends the Back to Top link be placed in the lower right side of the page, and says this is where people expect to see it. User research to determine in the lower left is used. - The recommendation from NN is to have one sticky, stationary Back to Top link per page, rather than multiple links in every section. - Movement back to top should not be animated. - Consider delaying the appearance of the Back to Top link until users reach 1800px vertical height. - `Back to top` - Example of potential lower right sticky link shown.",1.0,"Public Websites [MVP learning center templates]: Back to top component - This is a subtask of Accessibility feedback - Design intent collaboration - Public Websites [MVP learning center templates] #11386 ![image](https://user-images.githubusercontent.com/12564977/88180075-d12ef700-cbfa-11ea-9fbe-963189c12d33.png) 1. Jump links must not use smooth-scroll animated scroll. The setting must be 0. 2. “Back to top” should be a component. This would be a great opportunity for inter-op with the “On this page” component. Working in lock-step would be pretty cool! 3. Specification possibilities for Back to top link - Use for screens that are longer than 2400px (screens > 600px wide) or 1800px (screens < 600px wide) - Use when there are three or more h2 level headings (items in the jump links) Nielsen Norman (NN) recommends the Back to Top link be placed in the lower right side of the page, and says this is where people expect to see it. User research to determine in the lower left is used. - The recommendation from NN is to have one sticky, stationary Back to Top link per page, rather than multiple links in every section. - Movement back to top should not be animated. - Consider delaying the appearance of the Back to Top link until users reach 1800px vertical height. - `Back to top` - Example of potential lower right sticky link shown.",1,public websites back to top component this is a subtask of accessibility feedback design intent collaboration public websites jump links must not use smooth scroll animated scroll the setting must be “back to top” should be a component this would be a great opportunity for inter op with the “on this page” component working in lock step would be pretty cool specification possibilities for back to top link use for screens that are longer than screens wide or screens wide use when there are three or more level headings items in the jump links nielsen norman nn recommends the back to top link be placed in the lower right side of the page and says this is where people expect to see it user research to determine in the lower left is used the recommendation from nn is to have one sticky stationary back to top link per page rather than multiple links in every section movement back to top should not be animated consider delaying the appearance of the back to top link until users reach vertical height back to top example of potential lower right sticky link shown ,1 122147,16088611341.0,IssuesEvent,2021-04-26 14:13:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Standardized Design System Components - Breadcrumbs,analytics-insights design system gtm,"# Google Analytics Implementation ## Description - Standardize data layer events and variables to track [breadcrumbs](https://design.va.gov/storybook/?path=/docs/components-breadcrumbs--default) across va.gov ## Data Layer Specification ```javascript 'event': 'nav-breadcrumb', 'breadcrumb-clickLabel': //dynamically populate according to the breadcrumb label clicked on 'breadcrumb-clickLevel': //level number clicked on 'breadcrumb-totalLevels': //total number of click levels 'breadcrumb-mobile-first-enabled': //boolean for if the mobile first prop is used ``` ## Acceptance Criteria - [ ] Data layer for breadcrumbs as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1.0,"Standardized Design System Components - Breadcrumbs - # Google Analytics Implementation ## Description - Standardize data layer events and variables to track [breadcrumbs](https://design.va.gov/storybook/?path=/docs/components-breadcrumbs--default) across va.gov ## Data Layer Specification ```javascript 'event': 'nav-breadcrumb', 'breadcrumb-clickLabel': //dynamically populate according to the breadcrumb label clicked on 'breadcrumb-clickLevel': //level number clicked on 'breadcrumb-totalLevels': //total number of click levels 'breadcrumb-mobile-first-enabled': //boolean for if the mobile first prop is used ``` ## Acceptance Criteria - [ ] Data layer for breadcrumbs as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1,standardized design system components breadcrumbs google analytics implementation description standardize data layer events and variables to track across va gov data layer specification javascript event nav breadcrumb breadcrumb clicklabel dynamically populate according to the breadcrumb label clicked on breadcrumb clicklevel level number clicked on breadcrumb totallevels total number of click levels breadcrumb mobile first enabled boolean for if the mobile first prop is used acceptance criteria data layer for breadcrumbs as been deployed universally qa has been completed definition of done all appropriate issue tagging is completed all ac completed ,1 176439,28097097112.0,IssuesEvent,2023-03-30 16:32:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Components and pattern standards] Design components and patterns in use are outdated. (04.08.1),content design 508/Accessibility ia Supplemental Claims collab-cycle-feedback Staging CCIssue04.08 CC-Dashboard benefits-team-1,"### General Information #### VFS team name Benefits Team 1 #### VFS product name Supplemental Claims Form 20-0995 #### VFS feature name Supplemental Claims Form 20-0995 #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design Brian DeConinck - @briandeconinck - Accessibility *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components and patterns in use are outdated. ### Issue Details There is a success alert with ""You already have an intent to file"" content in it. Inside that alert is an additional component. We have updated the design system guidance since then and additional info components should no longer be used in alerts. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 08](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Use the new [expandable alert](https://design.va.gov/components/alert-expandable) instead with a success style. Since this alert is the only content on the page, you will probably need to reorganize the content. Consider having the expandable alert headline as ""You already have an Intent to File"" and when expanded the content would be... ""When you submit an Intent to File..."". Under the alert, put the content ""Our records show that you already submitted an Intent to File for disability compensation. Your Intent to File will expire on August 26, 2023. You’ll need to file your claim by this date to receive payments starting from your effective date."" Or you could remove the additional info component within the alert. Work with accessibility. One additional consideration: The expandable alert doesn't support a heading as its trigger control. That means a straight swap to an expandable alert will break the H3 focus pattern used throughout the workflow. Something to keep in mind while reorganizing the content here. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components and patterns in use are outdated. (04.08.1) - ### General Information #### VFS team name Benefits Team 1 #### VFS product name Supplemental Claims Form 20-0995 #### VFS feature name Supplemental Claims Form 20-0995 #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design Brian DeConinck - @briandeconinck - Accessibility *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components and patterns in use are outdated. ### Issue Details There is a success alert with ""You already have an intent to file"" content in it. Inside that alert is an additional component. We have updated the design system guidance since then and additional info components should no longer be used in alerts. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 08](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Use the new [expandable alert](https://design.va.gov/components/alert-expandable) instead with a success style. Since this alert is the only content on the page, you will probably need to reorganize the content. Consider having the expandable alert headline as ""You already have an Intent to File"" and when expanded the content would be... ""When you submit an Intent to File..."". Under the alert, put the content ""Our records show that you already submitted an Intent to File for disability compensation. Your Intent to File will expire on August 26, 2023. You’ll need to file your claim by this date to receive payments starting from your effective date."" Or you could remove the additional info component within the alert. Work with accessibility. One additional consideration: The expandable alert doesn't support a heading as its trigger control. That means a straight swap to an expandable alert will break the H3 focus pattern used throughout the workflow. Something to keep in mind while reorganizing the content here. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, design components and patterns in use are outdated general information vfs team name benefits team vfs product name supplemental claims form vfs feature name supplemental claims form point of contact reviewers allison christman design brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components and patterns in use are outdated issue details there is a success alert with you already have an intent to file content in it inside that alert is an additional component we have updated the design system guidance since then and additional info components should no longer be used in alerts link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation use the new instead with a success style since this alert is the only content on the page you will probably need to reorganize the content consider having the expandable alert headline as you already have an intent to file and when expanded the content would be when you submit an intent to file under the alert put the content our records show that you already submitted an intent to file for disability compensation your intent to file will expire on august you’ll need to file your claim by this date to receive payments starting from your effective date or you could remove the additional info component within the alert work with accessibility one additional consideration the expandable alert doesn t support a heading as its trigger control that means a straight swap to an expandable alert will break the focus pattern used throughout the workflow something to keep in mind while reorganizing the content here vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 85316,10603519002.0,IssuesEvent,2019-10-10 16:08:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Design Review with Shawna,design vsa vsa-ebenefits,"## Goal Meet with Shawna and seek feedback on the current design state for the Rated Disabilities feature. ## Considerations There are some alternate design options that need to be decided upon. ## Acceptance Criteria - [ ] Schedule a time with Shawna - [ ] Address her feedback",1.0,"Design Review with Shawna - ## Goal Meet with Shawna and seek feedback on the current design state for the Rated Disabilities feature. ## Considerations There are some alternate design options that need to be decided upon. ## Acceptance Criteria - [ ] Schedule a time with Shawna - [ ] Address her feedback",1,design review with shawna goal meet with shawna and seek feedback on the current design state for the rated disabilities feature considerations there are some alternate design options that need to be decided upon acceptance criteria schedule a time with shawna address her feedback,1 143104,21941797265.0,IssuesEvent,2022-05-23 18:56:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Good Services book research,service-design,"## Issue Description Research Good Services Book to ideate on takeaways --- ## Tasks - [x] Read book and capture learnings in group mural for synthesis ## Acceptance Criteria - [x] Mural is populated with learnings",1.0,"Good Services book research - ## Issue Description Research Good Services Book to ideate on takeaways --- ## Tasks - [x] Read book and capture learnings in group mural for synthesis ## Acceptance Criteria - [x] Mural is populated with learnings",1,good services book research issue description research good services book to ideate on takeaways tasks read book and capture learnings in group mural for synthesis acceptance criteria mural is populated with learnings,1 86824,10821666560.0,IssuesEvent,2019-11-08 19:14:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Capture Wait Time,design vaos,"## Story As the VA, I want to track veterans' appointment wait times when they schedule directly so that we can better understand the quality of care we are providing. ## AC - [ ] New page exists for 'when would you like to be seen' - [ ] New page comes after clinic selection in direct schedule flow - [ ] New page comes before calendar / datepicker in direct schedule flow - [ ] New page does not show in request flow",1.0,"Capture Wait Time - ## Story As the VA, I want to track veterans' appointment wait times when they schedule directly so that we can better understand the quality of care we are providing. ## AC - [ ] New page exists for 'when would you like to be seen' - [ ] New page comes after clinic selection in direct schedule flow - [ ] New page comes before calendar / datepicker in direct schedule flow - [ ] New page does not show in request flow",1,capture wait time story as the va i want to track veterans appointment wait times when they schedule directly so that we can better understand the quality of care we are providing ac new page exists for when would you like to be seen new page comes after clinic selection in direct schedule flow new page comes before calendar datepicker in direct schedule flow new page does not show in request flow,1 120122,15704889947.0,IssuesEvent,2021-03-26 15:30:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] MyVA - Review and update My VA test cases,design my-va-dashboard unplanned-work vsa-authenticated-exp,"## Background In preparation for Staging review we need to review our test cases. ## Tasks - [ ] Review [MyVA test cases](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/qa/MyVA%20-%20test%20cases.md) - [ ] Update documentation based on final designs - [ ] Review updates with the team - [ ] Communicate with @tlei123 to let him know this documentation has been updated and determine next steps with TestRail.",1.0,"[Design] MyVA - Review and update My VA test cases - ## Background In preparation for Staging review we need to review our test cases. ## Tasks - [ ] Review [MyVA test cases](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/qa/MyVA%20-%20test%20cases.md) - [ ] Update documentation based on final designs - [ ] Review updates with the team - [ ] Communicate with @tlei123 to let him know this documentation has been updated and determine next steps with TestRail.",1, myva review and update my va test cases background in preparation for staging review we need to review our test cases tasks review update documentation based on final designs review updates with the team communicate with to let him know this documentation has been updated and determine next steps with testrail ,1 140271,21053200582.0,IssuesEvent,2022-03-31 22:42:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Adjust Confirmation Copy for Dependency Claims,design vsa vsa-ebenefits,"## Background Currently there is copy on the confirmation screen for Dependency Claims that a Veteran can view their application status in MyVA instead of the Claim Status Tool ## Considerations This content was geared towards an older initiative; it seems as should have been pointed towards the CST. ## Tasks - [x] Adjust copy in the prototype/mockups - [ ] Ask FE to adjust the copy ## Acceptance Criteria - [x] Mockups are updated",1.0,"Adjust Confirmation Copy for Dependency Claims - ## Background Currently there is copy on the confirmation screen for Dependency Claims that a Veteran can view their application status in MyVA instead of the Claim Status Tool ## Considerations This content was geared towards an older initiative; it seems as should have been pointed towards the CST. ## Tasks - [x] Adjust copy in the prototype/mockups - [ ] Ask FE to adjust the copy ## Acceptance Criteria - [x] Mockups are updated",1,adjust confirmation copy for dependency claims background currently there is copy on the confirmation screen for dependency claims that a veteran can view their application status in myva instead of the claim status tool considerations this content was geared towards an older initiative it seems as should have been pointed towards the cst tasks adjust copy in the prototype mockups ask fe to adjust the copy acceptance criteria mockups are updated,1 109406,13768350317.0,IssuesEvent,2020-10-07 16:57:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Launch] BDD: UAT Testing for Benefits Delivery at Discharge,BDD UAT design vsa-benefits,"## User Story After staging review we will be ready for UAT. We have prepared a UAT plan and have been waiting to pull the trigger on scheduling. This story is capturing the work to do the UAT as well, not just the creation of the plan. ## Tasks - [ ] Final test users and test script defined - [ ] Schedule UAT with Perigian ## Acceptance Criteria: - [ ] 5-6 users UAT'ed ## Configuration - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (e.g. `vsa-authenticated-exp`, `vsa-caregiver`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1.0,"[Launch] BDD: UAT Testing for Benefits Delivery at Discharge - ## User Story After staging review we will be ready for UAT. We have prepared a UAT plan and have been waiting to pull the trigger on scheduling. This story is capturing the work to do the UAT as well, not just the creation of the plan. ## Tasks - [ ] Final test users and test script defined - [ ] Schedule UAT with Perigian ## Acceptance Criteria: - [ ] 5-6 users UAT'ed ## Configuration - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (e.g. `vsa-authenticated-exp`, `vsa-caregiver`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1, bdd uat testing for benefits delivery at discharge user story after staging review we will be ready for uat we have prepared a uat plan and have been waiting to pull the trigger on scheduling this story is capturing the work to do the uat as well not just the creation of the plan tasks final test users and test script defined schedule uat with perigian acceptance criteria users uat ed configuration attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team e g vsa authenticated exp vsa caregiver labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 120653,15789030430.0,IssuesEvent,2021-04-01 21:52:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Profile - make it more clear that we only support US phone numbers,design planned-work profile vsa-authenticated-exp,"## Background **Updated 3/30/21** We thought we needed to change the display of international phone numbers somehow since we are totally ignoring the country code at the moment. We've determined that what we actually need to do is make it more clear to people that we only support U.S. numbers at this time. See [slack convo](https://dsva.slack.com/archives/C909ZG2BB/p1599226764172300?thread_ts=1599169576.163500&cid=C909ZG2BB) and comments on this issue. ### Why There are some countries (e.g. Belize) that have 10 digits including the area code, so someone could save an international number to their profile, and not realize that their country code was actually being saved in the DB as their area code. ## Tasks - [x] Produce a mockup that: - removes the info box telling people we only accept US phone numbers - adds the helper text about only accepting US phone numbers to the label field. - makes the field label more specific (currently just says `number`) - [x] Produce a mockup with the new proposed error copy for invalid phone numbers. - [x] Work with content to produce final copy before handoff to FE.",1.0,"[Design] Profile - make it more clear that we only support US phone numbers - ## Background **Updated 3/30/21** We thought we needed to change the display of international phone numbers somehow since we are totally ignoring the country code at the moment. We've determined that what we actually need to do is make it more clear to people that we only support U.S. numbers at this time. See [slack convo](https://dsva.slack.com/archives/C909ZG2BB/p1599226764172300?thread_ts=1599169576.163500&cid=C909ZG2BB) and comments on this issue. ### Why There are some countries (e.g. Belize) that have 10 digits including the area code, so someone could save an international number to their profile, and not realize that their country code was actually being saved in the DB as their area code. ## Tasks - [x] Produce a mockup that: - removes the info box telling people we only accept US phone numbers - adds the helper text about only accepting US phone numbers to the label field. - makes the field label more specific (currently just says `number`) - [x] Produce a mockup with the new proposed error copy for invalid phone numbers. - [x] Work with content to produce final copy before handoff to FE.",1, profile make it more clear that we only support us phone numbers background updated we thought we needed to change the display of international phone numbers somehow since we are totally ignoring the country code at the moment we ve determined that what we actually need to do is make it more clear to people that we only support u s numbers at this time see and comments on this issue why there are some countries e g belize that have digits including the area code so someone could save an international number to their profile and not realize that their country code was actually being saved in the db as their area code tasks produce a mockup that removes the info box telling people we only accept us phone numbers adds the helper text about only accepting us phone numbers to the label field makes the field label more specific currently just says number produce a mockup with the new proposed error copy for invalid phone numbers work with content to produce final copy before handoff to fe ,1 166339,26341107890.0,IssuesEvent,2023-01-10 17:44:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"VistA Made Community Care Appointments ""Need To Make Changes"" Says Contact Provider and No Provider Listed",bug frontend vaos-product-design,"1. Go into VistA and make a VistA community care appt. 2. View the appointment details in VAOS. 3. Need to make changes section says to contact provider but no provider or facility information is listed. ![image.png](https://images.zenhubusercontent.com/5f2d82e4a65f7435058cfd75/1bc18934-b080-4652-8cc0-fa86aa484850)",1.0,"VistA Made Community Care Appointments ""Need To Make Changes"" Says Contact Provider and No Provider Listed - 1. Go into VistA and make a VistA community care appt. 2. View the appointment details in VAOS. 3. Need to make changes section says to contact provider but no provider or facility information is listed. ![image.png](https://images.zenhubusercontent.com/5f2d82e4a65f7435058cfd75/1bc18934-b080-4652-8cc0-fa86aa484850)",1,vista made community care appointments need to make changes says contact provider and no provider listed go into vista and make a vista community care appt view the appointment details in vaos need to make changes section says to contact provider but no provider or facility information is listed ,1 148887,23393886451.0,IssuesEvent,2022-08-11 20:45:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Create 3 Prototypes (Travel reimbursement),design ux HCE-Checkin,"## Tasks - [x] Review 18F PCI sketch files - [ ] Review the BTSSS files (touch base with Ben) to make sure we understand all of the fields that are required (can also look at the API) - [x] Recreate the work in Zach's sketch files - [x] Make sure it fits with the Design System - [x] Review and confirm content - [x] Make a Sketch clickthrough ## AC - we have a prototype to test with users",1.0,"[Design] Create 3 Prototypes (Travel reimbursement) - ## Tasks - [x] Review 18F PCI sketch files - [ ] Review the BTSSS files (touch base with Ben) to make sure we understand all of the fields that are required (can also look at the API) - [x] Recreate the work in Zach's sketch files - [x] Make sure it fits with the Design System - [x] Review and confirm content - [x] Make a Sketch clickthrough ## AC - we have a prototype to test with users",1, create prototypes travel reimbursement tasks review pci sketch files review the btsss files touch base with ben to make sure we understand all of the fields that are required can also look at the api recreate the work in zach s sketch files make sure it fits with the design system review and confirm content make a sketch clickthrough ac we have a prototype to test with users,1 108138,13560062172.0,IssuesEvent,2020-09-18 00:42:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Customer Support - Define E2E Support Models for Top Customer Segments,VSP-Initiative service-design,"## Problem Statement In order to scale the platform to handle more VFS teams, VSP needs a set of customer support models that enable us to consistently provide high quality support while establishing self-service pathways that work for different types of VFS teams. For VFS teams, our research has shown that a recurring pain point is a lack of understanding of why and how to engage with VSP at different points in the latter's user journey on the platform. How might we create customer support models that enable VSP to increase the number VFS teams it can simultaneously support while improving customer satisfaction? ## Hypothesis or Bet *How will this initiative impact the quality of VFS or VSP teams' work?* *How will this initiative be easy for VFS or VSP teams? Or how will it be easier than what they did before?* ## We will know we're done when... (""Definition of Done"") *What requirements does this project need to meet for you to finish this initiative?* ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. See (VSP Product Terminology)[https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md] for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1.0,"Customer Support - Define E2E Support Models for Top Customer Segments - ## Problem Statement In order to scale the platform to handle more VFS teams, VSP needs a set of customer support models that enable us to consistently provide high quality support while establishing self-service pathways that work for different types of VFS teams. For VFS teams, our research has shown that a recurring pain point is a lack of understanding of why and how to engage with VSP at different points in the latter's user journey on the platform. How might we create customer support models that enable VSP to increase the number VFS teams it can simultaneously support while improving customer satisfaction? ## Hypothesis or Bet *How will this initiative impact the quality of VFS or VSP teams' work?* *How will this initiative be easy for VFS or VSP teams? Or how will it be easier than what they did before?* ## We will know we're done when... (""Definition of Done"") *What requirements does this project need to meet for you to finish this initiative?* ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. See (VSP Product Terminology)[https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md] for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: _directory name used for your product documentation_ * **Product Outline**: _link to Product Outline_ * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: _link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping_ * **Release plan**: _link to Release Plan ticket_ ## TODOs - [ ] Convert this issue to an epic - [ ] Add your team's label to this epic ",1,customer support define support models for top customer segments problem statement in order to scale the platform to handle more vfs teams vsp needs a set of customer support models that enable us to consistently provide high quality support while establishing self service pathways that work for different types of vfs teams for vfs teams our research has shown that a recurring pain point is a lack of understanding of why and how to engage with vsp at different points in the latter s user journey on the platform how might we create customer support models that enable vsp to increase the number vfs teams it can simultaneously support while improving customer satisfaction hypothesis or bet how will this initiative impact the quality of vfs or vsp teams work how will this initiative be easy for vfs or vsp teams or how will it be easier than what they did before we will know we re done when definition of done what requirements does this project need to meet for you to finish this initiative launch checklist guidance delete before posting this checklist is intended to be used to help answer is my vsp initiative ready for launch all of the items in this checklist should be completed with artifacts linked or have a brief explanation of why they ve been skipped before launching a given vsp initiative all links or explanations can be provided in required artifacts sections the items that can be skipped are marked as such keep in mind the distinction between product and initiative each product needs specific supporting documentation but initiatives to improve existing products should reuse existing documentation for that product see vsp product terminology for details is this service tool feature tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a checked into note the product directory name should match with the list of vsp products external facing a exists for this product feature tool and should be located at platform product name readme md external facing a exists for this product feature tool and is updated for changes from this initiative and should be linked from the vfs facing readme for your product and should be located within platform product name unless you already have another location for it if applicable and post to about whether this should be added to the if applicable post to for external communication about this change e g vsp newsletter customer facing meetings measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying required artifacts documentation product name directory name used for your product documentation product outline link to product outline readme link to vfs facing readme for your product user guide link to user guide testing usability test link to github issue or provide reason for skipping manual qa link to github issue or documented results automated tests link to tests or n a measurement success metrics link to where success metrics are measured or where they re defined product outline is ok or provide reason for skipping release plan link to release plan ticket todos convert this issue to an epic add your team s label to this epic ,1 115223,14705071088.0,IssuesEvent,2021-01-04 17:29:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Review Erik's initial DD for Edu build ,EDU DD design needs-grooming vsa-authenticated-exp,"## Tasks - [ ] Review DD for Edu on staging - [ ] Provide feedback",1.0,"[Design] Review Erik's initial DD for Edu build - ## Tasks - [ ] Review DD for Edu on staging - [ ] Provide feedback",1, review erik s initial dd for edu build tasks review dd for edu on staging provide feedback,1 114307,14546010573.0,IssuesEvent,2020-12-15 20:32:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] Prototype for Veteran testing,design vet-center vsa vsa-facilities,"## Issue Description Make final adjustments to prototype/wireframe for use in Veteran testing for the Vet Center initiative --- ## Tasks - [ ] Iterate prototype/wire frame with final feedback before Veteran testing ## Acceptance Criteria - [ ] Prototype/wireframe is available for testing --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[DESIGN] Prototype for Veteran testing - ## Issue Description Make final adjustments to prototype/wireframe for use in Veteran testing for the Vet Center initiative --- ## Tasks - [ ] Iterate prototype/wire frame with final feedback before Veteran testing ## Acceptance Criteria - [ ] Prototype/wireframe is available for testing --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, prototype for veteran testing issue description make final adjustments to prototype wireframe for use in veteran testing for the vet center initiative tasks iterate prototype wire frame with final feedback before veteran testing acceptance criteria prototype wireframe is available for testing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 148717,23368410728.0,IssuesEvent,2022-08-10 17:25:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed, Design | Profile | BAI | UI Updates based on research sessions,design vsa vsa-authenticated-exp profile bad-address-indicator,"## Background User research for the BAI project revealed some confusion amongst users wrt steps they should take to confirm that an existing mailing address is correct. ## Tasks - [x] Validate proposed UI changes with Accessibility - [x] Re-locate the ""confirm"" instructions from the primary instructions (larger alert) and move to the smaller alert in the mailing address field within an act'l drop-down component ## Acceptance Criteria - [x] UI confirmed with Accessibility - [ ] Mocks reviewed with PO and PM ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1.0," Design | Profile | BAI | UI Updates based on research sessions - ## Background User research for the BAI project revealed some confusion amongst users wrt steps they should take to confirm that an existing mailing address is correct. ## Tasks - [x] Validate proposed UI changes with Accessibility - [x] Re-locate the ""confirm"" instructions from the primary instructions (larger alert) and move to the smaller alert in the mailing address field within an act'l drop-down component ## Acceptance Criteria - [x] UI confirmed with Accessibility - [ ] Mocks reviewed with PO and PM ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1, design profile bai ui updates based on research sessions background user research for the bai project revealed some confusion amongst users wrt steps they should take to confirm that an existing mailing address is correct tasks validate proposed ui changes with accessibility re locate the confirm instructions from the primary instructions larger alert and move to the smaller alert in the mailing address field within an act l drop down component acceptance criteria ui confirmed with accessibility mocks reviewed with po and pm how to configure this issue include practice area in title e g include project initiative name e g auth profile address change messaging add label for practice area frontend backend design add label for project if applicable assign to a profile team member associate with an epic if applicable if creating for yourself estimate work if enough info exists to do so ,1 109417,13769569689.0,IssuesEvent,2020-10-07 18:49:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Refine and Augment Direct Deposit- EDU Mockups,VA Profile-dependent design direct deposit vsa vsa-authenticated-exp vsa-ebenefits,"### Story As a VA payment recipient, I need a simple way to change my direct deposit information so that payments are deposited in the correct bank account. ### Goals Refine/understand use cases and states of DD-EDU so that mockups are complete and accurate. ### Considerations - [DD-EDU discovery; stakeholder questions at bottom](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/direct-deposit/edu-direct-deposit/design/edu-dd-discovery.md) - [DD-EDU Mockups (Adobe XD)](https://xd.adobe.com/view/532272b2-b423-4e1b-a8c6-d1a583da3d37-0671/) ### Tasks - [ ] Meet with business stakeholders - [ ] Collect clarification/feedback from team and stakeholders - [ ] Add any additional required states to mockups - [ ] Revise content and design as needed across mockups ### Acceptance criteria - [ ] All required states for DD-EDU reflected in mockups - [ ] Content changes made per clarification/feedback ",1.0,"Refine and Augment Direct Deposit- EDU Mockups - ### Story As a VA payment recipient, I need a simple way to change my direct deposit information so that payments are deposited in the correct bank account. ### Goals Refine/understand use cases and states of DD-EDU so that mockups are complete and accurate. ### Considerations - [DD-EDU discovery; stakeholder questions at bottom](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/direct-deposit/edu-direct-deposit/design/edu-dd-discovery.md) - [DD-EDU Mockups (Adobe XD)](https://xd.adobe.com/view/532272b2-b423-4e1b-a8c6-d1a583da3d37-0671/) ### Tasks - [ ] Meet with business stakeholders - [ ] Collect clarification/feedback from team and stakeholders - [ ] Add any additional required states to mockups - [ ] Revise content and design as needed across mockups ### Acceptance criteria - [ ] All required states for DD-EDU reflected in mockups - [ ] Content changes made per clarification/feedback ",1,refine and augment direct deposit edu mockups story as a va payment recipient i need a simple way to change my direct deposit information so that payments are deposited in the correct bank account goals refine understand use cases and states of dd edu so that mockups are complete and accurate considerations tasks meet with business stakeholders collect clarification feedback from team and stakeholders add any additional required states to mockups revise content and design as needed across mockups acceptance criteria all required states for dd edu reflected in mockups content changes made per clarification feedback ,1 152709,24008689093.0,IssuesEvent,2022-09-14 16:47:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyHealth - Secure Messaging - Support engineers during build,design my-health my-health-SM-CORE mhv-to-va.gov-SM,Support MHV front-end engineers during Secure Messaging build (ongoing through PI7),1.0,[Design] MyHealth - Secure Messaging - Support engineers during build - Support MHV front-end engineers during Secure Messaging build (ongoing through PI7),1, myhealth secure messaging support engineers during build support mhv front end engineers during secure messaging build ongoing through ,1 113264,14403977854.0,IssuesEvent,2020-12-03 16:42:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Write up tasks for developers for Storybook pilot,design-system-team,"## Issue Description Write up the steps for developers who will be part of the storybook pilot - Use a component — give user instructions on using a component - Update a component — we give a specific component to update - Fix responsiveness of a component — need to develop a table --- ## Tasks - [ ] Write up instructions for the tasks with link ",1.0,"Write up tasks for developers for Storybook pilot - ## Issue Description Write up the steps for developers who will be part of the storybook pilot - Use a component — give user instructions on using a component - Update a component — we give a specific component to update - Fix responsiveness of a component — need to develop a table --- ## Tasks - [ ] Write up instructions for the tasks with link ",1,write up tasks for developers for storybook pilot issue description write up the steps for developers who will be part of the storybook pilot use a component — give user instructions on using a component update a component — we give a specific component to update fix responsiveness of a component — need to develop a table tasks write up instructions for the tasks with link ,1 116466,14967034293.0,IssuesEvent,2021-01-27 15:15:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[PM] MyVA 2.0 Submit request for Usability Testing Prep review,design my-va-dashboard vsa-authenticated-exp,"## Background [Usability Testing Prep Review info](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#usability-testing-prep) [Submit Usability Testing Prep Review Request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=andreahewitt-odd%2C+shiragoodman&labels=vsp-product-support%2C+content-ia-team%2C+collaboration-cycle%2C+collab-cycle-review&template=usability-testing-prep.md&title=Usability+Testing+Prep+%5BTeam+Name%2C+Feature+Name%5D) ## Tasks - [ ] Create/include all required artifacts - [ ] Submit request for usability testing prep review",1.0,"[PM] MyVA 2.0 Submit request for Usability Testing Prep review - ## Background [Usability Testing Prep Review info](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/vsp-collaboration-cycle.md#usability-testing-prep) [Submit Usability Testing Prep Review Request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=andreahewitt-odd%2C+shiragoodman&labels=vsp-product-support%2C+content-ia-team%2C+collaboration-cycle%2C+collab-cycle-review&template=usability-testing-prep.md&title=Usability+Testing+Prep+%5BTeam+Name%2C+Feature+Name%5D) ## Tasks - [ ] Create/include all required artifacts - [ ] Submit request for usability testing prep review",1, myva submit request for usability testing prep review background tasks create include all required artifacts submit request for usability testing prep review,1 141622,21574340930.0,IssuesEvent,2022-05-02 12:12:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Review content of Overview/Landing page of SDT site,service-design,"## Issue Description _What should be retained, removed? What type of language or sections should be introduced given the Support nature of the team? [Working document](https://docs.google.com/document/d/14EOIq7YfZMxCLUOS3h2glRJSfQ583hOHaBpc47r978o/edit?usp=sharing) --- ## Tasks - [x] Organize page sections and compose any initial new language ## Acceptance Criteria - [x] Reference document of potential layout/content ",1.0,"Review content of Overview/Landing page of SDT site - ## Issue Description _What should be retained, removed? What type of language or sections should be introduced given the Support nature of the team? [Working document](https://docs.google.com/document/d/14EOIq7YfZMxCLUOS3h2glRJSfQ583hOHaBpc47r978o/edit?usp=sharing) --- ## Tasks - [x] Organize page sections and compose any initial new language ## Acceptance Criteria - [x] Reference document of potential layout/content ",1,review content of overview landing page of sdt site issue description what should be retained removed what type of language or sections should be introduced given the support nature of the team tasks organize page sections and compose any initial new language acceptance criteria reference document of potential layout content ,1 125238,16749161488.0,IssuesEvent,2021-06-11 19:56:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,COE - Provide a way for users to view their existing COE if they have chosen to fill out the form,LGY design frontend vsa vsa-ebenefits,"## Description As a user who has gone through the automatic COE check and is eligible for an automatic COE, but has opted to instead fill out the 26-1880, I would like a way to access my previously generated COE. ## Considerations Currently, users can click on a link called `Make changes online COE with VA Form 26-1880`. This link lives on the [COE page](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/139511607/simulate/sitemap) for when users successfully pass the coe check and are eligible to download one. If a user clicks this link they are sent to the form introduction page to fill out the form. Using the browser back button allows them to re-access their COE, but we should include a more explicit way return there. For example, on the Chapter 31 form introduction page, we include a link that allows users to go back and answer the wizard questions again. ## Tasks - [ ] add a more explicit way to return to the COE page ## Acceptance criteria - [ ] above task is done",1.0,"COE - Provide a way for users to view their existing COE if they have chosen to fill out the form - ## Description As a user who has gone through the automatic COE check and is eligible for an automatic COE, but has opted to instead fill out the 26-1880, I would like a way to access my previously generated COE. ## Considerations Currently, users can click on a link called `Make changes online COE with VA Form 26-1880`. This link lives on the [COE page](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/139511607/simulate/sitemap) for when users successfully pass the coe check and are eligible to download one. If a user clicks this link they are sent to the form introduction page to fill out the form. Using the browser back button allows them to re-access their COE, but we should include a more explicit way return there. For example, on the Chapter 31 form introduction page, we include a link that allows users to go back and answer the wizard questions again. ## Tasks - [ ] add a more explicit way to return to the COE page ## Acceptance criteria - [ ] above task is done",1,coe provide a way for users to view their existing coe if they have chosen to fill out the form description as a user who has gone through the automatic coe check and is eligible for an automatic coe but has opted to instead fill out the i would like a way to access my previously generated coe considerations currently users can click on a link called make changes online coe with va form this link lives on the for when users successfully pass the coe check and are eligible to download one if a user clicks this link they are sent to the form introduction page to fill out the form using the browser back button allows them to re access their coe but we should include a more explicit way return there for example on the chapter form introduction page we include a link that allows users to go back and answer the wizard questions again tasks add a more explicit way to return to the coe page acceptance criteria above task is done,1 122969,16396216012.0,IssuesEvent,2021-05-18 00:13:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reopened,Update 10-10CG Content (April 2021),Epic backend design frontend vsa-caregiver,"## User Story As a Veteran/Caregiver I want to fill out the latest version of the online form So that I can apply for the program with the most useful information. ## Acceptance Criteria - [Product] Receive & distribute new paper form - [Design] Prototypes are updated - [Design] New language is approved by VSP - [Design/Product] New changes are approved by Caregiver program - [Frontend] Front end is updated - [Backend] Any backend changes are made - [Product] Front end is QAed - [Backend] PDF functionality is updated - [Product] Pushed to production - [Product] Confirmed there are no errors",1.0,"Update 10-10CG Content (April 2021) - ## User Story As a Veteran/Caregiver I want to fill out the latest version of the online form So that I can apply for the program with the most useful information. ## Acceptance Criteria - [Product] Receive & distribute new paper form - [Design] Prototypes are updated - [Design] New language is approved by VSP - [Design/Product] New changes are approved by Caregiver program - [Frontend] Front end is updated - [Backend] Any backend changes are made - [Product] Front end is QAed - [Backend] PDF functionality is updated - [Product] Pushed to production - [Product] Confirmed there are no errors",1,update content april user story as a veteran caregiver i want to fill out the latest version of the online form so that i can apply for the program with the most useful information acceptance criteria receive distribute new paper form prototypes are updated new language is approved by vsp new changes are approved by caregiver program front end is updated any backend changes are made front end is qaed pdf functionality is updated pushed to production confirmed there are no errors,1 202508,15833303216.0,IssuesEvent,2021-04-06 15:30:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Platform Website — Create Confluence migration plan for VFS-facing docs,Epic VSP-Initiative content-ia-team documentation,"## Problem Statement The C+IA team spent 2020 Q4 moving backend documentation into Confluence. If the C+IA team continues the ""one practice area, one quarter"" rate, we won't be able to unveil Confluence entirely to VFS teams until 2022. This would lead to VFS team confusion since there would be no single documentation ""source of truth."" To remove the C+IA team as a bottleneck, we are determining: * HMW scale documentation migration to Confluence? * HMW provide a skeleton, workable experience to VFS readers who consume all content types? * This is a separate initiative documented in [Documentation Site — Migrate Homepage MVP documentation to Confluence #17060](https://github.com/department-of-veterans-affairs/va.gov-team/issues/17060) ## Hypothesis or Bet If we leverage VSP teams to move _their own_ VFS-facing docs into Confluence, then the C+IA team will be able to focus on the holistic Confluence documentation experience. This ticket complements #17060, which describes the work involved in providing a skeleton, workable documentation experience. This ticket describes creating a plan for fleshing out the skeleton, ie migrating and performing QA on lower-priority documentation. ## We will know we're done when... (""Definition of Done"") * [ ] We have created a plan that has the approval of each VSP team that owns VFS-facing documentation. * [ ] We have guidance around the placement. * [ ] We have guidance around moving the docs seamlessly. * [ ] Finalize release plan for Confluence documentation site. ## Known Blockers/Dependencies * Dependencies: Will have to communicate with VSP teams in order to create a migration plan ## Projected Launch Date * EOQ - March 2021 ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. [VSP Product Terminology](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md) for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: [/products/platform/platform-documentaiton](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/platform/platform-documentation) * **Product Outline**: [Product outline](https://github.com/department-of-veterans-affairs/va.gov-team/issues/17377) * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: * VSP teams understand the roles they will play in migrating the content that they own * **Release plan**: [link to Release Plan ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/17377) ## TODOs - [x] Convert this issue to an epic - [x] Add your team's label to this epic ",1.0,"Platform Website — Create Confluence migration plan for VFS-facing docs - ## Problem Statement The C+IA team spent 2020 Q4 moving backend documentation into Confluence. If the C+IA team continues the ""one practice area, one quarter"" rate, we won't be able to unveil Confluence entirely to VFS teams until 2022. This would lead to VFS team confusion since there would be no single documentation ""source of truth."" To remove the C+IA team as a bottleneck, we are determining: * HMW scale documentation migration to Confluence? * HMW provide a skeleton, workable experience to VFS readers who consume all content types? * This is a separate initiative documented in [Documentation Site — Migrate Homepage MVP documentation to Confluence #17060](https://github.com/department-of-veterans-affairs/va.gov-team/issues/17060) ## Hypothesis or Bet If we leverage VSP teams to move _their own_ VFS-facing docs into Confluence, then the C+IA team will be able to focus on the holistic Confluence documentation experience. This ticket complements #17060, which describes the work involved in providing a skeleton, workable documentation experience. This ticket describes creating a plan for fleshing out the skeleton, ie migrating and performing QA on lower-priority documentation. ## We will know we're done when... (""Definition of Done"") * [ ] We have created a plan that has the approval of each VSP team that owns VFS-facing documentation. * [ ] We have guidance around the placement. * [ ] We have guidance around moving the docs seamlessly. * [ ] Finalize release plan for Confluence documentation site. ## Known Blockers/Dependencies * Dependencies: Will have to communicate with VSP teams in order to create a migration plan ## Projected Launch Date * EOQ - March 2021 ## Launch Checklist ### Guidance (delete before posting) _This checklist is intended to be used to help answer, ""is my VSP initiative ready for launch?"". All of the items in this checklist should be completed, with artifacts linked---or have a brief explanation of why they've been skipped---before launching a given VSP initiative. All links or explanations can be provided in **Required Artifacts** sections. The items that can be skipped are marked as such._ _Keep in mind the distinction between **Product** and **Initiative** --- each Product needs specific supporting documentation, but Initiatives to improve existing Products should reuse existing documentation for that Product. [VSP Product Terminology](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-terminology.md) for details._ ### Is this service / tool / feature... ### ... tested? - [ ] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [ ] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [ ] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [ ] New documentation is written pursuant to our [documentation style guide](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/documentation/style-guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [ ] Internal-facing: there's a [Product Outline](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-outline-template.md) checked into [`products/platform/PRODUCT_NAME/`](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/platform/) * _Note: the Product Directory Name should match 1:1 with the List of VSP Products_ - [ ] External-facing: a [VFS-facing README](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/product-readme-template.md) exists for this product/feature tool - [ ] ... and should be located at `platform/PRODUCT_NAME/README.md` - [ ] External-facing: a [User Guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/product-management/writing-user-guides.md) exists for this product/feature/tool, and is updated for changes from this initiative - [ ] ... and should be linked from the VFS-facing README for your product - [ ] ... and should be located within `platform/PRODUCT_NAME/`, unless you already have another location for it - [ ] _(if applicable)_... and post to [#vsp-content-ia](https://dsva.slack.com/channels/vsp-content-ia) about whether this should be added to the [Documentation homepage](https://department-of-veterans-affairs.github.io/va.gov-team/) - [ ] _(if applicable)_ Post to [#vsp-service-design](https://dsva.slack.com/channels/vsp-service-design) for external communication about this change (e.g. VSP Newsletter, customer-facing meetings) ### ... measurable - [ ] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform/analytics) - [ ] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: [/products/platform/platform-documentaiton](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/platform/platform-documentation) * **Product Outline**: [Product outline](https://github.com/department-of-veterans-affairs/va.gov-team/issues/17377) * **README**: _link to VFS-facing README for your product_ * **User Guide**: _link to User Guide_ ### Testing * **Usability test**: _link to GitHub issue, or provide reason for skipping_ * **Manual QA**: _link to GitHub issue or documented results_ * **Automated tests**: _link to tests, or ""N/A""_ ### Measurement * **Success metrics**: * VSP teams understand the roles they will play in migrating the content that they own * **Release plan**: [link to Release Plan ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/17377) ## TODOs - [x] Convert this issue to an epic - [x] Add your team's label to this epic ",0,platform website — create confluence migration plan for vfs facing docs problem statement the c ia team spent moving backend documentation into confluence if the c ia team continues the one practice area one quarter rate we won t be able to unveil confluence entirely to vfs teams until this would lead to vfs team confusion since there would be no single documentation source of truth to remove the c ia team as a bottleneck we are determining hmw scale documentation migration to confluence hmw provide a skeleton workable experience to vfs readers who consume all content types this is a separate initiative documented in hypothesis or bet if we leverage vsp teams to move their own vfs facing docs into confluence then the c ia team will be able to focus on the holistic confluence documentation experience this ticket complements which describes the work involved in providing a skeleton workable documentation experience this ticket describes creating a plan for fleshing out the skeleton ie migrating and performing qa on lower priority documentation we will know we re done when definition of done we have created a plan that has the approval of each vsp team that owns vfs facing documentation we have guidance around the placement we have guidance around moving the docs seamlessly finalize release plan for confluence documentation site known blockers dependencies dependencies will have to communicate with vsp teams in order to create a migration plan projected launch date eoq march launch checklist guidance delete before posting this checklist is intended to be used to help answer is my vsp initiative ready for launch all of the items in this checklist should be completed with artifacts linked or have a brief explanation of why they ve been skipped before launching a given vsp initiative all links or explanations can be provided in required artifacts sections the items that can be skipped are marked as such keep in mind the distinction between product and initiative each product needs specific supporting documentation but initiatives to improve existing products should reuse existing documentation for that product for details is this service tool feature tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a checked into note the product directory name should match with the list of vsp products external facing a exists for this product feature tool and should be located at platform product name readme md external facing a exists for this product feature tool and is updated for changes from this initiative and should be linked from the vfs facing readme for your product and should be located within platform product name unless you already have another location for it if applicable and post to about whether this should be added to the if applicable post to for external communication about this change e g vsp newsletter customer facing meetings measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying required artifacts documentation product name product outline readme link to vfs facing readme for your product user guide link to user guide testing usability test link to github issue or provide reason for skipping manual qa link to github issue or documented results automated tests link to tests or n a measurement success metrics vsp teams understand the roles they will play in migrating the content that they own release plan todos convert this issue to an epic add your team s label to this epic ,0 118039,15216829094.0,IssuesEvent,2021-02-17 15:56:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create Common Component for standard Scroll View,Design -> Frontend components frontend va-mobile-app,"As a developer, I want to add a scroll view with the global y padding and styling without reusing code. I would also like a standard component that I can refactor once and apply globally. This ScrollView should have the standard topPadding of 20 and bottomPadding of 40 and stretch itself to fill all available space. Once built it should replace all scroll views in the app. ",1.0,"Create Common Component for standard Scroll View - As a developer, I want to add a scroll view with the global y padding and styling without reusing code. I would also like a standard component that I can refactor once and apply globally. This ScrollView should have the standard topPadding of 20 and bottomPadding of 40 and stretch itself to fill all available space. Once built it should replace all scroll views in the app. ",1,create common component for standard scroll view as a developer i want to add a scroll view with the global y padding and styling without reusing code i would also like a standard component that i can refactor once and apply globally this scrollview should have the standard toppadding of and bottompadding of and stretch itself to fill all available space once built it should replace all scroll views in the app ,1 118710,15359526006.0,IssuesEvent,2021-03-01 15:56:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[UI] Adding Link to VAOS on Questionnaire List,design sitewide content-product support vsa-healthcare-exp,"## User Story - As a Veteran, I want a way to differentiate my Questionnaire List from my appointment list. ## Related Documentation - [MVP: Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) ## Description A wireframes set for will be delivered showing a link to VAOS on the questionnaire list with the technical specifications needed for engineering to implement said feature. ## Tasks - [x] Work with Peggy Gannon on wording - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product/team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Published mockup link exists and it is added/updated within the product feature outline - [ ] Feedback from content is incorporated into the mockup",1.0,"[UI] Adding Link to VAOS on Questionnaire List - ## User Story - As a Veteran, I want a way to differentiate my Questionnaire List from my appointment list. ## Related Documentation - [MVP: Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) ## Description A wireframes set for will be delivered showing a link to VAOS on the questionnaire list with the technical specifications needed for engineering to implement said feature. ## Tasks - [x] Work with Peggy Gannon on wording - [ ] Finalize detailed mockup and callouts of [feature name](link to prototype) ## Acceptance Criteria - [ ] UI review meeting with product/team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Published mockup link exists and it is added/updated within the product feature outline - [ ] Feedback from content is incorporated into the mockup",1, adding link to vaos on questionnaire list user story as a veteran i want a way to differentiate my questionnaire list from my appointment list related documentation description a wireframes set for will be delivered showing a link to vaos on the questionnaire list with the technical specifications needed for engineering to implement said feature tasks work with peggy gannon on wording finalize detailed mockup and callouts of link to prototype acceptance criteria ui review meeting with product team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above published mockup link exists and it is added updated within the product feature outline feedback from content is incorporated into the mockup,1 105374,13182146861.0,IssuesEvent,2020-08-12 15:20:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Content Revisions for CH36's Prototype,design vsa vsa-ebenefits,"## Goal Given feedback, we need to implement the latest content changes for CH31 so the feature is copy complete and ready to go. ## Tasks - [ ] Take the recommendations and update the features' prototypes ## Acceptance Criteria - [ ] The prototypes are updated with the latest recommendations",1.0,"Content Revisions for CH36's Prototype - ## Goal Given feedback, we need to implement the latest content changes for CH31 so the feature is copy complete and ready to go. ## Tasks - [ ] Take the recommendations and update the features' prototypes ## Acceptance Criteria - [ ] The prototypes are updated with the latest recommendations",1,content revisions for s prototype goal given feedback we need to implement the latest content changes for so the feature is copy complete and ready to go tasks take the recommendations and update the features prototypes acceptance criteria the prototypes are updated with the latest recommendations,1 175184,27805988542.0,IssuesEvent,2023-03-17 19:58:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Update comms strategy,content design login.gov-adoption,"### Description In January 2023 the Login.gov adoption team devised an initial communications plan and strategy for the removal of DS Logon & My Health_e_ Vet as a valid sign in credentials, migrating users to Login.gov and communicating the change internally/externally. This document needs to be updated to reflect changes in product timelines, progress that has already been made, and findings thus far that may impact communications strategy. In addition, we will engage in exploration of additional design layouts to share this document. ### Acceptance criteria - [x] Updated Migration Content Strategy is in Mural ### Tasks - [x] @CarlDickerson update timelines based on changes/updates in product roadmap and timing. - [x] @CarlDickerson partner with design to explore additional options for displaying comms plan",1.0,"Update comms strategy - ### Description In January 2023 the Login.gov adoption team devised an initial communications plan and strategy for the removal of DS Logon & My Health_e_ Vet as a valid sign in credentials, migrating users to Login.gov and communicating the change internally/externally. This document needs to be updated to reflect changes in product timelines, progress that has already been made, and findings thus far that may impact communications strategy. In addition, we will engage in exploration of additional design layouts to share this document. ### Acceptance criteria - [x] Updated Migration Content Strategy is in Mural ### Tasks - [x] @CarlDickerson update timelines based on changes/updates in product roadmap and timing. - [x] @CarlDickerson partner with design to explore additional options for displaying comms plan",1,update comms strategy description in january the login gov adoption team devised an initial communications plan and strategy for the removal of ds logon my health e vet as a valid sign in credentials migrating users to login gov and communicating the change internally externally this document needs to be updated to reflect changes in product timelines progress that has already been made and findings thus far that may impact communications strategy in addition we will engage in exploration of additional design layouts to share this document acceptance criteria updated migration content strategy is in mural tasks carldickerson update timelines based on changes updates in product roadmap and timing carldickerson partner with design to explore additional options for displaying comms plan,1 94152,11852562877.0,IssuesEvent,2020-03-24 20:11:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Develop stylesheet for printing out form content,design new-unplanned ux vsa-caregiver,"## User Story Given that a user would like to print out a copy of the information they submitted for the 10-10CG online application I'd like to develop a stylesheet for printing the form So that the information can be printed in a user-friendly, easily readable way.",1.0,"Develop stylesheet for printing out form content - ## User Story Given that a user would like to print out a copy of the information they submitted for the 10-10CG online application I'd like to develop a stylesheet for printing the form So that the information can be printed in a user-friendly, easily readable way.",1,develop stylesheet for printing out form content user story given that a user would like to print out a copy of the information they submitted for the online application i d like to develop a stylesheet for printing the form so that the information can be printed in a user friendly easily readable way ,1 159407,24988652186.0,IssuesEvent,2022-11-02 16:52:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Determine potential intake features (landing page, submission process) where teams can request our assistance for mapping.",service-design,"## Issue Description Determine potential intake features (landing page, submission process) where teams can request our assistance for mapping. Possibilities: This could be a form for submission, a page that explains how to kickoff a request, Google Form, etc Here's an example from Platform Content: https://vfs.atlassian.net/wiki/spaces/CIT/pages/2262794259/Request+Platform+website+content+support Determine the necessary parameters/details a team would need to provide to make the request [Here's a research intake form example from Taylor](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2417524758/Research+Intake+Document+DRAFT) [Brainstorming document](https://vfs.atlassian.net/wiki/spaces/~622b5b63932f0f00716bdfd6/pages/2416869398/Mapping+intake+portal+brainstorming) [Mural for process brainstorming](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1666886472220/c097801ce764cd7e763461f50646f57f2e1c6f9d?sender=u4f7db1750f2355f805e60296) [Brainstorming for features per phase of intake](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1666717963461/d232a78b0b1304f152652d821f54172a76853172?sender=u4f7db1750f2355f805e60296) ## Tasks - [x] Brainstorm potential intake portals and considerations - [x] Draft the necessary parameters/details a team would need to provide to make the request ## Acceptance Criteria - [x] Landing page(s) decided upon - - [x] VA Platform/Support/Submit a mapping request - - [x] SDT Confluence space - [x] Intake tool/process decided upon ",1.0,"Determine potential intake features (landing page, submission process) where teams can request our assistance for mapping. - ## Issue Description Determine potential intake features (landing page, submission process) where teams can request our assistance for mapping. Possibilities: This could be a form for submission, a page that explains how to kickoff a request, Google Form, etc Here's an example from Platform Content: https://vfs.atlassian.net/wiki/spaces/CIT/pages/2262794259/Request+Platform+website+content+support Determine the necessary parameters/details a team would need to provide to make the request [Here's a research intake form example from Taylor](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2417524758/Research+Intake+Document+DRAFT) [Brainstorming document](https://vfs.atlassian.net/wiki/spaces/~622b5b63932f0f00716bdfd6/pages/2416869398/Mapping+intake+portal+brainstorming) [Mural for process brainstorming](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1666886472220/c097801ce764cd7e763461f50646f57f2e1c6f9d?sender=u4f7db1750f2355f805e60296) [Brainstorming for features per phase of intake](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1666717963461/d232a78b0b1304f152652d821f54172a76853172?sender=u4f7db1750f2355f805e60296) ## Tasks - [x] Brainstorm potential intake portals and considerations - [x] Draft the necessary parameters/details a team would need to provide to make the request ## Acceptance Criteria - [x] Landing page(s) decided upon - - [x] VA Platform/Support/Submit a mapping request - - [x] SDT Confluence space - [x] Intake tool/process decided upon ",1,determine potential intake features landing page submission process where teams can request our assistance for mapping issue description determine potential intake features landing page submission process where teams can request our assistance for mapping possibilities this could be a form for submission a page that explains how to kickoff a request google form etc here s an example from platform content determine the necessary parameters details a team would need to provide to make the request tasks brainstorm potential intake portals and considerations draft the necessary parameters details a team would need to provide to make the request acceptance criteria landing page s decided upon va platform support submit a mapping request sdt confluence space intake tool process decided upon ,1 122973,16413193774.0,IssuesEvent,2021-05-19 00:30:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Content Feedback - Staging review - VAOS for distribution,collab-cycle-feedback collaboration-cycle vaos-product-design vsp-product-support,"## VFS acceptance criteria - [x] Let VSP know when the **Must** feedback has been incorporated - [x] Leave any comments for feedback you decide _not_ to take - [ ] VFS team closes the ticket ## Thoughts/questions - ## Feedback - **Must** = the feedback must be applied - **Should** = the feedback is best practice - **Consider** = suggestions/enhancements ",1.0,"Content Feedback - Staging review - VAOS for distribution - ## VFS acceptance criteria - [x] Let VSP know when the **Must** feedback has been incorporated - [x] Leave any comments for feedback you decide _not_ to take - [ ] VFS team closes the ticket ## Thoughts/questions - ## Feedback - **Must** = the feedback must be applied - **Should** = the feedback is best practice - **Consider** = suggestions/enhancements ",1,content feedback staging review vaos for distribution vfs acceptance criteria let vsp know when the must feedback has been incorporated leave any comments for feedback you decide not to take vfs team closes the ticket thoughts questions feedback must the feedback must be applied should the feedback is best practice consider suggestions enhancements ,1 182238,30820854290.0,IssuesEvent,2023-08-01 16:13:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Feature] Community Care Consult - Veteran Preferences ,appointments-product-design appointments-pm appointments-feature,"**Objective:** Working on implementing the Community Care Consult in the appointments tool. ### Product Checklist
Toggle Product Checklist ## Product - [ ] Initiative Summary - [ ] Release Plan - [ ] Update product guide ### VSP Collaboration Cycle - [ ] Project Kickoff - [ ] Design Intent - [ ] Midpoint Review - [ ] Staging Review - [ ] Privacy & Security Review - [ ] Full Accessibility & 508 Audit
### UX Design Checklist
Toggle UX Design Checklist ## Design - [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to initiative brief - [ ] Add research links to initiative brief - [ ] Note any related icebox tickets - [ ] Review VAOS OKRs - [ ] Review OCTO goals - [ ] Document high-level research/design plans
### Engineering Checklist
Toggle Engineering Checklist ### Engineering - [ ] Review design specs - [ ] Add unit test coverage - [ ] Add E2E test coverage - [ ] Update Rspec - [ ] Update swagger - [ ] Document business logic changes
### QA Checklist
Toggle QA Checklist ### QA (for collab cycle) - ** please delete if not applicable ** - [ ] Regression test plan - [ ] Test plan - [ ] [Coverage for References - [ ] [Summary(Defects) - [ ] E2E tests - [ ] Code coverage ",1.0,"[Feature] Community Care Consult - Veteran Preferences - **Objective:** Working on implementing the Community Care Consult in the appointments tool. ### Product Checklist
Toggle Product Checklist ## Product - [ ] Initiative Summary - [ ] Release Plan - [ ] Update product guide ### VSP Collaboration Cycle - [ ] Project Kickoff - [ ] Design Intent - [ ] Midpoint Review - [ ] Staging Review - [ ] Privacy & Security Review - [ ] Full Accessibility & 508 Audit
### UX Design Checklist
Toggle UX Design Checklist ## Design - [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to initiative brief - [ ] Add research links to initiative brief - [ ] Note any related icebox tickets - [ ] Review VAOS OKRs - [ ] Review OCTO goals - [ ] Document high-level research/design plans
### Engineering Checklist
Toggle Engineering Checklist ### Engineering - [ ] Review design specs - [ ] Add unit test coverage - [ ] Add E2E test coverage - [ ] Update Rspec - [ ] Update swagger - [ ] Document business logic changes
### QA Checklist
Toggle QA Checklist ### QA (for collab cycle) - ** please delete if not applicable ** - [ ] Regression test plan - [ ] Test plan - [ ] [Coverage for References - [ ] [Summary(Defects) - [ ] E2E tests - [ ] Code coverage ",1, community care consult veteran preferences objective working on implementing the community care consult in the appointments tool product checklist toggle product checklist product initiative summary release plan update product guide vsp collaboration cycle project kickoff design intent midpoint review staging review privacy security review full accessibility audit ux design checklist toggle ux design checklist design review problem opportunity statement add questions and assumptions to initiative brief add research links to initiative brief note any related icebox tickets review vaos okrs review octo goals document high level research design plans engineering checklist toggle engineering checklist engineering review design specs add unit test coverage add test coverage update rspec update swagger document business logic changes qa checklist toggle qa checklist qa for collab cycle please delete if not applicable regression test plan test plan coverage for references summary defects tests code coverage ,1 113269,14404489065.0,IssuesEvent,2020-12-03 17:21:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Move MegaMenu out of the component library into Vets website,design-system-team,"## Issue Description Move MegaMenu out of the component library into Vets website --- ## Tasks - [ ] Remove MegaMenu out of the component library - [ ] Move MegaMenu to Vets website ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ",1.0,"Move MegaMenu out of the component library into Vets website - ## Issue Description Move MegaMenu out of the component library into Vets website --- ## Tasks - [ ] Remove MegaMenu out of the component library - [ ] Move MegaMenu to Vets website ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ",1,move megamenu out of the component library into vets website issue description move megamenu out of the component library into vets website tasks remove megamenu out of the component library move megamenu to vets website acceptance criteria what will be created or happen as a result of this story ,1 173121,27388750546.0,IssuesEvent,2023-02-28 14:59:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,MyHealth - Pharmacy - Onboard new MHV team for Pharmacy,frontend backend design research product onboarding my-health my-health-PRESCRIPTIONS,"## Issue Description The team that will be building Pharmacy on VA.gov has not worked on VA.gov before and will need some assistance with getting onboarded and acclimated to the environment. --- ## Tasks - [ ] Introduce the team to the [Onboarding Documentation in GitHub](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/digital-health-modernization/mhv-to-va.gov/team-onboarding/product-team-onboarding.md) ## Acceptance Criteria - [ ] The new team will have access to a quick guide that hits the highlights of how to get onboarded. - [ ] The new team will have information on where to go if they have questions beyond basic onboarding. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"MyHealth - Pharmacy - Onboard new MHV team for Pharmacy - ## Issue Description The team that will be building Pharmacy on VA.gov has not worked on VA.gov before and will need some assistance with getting onboarded and acclimated to the environment. --- ## Tasks - [ ] Introduce the team to the [Onboarding Documentation in GitHub](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/digital-health-modernization/mhv-to-va.gov/team-onboarding/product-team-onboarding.md) ## Acceptance Criteria - [ ] The new team will have access to a quick guide that hits the highlights of how to get onboarded. - [ ] The new team will have information on where to go if they have questions beyond basic onboarding. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,myhealth pharmacy onboard new mhv team for pharmacy issue description the team that will be building pharmacy on va gov has not worked on va gov before and will need some assistance with getting onboarded and acclimated to the environment tasks introduce the team to the acceptance criteria the new team will have access to a quick guide that hits the highlights of how to get onboarded the new team will have information on where to go if they have questions beyond basic onboarding how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 167586,26518057060.0,IssuesEvent,2023-01-18 22:45:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Desk Research] Supp Claims PACT Act,design benefits-team-1 squad-2,"Context and Conclusions Please begin to conduct desk research on the existing Notice of Disagreement. Resources to check out https://www.reddit.com/r/VeteransAffairs/ https://www.reddit.com/r/Veterans/ https://www.va.gov/resources/the-pact-act-and-your-va-benefits/ About Supplemental Claims https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/decision-reviews/Supplemental-Claims About PACT Act https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/disability/abd-vro/2022-06-PACT-Act-presumptive-veterans/PACT-Act-research-report.md and search for ""Pact Act"" ""Supplemental Claims"" and reach through their experiences when you have a good understanding of the policy and how it will impact Supplemental Claims. Document your findings here https://docs.google.com/document/d/17OBZtP2uX1XxIYwEBMlhztWrcc6mgf9rnF486ZF06NU/edit Reach out to Eileen with questions.",1.0,"[Desk Research] Supp Claims PACT Act - Context and Conclusions Please begin to conduct desk research on the existing Notice of Disagreement. Resources to check out https://www.reddit.com/r/VeteransAffairs/ https://www.reddit.com/r/Veterans/ https://www.va.gov/resources/the-pact-act-and-your-va-benefits/ About Supplemental Claims https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/decision-reviews/Supplemental-Claims About PACT Act https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/disability/abd-vro/2022-06-PACT-Act-presumptive-veterans/PACT-Act-research-report.md and search for ""Pact Act"" ""Supplemental Claims"" and reach through their experiences when you have a good understanding of the policy and how it will impact Supplemental Claims. Document your findings here https://docs.google.com/document/d/17OBZtP2uX1XxIYwEBMlhztWrcc6mgf9rnF486ZF06NU/edit Reach out to Eileen with questions.",1, supp claims pact act context and conclusions please begin to conduct desk research on the existing notice of disagreement resources to check out about supplemental claims about pact act and search for pact act supplemental claims and reach through their experiences when you have a good understanding of the policy and how it will impact supplemental claims document your findings here reach out to eileen with questions ,1 177520,28503506632.0,IssuesEvent,2023-04-18 19:19:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[SPIKE] [Design] Best method to document specifications to engineers,design ux HCE-Checkin,"## Time Boxed 1 1/2 hours ## Description Determine the best method to document design, functional or other specifications on specific symbols and page components to engineers, designers, product owners and other stakeholders. For example: * Heading classes to be used. E.g., when the markup needs to be a different heading than the actual heading design. * Use of mobile headings vs. desktop headings. * Notifications do not stack. But, on page refresh, check to see if there's an appointment in the check in window. ## Tasks - [x] Meet with Christina and Ben to knowledge share about this conversation - [x] [Review annotations library from DST](https://dsva.slack.com/archives/C04J6H2LYUU/p1680207421757729) - [x] Ask how engineers use and/or might use sketch or abstract to inspect components - [x] Determine solution - [x] Get approval or feedback from engineers ## AC - [ ] Solution determined ",1.0,"[SPIKE] [Design] Best method to document specifications to engineers - ## Time Boxed 1 1/2 hours ## Description Determine the best method to document design, functional or other specifications on specific symbols and page components to engineers, designers, product owners and other stakeholders. For example: * Heading classes to be used. E.g., when the markup needs to be a different heading than the actual heading design. * Use of mobile headings vs. desktop headings. * Notifications do not stack. But, on page refresh, check to see if there's an appointment in the check in window. ## Tasks - [x] Meet with Christina and Ben to knowledge share about this conversation - [x] [Review annotations library from DST](https://dsva.slack.com/archives/C04J6H2LYUU/p1680207421757729) - [x] Ask how engineers use and/or might use sketch or abstract to inspect components - [x] Determine solution - [x] Get approval or feedback from engineers ## AC - [ ] Solution determined ",1, best method to document specifications to engineers time boxed hours description determine the best method to document design functional or other specifications on specific symbols and page components to engineers designers product owners and other stakeholders for example heading classes to be used e g when the markup needs to be a different heading than the actual heading design use of mobile headings vs desktop headings notifications do not stack but on page refresh check to see if there s an appointment in the check in window tasks meet with christina and ben to knowledge share about this conversation ask how engineers use and or might use sketch or abstract to inspect components determine solution get approval or feedback from engineers ac solution determined ,1 103044,12838109251.0,IssuesEvent,2020-07-07 16:52:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Development/Design] 526: Wizard Updates,design discovery frontend vsa-benefits,"## Issue Description The public websites team is working on a new wizard for 526 and decision reviews. This story is to capture the time having the initial meetings and discussions leading up to a solution. ## Acceptance Criteria - [ ] New work captured in stories --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Development/Design] 526: Wizard Updates - ## Issue Description The public websites team is working on a new wizard for 526 and decision reviews. This story is to capture the time having the initial meetings and discussions leading up to a solution. ## Acceptance Criteria - [ ] New work captured in stories --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, wizard updates issue description the public websites team is working on a new wizard for and decision reviews this story is to capture the time having the initial meetings and discussions leading up to a solution acceptance criteria new work captured in stories how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 126621,17090548201.0,IssuesEvent,2021-07-08 16:50:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design] Profile - Improve UX for ""remove"" [contact information] button",508-issue-cognition 508/Accessibility design planned-work profile ux vsa-authenticated-exp,"## Background As identified in #19562 and as discussed in the [comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/22592#issuecomment-822782218) of #22592, we need a better solution for the `remove` button, which currently looks like a link. ![remove-button](https://user-images.githubusercontent.com/14154792/114609901-510b5e80-9c6d-11eb-9c77-b43f6dc03673.png ) ## Tasks - [x] Mock-up solutions - [x] review with team - [ ] document solution for FE (including updates to notification settings documentation if needed) - [ ] PM to create implementation ticket(s) for proposed solution",1.0,"[Design] Profile - Improve UX for ""remove"" [contact information] button - ## Background As identified in #19562 and as discussed in the [comments](https://github.com/department-of-veterans-affairs/va.gov-team/issues/22592#issuecomment-822782218) of #22592, we need a better solution for the `remove` button, which currently looks like a link. ![remove-button](https://user-images.githubusercontent.com/14154792/114609901-510b5e80-9c6d-11eb-9c77-b43f6dc03673.png ) ## Tasks - [x] Mock-up solutions - [x] review with team - [ ] document solution for FE (including updates to notification settings documentation if needed) - [ ] PM to create implementation ticket(s) for proposed solution",1, profile improve ux for remove button background as identified in and as discussed in the of we need a better solution for the remove button which currently looks like a link tasks mock up solutions review with team document solution for fe including updates to notification settings documentation if needed pm to create implementation ticket s for proposed solution,1 180081,30385694856.0,IssuesEvent,2023-07-13 00:20:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Feature] Open slot management ,appointments-product-design appointments-pm appointments-feature,"**Objective:** The team will work on the open slot management initiative. ### Product Checklist
Toggle Product Checklist ## Product - [ ] Initiative Summary - [ ] Release Plan - [ ] Update product guide ### VSP Collaboration Cycle - [ ] Project Kickoff - [ ] Design Intent - [ ] Midpoint Review - [ ] Staging Review - [ ] Privacy & Security Review - [ ] Full Accessibility & 508 Audit
### UX Design Checklist
Toggle UX Design Checklist ## Design - [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to initiative brief - [ ] Add research links to initiative brief - [ ] Note any related icebox tickets - [ ] Review VAOS OKRs - [ ] Review OCTO goals - [ ] Document high-level research/design plans
### Engineering Checklist
Toggle Engineering Checklist ### Engineering - [ ] Review design specs - [ ] Add unit test coverage - [ ] Add E2E test coverage - [ ] Update Rspec - [ ] Update swagger - [ ] Document business logic changes
### QA Checklist
Toggle QA Checklist ### QA (for collab cycle) - ** please delete if not applicable ** - [ ] Regression test plan - [ ] Test plan - [ ] [Coverage for References - [ ] [Summary(Defects) - [ ] E2E tests - [ ] Code coverage ",1.0,"[Feature] Open slot management - **Objective:** The team will work on the open slot management initiative. ### Product Checklist
Toggle Product Checklist ## Product - [ ] Initiative Summary - [ ] Release Plan - [ ] Update product guide ### VSP Collaboration Cycle - [ ] Project Kickoff - [ ] Design Intent - [ ] Midpoint Review - [ ] Staging Review - [ ] Privacy & Security Review - [ ] Full Accessibility & 508 Audit
### UX Design Checklist
Toggle UX Design Checklist ## Design - [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to initiative brief - [ ] Add research links to initiative brief - [ ] Note any related icebox tickets - [ ] Review VAOS OKRs - [ ] Review OCTO goals - [ ] Document high-level research/design plans
### Engineering Checklist
Toggle Engineering Checklist ### Engineering - [ ] Review design specs - [ ] Add unit test coverage - [ ] Add E2E test coverage - [ ] Update Rspec - [ ] Update swagger - [ ] Document business logic changes
### QA Checklist
Toggle QA Checklist ### QA (for collab cycle) - ** please delete if not applicable ** - [ ] Regression test plan - [ ] Test plan - [ ] [Coverage for References - [ ] [Summary(Defects) - [ ] E2E tests - [ ] Code coverage ",1, open slot management objective the team will work on the open slot management initiative product checklist toggle product checklist product initiative summary release plan update product guide vsp collaboration cycle project kickoff design intent midpoint review staging review privacy security review full accessibility audit ux design checklist toggle ux design checklist design review problem opportunity statement add questions and assumptions to initiative brief add research links to initiative brief note any related icebox tickets review vaos okrs review octo goals document high level research design plans engineering checklist toggle engineering checklist engineering review design specs add unit test coverage add test coverage update rspec update swagger document business logic changes qa checklist toggle qa checklist qa for collab cycle please delete if not applicable regression test plan test plan coverage for references summary defects tests code coverage ,1 85071,10585569852.0,IssuesEvent,2019-10-08 17:48:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Clear stale results after a rating value is added, changed, or removed",design frontend vsa-global-ux,"After a user submits their rating values into the calculator, the combined disability rating becomes visible in the bottom results panel, which currently only refreshes when the user again submits the form. This is a problem, because if the user's rating values are modified (by editing a rating value, adding or removing one), the results panel will still only reflect the combined disability rating from the last submit, which means this value is now stale and could be misleading to users. We should explore - 1. Replacing the combined disability rating with dashes if the user submits the form then changes their rating values. 2. Automatically hiding the results panel if the user submits the form then changes their rating values. ",1.0,"Clear stale results after a rating value is added, changed, or removed - After a user submits their rating values into the calculator, the combined disability rating becomes visible in the bottom results panel, which currently only refreshes when the user again submits the form. This is a problem, because if the user's rating values are modified (by editing a rating value, adding or removing one), the results panel will still only reflect the combined disability rating from the last submit, which means this value is now stale and could be misleading to users. We should explore - 1. Replacing the combined disability rating with dashes if the user submits the form then changes their rating values. 2. Automatically hiding the results panel if the user submits the form then changes their rating values. ",1,clear stale results after a rating value is added changed or removed after a user submits their rating values into the calculator the combined disability rating becomes visible in the bottom results panel which currently only refreshes when the user again submits the form this is a problem because if the user s rating values are modified by editing a rating value adding or removing one the results panel will still only reflect the combined disability rating from the last submit which means this value is now stale and could be misleading to users we should explore replacing the combined disability rating with dashes if the user submits the form then changes their rating values automatically hiding the results panel if the user submits the form then changes their rating values ,1 100944,12602531100.0,IssuesEvent,2020-06-11 11:54:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Development/Design] BDD: Add Wording for Exam Availability,design development frontend vsa-benefits,"## User Story or Problem Statement Barry Cooper has identified a requirement that we provide messaging to the veteran to remind them they need to be available for exams once they submit their application. We had asked Barry ""how many"" and he said it depends on how many things you are filing for since it requires different doctors/exams for most. Therefore, the wording should be pretty generic. Question for the design - should it be included at the start of the application somewhere as well as at the end when the submission occurs? ## Acceptance Criteria - [ ] We have the messaging in the appropriate places on the BDD flow ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Development/Design] BDD: Add Wording for Exam Availability - ## User Story or Problem Statement Barry Cooper has identified a requirement that we provide messaging to the veteran to remind them they need to be available for exams once they submit their application. We had asked Barry ""how many"" and he said it depends on how many things you are filing for since it requires different doctors/exams for most. Therefore, the wording should be pretty generic. Question for the design - should it be included at the start of the application somewhere as well as at the end when the submission occurs? ## Acceptance Criteria - [ ] We have the messaging in the appropriate places on the BDD flow ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, bdd add wording for exam availability user story or problem statement barry cooper has identified a requirement that we provide messaging to the veteran to remind them they need to be available for exams once they submit their application we had asked barry how many and he said it depends on how many things you are filing for since it requires different doctors exams for most therefore the wording should be pretty generic question for the design should it be included at the start of the application somewhere as well as at the end when the submission occurs acceptance criteria we have the messaging in the appropriate places on the bdd flow how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 182235,30820565147.0,IssuesEvent,2023-08-01 16:02:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Feature] Deep linking into Appointment Details page,appointments-product-design appointments-pm appointments-feature,"**Objective:** Work will focus on deep linking into the Appointment Details page ### Product Checklist
Toggle Product Checklist ## Product - [ ] Initiative Summary - [ ] Release Plan - [ ] Update product guide ### VSP Collaboration Cycle - [ ] Project Kickoff - [ ] Design Intent - [ ] Midpoint Review - [ ] Staging Review - [ ] Privacy & Security Review - [ ] Full Accessibility & 508 Audit
### UX Design Checklist
Toggle UX Design Checklist ## Design - [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to initiative brief - [ ] Add research links to initiative brief - [ ] Note any related icebox tickets - [ ] Review VAOS OKRs - [ ] Review OCTO goals - [ ] Document high-level research/design plans
### Engineering Checklist
Toggle Engineering Checklist ### Engineering - [ ] Review design specs - [ ] Add unit test coverage - [ ] Add E2E test coverage - [ ] Update Rspec - [ ] Update swagger - [ ] Document business logic changes
### QA Checklist
Toggle QA Checklist ### QA (for collab cycle) - ** please delete if not applicable ** - [ ] Regression test plan - [ ] Test plan - [ ] [Coverage for References - [ ] [Summary(Defects) - [ ] E2E tests - [ ] Code coverage ",1.0,"[Feature] Deep linking into Appointment Details page - **Objective:** Work will focus on deep linking into the Appointment Details page ### Product Checklist
Toggle Product Checklist ## Product - [ ] Initiative Summary - [ ] Release Plan - [ ] Update product guide ### VSP Collaboration Cycle - [ ] Project Kickoff - [ ] Design Intent - [ ] Midpoint Review - [ ] Staging Review - [ ] Privacy & Security Review - [ ] Full Accessibility & 508 Audit
### UX Design Checklist
Toggle UX Design Checklist ## Design - [ ] Review problem/opportunity statement - [ ] Add questions and assumptions to initiative brief - [ ] Add research links to initiative brief - [ ] Note any related icebox tickets - [ ] Review VAOS OKRs - [ ] Review OCTO goals - [ ] Document high-level research/design plans
### Engineering Checklist
Toggle Engineering Checklist ### Engineering - [ ] Review design specs - [ ] Add unit test coverage - [ ] Add E2E test coverage - [ ] Update Rspec - [ ] Update swagger - [ ] Document business logic changes
### QA Checklist
Toggle QA Checklist ### QA (for collab cycle) - ** please delete if not applicable ** - [ ] Regression test plan - [ ] Test plan - [ ] [Coverage for References - [ ] [Summary(Defects) - [ ] E2E tests - [ ] Code coverage ",1, deep linking into appointment details page objective work will focus on deep linking into the appointment details page product checklist toggle product checklist product initiative summary release plan update product guide vsp collaboration cycle project kickoff design intent midpoint review staging review privacy security review full accessibility audit ux design checklist toggle ux design checklist design review problem opportunity statement add questions and assumptions to initiative brief add research links to initiative brief note any related icebox tickets review vaos okrs review octo goals document high level research design plans engineering checklist toggle engineering checklist engineering review design specs add unit test coverage add test coverage update rspec update swagger document business logic changes qa checklist toggle qa checklist qa for collab cycle please delete if not applicable regression test plan test plan coverage for references summary defects tests code coverage ,1 131516,18295259375.0,IssuesEvent,2021-10-05 19:49:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Create a visual of Search Design Pattern,design vsa planned-work vsa-search-discovery,"## Description Establish a visual to accompany the description of search design pattern ([example](https://design.va.gov/experimental-design/copy-deep-link)) to be added to the experimental design system. ## Acceptance Criteria - [ ] Visual has been created to share with Natalie",1.0,"Create a visual of Search Design Pattern - ## Description Establish a visual to accompany the description of search design pattern ([example](https://design.va.gov/experimental-design/copy-deep-link)) to be added to the experimental design system. ## Acceptance Criteria - [ ] Visual has been created to share with Natalie",1,create a visual of search design pattern description establish a visual to accompany the description of search design pattern to be added to the experimental design system acceptance criteria visual has been created to share with natalie,1 145244,22630626340.0,IssuesEvent,2022-06-30 14:23:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,CST design iterations,design benefits-team-1 squad-1,"## Value Statement **_As a_ designer** **_I want to_ begin CST design iterations** **_So that_ I can improve the CST user experience through iteration and refinement** --- ## Background Context - Areas of Opportunity for CST improvements identified from research: https://docs.google.com/document/d/1jgQt3IbSx60VhkeFwcPqfO0AteuUKB2r-5PdcWGTLGw/edit#heading=h.kj1vat5w5hf6 ## Open questions - What's the delta between claim status data we have access to and what's currently shown in the CST UI? - Will we have access to Vets for usability research? - How much leeway will we have for general UI improvements that are not necessarily tied to a metric? - How does this impact eBenefits — or vice versa — if at all? ##Acceptance Criteria - Summarize context on where the work landed with the last team - Assessment of opportunities - Validate opportunity assessment with Matt",1.0,"CST design iterations - ## Value Statement **_As a_ designer** **_I want to_ begin CST design iterations** **_So that_ I can improve the CST user experience through iteration and refinement** --- ## Background Context - Areas of Opportunity for CST improvements identified from research: https://docs.google.com/document/d/1jgQt3IbSx60VhkeFwcPqfO0AteuUKB2r-5PdcWGTLGw/edit#heading=h.kj1vat5w5hf6 ## Open questions - What's the delta between claim status data we have access to and what's currently shown in the CST UI? - Will we have access to Vets for usability research? - How much leeway will we have for general UI improvements that are not necessarily tied to a metric? - How does this impact eBenefits — or vice versa — if at all? ##Acceptance Criteria - Summarize context on where the work landed with the last team - Assessment of opportunities - Validate opportunity assessment with Matt",1,cst design iterations value statement as a designer i want to begin cst design iterations so that i can improve the cst user experience through iteration and refinement background context areas of opportunity for cst improvements identified from research open questions what s the delta between claim status data we have access to and what s currently shown in the cst ui will we have access to vets for usability research how much leeway will we have for general ui improvements that are not necessarily tied to a metric how does this impact ebenefits — or vice versa — if at all acceptance criteria summarize context on where the work landed with the last team assessment of opportunities validate opportunity assessment with matt,1 85943,10697922010.0,IssuesEvent,2019-10-23 17:34:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Remove '(Optional)' from form fields,design vsa-benefits vsa-decision-reviews,"## User Story or Problem Statement In order to create consistency across the forms on VA.gov, all optional form fields should no longer say '(optional)'. ## Goal _Globally remove the '(optional)' part of labels on VA.gov forms_ ## Acceptance Criteria - _As the front end engineer, I need to globally remove '(optional)' from VA.gov forms_ ## Definition of Done - [ ] Identify labels that contain '(optional)' field - [ ] Globally remove '(optional)' tag from forms - [ ] _*This relates to ticket #1917 *Check the box below when this has been completed and comment ""done""._ ## Screen Shots",1.0,"Remove '(Optional)' from form fields - ## User Story or Problem Statement In order to create consistency across the forms on VA.gov, all optional form fields should no longer say '(optional)'. ## Goal _Globally remove the '(optional)' part of labels on VA.gov forms_ ## Acceptance Criteria - _As the front end engineer, I need to globally remove '(optional)' from VA.gov forms_ ## Definition of Done - [ ] Identify labels that contain '(optional)' field - [ ] Globally remove '(optional)' tag from forms - [ ] _*This relates to ticket #1917 *Check the box below when this has been completed and comment ""done""._ ## Screen Shots",1,remove optional from form fields user story or problem statement in order to create consistency across the forms on va gov all optional form fields should no longer say optional goal globally remove the optional part of labels on va gov forms acceptance criteria as the front end engineer i need to globally remove optional from va gov forms definition of done identify labels that contain optional field globally remove optional tag from forms this relates to ticket check the box below when this has been completed and comment done screen shots,1 116656,14987830093.0,IssuesEvent,2021-01-28 23:46:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Error | File could not be uploaded,Blocked by Design DF blocked frontend mobile API va-mobile-app,"## User story As a user, I want to know when my photos/files could not be uploaded to VA due to an upstream error ## Acceptance Criteria 1. TBD - scenarios that would trigger this? ## Related tickets Successful upload: ",1.0,"Error | File could not be uploaded - ## User story As a user, I want to know when my photos/files could not be uploaded to VA due to an upstream error ## Acceptance Criteria 1. TBD - scenarios that would trigger this? ## Related tickets Successful upload: ",1,error file could not be uploaded user story as a user i want to know when my photos files could not be uploaded to va due to an upstream error acceptance criteria tbd scenarios that would trigger this related tickets successful upload ,1 149504,23487818757.0,IssuesEvent,2022-08-17 15:45:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design]Payments Info V2 : Design Updates from Research Feedback,design vsa-authenticated-exp planned-work my-va-payment-info,"## Background Based on the user feedback we received during usability testing, we want to revisit the design of the Payments and Debts section on My VA. We heard that most users preferred the different types of debts i.e. ""copays"" and ""Debts"" broken out into separate sections. We also heard that the red font for debts was alarming and triggering for some users. Finally, we heard that the ""updated"" date was unnecessary or unhelpful for most users. ## Tasks - [x] Develop designs for various scenarios on desktop and mobile. i.e ""no copays"" or ""no debts"" on these platforms - [x] Remove the red and green colors from payments and debts amounts - [x] Determine if we should eliminate the updated dates and replace them with more useful information - [x] Design should include ""copays"" and ""debts"" broken out as separate amounts - [x] Mock up the benefit payments design for a user who receives paper checks - [x] Review updates with team ## Acceptance Criteria - [x] Design updates for Payments and Debts section are complete ",1.0,"[Design]Payments Info V2 : Design Updates from Research Feedback - ## Background Based on the user feedback we received during usability testing, we want to revisit the design of the Payments and Debts section on My VA. We heard that most users preferred the different types of debts i.e. ""copays"" and ""Debts"" broken out into separate sections. We also heard that the red font for debts was alarming and triggering for some users. Finally, we heard that the ""updated"" date was unnecessary or unhelpful for most users. ## Tasks - [x] Develop designs for various scenarios on desktop and mobile. i.e ""no copays"" or ""no debts"" on these platforms - [x] Remove the red and green colors from payments and debts amounts - [x] Determine if we should eliminate the updated dates and replace them with more useful information - [x] Design should include ""copays"" and ""debts"" broken out as separate amounts - [x] Mock up the benefit payments design for a user who receives paper checks - [x] Review updates with team ## Acceptance Criteria - [x] Design updates for Payments and Debts section are complete ",1, payments info design updates from research feedback background based on the user feedback we received during usability testing we want to revisit the design of the payments and debts section on my va we heard that most users preferred the different types of debts i e copays and debts broken out into separate sections we also heard that the red font for debts was alarming and triggering for some users finally we heard that the updated date was unnecessary or unhelpful for most users tasks develop designs for various scenarios on desktop and mobile i e no copays or no debts on these platforms remove the red and green colors from payments and debts amounts determine if we should eliminate the updated dates and replace them with more useful information design should include copays and debts broken out as separate amounts mock up the benefit payments design for a user who receives paper checks review updates with team acceptance criteria design updates for payments and debts section are complete ,1 229500,18357753498.0,IssuesEvent,2021-10-08 20:59:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Request to add new members to accessibility meetings,508/Accessibility vsp-product-support VSP-testing-team Internal request,"## Issue Description Noah will be taking over the weekly 508 discussion with Martha, and the Design System Council seat for Trevor. I'd like to request he be added to these calls, and Joe and Peter be added as optional attendees. --- ## Tasks - [ ] Create a new weekly meeting for informal discussion with Noah, and Peter and Joe optional - [x] Add Joe and Peter as optional to the monthly VA 508 call ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Request to add new members to accessibility meetings - ## Issue Description Noah will be taking over the weekly 508 discussion with Martha, and the Design System Council seat for Trevor. I'd like to request he be added to these calls, and Joe and Peter be added as optional attendees. --- ## Tasks - [ ] Create a new weekly meeting for informal discussion with Noah, and Peter and Joe optional - [x] Add Joe and Peter as optional to the monthly VA 508 call ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",0,request to add new members to accessibility meetings issue description noah will be taking over the weekly discussion with martha and the design system council seat for trevor i d like to request he be added to these calls and joe and peter be added as optional attendees tasks create a new weekly meeting for informal discussion with noah and peter and joe optional add joe and peter as optional to the monthly va call how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,0 150290,23640181654.0,IssuesEvent,2022-08-25 16:19:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] POSTER - Add Check-in Window Message to Poster,design HCE-Checkin,"## User Story As a Veteran, I would like to understand when I can check-in for my appointment so that I will not get frustrated if I try to do it too early. ## Tasks - [ ] Add verbiage to the poster to indicate when a Veteran can use their mobile device to check-in (i.e. no more than 30 minutes before and up to 15 minutes after the appointment) - 30 minutes is the priority - [ ] Test the poster with Veterans (Is this needed?) - [ ] Upload the poster to Git - [ ] Notify all facilities that are using the poster of the changes (see [Slack thread](https://dsva.slack.com/archives/C022AC2STBM/p1658412338303919)) ",1.0,"[Design] POSTER - Add Check-in Window Message to Poster - ## User Story As a Veteran, I would like to understand when I can check-in for my appointment so that I will not get frustrated if I try to do it too early. ## Tasks - [ ] Add verbiage to the poster to indicate when a Veteran can use their mobile device to check-in (i.e. no more than 30 minutes before and up to 15 minutes after the appointment) - 30 minutes is the priority - [ ] Test the poster with Veterans (Is this needed?) - [ ] Upload the poster to Git - [ ] Notify all facilities that are using the poster of the changes (see [Slack thread](https://dsva.slack.com/archives/C022AC2STBM/p1658412338303919)) ",1, poster add check in window message to poster user story as a veteran i would like to understand when i can check in for my appointment so that i will not get frustrated if i try to do it too early tasks add verbiage to the poster to indicate when a veteran can use their mobile device to check in i e no more than minutes before and up to minutes after the appointment minutes is the priority test the poster with veterans is this needed upload the poster to git notify all facilities that are using the poster of the changes see ,1 161858,25411605972.0,IssuesEvent,2022-11-22 19:30:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design | UI Alerts for Editing Contact Info | Update Design Files,design authenticated-experience profile contact-information sprint-planning alert updates,"## Background Per comment in ticket #31410 we are updating the content for one of the alerts on the contact page to this: - [Desktop](https://www.sketch.com/s/59857eb5-d9f9-4145-99d3-d9a1de2d0655/v/waVZjj/a/OmlnPxp) - [Mobile](https://www.sketch.com/s/59857eb5-d9f9-4145-99d3-d9a1de2d0655/v/dMz8DZ/a/pamAp4p/r/bWjPW0) ## Tasks - [x] Update sketch files - [x] Update use cases - [x] Update user flows - [x] Update CC guide ## Acceptance Criteria - [x] Above tasks are complete - [ ] Notify PM to send updated CC guide to poc",1.0,"Design | UI Alerts for Editing Contact Info | Update Design Files - ## Background Per comment in ticket #31410 we are updating the content for one of the alerts on the contact page to this: - [Desktop](https://www.sketch.com/s/59857eb5-d9f9-4145-99d3-d9a1de2d0655/v/waVZjj/a/OmlnPxp) - [Mobile](https://www.sketch.com/s/59857eb5-d9f9-4145-99d3-d9a1de2d0655/v/dMz8DZ/a/pamAp4p/r/bWjPW0) ## Tasks - [x] Update sketch files - [x] Update use cases - [x] Update user flows - [x] Update CC guide ## Acceptance Criteria - [x] Above tasks are complete - [ ] Notify PM to send updated CC guide to poc",1,design ui alerts for editing contact info update design files background per comment in ticket we are updating the content for one of the alerts on the contact page to this tasks update sketch files update use cases update user flows update cc guide acceptance criteria above tasks are complete notify pm to send updated cc guide to poc,1 181678,30724060766.0,IssuesEvent,2023-07-27 18:09:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Copy of List Loop Pattern Accessibility Fix,bug accessibility LGY needs-design list-loop Umbrella NDBX-Bug,"### Info: _Refer to department-of-veterans-affairs/va.gov-team#23562_ ### Description: [developers] ensure that the list loop pattern for previous military history accommodates unique accessible labels for past service fields. For example, if there are multiple ""branch of service"" dropdowns each of them must have a unique accessible label so screen reader users can easily tell them apart. ### Acceptance Criteria: - [ ] Update aria labels so that each Period of Service and it's related inputs are distinguishable to screen readers",1.0,"Copy of List Loop Pattern Accessibility Fix - ### Info: _Refer to department-of-veterans-affairs/va.gov-team#23562_ ### Description: [developers] ensure that the list loop pattern for previous military history accommodates unique accessible labels for past service fields. For example, if there are multiple ""branch of service"" dropdowns each of them must have a unique accessible label so screen reader users can easily tell them apart. ### Acceptance Criteria: - [ ] Update aria labels so that each Period of Service and it's related inputs are distinguishable to screen readers",1,copy of list loop pattern accessibility fix info refer to department of veterans affairs va gov team description ensure that the list loop pattern for previous military history accommodates unique accessible labels for past service fields for example if there are multiple branch of service dropdowns each of them must have a unique accessible label so screen reader users can easily tell them apart acceptance criteria update aria labels so that each period of service and it s related inputs are distinguishable to screen readers,1 91302,11492485357.0,IssuesEvent,2020-02-11 21:05:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Service user flow v1,design vsa vsa-facilities,"## User Story: As a Veteran, I want to be able to search by service so that I can find a facility near me offering the service I seek. ## Tasks - [ ] Create service user flow v1 - [ ] Consider which information is found on cards vs facility detail page ## Acceptance Criteria: [ ] Veteran can use service-first user flow to search for high priority services such as urgent care, emergency care, pharmacy, gastroenterology, diagnostic imaging and PTSD/SUD. [ ] Search results will be organized around service offerings, rather than facility types. [ ] Cards displayed in search results will contain information about the services offered at the location. [ ] Design includes ""escape hatch"" triggers for certain services, e.g. ""Emergency"" (If this is an emergency, Go to your nearest ER) or ""Mental Health"" (If you or someone you know is in crisis...) [ ] Design includes method for preparing the Veteran for the visit, agnostically. The specifics may be based on facility type (such as referral information or Urgent care eligibility link) ## Configuration - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (e.g. `vsa-authenticated-exp`, `vsa-caregiver`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Service user flow v1 - ## User Story: As a Veteran, I want to be able to search by service so that I can find a facility near me offering the service I seek. ## Tasks - [ ] Create service user flow v1 - [ ] Consider which information is found on cards vs facility detail page ## Acceptance Criteria: [ ] Veteran can use service-first user flow to search for high priority services such as urgent care, emergency care, pharmacy, gastroenterology, diagnostic imaging and PTSD/SUD. [ ] Search results will be organized around service offerings, rather than facility types. [ ] Cards displayed in search results will contain information about the services offered at the location. [ ] Design includes ""escape hatch"" triggers for certain services, e.g. ""Emergency"" (If this is an emergency, Go to your nearest ER) or ""Mental Health"" (If you or someone you know is in crisis...) [ ] Design includes method for preparing the Veteran for the visit, agnostically. The specifics may be based on facility type (such as referral information or Urgent care eligibility link) ## Configuration - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (e.g. `vsa-authenticated-exp`, `vsa-caregiver`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,service user flow user story as a veteran i want to be able to search by service so that i can find a facility near me offering the service i seek tasks create service user flow consider which information is found on cards vs facility detail page acceptance criteria veteran can use service first user flow to search for high priority services such as urgent care emergency care pharmacy gastroenterology diagnostic imaging and ptsd sud search results will be organized around service offerings rather than facility types cards displayed in search results will contain information about the services offered at the location design includes escape hatch triggers for certain services e g emergency if this is an emergency go to your nearest er or mental health if you or someone you know is in crisis design includes method for preparing the veteran for the visit agnostically the specifics may be based on facility type such as referral information or urgent care eligibility link configuration attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team e g vsa authenticated exp vsa caregiver labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 158144,24794233358.0,IssuesEvent,2022-10-24 15:53:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Task: Provide VA with CIE appointment icon list,design ux HCE-Checkin,Task: Provide CIE's appointment icon list to the VA design team,1.0,Task: Provide VA with CIE appointment icon list - Task: Provide CIE's appointment icon list to the VA design team,1,task provide va with cie appointment icon list task provide cie s appointment icon list to the va design team,1 177059,28314893166.0,IssuesEvent,2023-04-10 18:41:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[bug] Missing in-line errors for Review and Submit validation,needs-grooming Supplemental Claims needs-design benefits-team-1 squad-2,"## Value Statement **_As a_** veteran **_I want to_** know exactly what is causing an error in my submission **_So that_** I can fix the errors and submit my form --- ## Background Context - In the past 7 days, there have been 2 FE validation issues (from Apr 6, 2023). The validation errors that came up are '[You must enter a treatment date](http://sentry.vfs.va.gov/organizations/vsp/discover/platform-web:00caeedad8674afeabe284dee33b42de/?field=message&name=Supplemental+Claims&project=4&query=url%3Ahttps%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2F%2A+level%3Aerror+message%3A%22Validation+issue+not+displayed+https%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2Freview-and-submit%22&sort=-message&statsPeriod=7d&widths=-1)' and '[You must enter a treatment date #2](http://sentry.vfs.va.gov/organizations/vsp/discover/platform-web:ae9456ed5d1f447f81a24a960bc930e4/?field=message&name=Supplemental+Claims&project=4&query=url%3Ahttps%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2F%2A+level%3Aerror+message%3A%22Validation+issue+not+displayed+https%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2Freview-and-submit%22&sort=-message&statsPeriod=7d&widths=-1)'. As it's unclear how the applicant is able to reach the Review and Submit page with errors pending, we are adding validation on the Review and Submit page and notifying veterans if there is an error within the evidence they need to fix. Currently on staging ![image.png](https://images.zenhubusercontent.com/630d073e647e629355675b4b/01b474de-eddc-449b-984c-056329b5ec23) ## Acceptance Criteria - [ ] Validation is in place for Review and Submit page to check for errors. - [ ] In-line errors will show where applicable - [ ] Review and Submit accordion style is updated to match Design System standards for errors. ## Designs and Build Notes - Add here ## Out of scope - Add here ## Open questions - Add here ## Tasks - [ ] _Task_ - [ ] _Task_ - [ ] _Task_ ## Definition of Ready - [ ] Clear value description - [ ] Testable acceptance criteria - [ ] Accessibility added to acceptance criteria - [ ] Approved designs attached - [ ] Sample data provided where appropriate - [ ] Estimated to fit within the sprint - [ ] Dependencies and blockers linked ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[bug] Missing in-line errors for Review and Submit validation - ## Value Statement **_As a_** veteran **_I want to_** know exactly what is causing an error in my submission **_So that_** I can fix the errors and submit my form --- ## Background Context - In the past 7 days, there have been 2 FE validation issues (from Apr 6, 2023). The validation errors that came up are '[You must enter a treatment date](http://sentry.vfs.va.gov/organizations/vsp/discover/platform-web:00caeedad8674afeabe284dee33b42de/?field=message&name=Supplemental+Claims&project=4&query=url%3Ahttps%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2F%2A+level%3Aerror+message%3A%22Validation+issue+not+displayed+https%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2Freview-and-submit%22&sort=-message&statsPeriod=7d&widths=-1)' and '[You must enter a treatment date #2](http://sentry.vfs.va.gov/organizations/vsp/discover/platform-web:ae9456ed5d1f447f81a24a960bc930e4/?field=message&name=Supplemental+Claims&project=4&query=url%3Ahttps%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2F%2A+level%3Aerror+message%3A%22Validation+issue+not+displayed+https%3A%2F%2Fwww.va.gov%2Fdecision-reviews%2Fsupplemental-claim%2Ffile-supplemental-claim-form-20-0995%2Freview-and-submit%22&sort=-message&statsPeriod=7d&widths=-1)'. As it's unclear how the applicant is able to reach the Review and Submit page with errors pending, we are adding validation on the Review and Submit page and notifying veterans if there is an error within the evidence they need to fix. Currently on staging ![image.png](https://images.zenhubusercontent.com/630d073e647e629355675b4b/01b474de-eddc-449b-984c-056329b5ec23) ## Acceptance Criteria - [ ] Validation is in place for Review and Submit page to check for errors. - [ ] In-line errors will show where applicable - [ ] Review and Submit accordion style is updated to match Design System standards for errors. ## Designs and Build Notes - Add here ## Out of scope - Add here ## Open questions - Add here ## Tasks - [ ] _Task_ - [ ] _Task_ - [ ] _Task_ ## Definition of Ready - [ ] Clear value description - [ ] Testable acceptance criteria - [ ] Accessibility added to acceptance criteria - [ ] Approved designs attached - [ ] Sample data provided where appropriate - [ ] Estimated to fit within the sprint - [ ] Dependencies and blockers linked ## Definition of Done - [ ] Meets acceptance criteria - [ ] Passed E2E testing (90% coverage) - [ ] Passed unit testing (90% coverage) - [ ] Passed integration testing (if applicable) - [ ] Code reviewed (internal) - [ ] Submitted to staging - [ ] Reviewed and approved by product and/or design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, missing in line errors for review and submit validation value statement as a veteran i want to know exactly what is causing an error in my submission so that i can fix the errors and submit my form background context in the past days there have been fe validation issues from apr the validation errors that came up are and as it s unclear how the applicant is able to reach the review and submit page with errors pending we are adding validation on the review and submit page and notifying veterans if there is an error within the evidence they need to fix currently on staging acceptance criteria validation is in place for review and submit page to check for errors in line errors will show where applicable review and submit accordion style is updated to match design system standards for errors designs and build notes add here out of scope add here open questions add here tasks task task task definition of ready clear value description testable acceptance criteria accessibility added to acceptance criteria approved designs attached sample data provided where appropriate estimated to fit within the sprint dependencies and blockers linked definition of done meets acceptance criteria passed testing coverage passed unit testing coverage passed integration testing if applicable code reviewed internal submitted to staging reviewed and approved by product and or design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 91411,11500710336.0,IssuesEvent,2020-02-12 15:59:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"MDT- Address step- Veteran contact details - edit address details, v1",design vsa vsa-benefits-2," ## User Story: As a veteran, I need to be able to edit my mailing address so that I can update or correct information. ## Tasks - [x] Create a high fidelity mockup depicting how a veteran might edit address and contact details - [x] Upload exports to Invision and indicate initial focus point as a comment ## Acceptance Criteria: Mockup aligns with VA.gov’s design system Veteran is able to edit their mailing address The screen’s initial focus is incorporated Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Step ## Dep/Blockers ",1.0,"MDT- Address step- Veteran contact details - edit address details, v1 - ## User Story: As a veteran, I need to be able to edit my mailing address so that I can update or correct information. ## Tasks - [x] Create a high fidelity mockup depicting how a veteran might edit address and contact details - [x] Upload exports to Invision and indicate initial focus point as a comment ## Acceptance Criteria: Mockup aligns with VA.gov’s design system Veteran is able to edit their mailing address The screen’s initial focus is incorporated Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Step ## Dep/Blockers ",1,mdt address step veteran contact details edit address details user story as a veteran i need to be able to edit my mailing address so that i can update or correct information tasks create a high fidelity mockup depicting how a veteran might edit address and contact details upload exports to invision and indicate initial focus point as a comment acceptance criteria mockup aligns with va gov’s design system veteran is able to edit their mailing address the screen’s initial focus is incorporated sketch artboards are uploaded to invision and linked in this ticket as a comment next step dep blockers ,1 140731,21190326669.0,IssuesEvent,2022-04-08 16:38:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Onboarding New Team: 2 Designers and PM,service-design,"## Issue Description _Three new people have joined the team and we need to get them up to speed_ --- ## Dan Tasks - [x] Read through [SD space in confluence](https://vfs.atlassian.net/wiki/spaces/SDT/overview) - [x] (Designers) Read through [Design and research community of practice space](https://vfs.atlassian.net/wiki/spaces/DCP/overview) - [x] (All) Read through [About the Platform Space](https://vfs.atlassian.net/wiki/spaces/AP/overview?homepageId=1375240354) - [x] Join a VSP orientation session ## Nicole Tasks - [x] Read through [SD space in confluence](https://vfs.atlassian.net/wiki/spaces/SDT/overview) - [x] (Designers) Read through [Design and research community of practice space](https://vfs.atlassian.net/wiki/spaces/DCP/overview) - [x] (All) Read through [About the Platform Space](https://vfs.atlassian.net/wiki/spaces/AP/overview?homepageId=1375240354) - [x] Join a VSP orientation session ## Bryan Tasks - [x] Read through [SD space in confluence](https://vfs.atlassian.net/wiki/spaces/SDT/overview) - [x] (Bryan) Read through [Product community of practice space](https://vfs.atlassian.net/wiki/spaces/PMCP/overview) - [x] (All) Read through [About the Platform Space](https://vfs.atlassian.net/wiki/spaces/AP/overview?homepageId=1375240354) - [x] Join a VSP orientation session ",1.0,"Onboarding New Team: 2 Designers and PM - ## Issue Description _Three new people have joined the team and we need to get them up to speed_ --- ## Dan Tasks - [x] Read through [SD space in confluence](https://vfs.atlassian.net/wiki/spaces/SDT/overview) - [x] (Designers) Read through [Design and research community of practice space](https://vfs.atlassian.net/wiki/spaces/DCP/overview) - [x] (All) Read through [About the Platform Space](https://vfs.atlassian.net/wiki/spaces/AP/overview?homepageId=1375240354) - [x] Join a VSP orientation session ## Nicole Tasks - [x] Read through [SD space in confluence](https://vfs.atlassian.net/wiki/spaces/SDT/overview) - [x] (Designers) Read through [Design and research community of practice space](https://vfs.atlassian.net/wiki/spaces/DCP/overview) - [x] (All) Read through [About the Platform Space](https://vfs.atlassian.net/wiki/spaces/AP/overview?homepageId=1375240354) - [x] Join a VSP orientation session ## Bryan Tasks - [x] Read through [SD space in confluence](https://vfs.atlassian.net/wiki/spaces/SDT/overview) - [x] (Bryan) Read through [Product community of practice space](https://vfs.atlassian.net/wiki/spaces/PMCP/overview) - [x] (All) Read through [About the Platform Space](https://vfs.atlassian.net/wiki/spaces/AP/overview?homepageId=1375240354) - [x] Join a VSP orientation session ",1,onboarding new team designers and pm issue description three new people have joined the team and we need to get them up to speed dan tasks read through designers read through all read through join a vsp orientation session nicole tasks read through designers read through all read through join a vsp orientation session bryan tasks read through bryan read through all read through join a vsp orientation session ,1 154879,24362904236.0,IssuesEvent,2022-10-03 13:10:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Maintenance of design.va.gov: Q3 2022,Epic vsp-design-system-team PO Endorsed platform-okrs,"## Product Outline Design System Product Outline https://vfs.atlassian.net/l/c/Ah0VFf0A ## High Level User Story/ies - As a a VFS team member, I want to be able to see what components and patterns are in the Design System so I can use existing designs or code to build applications. - As a VFS team member, I want to be able to see what is new to the DS so I know what components or patterns are available when I'm building applications. - As a VFS designer, I want to be able to submit a design for consideration to be added to the design system so other teams can use the design. ## Hypothesis or Bet If we maintain design.va.gov with documentation of existing and new components and patterns, and proposed experimental designs, VFS teams will use it as a source when building digital applications. ## OKR _Which Objective / Key Result does this epic push forward?_ Quarterly Operations and Maintenance - Q3 2022 ## Definition of done ### What must be true in order for you to consider this epic complete? ",1.0,"Maintenance of design.va.gov: Q3 2022 - ## Product Outline Design System Product Outline https://vfs.atlassian.net/l/c/Ah0VFf0A ## High Level User Story/ies - As a a VFS team member, I want to be able to see what components and patterns are in the Design System so I can use existing designs or code to build applications. - As a VFS team member, I want to be able to see what is new to the DS so I know what components or patterns are available when I'm building applications. - As a VFS designer, I want to be able to submit a design for consideration to be added to the design system so other teams can use the design. ## Hypothesis or Bet If we maintain design.va.gov with documentation of existing and new components and patterns, and proposed experimental designs, VFS teams will use it as a source when building digital applications. ## OKR _Which Objective / Key Result does this epic push forward?_ Quarterly Operations and Maintenance - Q3 2022 ## Definition of done ### What must be true in order for you to consider this epic complete? ",1,maintenance of design va gov product outline design system product outline high level user story ies as a a vfs team member i want to be able to see what components and patterns are in the design system so i can use existing designs or code to build applications as a vfs team member i want to be able to see what is new to the ds so i know what components or patterns are available when i m building applications as a vfs designer i want to be able to submit a design for consideration to be added to the design system so other teams can use the design hypothesis or bet if we maintain design va gov with documentation of existing and new components and patterns and proposed experimental designs vfs teams will use it as a source when building digital applications okr which objective key result does this epic push forward quarterly operations and maintenance definition of done what must be true in order for you to consider this epic complete ,1 177558,28508756546.0,IssuesEvent,2023-04-19 01:06:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2),content design 508/Accessibility ia Supplemental Claims collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard benefits-team-1 squad-2,"### General Information #### VFS team name Benefits Team 1 #### VFS product name Supplemental Claims Form 20-0995 #### VFS feature name Supplemental Claims Form 20-0995 #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details If a user uploads evidence and gets an error message, the message reads ""something went wrong..."". ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Follow the [files design pattern](https://design.va.gov/patterns/ask-users-for/files#error-state) and change the text to ""We couldn't upload your file"" --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2) - ### General Information #### VFS team name Benefits Team 1 #### VFS product name Supplemental Claims Form 20-0995 #### VFS feature name Supplemental Claims Form 20-0995 #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details If a user uploads evidence and gets an error message, the message reads ""something went wrong..."". ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Follow the [files design pattern](https://design.va.gov/patterns/ask-users-for/files#error-state) and change the text to ""We couldn't upload your file"" --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, design components or patterns don t align with design system guidelines general information vfs team name benefits team vfs product name supplemental claims form vfs feature name supplemental claims form point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details if a user uploads evidence and gets an error message the message reads something went wrong link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation follow the and change the text to we couldn t upload your file vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 104520,13095776012.0,IssuesEvent,2020-08-03 14:38:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Post-MVP] Investigate adding sort functionality to YR,design frontend vsa vsa-public-websites,"# Description Investigate adding sort functionality to the YR tool. ""`sortBy` and `sortDirection` logic may be interesting to add in a future version since 3-7% of people who take advantage of GI Bill 9/11 benefits choose schools that start with the letter `A` since everything is sorted alphabetically by default currently"" ~ Luke Tickner ## Acceptance Criteria - [ ] Determine if we want to add sorting functionality - [ ] Modify the YR tool design to include the sorting functionality - [ ] Implement the sorting functionality + design into `vets-website` ",1.0,"[Post-MVP] Investigate adding sort functionality to YR - # Description Investigate adding sort functionality to the YR tool. ""`sortBy` and `sortDirection` logic may be interesting to add in a future version since 3-7% of people who take advantage of GI Bill 9/11 benefits choose schools that start with the letter `A` since everything is sorted alphabetically by default currently"" ~ Luke Tickner ## Acceptance Criteria - [ ] Determine if we want to add sorting functionality - [ ] Modify the YR tool design to include the sorting functionality - [ ] Implement the sorting functionality + design into `vets-website` ",1, investigate adding sort functionality to yr description investigate adding sort functionality to the yr tool sortby and sortdirection logic may be interesting to add in a future version since of people who take advantage of gi bill benefits choose schools that start with the letter a since everything is sorted alphabetically by default currently luke tickner acceptance criteria determine if we want to add sorting functionality modify the yr tool design to include the sorting functionality implement the sorting functionality design into vets website ,1 94728,11905810282.0,IssuesEvent,2020-03-30 19:14:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] COVID-19 My VA alert: Mock up alert for the dashboard,My VA design vsa-authenticated-exp,"## Background Epic #6974 We need to show an alert that links patients to an existing VA health chat tool on the My VA dashboard. This alert should only show for patients with access to this tool, which is currently patients that go to hospitals in VISNs 8 and 23 (VISN = Veterans Integrated Service Network = essentially a group of VA hospitals). ## Alert specs **Design** - This alert should appear on the top of users' My VA dashboard under the main heading for that page - I think the ""blue"" alert should work, but let me know if you think the yellow one is better for this **What this alert needs to include** - Patients can use health chat app to ask their doctors questions about COVID-19 - They can use this tool on their desktop, or download mobile apps for their phone - A link to this page to access the tool https://mobile.va.gov/app/va-health-chat Since we should be able to determine who should see this alert based on information in the code, we shouldn't need to mention that only users at certain facilities can use this tool. BUT we might want to consider it. If we do, the easiest thing would be to say it's available to people at certain facilities, and to go [to go here](https://mobile.va.gov/app/va-health-chat) to determine if they are at an eligible facility. ## Tasks - [ ] Design alert - [ ] Get copy (note: we'll need final approval from stakeholders on copy, so there might be some back and forth) ## Acceptance criteria - [ ] The alert is designed and final copy has been approved.",1.0,"[Design] COVID-19 My VA alert: Mock up alert for the dashboard - ## Background Epic #6974 We need to show an alert that links patients to an existing VA health chat tool on the My VA dashboard. This alert should only show for patients with access to this tool, which is currently patients that go to hospitals in VISNs 8 and 23 (VISN = Veterans Integrated Service Network = essentially a group of VA hospitals). ## Alert specs **Design** - This alert should appear on the top of users' My VA dashboard under the main heading for that page - I think the ""blue"" alert should work, but let me know if you think the yellow one is better for this **What this alert needs to include** - Patients can use health chat app to ask their doctors questions about COVID-19 - They can use this tool on their desktop, or download mobile apps for their phone - A link to this page to access the tool https://mobile.va.gov/app/va-health-chat Since we should be able to determine who should see this alert based on information in the code, we shouldn't need to mention that only users at certain facilities can use this tool. BUT we might want to consider it. If we do, the easiest thing would be to say it's available to people at certain facilities, and to go [to go here](https://mobile.va.gov/app/va-health-chat) to determine if they are at an eligible facility. ## Tasks - [ ] Design alert - [ ] Get copy (note: we'll need final approval from stakeholders on copy, so there might be some back and forth) ## Acceptance criteria - [ ] The alert is designed and final copy has been approved.",1, covid my va alert mock up alert for the dashboard background epic we need to show an alert that links patients to an existing va health chat tool on the my va dashboard this alert should only show for patients with access to this tool which is currently patients that go to hospitals in visns and visn veterans integrated service network essentially a group of va hospitals alert specs design this alert should appear on the top of users my va dashboard under the main heading for that page i think the blue alert should work but let me know if you think the yellow one is better for this what this alert needs to include patients can use health chat app to ask their doctors questions about covid they can use this tool on their desktop or download mobile apps for their phone a link to this page to access the tool since we should be able to determine who should see this alert based on information in the code we shouldn t need to mention that only users at certain facilities can use this tool but we might want to consider it if we do the easiest thing would be to say it s available to people at certain facilities and to go to determine if they are at an eligible facility tasks design alert get copy note we ll need final approval from stakeholders on copy so there might be some back and forth acceptance criteria the alert is designed and final copy has been approved ,1 143621,22106357615.0,IssuesEvent,2022-06-01 17:20:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Release to Production,frontend backend design research HCE-Checkin,"## ENGINEERING TASKS - [ ] Flip the feature flag on day of release ## RESEARCH TASKS - [ ] Push updated Product Guides to Git ## DESIGN TASKS - [ ] Merge final wireframes to Abstract main branch - [ ] Merge Sketch files to VA Sketch cloud ## PRODCT TASKS - [ ] Create release notes [here](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-release-notes.md) - [ ] Remove corresponding entry from the [Planned Releases page](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-planned-releases.md) - [ ] Send release notification via slack in the [check-in-experience](https://dsva.slack.com/archives/C022AC2STBM) channel - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Call-outs = include call outs to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - [ ] Send release notification via VA email - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Send email to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - Dore Mobley (not in slack) ",1.0,"Release to Production - ## ENGINEERING TASKS - [ ] Flip the feature flag on day of release ## RESEARCH TASKS - [ ] Push updated Product Guides to Git ## DESIGN TASKS - [ ] Merge final wireframes to Abstract main branch - [ ] Merge Sketch files to VA Sketch cloud ## PRODCT TASKS - [ ] Create release notes [here](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-release-notes.md) - [ ] Remove corresponding entry from the [Planned Releases page](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-planned-releases.md) - [ ] Send release notification via slack in the [check-in-experience](https://dsva.slack.com/archives/C022AC2STBM) channel - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Call-outs = include call outs to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - [ ] Send release notification via VA email - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Send email to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - Dore Mobley (not in slack) ",1,release to production engineering tasks flip the feature flag on day of release research tasks push updated product guides to git design tasks merge final wireframes to abstract main branch merge sketch files to va sketch cloud prodct tasks create release notes remove corresponding entry from the send release notification via slack in the channel text modernized check in production release on release notes can be found here link include link to the release notes for the date of the production release call outs include call outs to stephen barrs patrick bateman shawn adams jason woodman send release notification via va email text modernized check in production release on release notes can be found here link include link to the release notes for the date of the production release send email to stephen barrs patrick bateman shawn adams jason woodman dore mobley not in slack ,1 168667,26681187087.0,IssuesEvent,2023-01-26 17:49:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Identify and Validate the scenarios we already have/know,service-design,"## Purpose [Our gathering](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2430599269/Prioritization+of+Service+Blueprinting+Mapping+endeavors) of this information [Additional Research](https://vfs.atlassian.net/wiki/spaces/CUI/pages/2333999266/How+the+Platform+Can+Support+VFS+BE+Engineering+Tasks#Pain-Points-to-be-Solved-by-New-functionality) performed by Console UI team [Recent Findings](https://docs.google.com/presentation/d/1UdAEZhQPBMVvD_IfXPrBvSRqtCr_o3_0IBtf2fbG-FQ/edit#slide=id.gcd567e2ae4_0_432) from Governance team on Onboarding [VFS Top Tasks](https://vfs.atlassian.net/wiki/spaces/AP/pages/2036301898/VFS+Top+Tasks+-+Pain+points) - Pain points VFS Top Tasks [Research by SDT](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1718681607/VFS+Top+Tasks+Research) Check w/ CoP's for areas of concern? ## Tasks - [x] Reference lists above for #51953 - [x] Identify any others ## Acceptance Criteria - [x] Reference [list of scenarios](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2504327255/Scenario+organizer+for+VFS+top+tasks) to pursue ",1.0,"Identify and Validate the scenarios we already have/know - ## Purpose [Our gathering](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2430599269/Prioritization+of+Service+Blueprinting+Mapping+endeavors) of this information [Additional Research](https://vfs.atlassian.net/wiki/spaces/CUI/pages/2333999266/How+the+Platform+Can+Support+VFS+BE+Engineering+Tasks#Pain-Points-to-be-Solved-by-New-functionality) performed by Console UI team [Recent Findings](https://docs.google.com/presentation/d/1UdAEZhQPBMVvD_IfXPrBvSRqtCr_o3_0IBtf2fbG-FQ/edit#slide=id.gcd567e2ae4_0_432) from Governance team on Onboarding [VFS Top Tasks](https://vfs.atlassian.net/wiki/spaces/AP/pages/2036301898/VFS+Top+Tasks+-+Pain+points) - Pain points VFS Top Tasks [Research by SDT](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1718681607/VFS+Top+Tasks+Research) Check w/ CoP's for areas of concern? ## Tasks - [x] Reference lists above for #51953 - [x] Identify any others ## Acceptance Criteria - [x] Reference [list of scenarios](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2504327255/Scenario+organizer+for+VFS+top+tasks) to pursue ",1,identify and validate the scenarios we already have know purpose of this information performed by console ui team from governance team on onboarding pain points vfs top tasks check w cop s for areas of concern tasks reference lists above for identify any others acceptance criteria reference to pursue ,1 122643,16194762737.0,IssuesEvent,2021-05-04 13:21:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,NOD Phase 2 Design Tasks,NOD design vsa-claims-appeals,"## Issue Description Complete phase 2 design tasks. ####Content brief: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/content/content-briefs/content-brief-NOD.md --- ## Tasks - [x] Address all of Robin's comments from design --> dev (for the duration of the sprint) - [x] Create a 'board hearing preference' page ## Acceptance Criteria - [x] The above tasks have been met and implemented into the NOD Invision Prototype --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"NOD Phase 2 Design Tasks - ## Issue Description Complete phase 2 design tasks. ####Content brief: https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/content/content-briefs/content-brief-NOD.md --- ## Tasks - [x] Address all of Robin's comments from design --> dev (for the duration of the sprint) - [x] Create a 'board hearing preference' page ## Acceptance Criteria - [x] The above tasks have been met and implemented into the NOD Invision Prototype --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,nod phase design tasks issue description complete phase design tasks content brief tasks address all of robin s comments from design dev for the duration of the sprint create a board hearing preference page acceptance criteria the above tasks have been met and implemented into the nod invision prototype how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 145631,22752134317.0,IssuesEvent,2022-07-07 13:53:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Add Scenario to User Flow Documentation,design HCE-Checkin,"## Background We need to add this [scenario ](https://dsva.slack.com/archives/C022AC2STBM/p1657128770816119)and wording to our user flow documentation and messaging source of truth. ## Tasks - [ ] Add Scenario to User Flow Documentation",1.0,"[Design] Add Scenario to User Flow Documentation - ## Background We need to add this [scenario ](https://dsva.slack.com/archives/C022AC2STBM/p1657128770816119)and wording to our user flow documentation and messaging source of truth. ## Tasks - [ ] Add Scenario to User Flow Documentation",1, add scenario to user flow documentation background we need to add this wording to our user flow documentation and messaging source of truth tasks add scenario to user flow documentation,1 175735,27967411217.0,IssuesEvent,2023-03-24 20:58:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Update Sketch files: Add footer symbol at bottom of artboards that are missing it,design authenticated-experience profile,"## Background Some Sketch files include artboards that have a different footer than our standard footer symbol. For the sake of consistency, each artboard should have the same footer symbol. ## Tasks - [ ] Review Sketch files and ensure that all artboards have the footer symbol ## Acceptance criteria - [ ] All Sketch files have been updated accordingly",1.0,"Update Sketch files: Add footer symbol at bottom of artboards that are missing it - ## Background Some Sketch files include artboards that have a different footer than our standard footer symbol. For the sake of consistency, each artboard should have the same footer symbol. ## Tasks - [ ] Review Sketch files and ensure that all artboards have the footer symbol ## Acceptance criteria - [ ] All Sketch files have been updated accordingly",1,update sketch files add footer symbol at bottom of artboards that are missing it background some sketch files include artboards that have a different footer than our standard footer symbol for the sake of consistency each artboard should have the same footer symbol tasks review sketch files and ensure that all artboards have the footer symbol acceptance criteria all sketch files have been updated accordingly,1 161856,25411573108.0,IssuesEvent,2022-11-22 19:28:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Create detailed draft of Guide for the mapping process,service-design,"## Issue Description Document the mapping process, drafting the specific steps involved Should result in an internal guide that a SDT member can follow. Practical by Design [SB Process tips](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2431746066/Nice+Breakdown+of+SB+process+from+Practical+by+Design) NNG SB Course [notes](https://docs.google.com/document/d/16UT5GysDO6-4Mx2dXQkVBctLpN5_QkLxTj28Alvd2p0/edit?usp=sharing) ## Tasks - [x] Shape major steps into a specific [guide](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2436169729/How+To+Service+Blueprint+a+Process+-+the+SDT+way) - [x] Use [workshop data](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1666623990109/dba477fdf13b9e403ef4e67d39d246c973dd6b29?sender=u4397b715dc3690a417b71483) and research to delineate specific steps within each phase - [x] Refine w/ team input ## Acceptance Criteria - [x] Process is documented in an internal guide format.",1.0,"Create detailed draft of Guide for the mapping process - ## Issue Description Document the mapping process, drafting the specific steps involved Should result in an internal guide that a SDT member can follow. Practical by Design [SB Process tips](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2431746066/Nice+Breakdown+of+SB+process+from+Practical+by+Design) NNG SB Course [notes](https://docs.google.com/document/d/16UT5GysDO6-4Mx2dXQkVBctLpN5_QkLxTj28Alvd2p0/edit?usp=sharing) ## Tasks - [x] Shape major steps into a specific [guide](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2436169729/How+To+Service+Blueprint+a+Process+-+the+SDT+way) - [x] Use [workshop data](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1666623990109/dba477fdf13b9e403ef4e67d39d246c973dd6b29?sender=u4397b715dc3690a417b71483) and research to delineate specific steps within each phase - [x] Refine w/ team input ## Acceptance Criteria - [x] Process is documented in an internal guide format.",1,create detailed draft of guide for the mapping process issue description document the mapping process drafting the specific steps involved should result in an internal guide that a sdt member can follow practical by design nng sb course tasks shape major steps into a specific use and research to delineate specific steps within each phase refine w team input acceptance criteria process is documented in an internal guide format ,1 139002,20756043722.0,IssuesEvent,2022-03-15 12:18:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Explore how users engage w/ Platform,service-design,"## Issue Description What are touchpoints for the user? How are they aware of Platform offerings? How do they discover them specifically? --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Explore how users engage w/ Platform - ## Issue Description What are touchpoints for the user? How are they aware of Platform offerings? How do they discover them specifically? --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,explore how users engage w platform issue description what are touchpoints for the user how are they aware of platform offerings how do they discover them specifically tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 89102,11197786079.0,IssuesEvent,2020-01-03 14:17:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Update UX onboarding design review instructions,design product support,"## User Story As a designer, I need guidance on how to request a design review so I can learn how to prepare my designs for VSP team reviews. ## Goal Update the UX onboarding to include the new design review process based on VSP Design Rules of Engagement ## Acceptance Criteria - [x] Update design review slide ",1.0,"Update UX onboarding design review instructions - ## User Story As a designer, I need guidance on how to request a design review so I can learn how to prepare my designs for VSP team reviews. ## Goal Update the UX onboarding to include the new design review process based on VSP Design Rules of Engagement ## Acceptance Criteria - [x] Update design review slide ",1,update ux onboarding design review instructions user story as a designer i need guidance on how to request a design review so i can learn how to prepare my designs for vsp team reviews goal update the ux onboarding to include the new design review process based on vsp design rules of engagement acceptance criteria update design review slide ,1 92933,11726857555.0,IssuesEvent,2020-03-10 15:06:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Create and present on options for ""removing"" plain language",design vsa-caregiver,"## User Story Given that the Program Team wants to keep all language consistent between the paper and online forms Create and present on possible designs that meet this requirement While ensuring that users understand how to fill out the form.",1.0,"Create and present on options for ""removing"" plain language - ## User Story Given that the Program Team wants to keep all language consistent between the paper and online forms Create and present on possible designs that meet this requirement While ensuring that users understand how to fill out the form.",1,create and present on options for removing plain language user story given that the program team wants to keep all language consistent between the paper and online forms create and present on possible designs that meet this requirement while ensuring that users understand how to fill out the form ,1 124278,16602523853.0,IssuesEvent,2021-06-01 21:43:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design]: Design details and customize copy and/or error messaging for the ""upload"" component in 10-10CG",design vsa-caregiver,"## Description _Work with Justin to make sure the upload feature in the 10-10CG is optimized for the use case_ Note, I (Shawna) recommend this ticket happen *after* Justin pulls in and codes the basic upload pattern from other forms (e.g. the 21-526EZ) so we can play around with what works and doesn't from our form ## Acceptance Criteria - [ ] _Reserach error states_ - [ ] _Allign with content If needed_ - [ ] _Mockup error states_ ",1.0,"[Design]: Design details and customize copy and/or error messaging for the ""upload"" component in 10-10CG - ## Description _Work with Justin to make sure the upload feature in the 10-10CG is optimized for the use case_ Note, I (Shawna) recommend this ticket happen *after* Justin pulls in and codes the basic upload pattern from other forms (e.g. the 21-526EZ) so we can play around with what works and doesn't from our form ## Acceptance Criteria - [ ] _Reserach error states_ - [ ] _Allign with content If needed_ - [ ] _Mockup error states_ ",1, design details and customize copy and or error messaging for the upload component in description work with justin to make sure the upload feature in the is optimized for the use case note i shawna recommend this ticket happen after justin pulls in and codes the basic upload pattern from other forms e g the so we can play around with what works and doesn t from our form acceptance criteria reserach error states allign with content if needed mockup error states ,1 149544,23491117396.0,IssuesEvent,2022-08-17 18:50:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Discovery: Community Care display options,frontend backend design discovery vsa Facilities,"## High Level User Story As a Veteran, I need to understand where the search results are located on the map so I can choose a location close to me. ## Goals Good usability between map and search results ## Current behavior - Community care providers are returned as individual providers (and sometimes, as practice locations) which means a single map pin can correspond with multiple search results - Metro areas may have similar situation, based on facilities located close to each other ## Tasks Determine desired behavior when user clicks on search result in list, such as: - does the map filter and display only that location? - does the corresponding pin come to the surface with highlight? Determine desired behavior when user clicks on map pin - which search result is highlighted in the list? ",1.0,"Discovery: Community Care display options - ## High Level User Story As a Veteran, I need to understand where the search results are located on the map so I can choose a location close to me. ## Goals Good usability between map and search results ## Current behavior - Community care providers are returned as individual providers (and sometimes, as practice locations) which means a single map pin can correspond with multiple search results - Metro areas may have similar situation, based on facilities located close to each other ## Tasks Determine desired behavior when user clicks on search result in list, such as: - does the map filter and display only that location? - does the corresponding pin come to the surface with highlight? Determine desired behavior when user clicks on map pin - which search result is highlighted in the list? ",1,discovery community care display options high level user story as a veteran i need to understand where the search results are located on the map so i can choose a location close to me goals good usability between map and search results current behavior community care providers are returned as individual providers and sometimes as practice locations which means a single map pin can correspond with multiple search results metro areas may have similar situation based on facilities located close to each other tasks determine desired behavior when user clicks on search result in list such as does the map filter and display only that location does the corresponding pin come to the surface with highlight determine desired behavior when user clicks on map pin which search result is highlighted in the list ,1 141905,21638308225.0,IssuesEvent,2022-05-05 16:05:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Documentation Update: Process List,vsp-design-system-team,"## Issue Description Make updates to Process List on design.va.gov, Storybook and Sketch library to fix the discrepancies that have been identified. Discrepancies No concept of Content list vs. Dynamic process list in design.va.gov. --- ## Tasks - [x] Add View guidance for the Process List component in the Design System below label for va-process-list in Storybook that links back to Process List on design.va.gov (See example on va-modal) - [x] Add link in Storybook back to Process List on design.va.gov https://design.va.gov/components/process-list - [x] Update link to Storybook on design.va.gov to ""View va-process-list in Storybook"" ~~Add Content list and Dynamic process list to design.va.gov (Get mock ups from Natalie or Matt)~~ ## Acceptance Criteria - [x] Storybook has link “View guidance for Process List component in the Design System” - [x] Storybook has a link to the Process List component page on design.va.gov - [x] XXXX link to Storybook is labeled ""View va-process-list in Storybook"" ~~Process List page on design.va.gov includes Content List and Dynamic Process List~~ --- ",1.0,"Documentation Update: Process List - ## Issue Description Make updates to Process List on design.va.gov, Storybook and Sketch library to fix the discrepancies that have been identified. Discrepancies No concept of Content list vs. Dynamic process list in design.va.gov. --- ## Tasks - [x] Add View guidance for the Process List component in the Design System below label for va-process-list in Storybook that links back to Process List on design.va.gov (See example on va-modal) - [x] Add link in Storybook back to Process List on design.va.gov https://design.va.gov/components/process-list - [x] Update link to Storybook on design.va.gov to ""View va-process-list in Storybook"" ~~Add Content list and Dynamic process list to design.va.gov (Get mock ups from Natalie or Matt)~~ ## Acceptance Criteria - [x] Storybook has link “View guidance for Process List component in the Design System” - [x] Storybook has a link to the Process List component page on design.va.gov - [x] XXXX link to Storybook is labeled ""View va-process-list in Storybook"" ~~Process List page on design.va.gov includes Content List and Dynamic Process List~~ --- ",1,documentation update process list issue description make updates to process list on design va gov storybook and sketch library to fix the discrepancies that have been identified discrepancies no concept of content list vs dynamic process list in design va gov tasks add view guidance for the process list component in the design system below label for va process list in storybook that links back to process list on design va gov see example on va modal add link in storybook back to process list on design va gov update link to storybook on design va gov to view va process list in storybook add content list and dynamic process list to design va gov get mock ups from natalie or matt acceptance criteria storybook has link “view guidance for process list component in the design system” storybook has a link to the process list component page on design va gov xxxx link to storybook is labeled view va process list in storybook process list page on design va gov includes content list and dynamic process list ,1 106509,13305234007.0,IssuesEvent,2020-08-25 18:12:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] update profile header when no military info is available,design profile vsa-authenticated-exp,"## Background ![profile_without_military_info.png](https://images.zenhubusercontent.com/5e41b49969d880e9f4f122b1/2e0e220e-8b91-4a62-b3e5-009351afe32b) ## Tasks -[ ] Update alignment/header",1.0,"[Design] update profile header when no military info is available - ## Background ![profile_without_military_info.png](https://images.zenhubusercontent.com/5e41b49969d880e9f4f122b1/2e0e220e-8b91-4a62-b3e5-009351afe32b) ## Tasks -[ ] Update alignment/header",1, update profile header when no military info is available background tasks update alignment header,1 131351,18274827129.0,IssuesEvent,2021-10-04 17:31:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Content] Calendar - no slots near future alert,content vaos-product-design,"## Request Request review of the alert on the direct schedule calendar page. - If no slots in the next 2 months - If no slots in the next 4 months ## Background When a user inputs today's date in the preferred date, an ""urgent care"" alert appears above the calendar. The app queries for 2 months worth of slots. If there's a slot the alert copy is populated with the earliest available date. If there are no open slots, then the copy currently shows today's date (bug/no handling #30480) ## Screenshot ![image.png](https://images.zenhubusercontent.com/5f2d82e4a65f7435058cfd75/e1613a03-342f-4a64-b27e-8c4d48027ca4)",1.0,"[Content] Calendar - no slots near future alert - ## Request Request review of the alert on the direct schedule calendar page. - If no slots in the next 2 months - If no slots in the next 4 months ## Background When a user inputs today's date in the preferred date, an ""urgent care"" alert appears above the calendar. The app queries for 2 months worth of slots. If there's a slot the alert copy is populated with the earliest available date. If there are no open slots, then the copy currently shows today's date (bug/no handling #30480) ## Screenshot ![image.png](https://images.zenhubusercontent.com/5f2d82e4a65f7435058cfd75/e1613a03-342f-4a64-b27e-8c4d48027ca4)",1, calendar no slots near future alert request request review of the alert on the direct schedule calendar page if no slots in the next months if no slots in the next months background when a user inputs today s date in the preferred date an urgent care alert appears above the calendar the app queries for months worth of slots if there s a slot the alert copy is populated with the earliest available date if there are no open slots then the copy currently shows today s date bug no handling screenshot ,1 137733,20204512671.0,IssuesEvent,2022-02-11 18:40:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Claim Status Tool a11y Accessibility Issue,frontend design vsa vsa-claims-appeals Claim Status Tool benefits-crew,"## Issue Description The listing in the Claim Status Tool contains colored dots that are not in accordance with accessibility standards. See slack[ thread here](https://dsva.slack.com/archives/C8E985R32/p1644517476221339). --- ## Tasks - [ ] Examine design intent and develop new design to accordingly. ![Screen Shot 2022-02-10 at 13.13.07.png](https://images.zenhubusercontent.com/5ffca1cc8ef760e3db881927/346bde00-0033-4dff-b3fd-88fa2ca9b4e9) - More from Josh: If the intention is to bring less focus to closed items, it may be better not to have a dot icon at all If the intention is to bring more focus to closed items, it may be better to use an icon that (a) meets 3:1 color contrast requirements and (b) doesn't rely on color for its meaning (e.g. red dot won't be interpretable to color blind users so a unique icon may be preferred) ## Acceptance Criteria - [ ] New design forwarded to front end for implementation. --- ",1.0,"Claim Status Tool a11y Accessibility Issue - ## Issue Description The listing in the Claim Status Tool contains colored dots that are not in accordance with accessibility standards. See slack[ thread here](https://dsva.slack.com/archives/C8E985R32/p1644517476221339). --- ## Tasks - [ ] Examine design intent and develop new design to accordingly. ![Screen Shot 2022-02-10 at 13.13.07.png](https://images.zenhubusercontent.com/5ffca1cc8ef760e3db881927/346bde00-0033-4dff-b3fd-88fa2ca9b4e9) - More from Josh: If the intention is to bring less focus to closed items, it may be better not to have a dot icon at all If the intention is to bring more focus to closed items, it may be better to use an icon that (a) meets 3:1 color contrast requirements and (b) doesn't rely on color for its meaning (e.g. red dot won't be interpretable to color blind users so a unique icon may be preferred) ## Acceptance Criteria - [ ] New design forwarded to front end for implementation. --- ",1,claim status tool accessibility issue issue description the listing in the claim status tool contains colored dots that are not in accordance with accessibility standards see slack tasks examine design intent and develop new design to accordingly more from josh if the intention is to bring less focus to closed items it may be better not to have a dot icon at all if the intention is to bring more focus to closed items it may be better to use an icon that a meets color contrast requirements and b doesn t rely on color for its meaning e g red dot won t be interpretable to color blind users so a unique icon may be preferred acceptance criteria new design forwarded to front end for implementation ,1 106267,13258697879.0,IssuesEvent,2020-08-20 15:43:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Learning Center MVP - Explore variations between keyword search and tag results,design needs-grooming ux vsa-public-websites,"How can we make ~tag~` tagged view all [X] topic list of articles `and keyword search results look different? @jenniferlee-dsva is interested in exploring this idea. ^ Clarification: The variation is not about what appears as a search result when you click on a tag vs. enter a keyword in search; the variation that I would like the team to think about is when the user clicks on the `""View all X articles""` link > currently, we take them to a page that's basically a search results list; but please consider another UX - e.g., a landing page that just provides a list of all the articles in that topic category? /Jen 7/27 Our initial usability study doesn't ask users to try keyword searches or evaluate keyword search results, so we won't have qualitative data from that to back up an approach either way. Meg Peters has done a lot of. work with search, so might be good to check with her to see if she has any thoughts or has done research in this area before. This came out of #11491. @andaleliz or @rtwell to explore as time allows.",1.0,"[Design] Learning Center MVP - Explore variations between keyword search and tag results - How can we make ~tag~` tagged view all [X] topic list of articles `and keyword search results look different? @jenniferlee-dsva is interested in exploring this idea. ^ Clarification: The variation is not about what appears as a search result when you click on a tag vs. enter a keyword in search; the variation that I would like the team to think about is when the user clicks on the `""View all X articles""` link > currently, we take them to a page that's basically a search results list; but please consider another UX - e.g., a landing page that just provides a list of all the articles in that topic category? /Jen 7/27 Our initial usability study doesn't ask users to try keyword searches or evaluate keyword search results, so we won't have qualitative data from that to back up an approach either way. Meg Peters has done a lot of. work with search, so might be good to check with her to see if she has any thoughts or has done research in this area before. This came out of #11491. @andaleliz or @rtwell to explore as time allows.",1, learning center mvp explore variations between keyword search and tag results how can we make tag tagged view all topic list of articles and keyword search results look different jenniferlee dsva is interested in exploring this idea clarification the variation is not about what appears as a search result when you click on a tag vs enter a keyword in search the variation that i would like the team to think about is when the user clicks on the view all x articles link currently we take them to a page that s basically a search results list but please consider another ux e g a landing page that just provides a list of all the articles in that topic category jen our initial usability study doesn t ask users to try keyword searches or evaluate keyword search results so we won t have qualitative data from that to back up an approach either way meg peters has done a lot of work with search so might be good to check with her to see if she has any thoughts or has done research in this area before this came out of andaleliz or rtwell to explore as time allows ,1 183165,31165835351.0,IssuesEvent,2023-08-16 19:37:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,move Sign In Page through Design Review,design login.gov-adoption,"As a designer I need to understand what suggestions are coming from the Platform team so that I can incorporate them into our design. ACCEPTANCE: - complete collab cycle request - follow up quickly on asks from the platform tea - ask Design Lead/PM for support where needed DEF OF DONE: - Collab cycle successfully completed and sign in page mock confirmed so that build can begin",1.0,"move Sign In Page through Design Review - As a designer I need to understand what suggestions are coming from the Platform team so that I can incorporate them into our design. ACCEPTANCE: - complete collab cycle request - follow up quickly on asks from the platform tea - ask Design Lead/PM for support where needed DEF OF DONE: - Collab cycle successfully completed and sign in page mock confirmed so that build can begin",1,move sign in page through design review as a designer i need to understand what suggestions are coming from the platform team so that i can incorporate them into our design acceptance complete collab cycle request follow up quickly on asks from the platform tea ask design lead pm for support where needed def of done collab cycle successfully completed and sign in page mock confirmed so that build can begin,1 121688,16015433701.0,IssuesEvent,2021-04-20 15:28:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,NOD Summary Slide deck,NOD design documentation research vsa-claims-appeals,"## Issue Description Research Results Slide Deck --- ## Tasks - Prepare slide deck ## Acceptance Criteria - [x] Completed and posted to Github --- ",1.0,"NOD Summary Slide deck - ## Issue Description Research Results Slide Deck --- ## Tasks - Prepare slide deck ## Acceptance Criteria - [x] Completed and posted to Github --- ",1,nod summary slide deck issue description research results slide deck tasks prepare slide deck acceptance criteria completed and posted to github ,1 93010,11731267198.0,IssuesEvent,2020-03-10 23:33:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Make Final HLR Design Changes,design vsa-benefits vsa-decision-reviews,"## User Story or Problem Statement We need to ensure that certain design aspects of the form are consistent with other form patterns on VA.gov and to create designs for different states that the front end developers may need to implement properly in code. This story captures the work for the call center product guide for Higher Level Review. Here is the Invision prototype link to HLR: https://vsateams.invisionapp.com/share/W5U21BDFTQK ## Goal To make sure that the design is consistent with known form patterns on VA.gov. ## Tasks - [x] Info page - Update to show 2 question gating - [x] Intro page - Remove 'things to consider' list and replace with the single thing to consider - [x] Intro page - remove forwarding address mention - [x] Contact info - make language sections consistent with profile update info - [x] Contact info - make error states consistent with design system (no gray field bg, etc) - [x] Contested Issues - Work in 'required' at the top somewhere to indicate to users that they must select at least 1 contested issue - [x] Same Office - eliminate page and make this a checkbox option on the contested issues screen instead - [x] Review page - Make contested issues edit section consistent with button placement on other forms - [x] Review page - Show contested issues edit section state (what does it look like when user is editing/de/reselecting contested issues ## Acceptance Criteria - [ ] All tasks above have been implemented into the Invision prototype link referenced above ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] Make Final HLR Design Changes - ## User Story or Problem Statement We need to ensure that certain design aspects of the form are consistent with other form patterns on VA.gov and to create designs for different states that the front end developers may need to implement properly in code. This story captures the work for the call center product guide for Higher Level Review. Here is the Invision prototype link to HLR: https://vsateams.invisionapp.com/share/W5U21BDFTQK ## Goal To make sure that the design is consistent with known form patterns on VA.gov. ## Tasks - [x] Info page - Update to show 2 question gating - [x] Intro page - Remove 'things to consider' list and replace with the single thing to consider - [x] Intro page - remove forwarding address mention - [x] Contact info - make language sections consistent with profile update info - [x] Contact info - make error states consistent with design system (no gray field bg, etc) - [x] Contested Issues - Work in 'required' at the top somewhere to indicate to users that they must select at least 1 contested issue - [x] Same Office - eliminate page and make this a checkbox option on the contested issues screen instead - [x] Review page - Make contested issues edit section consistent with button placement on other forms - [x] Review page - Show contested issues edit section state (what does it look like when user is editing/de/reselecting contested issues ## Acceptance Criteria - [ ] All tasks above have been implemented into the Invision prototype link referenced above ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, make final hlr design changes user story or problem statement we need to ensure that certain design aspects of the form are consistent with other form patterns on va gov and to create designs for different states that the front end developers may need to implement properly in code this story captures the work for the call center product guide for higher level review here is the invision prototype link to hlr goal to make sure that the design is consistent with known form patterns on va gov tasks info page update to show question gating intro page remove things to consider list and replace with the single thing to consider intro page remove forwarding address mention contact info make language sections consistent with profile update info contact info make error states consistent with design system no gray field bg etc contested issues work in required at the top somewhere to indicate to users that they must select at least contested issue same office eliminate page and make this a checkbox option on the contested issues screen instead review page make contested issues edit section consistent with button placement on other forms review page show contested issues edit section state what does it look like when user is editing de reselecting contested issues acceptance criteria all tasks above have been implemented into the invision prototype link referenced above how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 123811,16539552291.0,IssuesEvent,2021-05-27 15:14:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] [New] - Update content to reflect 10MB file size,design vsa vsa-caregiver,"## User Story Update Sign as a Representative content to reflect new size restriction (10 MB) ## Acceptance Criteria - [x] Source of truth content doc is updated - [x] New content passed to frontend (#25166) ",1.0,"[Design] [New] - Update content to reflect 10MB file size - ## User Story Update Sign as a Representative content to reflect new size restriction (10 MB) ## Acceptance Criteria - [x] Source of truth content doc is updated - [x] New content passed to frontend (#25166) ",1, update content to reflect file size user story update sign as a representative content to reflect new size restriction mb acceptance criteria source of truth content doc is updated new content passed to frontend ,1 120879,15818675452.0,IssuesEvent,2021-04-05 16:21:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,NOD - Work with Content team,NOD design vsa-claims-appeals,"## Issue Description Engage content team for assistance with NOD --- ## Tasks - [ ] Set up call with Beth Potts ## Acceptance Criteria - [ ] Call scheduled --- ",1.0,"NOD - Work with Content team - ## Issue Description Engage content team for assistance with NOD --- ## Tasks - [ ] Set up call with Beth Potts ## Acceptance Criteria - [ ] Call scheduled --- ",1,nod work with content team issue description engage content team for assistance with nod tasks set up call with beth potts acceptance criteria call scheduled ,1 123334,16483309931.0,IssuesEvent,2021-05-24 14:33:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Preferred Facility: Update FE documentation post-content & IA review,design documentation planned-work preferred-facility vsa-authenticated-exp,"## Background Following completion of content and IA review of preferred facilities/your health facilities (#23288), there are some updates needed to the FE documentation. ## Tasks - [x] Update [FE documentation](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/preferred-facility/frontend/design-specs.md) per final [IA recommendations](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/information-architecture/ia-reviews/auth-profile-your-facilities.md) - [x] Update content documentation per content feedback",1.0,"[Design] Preferred Facility: Update FE documentation post-content & IA review - ## Background Following completion of content and IA review of preferred facilities/your health facilities (#23288), there are some updates needed to the FE documentation. ## Tasks - [x] Update [FE documentation](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/preferred-facility/frontend/design-specs.md) per final [IA recommendations](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/information-architecture/ia-reviews/auth-profile-your-facilities.md) - [x] Update content documentation per content feedback",1, preferred facility update fe documentation post content ia review background following completion of content and ia review of preferred facilities your health facilities there are some updates needed to the fe documentation tasks update per final update content documentation per content feedback,1 109298,13758643515.0,IssuesEvent,2020-10-07 00:38:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Analytics Implementation for Standardized Design System Components - Accordions,analytics-insights design system gtm needs-grooming,"From va.gov-team created by [jonwehausen](https://github.com/jonwehausen): department-of-veterans-affairs/va.gov-team#14487 # Google Analytics Implementation ## Description - Standardize data layer events and variables to track [accordions ](https://design.va.gov/components/accordions) across va.gov ## Data Layer Specification - Work in Progress **Accordion Expand** ```javascript 'event': 'nav-accordion-expand', 'accordion-parent-label': //when there are 2 labels on an accordion, the top-level heading 'accordion-child-label': //when there are 2 labels on an accordion, the lower-level heading 'accordion-relative-size': //placeholder, potential 'accordion-exact-size': //placeholder, potential ``` **Accordion Collapse** ```javascript 'event': 'nav-accordion-collapse', 'accordion-parent-label': 'accordion-child-label': ``` ## Acceptance Criteria - [ ] Data layer for accordions as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1.0,"Analytics Implementation for Standardized Design System Components - Accordions - From va.gov-team created by [jonwehausen](https://github.com/jonwehausen): department-of-veterans-affairs/va.gov-team#14487 # Google Analytics Implementation ## Description - Standardize data layer events and variables to track [accordions ](https://design.va.gov/components/accordions) across va.gov ## Data Layer Specification - Work in Progress **Accordion Expand** ```javascript 'event': 'nav-accordion-expand', 'accordion-parent-label': //when there are 2 labels on an accordion, the top-level heading 'accordion-child-label': //when there are 2 labels on an accordion, the lower-level heading 'accordion-relative-size': //placeholder, potential 'accordion-exact-size': //placeholder, potential ``` **Accordion Collapse** ```javascript 'event': 'nav-accordion-collapse', 'accordion-parent-label': 'accordion-child-label': ``` ## Acceptance Criteria - [ ] Data layer for accordions as been deployed universally - [ ] QA has been completed ## Definition of Done - [ ] All appropriate issue tagging is completed - [ ] All AC completed ",1,analytics implementation for standardized design system components accordions from va gov team created by department of veterans affairs va gov team google analytics implementation description standardize data layer events and variables to track across va gov data layer specification work in progress accordion expand javascript event nav accordion expand accordion parent label when there are labels on an accordion the top level heading accordion child label when there are labels on an accordion the lower level heading accordion relative size placeholder potential accordion exact size placeholder potential accordion collapse javascript event nav accordion collapse accordion parent label accordion child label acceptance criteria data layer for accordions as been deployed universally qa has been completed definition of done all appropriate issue tagging is completed all ac completed ,1 124207,16596035713.0,IssuesEvent,2021-06-01 13:36:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[UI] Refinement of Check-in User Journeys and Wireframes,HCE-Checkin design vsa-healthcare-exp,"## Product Links [Product Online](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/product/product-outline.md) ## Description Refine wireframes for check-in and pre-check in. Expand beyond just happy paths. ## Tasks - [x] Update wireframes in Sketch ## Acceptance Criteria - [x] Team reviews wireframe updates",1.0,"[UI] Refinement of Check-in User Journeys and Wireframes - ## Product Links [Product Online](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/product/product-outline.md) ## Description Refine wireframes for check-in and pre-check in. Expand beyond just happy paths. ## Tasks - [x] Update wireframes in Sketch ## Acceptance Criteria - [x] Team reviews wireframe updates",1, refinement of check in user journeys and wireframes product links description refine wireframes for check in and pre check in expand beyond just happy paths tasks update wireframes in sketch acceptance criteria team reviews wireframe updates,1 141307,21478976923.0,IssuesEvent,2022-04-26 15:53:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Date web component: accessibility review,vsp-design-system-team,"## Description We need to conduct a full accessibility review of the new Date web component. The component can be viewed in Storybook here: https://60f9b557105290003b387cd5-kdzjshpbzk.chromatic.com/?path=/docs/components-va-date--default ## Acceptance Criteria - [ ] Full accessibility review of the Date component is completed - [ ] Add descriptions of any issues found to this ticket - [ ] If any problems are found, add screen recordings and/or screenshots to comments on this ticket that show the problem. - [ ] Alert Katy and the developer who built the component when the review is complete - [ ] Re-review any fixes the developer makes to the component",1.0,"Date web component: accessibility review - ## Description We need to conduct a full accessibility review of the new Date web component. The component can be viewed in Storybook here: https://60f9b557105290003b387cd5-kdzjshpbzk.chromatic.com/?path=/docs/components-va-date--default ## Acceptance Criteria - [ ] Full accessibility review of the Date component is completed - [ ] Add descriptions of any issues found to this ticket - [ ] If any problems are found, add screen recordings and/or screenshots to comments on this ticket that show the problem. - [ ] Alert Katy and the developer who built the component when the review is complete - [ ] Re-review any fixes the developer makes to the component",1,date web component accessibility review description we need to conduct a full accessibility review of the new date web component the component can be viewed in storybook here acceptance criteria full accessibility review of the date component is completed add descriptions of any issues found to this ticket if any problems are found add screen recordings and or screenshots to comments on this ticket that show the problem alert katy and the developer who built the component when the review is complete re review any fixes the developer makes to the component,1 149699,23511217430.0,IssuesEvent,2022-08-18 16:43:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Use Confluence to build out the Map,service-design,"## Issue Description Use Confluence to add info on teams and their services to the [Airtable](https://airtable.com/appbYNZ8PkZY7o9vs/tblXHp3UQAcjuotNa/viwNjGJl7am1QN2yD?blocks=hide). Additional sources: [VSP Org chart](https://docs.google.com/drawings/d/1N7tW2wTNqViooXE6ts8QujG36oyAg4mqu1zyeQ67DiY/edit?pli=1) [Platform Roster](https://vfs.atlassian.net/wiki/spaces/AP/pages/1908834623/Platform+Roster?src=mail&src.mail.action=view&src.mail.notification=com.atlassian.confluence.plugins.confluence-notifications-batch-plugin%3Abatching-notification&src.mail.recipient=622b5b63932f0f00716bdfd6&src.mail.timestamp=1655481712198) ## User Story As a Platform team member, what tools or services does each team provide for what purpose? --- ## Tasks - [x] Add additional info on services into Airtable ## Acceptance Criteria - [x] Services for each team are documented in Airtable",1.0,"Use Confluence to build out the Map - ## Issue Description Use Confluence to add info on teams and their services to the [Airtable](https://airtable.com/appbYNZ8PkZY7o9vs/tblXHp3UQAcjuotNa/viwNjGJl7am1QN2yD?blocks=hide). Additional sources: [VSP Org chart](https://docs.google.com/drawings/d/1N7tW2wTNqViooXE6ts8QujG36oyAg4mqu1zyeQ67DiY/edit?pli=1) [Platform Roster](https://vfs.atlassian.net/wiki/spaces/AP/pages/1908834623/Platform+Roster?src=mail&src.mail.action=view&src.mail.notification=com.atlassian.confluence.plugins.confluence-notifications-batch-plugin%3Abatching-notification&src.mail.recipient=622b5b63932f0f00716bdfd6&src.mail.timestamp=1655481712198) ## User Story As a Platform team member, what tools or services does each team provide for what purpose? --- ## Tasks - [x] Add additional info on services into Airtable ## Acceptance Criteria - [x] Services for each team are documented in Airtable",1,use confluence to build out the map issue description use confluence to add info on teams and their services to the additional sources user story as a platform team member what tools or services does each team provide for what purpose tasks add additional info on services into airtable acceptance criteria services for each team are documented in airtable,1 173358,27426197076.0,IssuesEvent,2023-03-01 20:31:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,understanding of what current MHV preferences entail and document,design research ux my-health my-health-CTO-HEALTH-TEAM my-health-INTEGRATION,"## Overview Before we can make recommendations and design an experience for MHV preferences on VA.gov, we must first understand the current preferences on MHV, as well as how they overlap with preferences on VA.gov. ## Acceptance Criteria / Deliverables - Gain an understanding of what current MHV preferences entail and document - [ ] Where can view preferences? - [ ] Document findings",1.0,"understanding of what current MHV preferences entail and document - ## Overview Before we can make recommendations and design an experience for MHV preferences on VA.gov, we must first understand the current preferences on MHV, as well as how they overlap with preferences on VA.gov. ## Acceptance Criteria / Deliverables - Gain an understanding of what current MHV preferences entail and document - [ ] Where can view preferences? - [ ] Document findings",1,understanding of what current mhv preferences entail and document overview before we can make recommendations and design an experience for mhv preferences on va gov we must first understand the current preferences on mhv as well as how they overlap with preferences on va gov acceptance criteria deliverables gain an understanding of what current mhv preferences entail and document where can view preferences document findings,1 111441,14080396698.0,IssuesEvent,2020-11-04 16:04:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] My VA Dashboard: Revisit Direction/Wireframe explorations (mobile & desktop),design my-va-dashboard vsa-authenticated-exp,"## Background We are taking this sprint (S33) to revisit the direction of the MyVA dashboard redesign and explore different options and decide upon the approach going forward. The focus should be on sketches/low-fi wireframes not on detailed visual design. My VA goals: Get users to personalized information and tasks as quickly as possible. The page should be personalized, actionable, and scalable. [Mobile wireframes](https://cassandraallen738782.invisionapp.com/console/HP-mobile-logged-in-ckeyhydog01kz01xd3tao5pcj/ckgkztfzz09ib01ea4mv33wh0/play) ## Tasks ### Mobile wireframes - [x] Wireframe/sketch explorations - [x] Regularly share updates in Github - [x] Meet with Samara/Ryan/Matt as needed - [x] Decide on direction going forward ### Desktop wireframes - [ ] Convert mobile designs into desktop mockups",1.0,"[DESIGN] My VA Dashboard: Revisit Direction/Wireframe explorations (mobile & desktop) - ## Background We are taking this sprint (S33) to revisit the direction of the MyVA dashboard redesign and explore different options and decide upon the approach going forward. The focus should be on sketches/low-fi wireframes not on detailed visual design. My VA goals: Get users to personalized information and tasks as quickly as possible. The page should be personalized, actionable, and scalable. [Mobile wireframes](https://cassandraallen738782.invisionapp.com/console/HP-mobile-logged-in-ckeyhydog01kz01xd3tao5pcj/ckgkztfzz09ib01ea4mv33wh0/play) ## Tasks ### Mobile wireframes - [x] Wireframe/sketch explorations - [x] Regularly share updates in Github - [x] Meet with Samara/Ryan/Matt as needed - [x] Decide on direction going forward ### Desktop wireframes - [ ] Convert mobile designs into desktop mockups",1, my va dashboard revisit direction wireframe explorations mobile desktop background we are taking this sprint to revisit the direction of the myva dashboard redesign and explore different options and decide upon the approach going forward the focus should be on sketches low fi wireframes not on detailed visual design my va goals get users to personalized information and tasks as quickly as possible the page should be personalized actionable and scalable tasks mobile wireframes wireframe sketch explorations regularly share updates in github meet with samara ryan matt as needed decide on direction going forward desktop wireframes convert mobile designs into desktop mockups,1 115015,14674375738.0,IssuesEvent,2020-12-30 15:11:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Update CH36 Prototype,CH36 design vsa vsa-ebenefits,"## Background Based on Peggy's list of feedback, we need to ensure that the prototype is up to date ## Considerations - [ ] Peggy's ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/16690 ## Tasks - [ ] Update content changes per Peggy's ticket (seen above) ## Acceptance Criteria - [x] Content changes have been saved in prototype",1.0,"Update CH36 Prototype - ## Background Based on Peggy's list of feedback, we need to ensure that the prototype is up to date ## Considerations - [ ] Peggy's ticket: https://github.com/department-of-veterans-affairs/va.gov-team/issues/16690 ## Tasks - [ ] Update content changes per Peggy's ticket (seen above) ## Acceptance Criteria - [x] Content changes have been saved in prototype",1,update prototype background based on peggy s list of feedback we need to ensure that the prototype is up to date considerations peggy s ticket tasks update content changes per peggy s ticket seen above acceptance criteria content changes have been saved in prototype,1 116316,14942429700.0,IssuesEvent,2021-01-25 21:17:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[UI] Denoting other questionnaires to complete on Confirmation page,design vsa-healthcare-exp,"## User Story - As a Veteran, I want to be able to know if I have any more questionnaires to complete once I've completed one questionnaire. ## Related Documentation - [MVP: Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) ## Description A wireframe of the confirmation page depicting a solution for how many other questionnaires a Veteran still has to complete will be delivered with the technical specifications needed for engineering to implement said feature. ## Tasks - [x] Brainstorm different design solutions - [x] Present solutions to product team - [x] Finalize detailed mockup and callouts of ## Acceptance Criteria - [x] UI review meeting with product/team for feature capabilities - [x] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [x] Published mockup link exists and it is added/updated within the product feature outline",1.0,"[UI] Denoting other questionnaires to complete on Confirmation page - ## User Story - As a Veteran, I want to be able to know if I have any more questionnaires to complete once I've completed one questionnaire. ## Related Documentation - [MVP: Visit Intro Initiative (Proof of Concept)](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/visit-intro.md) ## Description A wireframe of the confirmation page depicting a solution for how many other questionnaires a Veteran still has to complete will be delivered with the technical specifications needed for engineering to implement said feature. ## Tasks - [x] Brainstorm different design solutions - [x] Present solutions to product team - [x] Finalize detailed mockup and callouts of ## Acceptance Criteria - [x] UI review meeting with product/team for feature capabilities - [x] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [x] Published mockup link exists and it is added/updated within the product feature outline",1, denoting other questionnaires to complete on confirmation page user story as a veteran i want to be able to know if i have any more questionnaires to complete once i ve completed one questionnaire related documentation description a wireframe of the confirmation page depicting a solution for how many other questionnaires a veteran still has to complete will be delivered with the technical specifications needed for engineering to implement said feature tasks brainstorm different design solutions present solutions to product team finalize detailed mockup and callouts of acceptance criteria ui review meeting with product team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above published mockup link exists and it is added updated within the product feature outline,1 83364,10346998552.0,IssuesEvent,2019-09-04 16:22:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Research] Search Landing Page Template - PLACEHOLDER,analytics-insights content design vsa-global-ux,"Identify Resources: 1. Research / UX 2. Designer ",1.0,"[Research] Search Landing Page Template - PLACEHOLDER - Identify Resources: 1. Research / UX 2. Designer ",1, search landing page template placeholder identify resources research ux designer ,1 142317,21715168836.0,IssuesEvent,2022-05-10 17:09:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Review IE team's new tool and SD approach,service-design,"## Issue Description Consider IE team's SD approach for their new tool https://app.zenhub.com/workspaces/integration-experience---platform-spike-team-61f18a64735e8e0015911cf7/issues/department-of-veterans-affairs/va.gov-team/38931 --- ## Tasks - [ ] Review ## Acceptance Criteria - [ ] to be determined",1.0,"Review IE team's new tool and SD approach - ## Issue Description Consider IE team's SD approach for their new tool https://app.zenhub.com/workspaces/integration-experience---platform-spike-team-61f18a64735e8e0015911cf7/issues/department-of-veterans-affairs/va.gov-team/38931 --- ## Tasks - [ ] Review ## Acceptance Criteria - [ ] to be determined",1,review ie team s new tool and sd approach issue description consider ie team s sd approach for their new tool tasks review acceptance criteria to be determined,1 104022,11387601976.0,IssuesEvent,2020-01-29 15:17:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[FE] Direct Deposit: Review product outline and update if needed,direct deposit documentation frontend profile vsa-authenticated-exp,"## Background We need to make sure the direct deposit documentation is fully up to date before fully moving on from the project. ## Tasks - [ ] Review the How to Access and Test, Error Handling, Service Level Objective, and API Calls and Dependent Systems. - [ ] Update these sections if necessary - Note: if no updates are needed beyond what is there, please comment on this thread and let me know. ## Acceptance criteria - [ ] The sections of the product outline listed above have been reviewed and updated as necessary.",1.0,"[FE] Direct Deposit: Review product outline and update if needed - ## Background We need to make sure the direct deposit documentation is fully up to date before fully moving on from the project. ## Tasks - [ ] Review the How to Access and Test, Error Handling, Service Level Objective, and API Calls and Dependent Systems. - [ ] Update these sections if necessary - Note: if no updates are needed beyond what is there, please comment on this thread and let me know. ## Acceptance criteria - [ ] The sections of the product outline listed above have been reviewed and updated as necessary.",0, direct deposit review product outline and update if needed background we need to make sure the direct deposit documentation is fully up to date before fully moving on from the project tasks review the how to access and test error handling service level objective and api calls and dependent systems update these sections if necessary note if no updates are needed beyond what is there please comment on this thread and let me know acceptance criteria the sections of the product outline listed above have been reviewed and updated as necessary ,0 107448,13460839269.0,IssuesEvent,2020-09-09 14:06:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Claims Status: Estimated Claim Completion Date Status Statement,design vsa-benefits,"## Issue Description Temporarily replace the estimated claim completion date with a general statement. This will need to be reviewed and reconsidered after the COVID-19 situation has resolved. There has been a request to change the estimated completion date for claims to a message. This is the suggested message: _The estimated claim completion date feature has been temporarily removed. Due to the impact COVID-19 has had on the availability and scheduling of required in-person medical disability exams, the estimated completion date is not accurate at this time. VA is coordinating efforts to ensure all exams are scheduled and conducted as soon as it is safe in each area. You can review the status of exams in your area here._ This story is to design this message into the CST page. However, it may be worth reaching back out to the stakeholders to see if the middle ground of including the estimate _with_ the message may be more accurate and therefore what we suggest. ## Acceptance Criteria - [ ] Decide whether we remove the date completely - [ ] Design with/without date and the message --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[Design] Claims Status: Estimated Claim Completion Date Status Statement - ## Issue Description Temporarily replace the estimated claim completion date with a general statement. This will need to be reviewed and reconsidered after the COVID-19 situation has resolved. There has been a request to change the estimated completion date for claims to a message. This is the suggested message: _The estimated claim completion date feature has been temporarily removed. Due to the impact COVID-19 has had on the availability and scheduling of required in-person medical disability exams, the estimated completion date is not accurate at this time. VA is coordinating efforts to ensure all exams are scheduled and conducted as soon as it is safe in each area. You can review the status of exams in your area here._ This story is to design this message into the CST page. However, it may be worth reaching back out to the stakeholders to see if the middle ground of including the estimate _with_ the message may be more accurate and therefore what we suggest. ## Acceptance Criteria - [ ] Decide whether we remove the date completely - [ ] Design with/without date and the message --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, claims status estimated claim completion date status statement issue description temporarily replace the estimated claim completion date with a general statement this will need to be reviewed and reconsidered after the covid situation has resolved there has been a request to change the estimated completion date for claims to a message this is the suggested message the estimated claim completion date feature has been temporarily removed due to the impact covid has had on the availability and scheduling of required in person medical disability exams the estimated completion date is not accurate at this time va is coordinating efforts to ensure all exams are scheduled and conducted as soon as it is safe in each area you can review the status of exams in your area here this story is to design this message into the cst page however it may be worth reaching back out to the stakeholders to see if the middle ground of including the estimate with the message may be more accurate and therefore what we suggest acceptance criteria decide whether we remove the date completely design with without date and the message how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 134278,19122409945.0,IssuesEvent,2021-12-01 00:59:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Pivot from Newsletter - Communications roundup experiment,service-design,"## Issue Description Run an experiment posting digests of Platform changes and informational announcements on a regular cadence on Platform website and Slack #vfs-all-teams channels. Purpose: Train VFS team members to expect to hear news about Platform on a regular cadence in #vfs-all-teams and on the Platform website. Provide timely, relevant notifications to VFS teams about changes that will impact their workflows. Measuring success: https://vfs.atlassian.net/l/c/vWnPoDVD --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] We have determined if the communications roundup should become an ongoing service provided by the Platform. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Pivot from Newsletter - Communications roundup experiment - ## Issue Description Run an experiment posting digests of Platform changes and informational announcements on a regular cadence on Platform website and Slack #vfs-all-teams channels. Purpose: Train VFS team members to expect to hear news about Platform on a regular cadence in #vfs-all-teams and on the Platform website. Provide timely, relevant notifications to VFS teams about changes that will impact their workflows. Measuring success: https://vfs.atlassian.net/l/c/vWnPoDVD --- ## Tasks - [ ] _What work is necessary for this story to be completed?_ ## Acceptance Criteria - [ ] We have determined if the communications roundup should become an ongoing service provided by the Platform. --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,pivot from newsletter communications roundup experiment issue description run an experiment posting digests of platform changes and informational announcements on a regular cadence on platform website and slack vfs all teams channels purpose train vfs team members to expect to hear news about platform on a regular cadence in vfs all teams and on the platform website provide timely relevant notifications to vfs teams about changes that will impact their workflows measuring success tasks what work is necessary for this story to be completed acceptance criteria we have determined if the communications roundup should become an ongoing service provided by the platform how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 274015,20822977786.0,IssuesEvent,2022-03-18 17:16:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Align Current Message Templates with Message Template Policies,VEText vt Product Support vt Documentation vt,"Text messages are broken into segments at 160 characters, which is contributing to large delays in time-sensitive communication between veterans and healthcare providers. To mitigate the issue, VEText should align text messages with the existing text message policies. - [ ] Edit top priority messages to below 500 characters - [ ] Ensure messages follow text message policies - [ ] Consult with leadership on message template content",1.0,"Align Current Message Templates with Message Template Policies - Text messages are broken into segments at 160 characters, which is contributing to large delays in time-sensitive communication between veterans and healthcare providers. To mitigate the issue, VEText should align text messages with the existing text message policies. - [ ] Edit top priority messages to below 500 characters - [ ] Ensure messages follow text message policies - [ ] Consult with leadership on message template content",0,align current message templates with message template policies text messages are broken into segments at characters which is contributing to large delays in time sensitive communication between veterans and healthcare providers to mitigate the issue vetext should align text messages with the existing text message policies edit top priority messages to below characters ensure messages follow text message policies consult with leadership on message template content,0 151127,23766546898.0,IssuesEvent,2022-09-01 13:14:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Determine format of Map,service-design,"## Questions to evaluate: How do we make it easily consumable while also making it comprehensive? What are the top / most important pieces of information to map? Consider multiple iterations dependent upon needs/consumer How do we map out ""reports to""? How do we map out Platform-Platform and Platform-VFS links/bridges? -Gaps -connections -Perhaps visually: how to make sure connections are clear? and rightly represented? -rollup for customers of each product on a team Note: teams tend not to talk/think about who their customers are. May be able to surface these voids Map Mural: https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1661266120803/aa3069d80fc9a3137a519fe3def0f42d1b27bff7?sender=u4397b715dc3690a417b71483 Correlation Mural: https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1661278901419/0c0f38ec98df4b2e188625688eae505e53f08f63?sender=u4397b715dc3690a417b71483 Data reference: https://airtable.com/appbYNZ8PkZY7o9vs/tblXHp3UQAcjuotNa/viwNjGJl7am1QN2yD?blocks=hide ## Tasks - [x] Workshop the above questions - [x] Synthesize discussion points ## Pivot We decided to survey teams about their offerings to fill out what we've learned from desk research. This will inform the map's format. ",1.0,"Determine format of Map - ## Questions to evaluate: How do we make it easily consumable while also making it comprehensive? What are the top / most important pieces of information to map? Consider multiple iterations dependent upon needs/consumer How do we map out ""reports to""? How do we map out Platform-Platform and Platform-VFS links/bridges? -Gaps -connections -Perhaps visually: how to make sure connections are clear? and rightly represented? -rollup for customers of each product on a team Note: teams tend not to talk/think about who their customers are. May be able to surface these voids Map Mural: https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1661266120803/aa3069d80fc9a3137a519fe3def0f42d1b27bff7?sender=u4397b715dc3690a417b71483 Correlation Mural: https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1661278901419/0c0f38ec98df4b2e188625688eae505e53f08f63?sender=u4397b715dc3690a417b71483 Data reference: https://airtable.com/appbYNZ8PkZY7o9vs/tblXHp3UQAcjuotNa/viwNjGJl7am1QN2yD?blocks=hide ## Tasks - [x] Workshop the above questions - [x] Synthesize discussion points ## Pivot We decided to survey teams about their offerings to fill out what we've learned from desk research. This will inform the map's format. ",1,determine format of map questions to evaluate how do we make it easily consumable while also making it comprehensive what are the top most important pieces of information to map consider multiple iterations dependent upon needs consumer how do we map out reports to how do we map out platform platform and platform vfs links bridges gaps connections perhaps visually how to make sure connections are clear and rightly represented rollup for customers of each product on a team note teams tend not to talk think about who their customers are may be able to surface these voids map mural correlation mural data reference tasks workshop the above questions synthesize discussion points pivot we decided to survey teams about their offerings to fill out what we ve learned from desk research this will inform the map s format ,1 112371,14241994144.0,IssuesEvent,2020-11-19 00:41:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] CC provider list MVP,design vaos,"### Request Provide desktop, tablet, and mobile specs for the first version of the Community Care provider list to replace the preferred provider form. - [x] Default state with language selector: no selections, first load of providers - [x] Error states: Closest city/state not selection, language preference not selected - [x] Current location (instead of address) selected + current location can't be determined [/] Default state without language selector + language selection page _(Deferred to next iteration)_ [/] Missing Address state: user doesn't have address in profile _(Deferred to next iteration)_ ### Requirements - Option to select closest city and state - Option to select preferred language - Option to select one preferred facility from list - Option to select no facility preference ### Additional Notes - Current form: ![Community Care - preferred provider form copy.png](https://images.zenhubusercontent.com/5f7dd2dad6b9a9301bbab94e/7f2de265-ee81-41c9-9ac3-9a51456ba7f8) - [Peggy's content feedback on the test prototype](https://app.zenhub.com/workspaces/vft-59c95ae5fda7577a9b3184f8/issues/department-of-veterans-affairs/va.gov-team/15711)",1.0,"[DESIGN] CC provider list MVP - ### Request Provide desktop, tablet, and mobile specs for the first version of the Community Care provider list to replace the preferred provider form. - [x] Default state with language selector: no selections, first load of providers - [x] Error states: Closest city/state not selection, language preference not selected - [x] Current location (instead of address) selected + current location can't be determined [/] Default state without language selector + language selection page _(Deferred to next iteration)_ [/] Missing Address state: user doesn't have address in profile _(Deferred to next iteration)_ ### Requirements - Option to select closest city and state - Option to select preferred language - Option to select one preferred facility from list - Option to select no facility preference ### Additional Notes - Current form: ![Community Care - preferred provider form copy.png](https://images.zenhubusercontent.com/5f7dd2dad6b9a9301bbab94e/7f2de265-ee81-41c9-9ac3-9a51456ba7f8) - [Peggy's content feedback on the test prototype](https://app.zenhub.com/workspaces/vft-59c95ae5fda7577a9b3184f8/issues/department-of-veterans-affairs/va.gov-team/15711)",1, cc provider list mvp request provide desktop tablet and mobile specs for the first version of the community care provider list to replace the preferred provider form default state with language selector no selections first load of providers error states closest city state not selection language preference not selected current location instead of address selected current location can t be determined default state without language selector language selection page deferred to next iteration missing address state user doesn t have address in profile deferred to next iteration requirements option to select closest city and state option to select preferred language option to select one preferred facility from list option to select no facility preference additional notes current form ,1 184565,32008703657.0,IssuesEvent,2023-09-21 16:25:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"[Content organization] Your page doesn't follow heading hierarchy. Headings aren't properly nested, and headings and/or labels aren't relevant to the page. (02.04.1)",content design accessibility ia collab-cycle-feedback Staging CCIssue02.04 CC-Dashboard Burial Umbrella non-disability,"### General Information #### VFS team name Non-Disability Experience Team #### VFS product name Burial Form 530 #### VFS feature name Temporary Online Form Deactivation #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Your page doesn't follow heading hierarchy. Headings aren't properly nested, and headings and/or labels aren't relevant to the page. ### Issue Details On the ""How to apply page"" there are 2 headings tags that have ""How do I apply?"". I assume this is just a mistake as one of them has no content under it. ### Link, screenshot or steps to recreate [Screen shot](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/62889-Allison-020401.png) ### VA.gov Experience Standard [Category Number 02, Issue Number 04](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 1.3.1_A WCAG SC 2.4.6_AA ### Platform Recommendation Remove the extra ""How do I apply?"" heading tag. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Content organization] Your page doesn't follow heading hierarchy. Headings aren't properly nested, and headings and/or labels aren't relevant to the page. (02.04.1) - ### General Information #### VFS team name Non-Disability Experience Team #### VFS product name Burial Form 530 #### VFS feature name Temporary Online Form Deactivation #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Your page doesn't follow heading hierarchy. Headings aren't properly nested, and headings and/or labels aren't relevant to the page. ### Issue Details On the ""How to apply page"" there are 2 headings tags that have ""How do I apply?"". I assume this is just a mistake as one of them has no content under it. ### Link, screenshot or steps to recreate [Screen shot](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/working-with-vsp/vsp-collaboration-cycle/staging-review-images/62889-Allison-020401.png) ### VA.gov Experience Standard [Category Number 02, Issue Number 04](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 1.3.1_A WCAG SC 2.4.6_AA ### Platform Recommendation Remove the extra ""How do I apply?"" heading tag. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, your page doesn t follow heading hierarchy headings aren t properly nested and headings and or labels aren t relevant to the page general information vfs team name non disability experience team vfs product name burial form vfs feature name temporary online form deactivation point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue your page doesn t follow heading hierarchy headings aren t properly nested and headings and or labels aren t relevant to the page issue details on the how to apply page there are headings tags that have how do i apply i assume this is just a mistake as one of them has no content under it link screenshot or steps to recreate va gov experience standard other references wcag sc a wcag sc aa platform recommendation remove the extra how do i apply heading tag vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 135541,19593977862.0,IssuesEvent,2022-01-05 15:50:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Analytics KPI dashboard request for VAOS-VAOS for Distribution Initiative,analytics-insights analytics-request kpi-dashboard vaos-product-design,"# Request a KPI Dashboard New Domo dashboard specific to the VAOS for Distribution initiative. At minimum, we'll need a funnel and total events for select points of the flow. --- Is this a new KPI dashboard request? Or is this an iteration? Please check the corrrect response. - [x] New dashboard - [ ] Iteration of current dashboard ## VFS Information ### KPIs Please reference [product outline](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/vaos-for-distribution-initiative/vaos-for-distribution-initiative.md) for details *Please leave the following blank* --- ## VSP Analytics & Insights Acceptance Criteria 1. Groom Analytics - [ ] Groom analytics for technical feasibility - [ ] Document data sources for each metric - [ ] Document unavailable vs. available metrics - [ ] If any, add implementation issue for additional necessary implementation 2. Draft PST Dashboard - [ ] Draft dashboard on Domo - [ ] Structure data for ETL - [ ] Pipe available metrics to Domo - [ ] Add appropriate team members to dashboard Please see [checklist for full KPI dashboarding QA checklist](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/teams/insights-analytics/analytics-tools/domo-dashboard-qa-checklist.md) ## Definition of Done - [ ] KPIs have been groomed and connected to Domo - [ ] Dashboard has been shared back with the VFS team - [ ] KPI Dashboard full QA checklist completed ",1.0,"Analytics KPI dashboard request for VAOS-VAOS for Distribution Initiative - # Request a KPI Dashboard New Domo dashboard specific to the VAOS for Distribution initiative. At minimum, we'll need a funnel and total events for select points of the flow. --- Is this a new KPI dashboard request? Or is this an iteration? Please check the corrrect response. - [x] New dashboard - [ ] Iteration of current dashboard ## VFS Information ### KPIs Please reference [product outline](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/health-care/covid-vaccine-distro/vaos-for-distribution-initiative/vaos-for-distribution-initiative.md) for details *Please leave the following blank* --- ## VSP Analytics & Insights Acceptance Criteria 1. Groom Analytics - [ ] Groom analytics for technical feasibility - [ ] Document data sources for each metric - [ ] Document unavailable vs. available metrics - [ ] If any, add implementation issue for additional necessary implementation 2. Draft PST Dashboard - [ ] Draft dashboard on Domo - [ ] Structure data for ETL - [ ] Pipe available metrics to Domo - [ ] Add appropriate team members to dashboard Please see [checklist for full KPI dashboarding QA checklist](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/teams/insights-analytics/analytics-tools/domo-dashboard-qa-checklist.md) ## Definition of Done - [ ] KPIs have been groomed and connected to Domo - [ ] Dashboard has been shared back with the VFS team - [ ] KPI Dashboard full QA checklist completed ",1,analytics kpi dashboard request for vaos vaos for distribution initiative request a kpi dashboard new domo dashboard specific to the vaos for distribution initiative at minimum we ll need a funnel and total events for select points of the flow is this a new kpi dashboard request or is this an iteration please check the corrrect response new dashboard iteration of current dashboard vfs information kpis please reference for details please leave the following blank vsp analytics insights acceptance criteria groom analytics groom analytics for technical feasibility document data sources for each metric document unavailable vs available metrics if any add implementation issue for additional necessary implementation draft pst dashboard draft dashboard on domo structure data for etl pipe available metrics to domo add appropriate team members to dashboard please see definition of done kpis have been groomed and connected to domo dashboard has been shared back with the vfs team kpi dashboard full qa checklist completed ,1 111449,14085287908.0,IssuesEvent,2020-11-05 00:35:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Technical discovery: Back to top UX in learning center,design frontend vsa vsa-public-websites,"## Technical discovery: Back to top UX in learning center This is for mvp 1.1 learning center templates. Please work with @rtwell on the desired FE design and UX for implementation. **Basic requirement:** Each article page should enable a dynamic back to top link. This back to top should appear based on page height/length. ",1.0,"Technical discovery: Back to top UX in learning center - ## Technical discovery: Back to top UX in learning center This is for mvp 1.1 learning center templates. Please work with @rtwell on the desired FE design and UX for implementation. **Basic requirement:** Each article page should enable a dynamic back to top link. This back to top should appear based on page height/length. ",1,technical discovery back to top ux in learning center technical discovery back to top ux in learning center this is for mvp learning center templates please work with rtwell on the desired fe design and ux for implementation basic requirement each article page should enable a dynamic back to top link this back to top should appear based on page height length ,1 124227,16597657898.0,IssuesEvent,2021-06-01 15:11:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[DESIGN] Spec for VAMC locations page,design vsa vsa-facilities,"## Issue Description We need to update the Locations page to separate mobile clinics from physical locations. The current page combines all types of locations under ""Health clinic locations"" heading. Example: [Cheyenne health care](https://www.va.gov/cheyenne-health-care/locations/) --- ## Tasks - [x] Update VAMC spec with following headings - Main location - Health clinic locations - Mobile clinics ## Acceptance Criteria Design spec is ready for engineering and includes the following - [x] The VAMC system location page retains headings for ""Main locations"" and ""Health clinic locations"". - [x] Displayed details are the same for locations listed under ""Main locations"" and ""Health clinic locations"" - [x] VA Clinic locations listed under ""Health clinic locations"" are sorted alphabetically - [ ] CLCs and Domiliciliaries (when relevant) are alphabetical below listed VA clinics - [x] The VAMC system location page has a separate ""Mobile clinics"" heading. - [x] Displayed details do not include address or link for directions for locations listed under ""Mobile clinics"" heading (but are otherwise the same) - [x] Heading levels are specified - [x] Heading levels do not skip ",1.0,"[DESIGN] Spec for VAMC locations page - ## Issue Description We need to update the Locations page to separate mobile clinics from physical locations. The current page combines all types of locations under ""Health clinic locations"" heading. Example: [Cheyenne health care](https://www.va.gov/cheyenne-health-care/locations/) --- ## Tasks - [x] Update VAMC spec with following headings - Main location - Health clinic locations - Mobile clinics ## Acceptance Criteria Design spec is ready for engineering and includes the following - [x] The VAMC system location page retains headings for ""Main locations"" and ""Health clinic locations"". - [x] Displayed details are the same for locations listed under ""Main locations"" and ""Health clinic locations"" - [x] VA Clinic locations listed under ""Health clinic locations"" are sorted alphabetically - [ ] CLCs and Domiliciliaries (when relevant) are alphabetical below listed VA clinics - [x] The VAMC system location page has a separate ""Mobile clinics"" heading. - [x] Displayed details do not include address or link for directions for locations listed under ""Mobile clinics"" heading (but are otherwise the same) - [x] Heading levels are specified - [x] Heading levels do not skip ",1, spec for vamc locations page issue description we need to update the locations page to separate mobile clinics from physical locations the current page combines all types of locations under health clinic locations heading example tasks update vamc spec with following headings main location health clinic locations mobile clinics acceptance criteria design spec is ready for engineering and includes the following the vamc system location page retains headings for main locations and health clinic locations displayed details are the same for locations listed under main locations and health clinic locations va clinic locations listed under health clinic locations are sorted alphabetically clcs and domiliciliaries when relevant are alphabetical below listed va clinics the vamc system location page has a separate mobile clinics heading displayed details do not include address or link for directions for locations listed under mobile clinics heading but are otherwise the same heading levels are specified heading levels do not skip ,1 140729,21190307644.0,IssuesEvent,2022-04-08 16:37:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Research industry standards and approaches,service-design,"## Issue Description Analyze best practices across industry and record learnings in Mural --- ## Tasks - [x] https://www.nngroup.com/articles/service-design-101/ - Dan - [x] https://boagworld.com/audio/service-design/#Why_is_Service_Design_a_Thing - Nicole - [x] https://gds.blog.gov.uk/2016/04/18/what-we-mean-by-service-design/ - Taylor - [x] https://www.interaction-design.org/literature/topics/service-design - Bryan - [x] https://uxplanet.org/service-design-is-everywhere-a58fd5901e63 - Dan - [x] https://careerfoundry.com/en/blog/ux-design/what-is-service-design-how-to-implement-service-design-processes/ - Nicole - [x] https://cio-wiki.org/wiki/ITIL_Service_Design#:~:text=The%20scope%20of%20Service%20Design,conformance%20to%20standards%20and%20regulations. - Taylor - [x] https://www.interaction-design.org/literature/article/the-principles-of-service-design-thinking-building-better-services - Bryan - [x] http://www.practicalservicedesign.com/service-design-101 - Bryan ## Acceptance Criteria - [ ] Takeaways and learnings recorded in Mural for workshop ## Deadline - April 6th ",1.0,"Research industry standards and approaches - ## Issue Description Analyze best practices across industry and record learnings in Mural --- ## Tasks - [x] https://www.nngroup.com/articles/service-design-101/ - Dan - [x] https://boagworld.com/audio/service-design/#Why_is_Service_Design_a_Thing - Nicole - [x] https://gds.blog.gov.uk/2016/04/18/what-we-mean-by-service-design/ - Taylor - [x] https://www.interaction-design.org/literature/topics/service-design - Bryan - [x] https://uxplanet.org/service-design-is-everywhere-a58fd5901e63 - Dan - [x] https://careerfoundry.com/en/blog/ux-design/what-is-service-design-how-to-implement-service-design-processes/ - Nicole - [x] https://cio-wiki.org/wiki/ITIL_Service_Design#:~:text=The%20scope%20of%20Service%20Design,conformance%20to%20standards%20and%20regulations. - Taylor - [x] https://www.interaction-design.org/literature/article/the-principles-of-service-design-thinking-building-better-services - Bryan - [x] http://www.practicalservicedesign.com/service-design-101 - Bryan ## Acceptance Criteria - [ ] Takeaways and learnings recorded in Mural for workshop ## Deadline - April 6th ",1,research industry standards and approaches issue description analyze best practices across industry and record learnings in mural tasks dan nicole taylor bryan dan nicole taylor bryan bryan acceptance criteria takeaways and learnings recorded in mural for workshop deadline april ,1 93733,11801511870.0,IssuesEvent,2020-03-18 19:36:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Link to urgent care benefit webpage,content-ia-team design frontend vsa vsa-facilities,"## User Story: - As a Veteran, I need to understand my urgent care benefits so that I can receive care without out of pocket cost. ## Objectives or Key Results this is meant to further - Improve the Veteran Search Experience (Veterans have the information they need to be prepared for an urgent care visit. ) - Community Care Implementation ## Tasks [ ] Add Alert to display between search boxes and map when 1. Facility type = ""Urgent care"" and Service type drop down= ""Community urgent care providers (in VA’s network)"" 2. Facility type= ""Community pharmacies (in VA’s network)"", [ ] Add alert text (similar to style in image below, **but with the following text**: > **Important information about your Community Care appointment** > Click below to learn how to prepare for your urgent care appointment with a Community Care provider. > {button} Learn about VA urgent care benefit [ ] Add button to link to webpage [ ] Add placeholder link: https://www.va.gov/COMMUNITYCARE/programs/veterans/UrgentCareInstructions.asp [ ] Get facility IDs to call for link ![image](https://user-images.githubusercontent.com/55411834/74374169-becea880-4d92-11ea-8b81-3f68a1a6df46.png) **** ## Acceptance Criteria: [ ] Veterans using assistive technology can access link to eligibility info. [ ]When search parameters for **Facility type** = ""Urgent care"" and Service type drop down= ""VA urgent care"", alert **is not** displayed. [ ] When search parameters for **Facility type** = ""Urgent care"" and Service type drop down= ""Community urgent care providers (in VA’s network)"", alert and link to eligibility web page **are** displayed. [ ] When search parameters for **Facility type** = ""Community pharmacies (in VA’s network)"", alert and link to eligibility web page *are** displayed. [ ] Alert displays between search boxes and map and with the following language: > **Important information about your Community Care appointment** > Click below to learn how to prepare for your urgent care appointment with a Community Care provider. > {button} Learn about VA urgent care benefit [ ] Alert displays with button which links to new webpage ",1.0,"Link to urgent care benefit webpage - ## User Story: - As a Veteran, I need to understand my urgent care benefits so that I can receive care without out of pocket cost. ## Objectives or Key Results this is meant to further - Improve the Veteran Search Experience (Veterans have the information they need to be prepared for an urgent care visit. ) - Community Care Implementation ## Tasks [ ] Add Alert to display between search boxes and map when 1. Facility type = ""Urgent care"" and Service type drop down= ""Community urgent care providers (in VA’s network)"" 2. Facility type= ""Community pharmacies (in VA’s network)"", [ ] Add alert text (similar to style in image below, **but with the following text**: > **Important information about your Community Care appointment** > Click below to learn how to prepare for your urgent care appointment with a Community Care provider. > {button} Learn about VA urgent care benefit [ ] Add button to link to webpage [ ] Add placeholder link: https://www.va.gov/COMMUNITYCARE/programs/veterans/UrgentCareInstructions.asp [ ] Get facility IDs to call for link ![image](https://user-images.githubusercontent.com/55411834/74374169-becea880-4d92-11ea-8b81-3f68a1a6df46.png) **** ## Acceptance Criteria: [ ] Veterans using assistive technology can access link to eligibility info. [ ]When search parameters for **Facility type** = ""Urgent care"" and Service type drop down= ""VA urgent care"", alert **is not** displayed. [ ] When search parameters for **Facility type** = ""Urgent care"" and Service type drop down= ""Community urgent care providers (in VA’s network)"", alert and link to eligibility web page **are** displayed. [ ] When search parameters for **Facility type** = ""Community pharmacies (in VA’s network)"", alert and link to eligibility web page *are** displayed. [ ] Alert displays between search boxes and map and with the following language: > **Important information about your Community Care appointment** > Click below to learn how to prepare for your urgent care appointment with a Community Care provider. > {button} Learn about VA urgent care benefit [ ] Alert displays with button which links to new webpage ",1,link to urgent care benefit webpage user story as a veteran i need to understand my urgent care benefits so that i can receive care without out of pocket cost objectives or key results this is meant to further improve the veteran search experience veterans have the information they need to be prepared for an urgent care visit community care implementation tasks add alert to display between search boxes and map when facility type urgent care and service type drop down community urgent care providers in va’s network facility type community pharmacies in va’s network add alert text similar to style in image below but with the following text important information about your community care appointment click below to learn how to prepare for your urgent care appointment with a community care provider button learn about va urgent care benefit add button to link to webpage add placeholder link get facility ids to call for link acceptance criteria veterans using assistive technology can access link to eligibility info when search parameters for facility type urgent care and service type drop down va urgent care alert is not displayed when search parameters for facility type urgent care and service type drop down community urgent care providers in va’s network alert and link to eligibility web page are displayed when search parameters for facility type community pharmacies in va’s network alert and link to eligibility web page are displayed alert displays between search boxes and map and with the following language important information about your community care appointment click below to learn how to prepare for your urgent care appointment with a community care provider button learn about va urgent care benefit alert displays with button which links to new webpage ,1 87331,10889597600.0,IssuesEvent,2019-11-18 18:35:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] View All Contested Issues,HLR design vsa-benefits vsa-decision-reviews,"## User Story or Problem Statement As a claimant, I need to view all of my contested issues in a single location so I can be sure what issues I have contested. ## Goal _A user is able to see all of their contested issues on a single page_ ## Tasks - [ ] _Identify if a page with all contested issues already exists_ - [ ] *If not,* design a page that displays all contested issues ## Acceptance Criteria Scenario: A Veteran wants to see all of their contested issues, not just ones applicable for a Higher Level Review GIVEN a system user is logged into va.gov WHEN the user selects to view all of their contested issues THEN the system directs them to a page that has all of the contested issues listed",1.0,"[Design] View All Contested Issues - ## User Story or Problem Statement As a claimant, I need to view all of my contested issues in a single location so I can be sure what issues I have contested. ## Goal _A user is able to see all of their contested issues on a single page_ ## Tasks - [ ] _Identify if a page with all contested issues already exists_ - [ ] *If not,* design a page that displays all contested issues ## Acceptance Criteria Scenario: A Veteran wants to see all of their contested issues, not just ones applicable for a Higher Level Review GIVEN a system user is logged into va.gov WHEN the user selects to view all of their contested issues THEN the system directs them to a page that has all of the contested issues listed",1, view all contested issues user story or problem statement as a claimant i need to view all of my contested issues in a single location so i can be sure what issues i have contested goal a user is able to see all of their contested issues on a single page tasks identify if a page with all contested issues already exists if not design a page that displays all contested issues acceptance criteria scenario a veteran wants to see all of their contested issues not just ones applicable for a higher level review given a system user is logged into va gov when the user selects to view all of their contested issues then the system directs them to a page that has all of the contested issues listed,1 133594,18910340579.0,IssuesEvent,2021-11-16 13:31:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Edits and Documentation of Authenticated Info List Pattern,design vsa-claims-appeals,"## Issue Description We need to get the authenticated info list pattern ready for consideration into the experimental design system and make necessary changes. --- ## Tasks - [x] Address feedback from accessibility team - [x] Document the pattern per the design system's request ## Acceptance Criteria - [x] Designs have been changed per accessibility's feedback and uploaded to GH - [x] Pattern has been documented in GH and updated design examples have been uploaded --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1.0,"Edits and Documentation of Authenticated Info List Pattern - ## Issue Description We need to get the authenticated info list pattern ready for consideration into the experimental design system and make necessary changes. --- ## Tasks - [x] Address feedback from accessibility team - [x] Document the pattern per the design system's request ## Acceptance Criteria - [x] Designs have been changed per accessibility's feedback and uploaded to GH - [x] Pattern has been documented in GH and updated design examples have been uploaded --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1,edits and documentation of authenticated info list pattern issue description we need to get the authenticated info list pattern ready for consideration into the experimental design system and make necessary changes tasks address feedback from accessibility team document the pattern per the design system s request acceptance criteria designs have been changed per accessibility s feedback and uploaded to gh pattern has been documented in gh and updated design examples have been uploaded how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 145531,22708360742.0,IssuesEvent,2022-07-05 16:37:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyHealth Messages FAQ unauth desktop,design myhealth myhealth-groundwork,Create the desktop design for MyHealth messages FAQ page. Please drop the link to the prototype into a comment in this ticket.,1.0,[Design] MyHealth Messages FAQ unauth desktop - Create the desktop design for MyHealth messages FAQ page. Please drop the link to the prototype into a comment in this ticket.,1, myhealth messages faq unauth desktop create the desktop design for myhealth messages faq page please drop the link to the prototype into a comment in this ticket ,1 112300,14237366788.0,IssuesEvent,2020-11-18 17:07:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Direct deposit for edu: Add state for if someone is eligible for only one type of direct deposit but not the other,design direct deposit profile vsa-authenticated-exp vsa-ebenefits,"## Background Most of the [direct deposit for edu designs](https://xd.adobe.com/view/532272b2-b423-4e1b-a8c6-d1a583da3d37-0671/) are done. However, I just realized we don't have a state that shows what this page looks like if someone only is eligible for one type of direct deposit but not the other. [These designs](https://xd.adobe.com/view/532272b2-b423-4e1b-a8c6-d1a583da3d37-0671/screen/c47baced-0945-46f1-a01b-5e7df4662eda) show what it would look like if someone is eligible for BOTH types of direct deposit but has only added info for one. But we still need designs for if someone is only eligible for one type of direct deposit but not the other. For this state, our options are: - Don't show the direct deposit block for the benefit type for which someone is not eligible (eg. if someone is only eligible for direct deposit for edu but not direct deposit for comp & pen, we don't show the comp & pen block at all). - Show both blocks. For the ""eligible"" block, we'll show the add/edit state depending on what applies. For whatever benefit someone is not eligible for direct deposit payment (aka they just don't receive this kind of payment from the VA), we put messaging in the block that explains that this person does not receive either comp & pen or edu payments (depending on which benefit), and maybe a link to that benefit hub landing page to explore that benefit. ## Tasks - [x] Decide on approach. - [x] Review approach with Samara/Tressa/Cassandra - [x] Mockups - [ ] Copy review, if applicable ## Acceptance Criteria - [ ] Provide an updated mockup to Samara - [ ] Request copy feedback from Peggy ",1.0,"[Design] Direct deposit for edu: Add state for if someone is eligible for only one type of direct deposit but not the other - ## Background Most of the [direct deposit for edu designs](https://xd.adobe.com/view/532272b2-b423-4e1b-a8c6-d1a583da3d37-0671/) are done. However, I just realized we don't have a state that shows what this page looks like if someone only is eligible for one type of direct deposit but not the other. [These designs](https://xd.adobe.com/view/532272b2-b423-4e1b-a8c6-d1a583da3d37-0671/screen/c47baced-0945-46f1-a01b-5e7df4662eda) show what it would look like if someone is eligible for BOTH types of direct deposit but has only added info for one. But we still need designs for if someone is only eligible for one type of direct deposit but not the other. For this state, our options are: - Don't show the direct deposit block for the benefit type for which someone is not eligible (eg. if someone is only eligible for direct deposit for edu but not direct deposit for comp & pen, we don't show the comp & pen block at all). - Show both blocks. For the ""eligible"" block, we'll show the add/edit state depending on what applies. For whatever benefit someone is not eligible for direct deposit payment (aka they just don't receive this kind of payment from the VA), we put messaging in the block that explains that this person does not receive either comp & pen or edu payments (depending on which benefit), and maybe a link to that benefit hub landing page to explore that benefit. ## Tasks - [x] Decide on approach. - [x] Review approach with Samara/Tressa/Cassandra - [x] Mockups - [ ] Copy review, if applicable ## Acceptance Criteria - [ ] Provide an updated mockup to Samara - [ ] Request copy feedback from Peggy ",1, direct deposit for edu add state for if someone is eligible for only one type of direct deposit but not the other background most of the are done however i just realized we don t have a state that shows what this page looks like if someone only is eligible for one type of direct deposit but not the other show what it would look like if someone is eligible for both types of direct deposit but has only added info for one but we still need designs for if someone is only eligible for one type of direct deposit but not the other for this state our options are don t show the direct deposit block for the benefit type for which someone is not eligible eg if someone is only eligible for direct deposit for edu but not direct deposit for comp pen we don t show the comp pen block at all show both blocks for the eligible block we ll show the add edit state depending on what applies for whatever benefit someone is not eligible for direct deposit payment aka they just don t receive this kind of payment from the va we put messaging in the block that explains that this person does not receive either comp pen or edu payments depending on which benefit and maybe a link to that benefit hub landing page to explore that benefit tasks decide on approach review approach with samara tressa cassandra mockups copy review if applicable acceptance criteria provide an updated mockup to samara request copy feedback from peggy ,1 111586,14111493895.0,IssuesEvent,2020-11-07 00:26:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,(HOLD) CC request card styles update,design frontend needs-grooming vaos,"## Issue Description Clean up styles of community care provider information on request card displayed on homepage --- ## Acceptance Criteria - [ ] DESIGN - All desktop, tablet, and mobile designs match the specs **_LINK TBD_** ",1.0,"(HOLD) CC request card styles update - ## Issue Description Clean up styles of community care provider information on request card displayed on homepage --- ## Acceptance Criteria - [ ] DESIGN - All desktop, tablet, and mobile designs match the specs **_LINK TBD_** ",1, hold cc request card styles update issue description clean up styles of community care provider information on request card displayed on homepage acceptance criteria design all desktop tablet and mobile designs match the specs link tbd ,1 165886,26247567808.0,IssuesEvent,2023-01-05 16:24:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Ongoing Service] - FY2023 Q1 - Provide Service Design support to Platform teams,Epic service-design,"### **Problem Statement** ### VSP teams often need SD support to examine their services or offerings. How might we offer support on an ongoing basis? ### **Sample Services** ### Collaboration on shared projects/endeavors Feedback on Communications Feedback on new tools and services Research Requests Mapping requests",1.0,"[Ongoing Service] - FY2023 Q1 - Provide Service Design support to Platform teams - ### **Problem Statement** ### VSP teams often need SD support to examine their services or offerings. How might we offer support on an ongoing basis? ### **Sample Services** ### Collaboration on shared projects/endeavors Feedback on Communications Feedback on new tools and services Research Requests Mapping requests",1, provide service design support to platform teams problem statement vsp teams often need sd support to examine their services or offerings how might we offer support on an ongoing basis sample services collaboration on shared projects endeavors feedback on communications feedback on new tools and services research requests mapping requests,1 143620,22106307568.0,IssuesEvent,2022-06-01 17:18:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Add instructions to guidance for internal Survey launch steps,service-design,"## Issue Description Need a reminder to adjust page content dependent upon Survey status https://vfs.atlassian.net/wiki/spaces/SDT/pages/1445724309/How-to+Launch+the+Platform+Satisfaction+Survey --- ## Tasks - [ ] Add instructions for updating the Platform page both when Survey goes live and when it closes out. ## Acceptance Criteria - [ ] Confluence instructions are updated.",1.0,"Add instructions to guidance for internal Survey launch steps - ## Issue Description Need a reminder to adjust page content dependent upon Survey status https://vfs.atlassian.net/wiki/spaces/SDT/pages/1445724309/How-to+Launch+the+Platform+Satisfaction+Survey --- ## Tasks - [ ] Add instructions for updating the Platform page both when Survey goes live and when it closes out. ## Acceptance Criteria - [ ] Confluence instructions are updated.",1,add instructions to guidance for internal survey launch steps issue description need a reminder to adjust page content dependent upon survey status tasks add instructions for updating the platform page both when survey goes live and when it closes out acceptance criteria confluence instructions are updated ,1 140243,21050218362.0,IssuesEvent,2022-03-31 19:52:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Editing Edge Cases: Time expired (after midnight) up until their appointment time with valid link,design ux HCE-Checkin,"# Description A Veteran attempts to pre-check-in after 12:00am on the day of their appointment. We need a messaging to let user know that they can no longer complete pre-check-in prior to their appointment. - Engineering isn’t track this currently, but they can (per Adrian). If they can, there should be a specific message related to the use case. # Tasks - [ ] Create new content and designs in Sketch - [ ] Review with content # Acceptance Criteria - [ ] Review final designs with product and UX - [ ] Create FE ticket for this new scenario (i.e. midnight to appointment time on day of appointment)",1.0,"[Design] Editing Edge Cases: Time expired (after midnight) up until their appointment time with valid link - # Description A Veteran attempts to pre-check-in after 12:00am on the day of their appointment. We need a messaging to let user know that they can no longer complete pre-check-in prior to their appointment. - Engineering isn’t track this currently, but they can (per Adrian). If they can, there should be a specific message related to the use case. # Tasks - [ ] Create new content and designs in Sketch - [ ] Review with content # Acceptance Criteria - [ ] Review final designs with product and UX - [ ] Create FE ticket for this new scenario (i.e. midnight to appointment time on day of appointment)",1, editing edge cases time expired after midnight up until their appointment time with valid link description a veteran attempts to pre check in after on the day of their appointment we need a messaging to let user know that they can no longer complete pre check in prior to their appointment engineering isn’t track this currently but they can per adrian if they can there should be a specific message related to the use case tasks create new content and designs in sketch review with content acceptance criteria review final designs with product and ux create fe ticket for this new scenario i e midnight to appointment time on day of appointment ,1 139882,20979668828.0,IssuesEvent,2022-03-28 18:34:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Include Pain Point Artifact Research in Feedback Themes ,service-design,"## Issue Description _We previously did research for the pain point artifact work we did. We learned lots of great information that can be included in the [feedback themes doc](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1645655432415/26f1766bc490b410bff347eb2d97e4904d090f79?sender=u9ea6bd3ca12795949b606150)._ --- ## Tasks - [x] _Comb through all findings from the workshops for the pain point artifact and add them to the feedback themes doc that we provide to Platform teams_ ## Acceptance Criteria - [x] _Findings from pain point artifacts workshop are included in feedback themes_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Include Pain Point Artifact Research in Feedback Themes - ## Issue Description _We previously did research for the pain point artifact work we did. We learned lots of great information that can be included in the [feedback themes doc](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1645655432415/26f1766bc490b410bff347eb2d97e4904d090f79?sender=u9ea6bd3ca12795949b606150)._ --- ## Tasks - [x] _Comb through all findings from the workshops for the pain point artifact and add them to the feedback themes doc that we provide to Platform teams_ ## Acceptance Criteria - [x] _Findings from pain point artifacts workshop are included in feedback themes_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,include pain point artifact research in feedback themes issue description we previously did research for the pain point artifact work we did we learned lots of great information that can be included in the tasks comb through all findings from the workshops for the pain point artifact and add them to the feedback themes doc that we provide to platform teams acceptance criteria findings from pain point artifacts workshop are included in feedback themes how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 134835,19377165471.0,IssuesEvent,2021-12-17 00:05:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Remove date-fns from MaintenanceBanner,frontend vsp-design-system-team,"## Background A few things lead to this: 1. We use `date-fns` in the `MaintenanceBanner` component 2. This leads to using vanilla `Date` objects and `date-fns` in [maintenanceBanner.js](https://github.com/department-of-veterans-affairs/vets-website/blob/direct-deposit-review-fix-cv/src/platform/site-wide/banners/config/maintenanceBanner.js#L2) 3. That :point_up: module is included for the bundle on every page - I'm pretty sure this is true, but haven't traced it back yet 4. Whenever we use `date-fns`, we can't get Webpack to tree-shake the library properly, so the entire library is included rather than just the desired functions The end result is that we're including the entire `date-fns` library on every page. --- ## Tasks - [ ] Remove `date-fns` from the `MaintenanceBanner` ## Acceptance Criteria - [ ] The `component-library` repo does not have `date-fns` or `date-fns-tz` ad dependencies ## Followup - Update `maintenanceBanner.js` to not use `date-fns`",1.0,"Remove date-fns from MaintenanceBanner - ## Background A few things lead to this: 1. We use `date-fns` in the `MaintenanceBanner` component 2. This leads to using vanilla `Date` objects and `date-fns` in [maintenanceBanner.js](https://github.com/department-of-veterans-affairs/vets-website/blob/direct-deposit-review-fix-cv/src/platform/site-wide/banners/config/maintenanceBanner.js#L2) 3. That :point_up: module is included for the bundle on every page - I'm pretty sure this is true, but haven't traced it back yet 4. Whenever we use `date-fns`, we can't get Webpack to tree-shake the library properly, so the entire library is included rather than just the desired functions The end result is that we're including the entire `date-fns` library on every page. --- ## Tasks - [ ] Remove `date-fns` from the `MaintenanceBanner` ## Acceptance Criteria - [ ] The `component-library` repo does not have `date-fns` or `date-fns-tz` ad dependencies ## Followup - Update `maintenanceBanner.js` to not use `date-fns`",1,remove date fns from maintenancebanner background a few things lead to this we use date fns in the maintenancebanner component this leads to using vanilla date objects and date fns in that point up module is included for the bundle on every page i m pretty sure this is true but haven t traced it back yet whenever we use date fns we can t get webpack to tree shake the library properly so the entire library is included rather than just the desired functions the end result is that we re including the entire date fns library on every page tasks remove date fns from the maintenancebanner acceptance criteria the component library repo does not have date fns or date fns tz ad dependencies followup update maintenancebanner js to not use date fns ,1 93808,11809770639.0,IssuesEvent,2020-03-19 15:27:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Cancel Modal for Cerner site(s) from Appointment homepage,content design frontend vaos,"As a Veteran, I need to be redirected to my ""My VA Health"" portal to cancel appointments that are at registered Cerner sites (ex - Columbus or Spokane) from the VAOS Appointments homepage. --- ## Acceptance Criteria - [ ] When user clicks 'cancel' for Cerner-site appointments, ""Cancel modal"" alerts user that appointment cannot be canceled in VAOS and that user must cancel in their My VA Health Portal - [ ] Add Button that says ""Go to My VA Health"" that directs user to their My VA Health Portal - [ ] This specific cancel modal and button should show for all Cerner sites' appointments only",1.0,"Cancel Modal for Cerner site(s) from Appointment homepage - As a Veteran, I need to be redirected to my ""My VA Health"" portal to cancel appointments that are at registered Cerner sites (ex - Columbus or Spokane) from the VAOS Appointments homepage. --- ## Acceptance Criteria - [ ] When user clicks 'cancel' for Cerner-site appointments, ""Cancel modal"" alerts user that appointment cannot be canceled in VAOS and that user must cancel in their My VA Health Portal - [ ] Add Button that says ""Go to My VA Health"" that directs user to their My VA Health Portal - [ ] This specific cancel modal and button should show for all Cerner sites' appointments only",1,cancel modal for cerner site s from appointment homepage as a veteran i need to be redirected to my my va health portal to cancel appointments that are at registered cerner sites ex columbus or spokane from the vaos appointments homepage acceptance criteria when user clicks cancel for cerner site appointments cancel modal alerts user that appointment cannot be canceled in vaos and that user must cancel in their my va health portal add button that says go to my va health that directs user to their my va health portal this specific cancel modal and button should show for all cerner sites appointments only,1 99206,12406046081.0,IssuesEvent,2020-05-21 18:24:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Update DD Header,design needs-grooming profile vsa-authenticated-exp,"## Background The current direct deposit header is very long - especially on mobile. We need to update the copy (if possible) so it's not so long. Epic #2086 ## Current copy ![Screen Shot 2020-05-21 at 10.01.21 AM.png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/c5dce00b-0b55-415c-821c-16a63656ab2e) Direct deposit information for disability compensation and pension benefits ## Tasks - [ ] Update copy - [ ] Implement correct copy. ## Acceptance criteria - [ ] All mocks have been updated",1.0,"[Design] Update DD Header - ## Background The current direct deposit header is very long - especially on mobile. We need to update the copy (if possible) so it's not so long. Epic #2086 ## Current copy ![Screen Shot 2020-05-21 at 10.01.21 AM.png](https://images.zenhubusercontent.com/5dfa65bbbd078d1699e52294/c5dce00b-0b55-415c-821c-16a63656ab2e) Direct deposit information for disability compensation and pension benefits ## Tasks - [ ] Update copy - [ ] Implement correct copy. ## Acceptance criteria - [ ] All mocks have been updated",1, update dd header background the current direct deposit header is very long especially on mobile we need to update the copy if possible so it s not so long epic current copy direct deposit information for disability compensation and pension benefits tasks update copy implement correct copy acceptance criteria all mocks have been updated,1 181883,30753965632.0,IssuesEvent,2023-07-28 22:42:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Appointment List Content Review from VAOS (VA Online Scheduling) ,ux appointments-product-design,"## What does your team need support for? Check all that apply. - [ ] Launching one or more new unauthenticated (static) VA.gov pages - [ ] Making revisions to one or more existing unauthenticated (static) VA.gov page - [ ] Launching a new online form, app, or tool on VA.gov - [X] Making revisions to an existing online form, app, or tool on VA.gov - [ ] Something else (please add details in the next question) ## What do you need help with? - [X] Content support - [ ] IA support *Please describe your need and provide any additional documents and/or links that will help us help you. If we need to add a react widget to a page, be sure to provide the code here.* ## Will this new product be released incrementally (for instance 25% of users initially)? - [ ] Yes - [ ] No **Note:** If you checked yes, we'll reach out to discuss details about the content in the react widget. ## When do you expect to launch your product to 100% of users? --- ## Supporting artifacts ### **Appointment display breakdown** Here is how an appointment is broken down within the appointment list: #### **Data fields for each appointment:** **Date** - Date of the appointment - (##) **Day** - Day of the appointment - (Mon, Tue, Wed, Thu, Fri, Sat, Sun) **Time** - Time of the appointment - (00:00 am/pm PST/EST) **Type of care** - What the appointment is for - (Primary care, Mental Health, etc.) **Provider** - Who the appointment is with - (Dr. Johnathan Schmidt) **Modality** - How the appointment will be attended - ( :office: In person, :telephone_receiver: Phone call, :movie_camera: Video) **Place** - Where is the appointment - (Vancouver VA Medical Center) **Details link** - Indication that more info can be found by clicking here - (Details) #### **How data is grouped:** Grouped information will be in sentence form allowing for gaps in data availability **Date | Day** - (8 Mon) **Time** - (00:00 am/pm PST/EST) **Type of care | Provider** - *sentence form* (Primary Care with Rebecca Jones) **Modality | Place** - *sentence form* (:office: In person at Vancouver VA Medical Center) **Details link** - (Details) #### **What if data is missing?** In some cases, there is data that is not provided, or unavailable to veterans. There are a few ways that could be displayed **Date** - Date will always be available for upcoming and past and canceled appointments. **Day** - Day will always be available for upcoming and past and canceled appointments. **Time** - Time will always be available for upcoming and past and canceled appointments. **Type of care** - When type of care is not available, “VA appointment” will take its place (this is how it currently is on va.gov). **Provider** - Provider left blank when provider information is unavailable. **Modality** - The only case where modality is unavailable, is community care. “:office: Community care” will take its place. **Place** - Place left blank when provider information is unavailable. **Details link** - Details link will always be available for all appointments. ### **How these will look in appointment list** #### **When all info is available** In this case, every piece of data is available to display on appt list. ![Screen Shot 2022-08-04 at 9.42.05 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/925074f3-1d5f-4bae-9790-39c089f15f44) #### **Type of care Unavailable** When type of care data is unavailable, “VA appointment” will take its place (this is how it currently is on va.gov). If it is a CC appt, it would read “community care” ![Screen Shot 2022-08-04 at 9.42.13 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/8a059937-f908-4070-911a-9d6adb8136d6) #### **Type of care and Provider unavailable** When type of care data is unavailable, “VA appointment” will take its place (this is how it currently is on va.gov). If it is a CC appt, it would read “community care”. When provider info is unavailable, that area is left blank. ![Screen Shot 2022-08-04 at 9.42.22 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/2a1b4c0e-b3eb-4754-be2d-d6496cea6ec7) #### **Type of care, Provider and place unavailable** When type of care data is unavailable, “VA appointment” will take its place (this is how it currently is on va.gov). If it is a CC appt, it would read “community care”. Provider left blank when unavailable. Place left plank when unavailable. ![Screen Shot 2022-08-04 at 9.42.32 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/66a5a929-e492-4ced-bc36-1934d67dbcc4) --- ## Will this work be going through the Collaboration Cycle? - [ ] Yes - [ ] No ## When does this work need to be done? - Estimated launch date: - Estimated staging review date: - Content and IA work needed by: ## Do you plan to bring this to an upcoming content office hours session? - [ ] Yes, benefit content office hours (Thursdays, 3:00 p.m. to 3:45 p.m. ET) - [ ] Yes, health content office hours (Thursdays, 11:00 a.m. to 11:30 a.m. ET) - [ ] Yes, unauth office hours (Mondays, 11:00 a.m. to 11:30 a.m. ET) - [ ] No, but I'd like to schedule time to talk about this request - [ ] No, let's work asynchronously and meet if needed **Note:** If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet. ## About your team - Team name: VAOS (VA Online Scheduling) - OCTO-DE product owner: Lauren Alexanderson - Product manager: Leah De La Costa and Jeff Roof - Designer: Peter Russo and Cierra Maddox - FE engineer: Simi Adebowale - Product/team Slack channel: #vaos-team ## Next steps **Once you’ve submitted this ticket, please post a link to this issue in the [#va-sitewide-content-ia](https://dsva.slack.com/channels/va-sitewide-content-ia) Slack channel and tag Randi Hecht.** If you also need engineering support from the Public Websites team, fill out their [intake request form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E). If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a [Redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=mnorthuis&labels=ia&template=redirect-request.md&title=Redirect+Request) ",1.0,"Appointment List Content Review from VAOS (VA Online Scheduling) - ## What does your team need support for? Check all that apply. - [ ] Launching one or more new unauthenticated (static) VA.gov pages - [ ] Making revisions to one or more existing unauthenticated (static) VA.gov page - [ ] Launching a new online form, app, or tool on VA.gov - [X] Making revisions to an existing online form, app, or tool on VA.gov - [ ] Something else (please add details in the next question) ## What do you need help with? - [X] Content support - [ ] IA support *Please describe your need and provide any additional documents and/or links that will help us help you. If we need to add a react widget to a page, be sure to provide the code here.* ## Will this new product be released incrementally (for instance 25% of users initially)? - [ ] Yes - [ ] No **Note:** If you checked yes, we'll reach out to discuss details about the content in the react widget. ## When do you expect to launch your product to 100% of users? --- ## Supporting artifacts ### **Appointment display breakdown** Here is how an appointment is broken down within the appointment list: #### **Data fields for each appointment:** **Date** - Date of the appointment - (##) **Day** - Day of the appointment - (Mon, Tue, Wed, Thu, Fri, Sat, Sun) **Time** - Time of the appointment - (00:00 am/pm PST/EST) **Type of care** - What the appointment is for - (Primary care, Mental Health, etc.) **Provider** - Who the appointment is with - (Dr. Johnathan Schmidt) **Modality** - How the appointment will be attended - ( :office: In person, :telephone_receiver: Phone call, :movie_camera: Video) **Place** - Where is the appointment - (Vancouver VA Medical Center) **Details link** - Indication that more info can be found by clicking here - (Details) #### **How data is grouped:** Grouped information will be in sentence form allowing for gaps in data availability **Date | Day** - (8 Mon) **Time** - (00:00 am/pm PST/EST) **Type of care | Provider** - *sentence form* (Primary Care with Rebecca Jones) **Modality | Place** - *sentence form* (:office: In person at Vancouver VA Medical Center) **Details link** - (Details) #### **What if data is missing?** In some cases, there is data that is not provided, or unavailable to veterans. There are a few ways that could be displayed **Date** - Date will always be available for upcoming and past and canceled appointments. **Day** - Day will always be available for upcoming and past and canceled appointments. **Time** - Time will always be available for upcoming and past and canceled appointments. **Type of care** - When type of care is not available, “VA appointment” will take its place (this is how it currently is on va.gov). **Provider** - Provider left blank when provider information is unavailable. **Modality** - The only case where modality is unavailable, is community care. “:office: Community care” will take its place. **Place** - Place left blank when provider information is unavailable. **Details link** - Details link will always be available for all appointments. ### **How these will look in appointment list** #### **When all info is available** In this case, every piece of data is available to display on appt list. ![Screen Shot 2022-08-04 at 9.42.05 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/925074f3-1d5f-4bae-9790-39c089f15f44) #### **Type of care Unavailable** When type of care data is unavailable, “VA appointment” will take its place (this is how it currently is on va.gov). If it is a CC appt, it would read “community care” ![Screen Shot 2022-08-04 at 9.42.13 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/8a059937-f908-4070-911a-9d6adb8136d6) #### **Type of care and Provider unavailable** When type of care data is unavailable, “VA appointment” will take its place (this is how it currently is on va.gov). If it is a CC appt, it would read “community care”. When provider info is unavailable, that area is left blank. ![Screen Shot 2022-08-04 at 9.42.22 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/2a1b4c0e-b3eb-4754-be2d-d6496cea6ec7) #### **Type of care, Provider and place unavailable** When type of care data is unavailable, “VA appointment” will take its place (this is how it currently is on va.gov). If it is a CC appt, it would read “community care”. Provider left blank when unavailable. Place left plank when unavailable. ![Screen Shot 2022-08-04 at 9.42.32 AM.png](https://images.zenhubusercontent.com/618c20406719b91000e30ee6/66a5a929-e492-4ced-bc36-1934d67dbcc4) --- ## Will this work be going through the Collaboration Cycle? - [ ] Yes - [ ] No ## When does this work need to be done? - Estimated launch date: - Estimated staging review date: - Content and IA work needed by: ## Do you plan to bring this to an upcoming content office hours session? - [ ] Yes, benefit content office hours (Thursdays, 3:00 p.m. to 3:45 p.m. ET) - [ ] Yes, health content office hours (Thursdays, 11:00 a.m. to 11:30 a.m. ET) - [ ] Yes, unauth office hours (Mondays, 11:00 a.m. to 11:30 a.m. ET) - [ ] No, but I'd like to schedule time to talk about this request - [ ] No, let's work asynchronously and meet if needed **Note:** If we think this work would benefit from a collaborative session with you, we may ask you to bring it to office hours or set up a separate time to meet. ## About your team - Team name: VAOS (VA Online Scheduling) - OCTO-DE product owner: Lauren Alexanderson - Product manager: Leah De La Costa and Jeff Roof - Designer: Peter Russo and Cierra Maddox - FE engineer: Simi Adebowale - Product/team Slack channel: #vaos-team ## Next steps **Once you’ve submitted this ticket, please post a link to this issue in the [#va-sitewide-content-ia](https://dsva.slack.com/channels/va-sitewide-content-ia) Slack channel and tag Randi Hecht.** If you also need engineering support from the Public Websites team, fill out their [intake request form](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=Public+Websites%2C+Sitewide+content&labels=vsa-public-websites%2C+vsa%2C+vsa-public-websites-intake%2C+sitewide-content%2C+needs-grooming&template=public-websites-intake.md&title=%3CType+of+Request%3E+from+%3CTeam%3E). If you need a page/URL redirected, a URL changed or a vanity URL set up, please submit a [Redirect, URL change, or vanity URL request](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new?assignees=mnorthuis&labels=ia&template=redirect-request.md&title=Redirect+Request) ",1,appointment list content review from vaos va online scheduling what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with content support ia support please describe your need and provide any additional documents and or links that will help us help you if we need to add a react widget to a page be sure to provide the code here will this new product be released incrementally for instance of users initially yes no note if you checked yes we ll reach out to discuss details about the content in the react widget when do you expect to launch your product to of users supporting artifacts appointment display breakdown here is how an appointment is broken down within the appointment list data fields for each appointment date date of the appointment day day of the appointment mon tue wed thu fri sat sun time time of the appointment am pm pst est type of care what the appointment is for primary care mental health etc provider who the appointment is with dr johnathan schmidt modality how the appointment will be attended office in person telephone receiver phone call movie camera video place where is the appointment vancouver va medical center details link indication that more info can be found by clicking here details how data is grouped grouped information will be in sentence form allowing for gaps in data availability date day mon time am pm pst est type of care provider sentence form primary care with rebecca jones modality place sentence form office in person at vancouver va medical center details link details what if data is missing in some cases there is data that is not provided or unavailable to veterans there are a few ways that could be displayed date date will always be available for upcoming and past and canceled appointments day day will always be available for upcoming and past and canceled appointments time time will always be available for upcoming and past and canceled appointments type of care when type of care is not available “va appointment” will take its place this is how it currently is on va gov provider provider left blank when provider information is unavailable modality the only case where modality is unavailable is community care “ office community care” will take its place place place left blank when provider information is unavailable details link details link will always be available for all appointments how these will look in appointment list when all info is available in this case every piece of data is available to display on appt list type of care unavailable when type of care data is unavailable “va appointment” will take its place this is how it currently is on va gov if it is a cc appt it would read “community care” type of care and provider unavailable when type of care data is unavailable “va appointment” will take its place this is how it currently is on va gov if it is a cc appt it would read “community care” when provider info is unavailable that area is left blank type of care provider and place unavailable when type of care data is unavailable “va appointment” will take its place this is how it currently is on va gov if it is a cc appt it would read “community care” provider left blank when unavailable place left plank when unavailable will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date estimated staging review date content and ia work needed by do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name vaos va online scheduling octo de product owner lauren alexanderson product manager leah de la costa and jeff roof designer peter russo and cierra maddox fe engineer simi adebowale product team slack channel vaos team next steps once you’ve submitted this ticket please post a link to this issue in the  slack channel and tag randi hecht if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 184081,31816902365.0,IssuesEvent,2023-09-13 21:15:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[UX][Design] DS v3 #4: Update additional info components,design ux HCE-Checkin,"## Background Design System v3 Components have been prioritized in the [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010). Additional info components also need to be updated as part of the v3 switch. ## Tasks - [ ] **Update the Design pages in the ** **Unified check-in**, **Check-in**, and **Pre-Check-in** **files** - [ ] Identify screens that use additional info components - [ ] Update the corresponding symbols in these files with the new Component Library Sketch component (see ticket [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010) for more info on setting up the new Sketch library) - [ ] Check all Design page boards to make sure they're updated in case of detached symbols - [ ] **Sync with FE engineers** to make sure they're all set on toggling the additional info component to the new version ## Acceptance Criteria - [ ] Additional info components are updated in unified, Check-in, and Pre-Check-in Design page files - [ ] FE is set to toggle to v3 of this component",1.0,"[UX][Design] DS v3 #4: Update additional info components - ## Background Design System v3 Components have been prioritized in the [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010). Additional info components also need to be updated as part of the v3 switch. ## Tasks - [ ] **Update the Design pages in the ** **Unified check-in**, **Check-in**, and **Pre-Check-in** **files** - [ ] Identify screens that use additional info components - [ ] Update the corresponding symbols in these files with the new Component Library Sketch component (see ticket [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010) for more info on setting up the new Sketch library) - [ ] Check all Design page boards to make sure they're updated in case of detached symbols - [ ] **Sync with FE engineers** to make sure they're all set on toggling the additional info component to the new version ## Acceptance Criteria - [ ] Additional info components are updated in unified, Check-in, and Pre-Check-in Design page files - [ ] FE is set to toggle to v3 of this component",1, ds update additional info components background design system components have been prioritized in the additional info components also need to be updated as part of the switch tasks update the design pages in the unified check in check in and pre check in files identify screens that use additional info components update the corresponding symbols in these files with the new component library sketch component see ticket for more info on setting up the new sketch library check all design page boards to make sure they re updated in case of detached symbols sync with fe engineers to make sure they re all set on toggling the additional info component to the new version acceptance criteria additional info components are updated in unified check in and pre check in design page files fe is set to toggle to of this component,1 93124,11740965800.0,IssuesEvent,2020-03-11 20:42:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design] MDT- Review order page - edit contact details, v1",design vsa vsa-benefits-2,"## User story: ## Tasks: - Create high fidelity mockup(s) showing how a Veteran might update their address and contact details - Upload to Invision with a comment to highlight initial focus state ## Acceptance criteria: - [x] Mockup aligns with VA.gov’s design system - [x] Include a way for Veterans to edit their mailing and email addresses - [x] Include a way for Veterans to save or cancel their edits - [x] Initial focus point documented in Invision - [x] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Dependencies: ",1.0,"[Design] MDT- Review order page - edit contact details, v1 - ## User story: ## Tasks: - Create high fidelity mockup(s) showing how a Veteran might update their address and contact details - Upload to Invision with a comment to highlight initial focus state ## Acceptance criteria: - [x] Mockup aligns with VA.gov’s design system - [x] Include a way for Veterans to edit their mailing and email addresses - [x] Include a way for Veterans to save or cancel their edits - [x] Initial focus point documented in Invision - [x] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Dependencies: ",1, mdt review order page edit contact details user story tasks create high fidelity mockup s showing how a veteran might update their address and contact details upload to invision with a comment to highlight initial focus state acceptance criteria mockup aligns with va gov’s design system include a way for veterans to edit their mailing and email addresses include a way for veterans to save or cancel their edits initial focus point documented in invision sketch artboards are uploaded to invision and linked in this ticket as a comment dependencies ,1 96688,12150743490.0,IssuesEvent,2020-04-24 18:33:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reopened,Update content pages/My VA links,Epic content design frontend personalization-2.0 profile vsa-authenticated-exp,"## User story As a person trying to access my VA.gov profile/settings, I may be accessing my profile from another part of VA.gov and need links to the profile/settings to work correctly and content to be accurate so I don't get lost. Related to Epic #5518 ## Tasks - [ ] Update My VA account link #8400 ",1.0,"Update content pages/My VA links - ## User story As a person trying to access my VA.gov profile/settings, I may be accessing my profile from another part of VA.gov and need links to the profile/settings to work correctly and content to be accurate so I don't get lost. Related to Epic #5518 ## Tasks - [ ] Update My VA account link #8400 ",1,update content pages my va links user story as a person trying to access my va gov profile settings i may be accessing my profile from another part of va gov and need links to the profile settings to work correctly and content to be accurate so i don t get lost related to epic tasks update my va account link ,1 151679,23856814259.0,IssuesEvent,2022-09-07 01:05:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[task] Supplemental Claims | Test our assumptions about value,design product Supplemental Claims benefits-team-1 squad-2,"## Value Statement **_As a_** Veteran **_I want to_** share feedback on the behaviors and actions that drive value in the Supplemental Claims product **_So that_** my insights can shape the direction of MVP. --- ## Background Context As a team, we need to test the assumptions about the value that we've built into the MVP design for Supplemental Claims so that our approach is informed by users. We want to avoid confirmation bias or a risky escalation of commitment. ## Acceptance Criteria - [x] _We are aligned on the assumptions we've made about value._ - [x] _We know what we want to learn through testing._ - [x] _We've understand how we'll evaluate the behavior we observe (What does the user need to do achieve the assumption to be 'truthy'?)._ ## Definition of Ready - [x] _Clear value description_ - [x] _Testable acceptance criteria_ - [x] _Accessibility added to acceptance criteria_ - [x] _Approved designs attached_ - [x] _Sample data provided where appropriate_ - [x] _Estimated to fit within the sprint_ - [x] _Dependencies and blockers linked_ --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"[task] Supplemental Claims | Test our assumptions about value - ## Value Statement **_As a_** Veteran **_I want to_** share feedback on the behaviors and actions that drive value in the Supplemental Claims product **_So that_** my insights can shape the direction of MVP. --- ## Background Context As a team, we need to test the assumptions about the value that we've built into the MVP design for Supplemental Claims so that our approach is informed by users. We want to avoid confirmation bias or a risky escalation of commitment. ## Acceptance Criteria - [x] _We are aligned on the assumptions we've made about value._ - [x] _We know what we want to learn through testing._ - [x] _We've understand how we'll evaluate the behavior we observe (What does the user need to do achieve the assumption to be 'truthy'?)._ ## Definition of Ready - [x] _Clear value description_ - [x] _Testable acceptance criteria_ - [x] _Accessibility added to acceptance criteria_ - [x] _Approved designs attached_ - [x] _Sample data provided where appropriate_ - [x] _Estimated to fit within the sprint_ - [x] _Dependencies and blockers linked_ --- ## How to configure this issue - [x] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1, supplemental claims test our assumptions about value value statement as a veteran i want to share feedback on the behaviors and actions that drive value in the supplemental claims product so that my insights can shape the direction of mvp background context as a team we need to test the assumptions about the value that we ve built into the mvp design for supplemental claims so that our approach is informed by users we want to avoid confirmation bias or a risky escalation of commitment acceptance criteria we are aligned on the assumptions we ve made about value we know what we want to learn through testing we ve understand how we ll evaluate the behavior we observe what does the user need to do achieve the assumption to be truthy definition of ready clear value description testable acceptance criteria accessibility added to acceptance criteria approved designs attached sample data provided where appropriate estimated to fit within the sprint dependencies and blockers linked how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 93637,11790010689.0,IssuesEvent,2020-03-17 18:09:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Update MDT usability test materials (v2),design vsa vsa-benefits-2,"## User Story or Problem Statement Problem description: How might we create a usability test that allows Veterans/usability participants to give feedback on the application as they would actually use it? ## Goal The goal is to create a usability test conversation guide that does not stop the participant between pages (per Shawna's feedback) ## Objectives or Key Results this is meant to further - _Include references to KPIs we intend to impact_ --- ## Tasks - [ ] Rework the usability test conversation guide to include fewer (or no) hard stops for users mid-flow. ## Acceptance Criteria - [ ] New conversation guide completed in google docs for VSP feedback round (GH md file to come after) - [ ] Conversation guide uploaded as a PDF if needed ",1.0,"[Design] Update MDT usability test materials (v2) - ## User Story or Problem Statement Problem description: How might we create a usability test that allows Veterans/usability participants to give feedback on the application as they would actually use it? ## Goal The goal is to create a usability test conversation guide that does not stop the participant between pages (per Shawna's feedback) ## Objectives or Key Results this is meant to further - _Include references to KPIs we intend to impact_ --- ## Tasks - [ ] Rework the usability test conversation guide to include fewer (or no) hard stops for users mid-flow. ## Acceptance Criteria - [ ] New conversation guide completed in google docs for VSP feedback round (GH md file to come after) - [ ] Conversation guide uploaded as a PDF if needed ",1, update mdt usability test materials user story or problem statement problem description how might we create a usability test that allows veterans usability participants to give feedback on the application as they would actually use it goal the goal is to create a usability test conversation guide that does not stop the participant between pages per shawna s feedback objectives or key results this is meant to further include references to kpis we intend to impact tasks rework the usability test conversation guide to include fewer or no hard stops for users mid flow acceptance criteria new conversation guide completed in google docs for vsp feedback round gh md file to come after conversation guide uploaded as a pdf if needed ,1 158173,24798085051.0,IssuesEvent,2022-10-24 19:06:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reopened,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2),content design 508/Accessibility ia my-va-dashboard authenticated-experience collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard,"### General Information #### VFS team name Authenticated Experience #### VFS product name My VA #### VFS feature name On-site Notifications #### Point of Contact/Reviewers Allison Christman (@allison0034) - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details Alert does not contain heading ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA --- ### Platform Recommendation Add a heading to the alert. See Alert headings ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. ",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2) - ### General Information #### VFS team name Authenticated Experience #### VFS product name My VA #### VFS feature name On-site Notifications #### Point of Contact/Reviewers Allison Christman (@allison0034) - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details Alert does not contain heading ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA --- ### Platform Recommendation Add a heading to the alert. See Alert headings ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. ",1, design components or patterns don t align with design system guidelines general information vfs team name authenticated experience vfs product name my va vfs feature name on site notifications point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details alert does not contain heading link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation add a heading to the alert see alert headings vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 106003,13237661386.0,IssuesEvent,2020-08-18 22:10:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,CONSIDER: Navigation for VAMC facility operating status,design frontend frontend-vamc vsa vsa-facilities,"## Issue Description As a Veteran, I want to easily learn more about a facility's operating status so that I can be prepared to visit. The status alone does not provide enough information to prepare a Veteran for a visit. Veterans need to view details related to ""Facility Notice"" or ""Limited services and hours"".
Currently, a facility's operating status is visible within the Location and Contact information page (assuming the location has a status). ![image](https://user-images.githubusercontent.com/55411834/90570187-70003200-e16c-11ea-92fa-640a2a0ee03e.png)
To learn more about the status, the Veteran needs to go to the Operating status page (currently linked through the COVID banner) and scroll past the situation update. ![operating status page](https://user-images.githubusercontent.com/55411834/90570367-bfdef900-e16c-11ea-834b-90d8b64113fb.png)
--- ## Tasks - [ ] Determine a more direct/appropriate navigation for learning more about a facility's operating status. ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"CONSIDER: Navigation for VAMC facility operating status - ## Issue Description As a Veteran, I want to easily learn more about a facility's operating status so that I can be prepared to visit. The status alone does not provide enough information to prepare a Veteran for a visit. Veterans need to view details related to ""Facility Notice"" or ""Limited services and hours"".
Currently, a facility's operating status is visible within the Location and Contact information page (assuming the location has a status). ![image](https://user-images.githubusercontent.com/55411834/90570187-70003200-e16c-11ea-92fa-640a2a0ee03e.png)
To learn more about the status, the Veteran needs to go to the Operating status page (currently linked through the COVID banner) and scroll past the situation update. ![operating status page](https://user-images.githubusercontent.com/55411834/90570367-bfdef900-e16c-11ea-834b-90d8b64113fb.png)
--- ## Tasks - [ ] Determine a more direct/appropriate navigation for learning more about a facility's operating status. ## Acceptance Criteria - [ ] _What will be created or happen as a result of this story?_ --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,consider navigation for vamc facility operating status issue description as a veteran i want to easily learn more about a facility s operating status so that i can be prepared to visit the status alone does not provide enough information to prepare a veteran for a visit veterans need to view details related to facility notice or limited services and hours currently a facility s operating status is visible within the location and contact information page assuming the location has a status to learn more about the status the veteran needs to go to the operating status page currently linked through the covid banner and scroll past the situation update tasks determine a more direct appropriate navigation for learning more about a facility s operating status acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 40917,12800040457.0,IssuesEvent,2020-07-02 16:21:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,API key discussion,backend security vsa vsa-facilities,"## Purpose of this issue This issue was created to bring parties together to discuss and document API key management, including - Documentation of existing decisions: how we got here and why - Challenges faced in current implementation - Path forward for each team to integrate with API ## Problem(s) to be solved - Facility Locator needs an efficient path for consuming fresh quality data - Avoid unauthorized usage caused by exposing the Facilities API key in VAOS and VA.gov’s Facility Locator, given that this is available in an unauthenticated fashion - Limit cascading risks between applications as API changes - Create transparency and the ability to see who using what. (e.g. we broke VAOS twice. Once when we burned through our rate limit on PROD and then again in staging.) - It appears review instances might be using a different url for facilities API - Previously successful requests now receive LIGHTHOUSE_FACILITIES400 errors with no additional info about what’s going wrong ## Proposed plan 1. VSP: Change VA.gov Facility Locator to use its existing facilities API key in its front-end and remove the “simple proxy” in the “v1” version of vets-api 2. Lighthouse: Issue a new facilities API key for VAOS to use in its front-end. 3. VAOS: Make use of the new key from (2) for facilities API access and its existing key for the CCE API access. The CCE API key should be protected as there is sensitive data communicated back in this API. This was the case in the past so should be no issue here. 4. Lighthouse: will change the scope of the VAOS CCE API to be just for the CCE API. 5. VSP+Lighthouse(TBD): Remove the v0 vets-api ## Questions - Should all endpoint be protected by API keys? - Should we all be using the same API key or should it be app-based? ",True,"API key discussion - ## Purpose of this issue This issue was created to bring parties together to discuss and document API key management, including - Documentation of existing decisions: how we got here and why - Challenges faced in current implementation - Path forward for each team to integrate with API ## Problem(s) to be solved - Facility Locator needs an efficient path for consuming fresh quality data - Avoid unauthorized usage caused by exposing the Facilities API key in VAOS and VA.gov’s Facility Locator, given that this is available in an unauthenticated fashion - Limit cascading risks between applications as API changes - Create transparency and the ability to see who using what. (e.g. we broke VAOS twice. Once when we burned through our rate limit on PROD and then again in staging.) - It appears review instances might be using a different url for facilities API - Previously successful requests now receive LIGHTHOUSE_FACILITIES400 errors with no additional info about what’s going wrong ## Proposed plan 1. VSP: Change VA.gov Facility Locator to use its existing facilities API key in its front-end and remove the “simple proxy” in the “v1” version of vets-api 2. Lighthouse: Issue a new facilities API key for VAOS to use in its front-end. 3. VAOS: Make use of the new key from (2) for facilities API access and its existing key for the CCE API access. The CCE API key should be protected as there is sensitive data communicated back in this API. This was the case in the past so should be no issue here. 4. Lighthouse: will change the scope of the VAOS CCE API to be just for the CCE API. 5. VSP+Lighthouse(TBD): Remove the v0 vets-api ## Questions - Should all endpoint be protected by API keys? - Should we all be using the same API key or should it be app-based? ",0,api key discussion purpose of this issue this issue was created to bring parties together to discuss and document api key management including documentation of existing decisions how we got here and why challenges faced in current implementation path forward for each team to integrate with api problem s to be solved facility locator needs an efficient path for consuming fresh quality data avoid unauthorized usage caused by exposing the facilities api key in vaos and va gov’s facility locator given that this is available in an unauthenticated fashion limit cascading risks between applications as api changes create transparency and the ability to see who using what e g we broke vaos twice once when we burned through our rate limit on prod and then again in staging it appears review instances might be using a different url for facilities api previously successful requests now receive lighthouse errors with no additional info about what’s going wrong proposed plan vsp change va gov facility locator to use its existing facilities api key in its front end and remove the “simple proxy” in the “ ” version of vets api lighthouse issue a new facilities api key for vaos to use in its front end vaos make use of the new key from for facilities api access and its existing key for the cce api access the cce api key should be protected as there is sensitive data communicated back in this api this was the case in the past so should be no issue here lighthouse will change the scope of the vaos cce api to be just for the cce api vsp lighthouse tbd remove the vets api questions should all endpoint be protected by api keys should we all be using the same api key or should it be app based ,0 161805,25406859292.0,IssuesEvent,2022-11-22 15:53:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Finalize details and Publish landing,service-design,"## Issue Description Establish the landing page(s) for teams wanting SDT assistance in Mapping of a task, journey, or experience Should we also consider broader intakes (research guidance, SD guidance, etc?) [Draft in team Confluence space](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2429157514/Request+mapping+support) ## Tasks - [x] Construct content - [x] establish layout - [ ] Workshop w/ team - [ ] Publish landing ## Acceptance Criteria - [ ] Landing is available to desired user(s) - [ ] Required information for assistance is specified. - [ ] Landing allows user to learn what type of help is available - [ ] Landing allows user to understand what is needed to begin - [ ] Landing allows user to understand what sort of timetable is involved",1.0,"Finalize details and Publish landing - ## Issue Description Establish the landing page(s) for teams wanting SDT assistance in Mapping of a task, journey, or experience Should we also consider broader intakes (research guidance, SD guidance, etc?) [Draft in team Confluence space](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2429157514/Request+mapping+support) ## Tasks - [x] Construct content - [x] establish layout - [ ] Workshop w/ team - [ ] Publish landing ## Acceptance Criteria - [ ] Landing is available to desired user(s) - [ ] Required information for assistance is specified. - [ ] Landing allows user to learn what type of help is available - [ ] Landing allows user to understand what is needed to begin - [ ] Landing allows user to understand what sort of timetable is involved",1,finalize details and publish landing issue description establish the landing page s for teams wanting sdt assistance in mapping of a task journey or experience should we also consider broader intakes research guidance sd guidance etc tasks construct content establish layout workshop w team publish landing acceptance criteria landing is available to desired user s required information for assistance is specified landing allows user to learn what type of help is available landing allows user to understand what is needed to begin landing allows user to understand what sort of timetable is involved,1 109429,13770865104.0,IssuesEvent,2020-10-07 20:57:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Product/Design] How do we guide people to the new My VA dashboard?,design my-va-dashboard needs-grooming personalization-2.0 product vsa-authenticated-exp,"## Background On 10.7.2020, we made the decision to not continue pursuing a logged-in homepage redesign and pivoted to redesigning the My VA dashboard. As a result, the concern came up — how do we guide people to their new dashboard? 8% of VA.gov users use My VA, whereas about 50% use the homepage. This makes sense now — homepages are always the most-used page on a website, and My VA isn't very usable in its current state. However, after the redesign, the My VA dashboard is likely going to be a better place for users to start their logged-in experience on VA.gov than the homepage will be. How do we get people there? Potential ideas: - **Redirect people who log-in from the homepage to My VA** — This is our preferred approach, but we should evaluate this in user testing. - **Direct people to the My VA dashboard from the homepage** — I think this idea is less good. This would likely be a temporary solution; we could either show people a modal asking them if they want to redirect when they log in (no = land on homepage), or utilize the feature announcement banner that sticks to the bottom of the page after the new page initially launches. ## Tasks - [ ] Evaluate redirect strategy in user testing - [ ] Determine approach for guiding people to My VA ",1.0,"[Product/Design] How do we guide people to the new My VA dashboard? - ## Background On 10.7.2020, we made the decision to not continue pursuing a logged-in homepage redesign and pivoted to redesigning the My VA dashboard. As a result, the concern came up — how do we guide people to their new dashboard? 8% of VA.gov users use My VA, whereas about 50% use the homepage. This makes sense now — homepages are always the most-used page on a website, and My VA isn't very usable in its current state. However, after the redesign, the My VA dashboard is likely going to be a better place for users to start their logged-in experience on VA.gov than the homepage will be. How do we get people there? Potential ideas: - **Redirect people who log-in from the homepage to My VA** — This is our preferred approach, but we should evaluate this in user testing. - **Direct people to the My VA dashboard from the homepage** — I think this idea is less good. This would likely be a temporary solution; we could either show people a modal asking them if they want to redirect when they log in (no = land on homepage), or utilize the feature announcement banner that sticks to the bottom of the page after the new page initially launches. ## Tasks - [ ] Evaluate redirect strategy in user testing - [ ] Determine approach for guiding people to My VA ",1, how do we guide people to the new my va dashboard background on we made the decision to not continue pursuing a logged in homepage redesign and pivoted to redesigning the my va dashboard as a result the concern came up — how do we guide people to their new dashboard of va gov users use my va whereas about use the homepage this makes sense now — homepages are always the most used page on a website and my va isn t very usable in its current state however after the redesign the my va dashboard is likely going to be a better place for users to start their logged in experience on va gov than the homepage will be how do we get people there potential ideas redirect people who log in from the homepage to my va — this is our preferred approach but we should evaluate this in user testing direct people to the my va dashboard from the homepage — i think this idea is less good this would likely be a temporary solution we could either show people a modal asking them if they want to redirect when they log in no land on homepage or utilize the feature announcement banner that sticks to the bottom of the page after the new page initially launches tasks evaluate redirect strategy in user testing determine approach for guiding people to my va ,1 90429,11393266162.0,IssuesEvent,2020-01-30 06:01:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"MDT- Order confirmation - default state, v1",design vsa vsa-benefits-2,"## User Story: As a veteran, I need to be able to see the next steps and print off a receipt so that I can have some documentation of the order if needed. ## Tasks - Create a high fidelity mockup of the order confirmation page - Upload to Invision with a comment to highlight initial focus state ## Acceptance Criteria: - [ ] Mockup aligns with VA.gov’s design system - [ ] Includes information on what the Veteran can expect next - [ ] Includes information on what the Veteran can do in the meantime - [ ] Includes a way to print screen / generate receipt - [ ] Initial focus point documented in Invision - [ ] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps - design review ## Dep/Blockers ",1.0,"MDT- Order confirmation - default state, v1 - ## User Story: As a veteran, I need to be able to see the next steps and print off a receipt so that I can have some documentation of the order if needed. ## Tasks - Create a high fidelity mockup of the order confirmation page - Upload to Invision with a comment to highlight initial focus state ## Acceptance Criteria: - [ ] Mockup aligns with VA.gov’s design system - [ ] Includes information on what the Veteran can expect next - [ ] Includes information on what the Veteran can do in the meantime - [ ] Includes a way to print screen / generate receipt - [ ] Initial focus point documented in Invision - [ ] Sketch artboards are uploaded to Invision and linked in this ticket as a comment ## Next Steps - design review ## Dep/Blockers ",1,mdt order confirmation default state user story as a veteran i need to be able to see the next steps and print off a receipt so that i can have some documentation of the order if needed tasks create a high fidelity mockup of the order confirmation page upload to invision with a comment to highlight initial focus state acceptance criteria mockup aligns with va gov’s design system includes information on what the veteran can expect next includes information on what the veteran can do in the meantime includes a way to print screen generate receipt initial focus point documented in invision sketch artboards are uploaded to invision and linked in this ticket as a comment next steps design review dep blockers ,1 121076,15836752866.0,IssuesEvent,2021-04-06 19:47:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,CLP - Back to Top alignment ,design frontend needs-grooming planned-work vsa vsa-public-websites,"## Issue Description _Based on recent design review post Staging review it was identified that the back to top component, need to be align the button the right-most ""column"" example below. Also discussed rounding out the right side but will need @rtwell review and approval in support_ Example: Alignment for CLP Back to Top: ![Screen Shot 2021-03-24 at 11 35 00 AM](https://user-images.githubusercontent.com/70410912/112364300-fb5e1a80-8c9b-11eb-8e45-a7422083090d.png) [Practice Area Feedback Ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/20883) ## Acceptance Criteria - [ ] Designer comments on this issue to approve page styling - [ ] Back to top is aligned per guidance - [ ] Validated and tested - Back to top feature is visual and accessible per desired approach. - [ ] End-to-end tests show 0 violations. ## Appendix
Ensure your code changes are covered by E2E tests (expand) - Add E2E tests if none exist for this addition/change. - Update existing E2E tests if this code will change functionality. - Include axe checks, including hidden content
Run axe checks using the Chrome or Firefox browser plugin (expand) - Ensure no heading levels are skipped. - Ensure all buttons and labeled inputs use semantic HTML elements. - Ensure all buttons, labeled elements and images are identified using HTML semantic markers or ARIA roles. - Ensure form fields have clearly defined boundaries or outlines. - Ensure form fields do not use placeholder text. - Ensure form fields have highly visible and specific error states.
Test for color contrast and color blindness issues (expand) - All text has appropriate contrast.
Zoom layouts to 400% at 1280px width (expand) - Ensure readability and usability are supported when zoomed up to 400% at 1280px browser width - Ensure no content gets focused offscreen or is hidden from view.
Test with 1 or 2 screen readers (expand) - Ensure the page includes a skip navigation link. - Ensure all links are properly descriptive. - Ensure screen reader users can hear the text equivalent for each image conveying information. - Ensure screen reader users can hear the text equivalent for each image button. - Ensure screen reader users can hear labels and instructions for inputs. - Ensure purely decorative images are not announced by the screenreader.
Navigate using the keyboard only (expand) - Ensure all links (navigation, text and/or image), form controls and page functions can be reached with the tab key in a logical order. - Ensure all links (navigation, text and/or image), form controls and page functions can be triggered with the spacebar, enter key, or arrow keys. - Ensure all interactive elements can be reached with the tab key in a logical order - Ensure all interactive elements can be triggered with the spacebar, enter key, or arrow keys. - Ensure focus is always visible and appears in logical order. - Ensure each interactive element has visible focus state which appears in logical order.
--- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"CLP - Back to Top alignment - ## Issue Description _Based on recent design review post Staging review it was identified that the back to top component, need to be align the button the right-most ""column"" example below. Also discussed rounding out the right side but will need @rtwell review and approval in support_ Example: Alignment for CLP Back to Top: ![Screen Shot 2021-03-24 at 11 35 00 AM](https://user-images.githubusercontent.com/70410912/112364300-fb5e1a80-8c9b-11eb-8e45-a7422083090d.png) [Practice Area Feedback Ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/20883) ## Acceptance Criteria - [ ] Designer comments on this issue to approve page styling - [ ] Back to top is aligned per guidance - [ ] Validated and tested - Back to top feature is visual and accessible per desired approach. - [ ] End-to-end tests show 0 violations. ## Appendix
Ensure your code changes are covered by E2E tests (expand) - Add E2E tests if none exist for this addition/change. - Update existing E2E tests if this code will change functionality. - Include axe checks, including hidden content
Run axe checks using the Chrome or Firefox browser plugin (expand) - Ensure no heading levels are skipped. - Ensure all buttons and labeled inputs use semantic HTML elements. - Ensure all buttons, labeled elements and images are identified using HTML semantic markers or ARIA roles. - Ensure form fields have clearly defined boundaries or outlines. - Ensure form fields do not use placeholder text. - Ensure form fields have highly visible and specific error states.
Test for color contrast and color blindness issues (expand) - All text has appropriate contrast.
Zoom layouts to 400% at 1280px width (expand) - Ensure readability and usability are supported when zoomed up to 400% at 1280px browser width - Ensure no content gets focused offscreen or is hidden from view.
Test with 1 or 2 screen readers (expand) - Ensure the page includes a skip navigation link. - Ensure all links are properly descriptive. - Ensure screen reader users can hear the text equivalent for each image conveying information. - Ensure screen reader users can hear the text equivalent for each image button. - Ensure screen reader users can hear labels and instructions for inputs. - Ensure purely decorative images are not announced by the screenreader.
Navigate using the keyboard only (expand) - Ensure all links (navigation, text and/or image), form controls and page functions can be reached with the tab key in a logical order. - Ensure all links (navigation, text and/or image), form controls and page functions can be triggered with the spacebar, enter key, or arrow keys. - Ensure all interactive elements can be reached with the tab key in a logical order - Ensure all interactive elements can be triggered with the spacebar, enter key, or arrow keys. - Ensure focus is always visible and appears in logical order. - Ensure each interactive element has visible focus state which appears in logical order.
--- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,clp back to top alignment issue description based on recent design review post staging review it was identified that the back to top component need to be align the button the right most column example below also discussed rounding out the right side but will need rtwell review and approval in support example alignment for clp back to top acceptance criteria designer comments on this issue to approve page styling back to top is aligned per guidance validated and tested back to top feature is visual and accessible per desired approach end to end tests show violations appendix ensure your code changes are covered by tests expand add tests if none exist for this addition change update existing tests if this code will change functionality include axe checks including hidden content run axe checks using the chrome or firefox browser plugin expand ensure no heading levels are skipped ensure all buttons and labeled inputs use semantic html elements ensure all buttons labeled elements and images are identified using html semantic markers or aria roles ensure form fields have clearly defined boundaries or outlines ensure form fields do not use placeholder text ensure form fields have highly visible and specific error states test for color contrast and color blindness issues expand all text has appropriate contrast zoom layouts to at width expand ensure readability and usability are supported when zoomed up to at browser width ensure no content gets focused offscreen or is hidden from view test with or screen readers expand ensure the page includes a skip navigation link ensure all links are properly descriptive ensure screen reader users can hear the text equivalent for each image conveying information ensure screen reader users can hear the text equivalent for each image button ensure screen reader users can hear labels and instructions for inputs ensure purely decorative images are not announced by the screenreader navigate using the keyboard only expand ensure all links navigation text and or image form controls and page functions can be reached with the tab key in a logical order ensure all links navigation text and or image form controls and page functions can be triggered with the spacebar enter key or arrow keys ensure all interactive elements can be reached with the tab key in a logical order ensure all interactive elements can be triggered with the spacebar enter key or arrow keys ensure focus is always visible and appears in logical order ensure each interactive element has visible focus state which appears in logical order how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 157664,24706385953.0,IssuesEvent,2022-10-19 19:27:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] [UX] Create Final Wireframes for Needs Information Updated Scenarios,design ux HCE-Checkin,"## Tasks - [ ] Create final mockups with callouts for these scenarios - Need to Update Contact Info & needed - Choose to NOT file Updates needed - Claim filed/ Updated needed - Claim NOT filed - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1.0,"[Design] [UX] Create Final Wireframes for Needs Information Updated Scenarios - ## Tasks - [ ] Create final mockups with callouts for these scenarios - Need to Update Contact Info & needed - Choose to NOT file Updates needed - Claim filed/ Updated needed - Claim NOT filed - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation. ",1, create final wireframes for needs information updated scenarios tasks create final mockups with callouts for these scenarios need to update contact info needed choose to not file updates needed claim filed updated needed claim not filed decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation ,1 118382,15285881784.0,IssuesEvent,2021-02-23 14:05:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Document Contact information in form patterns library,design-system-update vsp-design-system-team,"## Issue Description Document Contact information in form patterns library --- ## Tasks - [ ] Audit - [ ] Create Sketch Templates - [ ] Write documentation - [ ] Review/approval of documentation - [ ] Publish/announce pattern release ## Acceptance Criteria - [ ] There is documentation for Contact information in form patterns library --- ",2.0,"Document Contact information in form patterns library - ## Issue Description Document Contact information in form patterns library --- ## Tasks - [ ] Audit - [ ] Create Sketch Templates - [ ] Write documentation - [ ] Review/approval of documentation - [ ] Publish/announce pattern release ## Acceptance Criteria - [ ] There is documentation for Contact information in form patterns library --- ",1,document contact information in form patterns library issue description document contact information in form patterns library tasks audit create sketch templates write documentation review approval of documentation publish announce pattern release acceptance criteria there is documentation for contact information in form patterns library ,1 113263,14403975643.0,IssuesEvent,2020-12-03 16:42:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Write up tasks for Designers for Storybook Pilot,design-system-team,"## Issue Description Write up tasks for Designers for Storybook Pilot --- ## Tasks - [ ] Define tasks ",1.0,"Write up tasks for Designers for Storybook Pilot - ## Issue Description Write up tasks for Designers for Storybook Pilot --- ## Tasks - [ ] Define tasks ",1,write up tasks for designers for storybook pilot issue description write up tasks for designers for storybook pilot tasks define tasks ,1 174294,27614525530.0,IssuesEvent,2023-03-09 18:15:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2),content design 508/Accessibility ia my-va-dashboard authenticated-experience collab-cycle-feedback Staging CCIssue04.07 CC-Dashboard,"### General Information #### VFS team name Authenticated Experience #### VFS product name My VA #### VFS feature name Audit UX Improvements #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details Under health care, there is a choose your health management portal Cerner alert with a warning alert style. Our warning alert guidance is ""Used to warn a user, such as when there are negative consequences, or when something has gone wrong."" This content does not have a negative consequence for the user. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Since we have noticed alert fatigue, I would rec removing the alert styling all together, however if you feel this needs to be styled as an alert, use the info alert styling. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1.0,"[Components and pattern standards] Design components or patterns don't align with Design System guidelines. (04.07.2) - ### General Information #### VFS team name Authenticated Experience #### VFS product name My VA #### VFS feature name Audit UX Improvements #### Point of Contact/Reviewers Allison Christman - @allison0034 - Design *For more information on how to interpret this ticket, please refer to the [Anatomy of a Staging Review issue ticket](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Anatomy-of-a-Staging-Review-Issue-ticket.2060320997.html) guidance on Platform Website. --- ### Platform Issue Design components or patterns don't align with Design System guidelines. ### Issue Details Under health care, there is a choose your health management portal Cerner alert with a warning alert style. Our warning alert guidance is ""Used to warn a user, such as when there are negative consequences, or when something has gone wrong."" This content does not have a negative consequence for the user. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 04, Issue Number 07](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References WCAG SC 3.2.4 AA ### Platform Recommendation Since we have noticed alert fatigue, I would rec removing the alert styling all together, however if you feel this needs to be styled as an alert, use the info alert styling. --- ### VFS Guidance - Close the ticket when the issue has been resolved or validated by your Product Owner - If your team has additional questions or needs Platform help validating the issue, please comment on the ticket - Some feedback provided may be out of scope for your iteration of the product, however, Platform's OCTO leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue. - If you do not believe that this Staging Review issue ticket is the responsibility of your team, comment below providing an explanation and who you believe is responsible. Please tag the Point of Contact/Reviewers. Governance team will research and will follow up.",1, design components or patterns don t align with design system guidelines general information vfs team name authenticated experience vfs product name my va vfs feature name audit ux improvements point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details under health care there is a choose your health management portal cerner alert with a warning alert style our warning alert guidance is used to warn a user such as when there are negative consequences or when something has gone wrong this content does not have a negative consequence for the user link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation since we have noticed alert fatigue i would rec removing the alert styling all together however if you feel this needs to be styled as an alert use the info alert styling vfs guidance close the ticket when the issue has been resolved or validated by your product owner if your team has additional questions or needs platform help validating the issue please comment on the ticket some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up ,1 136196,19721995630.0,IssuesEvent,2022-01-13 16:11:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Overall user experience] Design component or pattern in use isn't considered a best practice. (01.01.5),vsa-public-websites design ia collab-cycle-feedback Staging CCIssue01.01 CC-Dashboard,"### General Information #### VFS team name Public Websites #### VFS product name Outreach & Events Enhancements #### Point of Contact/Reviewers Sean Sewell (@seansewell) - Design --- ### Platform Issue Design component or pattern in use isn't considered a best practice. ### Issue Details Error state messaging is appearing below the input field name. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 01, Issue Number 01](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References --- ### Platform Recommendation Error messaging should appear below the label but above the field name. https://d.pr/i/62NSFA Error messaging copy guidance is in the dates section of the design system website. https://design.va.gov/patterns/form-patterns#usability-guidance-10 ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. ",1.0,"[Overall user experience] Design component or pattern in use isn't considered a best practice. (01.01.5) - ### General Information #### VFS team name Public Websites #### VFS product name Outreach & Events Enhancements #### Point of Contact/Reviewers Sean Sewell (@seansewell) - Design --- ### Platform Issue Design component or pattern in use isn't considered a best practice. ### Issue Details Error state messaging is appearing below the input field name. ### Link, screenshot or steps to recreate ### VA.gov Experience Standard [Category Number 01, Issue Number 01](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/VA.gov-experience-standards.1683980311.html) ### Other References --- ### Platform Recommendation Error messaging should appear below the label but above the field name. https://d.pr/i/62NSFA Error messaging copy guidance is in the dates section of the design system website. https://design.va.gov/patterns/form-patterns#usability-guidance-10 ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] Close the ticket when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment in the ticket. ",1, design component or pattern in use isn t considered a best practice general information vfs team name public websites vfs product name outreach events enhancements point of contact reviewers sean sewell seansewell design platform issue design component or pattern in use isn t considered a best practice issue details error state messaging is appearing below the input field name link screenshot or steps to recreate va gov experience standard other references platform recommendation error messaging should appear below the label but above the field name error messaging copy guidance is in the dates section of the design system website vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 154878,24362898734.0,IssuesEvent,2022-10-03 13:10:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design System Tech Debt: Q3 2022,Epic vsp-design-system-team PO Endorsed platform-okrs,"## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/product-outline-template.md) ## High Level User Story/ies - As a design system developer, I need a well-maintained project so I can develop new features with confidence - As a VFS developer, I need to know that the design components I need to use are well-maintained so I can develop with confidence ## Hypothesis or Bet If we regularly undertake tasks to maintain, update, and improve the component-library, Formation, and the forms library, we will keep these projects healthy, make it easier to develop new features, and maintain and improve their reliability with frontend projects. ## OKR _Which Objective / Key Result does this epic push forward?_ Quarterly Service Delivery - Q3 2022 ## Definition of done ### What must be true in order for you to consider this epic complete? We have closed > 3 DS items in Q3 to improve DS operations. ",1.0,"Design System Tech Debt: Q3 2022 - ## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/product-management/product-outline-template.md) ## High Level User Story/ies - As a design system developer, I need a well-maintained project so I can develop new features with confidence - As a VFS developer, I need to know that the design components I need to use are well-maintained so I can develop with confidence ## Hypothesis or Bet If we regularly undertake tasks to maintain, update, and improve the component-library, Formation, and the forms library, we will keep these projects healthy, make it easier to develop new features, and maintain and improve their reliability with frontend projects. ## OKR _Which Objective / Key Result does this epic push forward?_ Quarterly Service Delivery - Q3 2022 ## Definition of done ### What must be true in order for you to consider this epic complete? We have closed > 3 DS items in Q3 to improve DS operations. ",1,design system tech debt product outline high level user story ies as a design system developer i need a well maintained project so i can develop new features with confidence as a vfs developer i need to know that the design components i need to use are well maintained so i can develop with confidence hypothesis or bet if we regularly undertake tasks to maintain update and improve the component library formation and the forms library we will keep these projects healthy make it easier to develop new features and maintain and improve their reliability with frontend projects okr which objective key result does this epic push forward quarterly service delivery definition of done what must be true in order for you to consider this epic complete we have closed ds items in to improve ds operations ,1 173779,27523001069.0,IssuesEvent,2023-03-06 16:10:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Release to Production,frontend design product ux HCE-Checkin,"## ENGINEERING TASKS - [x] Merge code to main branch (or flip the feature flag) on day of release - [x] Conduct prod or staging validation, if necessary - [ ] Needed - [ ] Not needed ## RESEARCH TASKS - [x] Push updated Product Guides to Git, if necessary ## DESIGN TASKS - [x] Merge final wireframes to Abstract main branch, if necessary - [x] Merge Sketch files to VA Sketch cloud, if necessary ## PRODUCT TASKS - [x] Create release notes [here](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-release-notes.md) - [x] Remove corresponding entry from the [Planned Releases page](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-planned-releases.md) - [x] Send release notification via slack in the [check-in-expreience](https://dsva.slack.com/archives/C022AC2STBM) channel - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Call-outs = include call outs to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - [x] Send release notification via VA email - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Send email to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - Dore Mobley (not in slack) ",1.0,"Release to Production - ## ENGINEERING TASKS - [x] Merge code to main branch (or flip the feature flag) on day of release - [x] Conduct prod or staging validation, if necessary - [ ] Needed - [ ] Not needed ## RESEARCH TASKS - [x] Push updated Product Guides to Git, if necessary ## DESIGN TASKS - [x] Merge final wireframes to Abstract main branch, if necessary - [x] Merge Sketch files to VA Sketch cloud, if necessary ## PRODUCT TASKS - [x] Create release notes [here](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-release-notes.md) - [x] Remove corresponding entry from the [Planned Releases page](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/release-plan/check-in-planned-releases.md) - [x] Send release notification via slack in the [check-in-expreience](https://dsva.slack.com/archives/C022AC2STBM) channel - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Call-outs = include call outs to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - [x] Send release notification via VA email - Text = ""Modernized Check-in Production Release on . Release notes can be found here"" - Link = include link to the release notes for the date of the production release - Send email to - Stephen Barrs - Patrick Bateman - Shawn Adams - Jason Woodman - Dore Mobley (not in slack) ",1,release to production engineering tasks merge code to main branch or flip the feature flag on day of release conduct prod or staging validation if necessary needed not needed research tasks push updated product guides to git if necessary design tasks merge final wireframes to abstract main branch if necessary merge sketch files to va sketch cloud if necessary product tasks create release notes remove corresponding entry from the send release notification via slack in the channel text modernized check in production release on release notes can be found here link include link to the release notes for the date of the production release call outs include call outs to stephen barrs patrick bateman shawn adams jason woodman send release notification via va email text modernized check in production release on release notes can be found here link include link to the release notes for the date of the production release send email to stephen barrs patrick bateman shawn adams jason woodman dore mobley not in slack ,1 136181,19720414581.0,IssuesEvent,2022-01-13 14:53:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create guidance for converting Liquid template patterns to new web components,vsp-design-system-team,"## Description Dependent on the creation of the following web components: - `va-process-list` - `va-pagination` - `va-banner` - `va-table` - `va-modal` The above components could be very useful inside the Liquid templates. In order to encourage the migration to them, we should write some guidance on how to convert existing patterns within the Liquid templates to the above components. ## Details This guidance should include: - general information about using Design System web components inside Liquid templates - specific guidance for each of the above components - an example migration for each of the above components. The general information about using the Design System web components inside Liquid templates should be added to the ""For developers"" section of design.va.gov under ""Using Web Components"". The specific guidance should be shared with the teams responsible for maintaining the templates. ## Acceptance Criteria - [ ] Write up guidance - [ ] Add general guidance to design.va.gov - [ ] Reach out to teams responsible for templates and share specific guidance",1.0,"Create guidance for converting Liquid template patterns to new web components - ## Description Dependent on the creation of the following web components: - `va-process-list` - `va-pagination` - `va-banner` - `va-table` - `va-modal` The above components could be very useful inside the Liquid templates. In order to encourage the migration to them, we should write some guidance on how to convert existing patterns within the Liquid templates to the above components. ## Details This guidance should include: - general information about using Design System web components inside Liquid templates - specific guidance for each of the above components - an example migration for each of the above components. The general information about using the Design System web components inside Liquid templates should be added to the ""For developers"" section of design.va.gov under ""Using Web Components"". The specific guidance should be shared with the teams responsible for maintaining the templates. ## Acceptance Criteria - [ ] Write up guidance - [ ] Add general guidance to design.va.gov - [ ] Reach out to teams responsible for templates and share specific guidance",1,create guidance for converting liquid template patterns to new web components description dependent on the creation of the following web components va process list va pagination va banner va table va modal the above components could be very useful inside the liquid templates in order to encourage the migration to them we should write some guidance on how to convert existing patterns within the liquid templates to the above components details this guidance should include general information about using design system web components inside liquid templates specific guidance for each of the above components an example migration for each of the above components the general information about using the design system web components inside liquid templates should be added to the for developers section of design va gov under using web components the specific guidance should be shared with the teams responsible for maintaining the templates acceptance criteria write up guidance add general guidance to design va gov reach out to teams responsible for templates and share specific guidance,1 182258,30822710796.0,IssuesEvent,2023-08-01 17:32:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Add ability to cancel an appointment,design ux HCE-Checkin,"## Description Veterans are seeing similarities of completing pre-check-in with confirming an appointment via the VeText appt reminder process. > ""Is there a link that I can go to to change my appointment? For example, change or cancel. Sometimes something comes up and I need to either change or cancel."" If a Veteran is completing pre-check-in for one appt in the web app and they want to complete pre-check-in for another appt within the same session, there options are to either 1) View details, or 2) Confirm the appt. This is identical to the VeText process. Therefore, Veterans asked if they could also cancel their appt too because that's what they typically do in VeText. So, adding cancel as an option during the pre-check-in process should be considered. Other consideration is whether cancel should be included for appts that have completed pre-check-in. This would be similar to the Appointments web app. So, would need to check how they handle cancelling appts. For now, this ticket does not include this. ## Tasks - [ ] Talk to VeText about the flow when a Veteran answers N1 to cancel. What happens then? - [ ] Create user flow for cancel - [ ] Create wireframes - [ ] Review with stakeholders, e.g., ux team, product team, VeText, Laura, etc. ## AC - [ ] User flow complete - [ ] Wireframes complete - [ ] Wireframes have been reviewed - [ ] Create ticket for FE to begin work ",1.0,"Add ability to cancel an appointment - ## Description Veterans are seeing similarities of completing pre-check-in with confirming an appointment via the VeText appt reminder process. > ""Is there a link that I can go to to change my appointment? For example, change or cancel. Sometimes something comes up and I need to either change or cancel."" If a Veteran is completing pre-check-in for one appt in the web app and they want to complete pre-check-in for another appt within the same session, there options are to either 1) View details, or 2) Confirm the appt. This is identical to the VeText process. Therefore, Veterans asked if they could also cancel their appt too because that's what they typically do in VeText. So, adding cancel as an option during the pre-check-in process should be considered. Other consideration is whether cancel should be included for appts that have completed pre-check-in. This would be similar to the Appointments web app. So, would need to check how they handle cancelling appts. For now, this ticket does not include this. ## Tasks - [ ] Talk to VeText about the flow when a Veteran answers N1 to cancel. What happens then? - [ ] Create user flow for cancel - [ ] Create wireframes - [ ] Review with stakeholders, e.g., ux team, product team, VeText, Laura, etc. ## AC - [ ] User flow complete - [ ] Wireframes complete - [ ] Wireframes have been reviewed - [ ] Create ticket for FE to begin work ",1,add ability to cancel an appointment description veterans are seeing similarities of completing pre check in with confirming an appointment via the vetext appt reminder process is there a link that i can go to to change my appointment for example change or cancel sometimes something comes up and i need to either change or cancel if a veteran is completing pre check in for one appt in the web app and they want to complete pre check in for another appt within the same session there options are to either view details or confirm the appt this is identical to the vetext process therefore veterans asked if they could also cancel their appt too because that s what they typically do in vetext so adding cancel as an option during the pre check in process should be considered other consideration is whether cancel should be included for appts that have completed pre check in this would be similar to the appointments web app so would need to check how they handle cancelling appts for now this ticket does not include this tasks talk to vetext about the flow when a veteran answers to cancel what happens then create user flow for cancel create wireframes review with stakeholders e g ux team product team vetext laura etc ac user flow complete wireframes complete wireframes have been reviewed create ticket for fe to begin work ,1 107268,13448123859.0,IssuesEvent,2020-09-08 15:04:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Conduct UAT,UAT design profile vsa-authenticated-exp,"## Background We are conducting UAT for Profile 2.0 [UAT Plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Profile%202.0%20Release%20Plan.md) ## Tasks - [x] Conduct UAT - [x] Document any issues that come out of UAT ",1.0,"[Design] Conduct UAT - ## Background We are conducting UAT for Profile 2.0 [UAT Plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/profile/Combine%20Profile%20and%20Account/Profile%202.0%20Release%20Plan.md) ## Tasks - [x] Conduct UAT - [x] Document any issues that come out of UAT ",1, conduct uat background we are conducting uat for profile tasks conduct uat document any issues that come out of uat ,1 160142,25109441869.0,IssuesEvent,2022-11-08 19:12:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Develop and document the mapping process,service-design,"## Issue Description Document the mapping process, expanding upon the major phases developed in Issue [45606](https://app.zenhub.com/workspace/o/department-of-veterans-affairs/va.gov-team/issues/45606). Should result in an internal guide that a SDT member can follow. ## Tasks - [x] Workshop Phases-to-specifics details - [x] Spell out specific steps within each phase to accomplish a completed map - [x] Refine w/ team input - [x] Shape raw steps into a crude guide in [Confluence](https://vfs.atlassian.net/l/cp/szWWFLku) ## Acceptance Criteria - [x] Guide structure and basic contents are decided ",1.0,"Develop and document the mapping process - ## Issue Description Document the mapping process, expanding upon the major phases developed in Issue [45606](https://app.zenhub.com/workspace/o/department-of-veterans-affairs/va.gov-team/issues/45606). Should result in an internal guide that a SDT member can follow. ## Tasks - [x] Workshop Phases-to-specifics details - [x] Spell out specific steps within each phase to accomplish a completed map - [x] Refine w/ team input - [x] Shape raw steps into a crude guide in [Confluence](https://vfs.atlassian.net/l/cp/szWWFLku) ## Acceptance Criteria - [x] Guide structure and basic contents are decided ",1,develop and document the mapping process issue description document the mapping process expanding upon the major phases developed in issue should result in an internal guide that a sdt member can follow tasks workshop phases to specifics details spell out specific steps within each phase to accomplish a completed map refine w team input shape raw steps into a crude guide in acceptance criteria guide structure and basic contents are decided ,1 83302,10339539944.0,IssuesEvent,2019-09-03 19:35:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Create mock for UI where type of care not available in given healthcare system,design vaos,"## Story As a veteran, I want to know what to do when the type of care I'm requesting doesn't exist in the VA healthcare system in which I'm registered so that I can take the next action to get the care I need. ## AC - [ ] Mock exists for UI state where veteran is registered to a VA healthcare system but that system(s) doesn't have the type of care they're requesting - [ ] Mock uploaded to VAOS design folder in GH - [ ] Mock includes information about which page(s) the pages that should include this messaging - [ ] UI should include appropriate explanation of situation to veterans as well as next steps for them to take to get care they need ## Thoughts We should understand how / if this should tie into Community Care (i.e., maybe we want to show veterans private options when their thing isn't available at a VA system where they're registered). ",1.0,"Create mock for UI where type of care not available in given healthcare system - ## Story As a veteran, I want to know what to do when the type of care I'm requesting doesn't exist in the VA healthcare system in which I'm registered so that I can take the next action to get the care I need. ## AC - [ ] Mock exists for UI state where veteran is registered to a VA healthcare system but that system(s) doesn't have the type of care they're requesting - [ ] Mock uploaded to VAOS design folder in GH - [ ] Mock includes information about which page(s) the pages that should include this messaging - [ ] UI should include appropriate explanation of situation to veterans as well as next steps for them to take to get care they need ## Thoughts We should understand how / if this should tie into Community Care (i.e., maybe we want to show veterans private options when their thing isn't available at a VA system where they're registered). ",1,create mock for ui where type of care not available in given healthcare system story as a veteran i want to know what to do when the type of care i m requesting doesn t exist in the va healthcare system in which i m registered so that i can take the next action to get the care i need ac mock exists for ui state where veteran is registered to a va healthcare system but that system s doesn t have the type of care they re requesting mock uploaded to vaos design folder in gh mock includes information about which page s the pages that should include this messaging ui should include appropriate explanation of situation to veterans as well as next steps for them to take to get care they need thoughts we should understand how if this should tie into community care i e maybe we want to show veterans private options when their thing isn t available at a va system where they re registered ,1 388684,26777919308.0,IssuesEvent,2023-01-31 18:36:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Monitoring] Update ""Monitor infrastructure and applications with Datadog"" documentation",documentation monitoring platform-tech-team-2,"## Description Update the document based on feedback from the recent mini-workshop with Platform Tech Team 2. ## Resources - [Monitor infrastructure and applications with Datadog](https://vfs.atlassian.net/wiki/spaces/OT/pages/2236612646/Monitor+infrastructure+and+applications+with+Datadog) ## Feedback Needs work: - Make sure links are correct - Add a link that contains info about all the Slack channels that alerts are sent to ## Acceptance Criteria - [x] The document is updated and shared with the team for review ## Refinement Guidance - Check the following before working on this issue: - [x] _Team label assigned (""platform-tech-team-2"")_ - [x] _Epic assigned (if needed)_ - [x] _Estimated (points assigned)_ - [x] _Sprint assigned (once planned)_ - [x] _Team member(s) assigned_ ",1.0,"[Monitoring] Update ""Monitor infrastructure and applications with Datadog"" documentation - ## Description Update the document based on feedback from the recent mini-workshop with Platform Tech Team 2. ## Resources - [Monitor infrastructure and applications with Datadog](https://vfs.atlassian.net/wiki/spaces/OT/pages/2236612646/Monitor+infrastructure+and+applications+with+Datadog) ## Feedback Needs work: - Make sure links are correct - Add a link that contains info about all the Slack channels that alerts are sent to ## Acceptance Criteria - [x] The document is updated and shared with the team for review ## Refinement Guidance - Check the following before working on this issue: - [x] _Team label assigned (""platform-tech-team-2"")_ - [x] _Epic assigned (if needed)_ - [x] _Estimated (points assigned)_ - [x] _Sprint assigned (once planned)_ - [x] _Team member(s) assigned_ ",0, update monitor infrastructure and applications with datadog documentation description update the document based on feedback from the recent mini workshop with platform tech team resources feedback needs work make sure links are correct add a link that contains info about all the slack channels that alerts are sent to acceptance criteria the document is updated and shared with the team for review refinement guidance check the following before working on this issue team label assigned platform tech team epic assigned if needed estimated points assigned sprint assigned once planned team member s assigned ,0 82632,10264973681.0,IssuesEvent,2019-08-22 17:42:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"[Design] Product Health V2 ""Blue Sky"" Preliminary Design",analytics-insights design,"## User Story As a member of VSP, I need to understand what the Insights product health V2 tool looks like so I can plan my analytics accordingly. ## Goal Document and create a 'paper' draft of the product health V2 tool. ## Acceptance Criteria - [x] Document 'requirements' of the V2 ""blue sky"" tool - [x] Create a visual draft of the V2 ""blue sky"" tool - [ ] Share with the team & leadership ## Definition of Done - [ ] **Attached to a Milestone** - [ ] **Attached to an Epic** - [ ] **Labeled with Team** - [ ] **Labeled with Practice Area** - [ ] **Labeled with Type** ",1.0,"[Design] Product Health V2 ""Blue Sky"" Preliminary Design - ## User Story As a member of VSP, I need to understand what the Insights product health V2 tool looks like so I can plan my analytics accordingly. ## Goal Document and create a 'paper' draft of the product health V2 tool. ## Acceptance Criteria - [x] Document 'requirements' of the V2 ""blue sky"" tool - [x] Create a visual draft of the V2 ""blue sky"" tool - [ ] Share with the team & leadership ## Definition of Done - [ ] **Attached to a Milestone** - [ ] **Attached to an Epic** - [ ] **Labeled with Team** - [ ] **Labeled with Practice Area** - [ ] **Labeled with Type** ",1, product health blue sky preliminary design user story as a member of vsp i need to understand what the insights product health tool looks like so i can plan my analytics accordingly goal document and create a paper draft of the product health tool acceptance criteria document requirements of the blue sky tool create a visual draft of the blue sky tool share with the team leadership definition of done attached to a milestone attached to an epic labeled with team labeled with practice area labeled with type ,1 143756,22152634823.0,IssuesEvent,2022-06-03 18:38:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Post Guidelines in planned space,service-design,"## Issue Description Post Guidelines in determined location --- ## Tasks - [x] Post Guidelines in final form in determined location ## Acceptance Criteria - [x] Confluence updated with Guidelines and supporting explanations",1.0,"Post Guidelines in planned space - ## Issue Description Post Guidelines in determined location --- ## Tasks - [x] Post Guidelines in final form in determined location ## Acceptance Criteria - [x] Confluence updated with Guidelines and supporting explanations",1,post guidelines in planned space issue description post guidelines in determined location tasks post guidelines in final form in determined location acceptance criteria confluence updated with guidelines and supporting explanations,1 141348,21482555587.0,IssuesEvent,2022-04-26 19:16:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Discovery: Investigate upgrading to USWDS 2.x,frontend vsp-design-system-team,"## Background The VA design system is currently using USWDS 1.x as a base. USWDS is currently on 2.x. ## Discovery goal Is it worth spending the effort to make the upgrade? ## Questions - What's the estimated level of effort associated with the upgrade? - What benefit would we derive from it? - What does it do that we don't? - What are we re-implementing in the design system that we could lean on 2.x for?",1.0,"Discovery: Investigate upgrading to USWDS 2.x - ## Background The VA design system is currently using USWDS 1.x as a base. USWDS is currently on 2.x. ## Discovery goal Is it worth spending the effort to make the upgrade? ## Questions - What's the estimated level of effort associated with the upgrade? - What benefit would we derive from it? - What does it do that we don't? - What are we re-implementing in the design system that we could lean on 2.x for?",1,discovery investigate upgrading to uswds x background the va design system is currently using uswds x as a base uswds is currently on x discovery goal is it worth spending the effort to make the upgrade questions what s the estimated level of effort associated with the upgrade what benefit would we derive from it what does it do that we don t what are we re implementing in the design system that we could lean on x for ,1 143189,21956256934.0,IssuesEvent,2022-05-24 12:23:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Update Form Controls Label, Required, Error, and Aria-Describedby",vsp-design-system-team,"## Description The following components need to be examined to make sure they are following the same format and practices listed below, and if they are not they need to be adjusted to be in compliance with the rules listed. `va-date`, `va-number-input`, `va-text-input`, `va-radio`, `va-radio-options`, `va-checkbox-group`, `va-checkbox`, `va-select`, `va-textarea` Best Practices: * Destructure all values set via this ie: `const {value, label} = this;` between render and return * Label and Required should be in the following format: ``` {label && ( )} ``` * Error should be in the following format: ``` {error && {i18next.t('error')} {error} } ``` * Aria-describedby should be in the following format and should not have a custom prop unless required by another team: ``` aria-describedby={error ? 'error-message' : null} ``` ## Acceptance Criteria - [ ] Check all components listed above and make sure all are following the same guidelines via the best practices outlined above. - [ ] Make any adjustments needed within the existing components to follow the guidelines - [ ] Check and update the testing suites for the components with any changes made - [ ] Check and update the CSS on the components for any updates made ex: `.sr-only` and `.required`",1.0,"Update Form Controls Label, Required, Error, and Aria-Describedby - ## Description The following components need to be examined to make sure they are following the same format and practices listed below, and if they are not they need to be adjusted to be in compliance with the rules listed. `va-date`, `va-number-input`, `va-text-input`, `va-radio`, `va-radio-options`, `va-checkbox-group`, `va-checkbox`, `va-select`, `va-textarea` Best Practices: * Destructure all values set via this ie: `const {value, label} = this;` between render and return * Label and Required should be in the following format: ``` {label && ( )} ``` * Error should be in the following format: ``` {error && {i18next.t('error')} {error} } ``` * Aria-describedby should be in the following format and should not have a custom prop unless required by another team: ``` aria-describedby={error ? 'error-message' : null} ``` ## Acceptance Criteria - [ ] Check all components listed above and make sure all are following the same guidelines via the best practices outlined above. - [ ] Make any adjustments needed within the existing components to follow the guidelines - [ ] Check and update the testing suites for the components with any changes made - [ ] Check and update the CSS on the components for any updates made ex: `.sr-only` and `.required`",1,update form controls label required error and aria describedby description the following components need to be examined to make sure they are following the same format and practices listed below and if they are not they need to be adjusted to be in compliance with the rules listed va date va number input va text input va radio va radio options va checkbox group va checkbox va select va textarea best practices destructure all values set via this ie const value label this between render and return label and required should be in the following format label label required t required error should be in the following format error t error error aria describedby should be in the following format and should not have a custom prop unless required by another team aria describedby error error message null acceptance criteria check all components listed above and make sure all are following the same guidelines via the best practices outlined above make any adjustments needed within the existing components to follow the guidelines check and update the testing suites for the components with any changes made check and update the css on the components for any updates made ex sr only and required ,1 105925,13232808870.0,IssuesEvent,2020-08-18 13:54:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Content Revisions for View Payment's Prototype,design vsa vsa-ebenefits,"## Goal Given feedback, we need to implement the latest content changes for CH31 so the feature is copy complete and ready to go. ## Tasks - [x] Take the [recommendations](#) and update the features' prototypes - [x] Update the changelog in {feature-name}/research-design ## Acceptance Criteria - [x] The prototypes are updated with the latest recommendations, as needed - [x] Prototypes are shared with FE ",1.0,"Content Revisions for View Payment's Prototype - ## Goal Given feedback, we need to implement the latest content changes for CH31 so the feature is copy complete and ready to go. ## Tasks - [x] Take the [recommendations](#) and update the features' prototypes - [x] Update the changelog in {feature-name}/research-design ## Acceptance Criteria - [x] The prototypes are updated with the latest recommendations, as needed - [x] Prototypes are shared with FE ",1,content revisions for view payment s prototype goal given feedback we need to implement the latest content changes for so the feature is copy complete and ready to go tasks take the and update the features prototypes update the changelog in feature name research design acceptance criteria the prototypes are updated with the latest recommendations as needed prototypes are shared with fe ,1 126309,17018080161.0,IssuesEvent,2021-07-02 14:42:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Overall user experience] Design component or pattern in use isn't considered a best practice.,Staging collab-cycle-feedback design vsa-decision-tools,"### General Information #### VFS team name Decision Tools #### VFS product name Find a VA Form, Add Relevance, Popularity, Related to #### Point of Contact/Reviewers Allison Christman --- ### Platform Issue Design component or pattern in use isn't considered a best practice. ### Issue Details Spacing above and below search box content is not equal Spacing between form name and clickable and non clickable titles is inconsistent ### Link, screenshot or steps to recreate cat1_issue1_allison.png cat1_issue1_allison2.png ### Supporting Guidance Category 01, Issue 01 ### Other References --- ### Platform Recommendation Make the spacing above “Enter a…” and below the text box are the same Make the spacing between the clickable and non clickable titles consistent. ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] VFS team closes the ticket when the issue has been resolved",1.0,"[Overall user experience] Design component or pattern in use isn't considered a best practice. - ### General Information #### VFS team name Decision Tools #### VFS product name Find a VA Form, Add Relevance, Popularity, Related to #### Point of Contact/Reviewers Allison Christman --- ### Platform Issue Design component or pattern in use isn't considered a best practice. ### Issue Details Spacing above and below search box content is not equal Spacing between form name and clickable and non clickable titles is inconsistent ### Link, screenshot or steps to recreate cat1_issue1_allison.png cat1_issue1_allison2.png ### Supporting Guidance Category 01, Issue 01 ### Other References --- ### Platform Recommendation Make the spacing above “Enter a…” and below the text box are the same Make the spacing between the clickable and non clickable titles consistent. ### VFS Team Tasks to Complete - [ ] Comment on the ticket if there are questions or concerns - [ ] VFS team closes the ticket when the issue has been resolved",1, design component or pattern in use isn t considered a best practice general information vfs team name decision tools vfs product name find a va form add relevance popularity related to point of contact reviewers allison christman platform issue design component or pattern in use isn t considered a best practice issue details spacing above and below search box content is not equal spacing between form name and clickable and non clickable titles is inconsistent link screenshot or steps to recreate allison png png supporting guidance category issue other references platform recommendation make the spacing above “enter a…” and below the text box are the same make the spacing between the clickable and non clickable titles consistent vfs team tasks to complete comment on the ticket if there are questions or concerns vfs team closes the ticket when the issue has been resolved,1 183456,31479726005.0,IssuesEvent,2023-08-30 13:09:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Research DI experience of VFS teams,service-design,"## Purpose What would improve the experience of VFS teams going through DI? Let's ask them ## Tasks - [ ] Get recent teams who've gone through DI from GT - [ ] Schedule structured interviews (30 minute sessions?) - [ ] Create Interview plan/script - [ ] Execute sessions - [ ] Synthesize learnings from multiple teams - [ ] Identify recommendations ## Acceptance Criteria - [ ] Plan is ready - [ ] Interviews scheduled - [ ] synthesis complete - [ ] recommendations documented ",1.0,"Research DI experience of VFS teams - ## Purpose What would improve the experience of VFS teams going through DI? Let's ask them ## Tasks - [ ] Get recent teams who've gone through DI from GT - [ ] Schedule structured interviews (30 minute sessions?) - [ ] Create Interview plan/script - [ ] Execute sessions - [ ] Synthesize learnings from multiple teams - [ ] Identify recommendations ## Acceptance Criteria - [ ] Plan is ready - [ ] Interviews scheduled - [ ] synthesis complete - [ ] recommendations documented ",1,research di experience of vfs teams purpose what would improve the experience of vfs teams going through di let s ask them tasks get recent teams who ve gone through di from gt schedule structured interviews minute sessions create interview plan script execute sessions synthesize learnings from multiple teams identify recommendations acceptance criteria plan is ready interviews scheduled synthesis complete recommendations documented ,1 155442,24466168908.0,IssuesEvent,2022-10-07 15:11:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Workshop: map features discussion,service-design,"## Issue Description Meet to discuss what features we believe will be most important to include in the map. “A map of how all the different people, processes, technology, policies, and touchpoints fit together in the delivery of a service” --NNgroup user quote ## Desired Outcome(s) of a map -any SDT member(s) can use the resultant process to map out an end-to-end experience of performing a VFS user task -any SDT member(s) can use the resultant process to map out an end-to-end experience of using a Platform product -pain points for a given process should be easy to identify visually on map -Where a user engages and disengages from a mapped process is clear -**PO's desired outcome: Want to use it to help us to internally better understand How We Work, and also to communicate to others externally How We Work.** ## Resources Mural sandbox for [Features Notes](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1664887152841/9142688a12637c490a2b825602bbc1f4a31c419a?sender=u4397b715dc3690a417b71483) Concept shared by Nicole: [End-to-End mapping](https://app.mural.co/t/adhocvetsgov9623/template/d4c318b7-48d1-46d9-a64f-c12448617e2a) ## Tasks - Workshop: - [ ] Workshop the features that have been noted as most desirable ## Acceptance Criteria - [ ] A list will be compiled of the desirable features and characteristics of the map",1.0,"Workshop: map features discussion - ## Issue Description Meet to discuss what features we believe will be most important to include in the map. “A map of how all the different people, processes, technology, policies, and touchpoints fit together in the delivery of a service” --NNgroup user quote ## Desired Outcome(s) of a map -any SDT member(s) can use the resultant process to map out an end-to-end experience of performing a VFS user task -any SDT member(s) can use the resultant process to map out an end-to-end experience of using a Platform product -pain points for a given process should be easy to identify visually on map -Where a user engages and disengages from a mapped process is clear -**PO's desired outcome: Want to use it to help us to internally better understand How We Work, and also to communicate to others externally How We Work.** ## Resources Mural sandbox for [Features Notes](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1664887152841/9142688a12637c490a2b825602bbc1f4a31c419a?sender=u4397b715dc3690a417b71483) Concept shared by Nicole: [End-to-End mapping](https://app.mural.co/t/adhocvetsgov9623/template/d4c318b7-48d1-46d9-a64f-c12448617e2a) ## Tasks - Workshop: - [ ] Workshop the features that have been noted as most desirable ## Acceptance Criteria - [ ] A list will be compiled of the desirable features and characteristics of the map",1,workshop map features discussion issue description meet to discuss what features we believe will be most important to include in the map “a map of how all the different people processes technology policies and touchpoints fit together in the delivery of a service” nngroup user quote desired outcome s of a map any sdt member s can use the resultant process to map out an end to end experience of performing a vfs user task any sdt member s can use the resultant process to map out an end to end experience of using a platform product pain points for a given process should be easy to identify visually on map where a user engages and disengages from a mapped process is clear po s desired outcome want to use it to help us to internally better understand how we work and also to communicate to others externally how we work resources mural sandbox for concept shared by nicole tasks workshop workshop the features that have been noted as most desirable acceptance criteria a list will be compiled of the desirable features and characteristics of the map,1 760846,26658433760.0,IssuesEvent,2023-01-25 18:49:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Exception coercion logic is extracted from the `ApplicationController`,backend low priority platform-cop-backend platform-cop,"## User Story or Problem Statement As a VSP engineer, I need to clean up the `ApplicationController` error handling so I can more easily understand the logic involved. #### Background We should address some of the complexities in `ApplicationController`, related to rescuing and coercing error classes. The purpose of transforming an error class is so that `vets-api` can exercise finer-grained control over the specific responses the client consumes. E.g., if the `ApplicationController` rescues an `ActionController::ParameterMissing` exception, we expect it to transform into a `Common::Exceptions::ParameterMissing` object, which inherits from `Common::Exceptions::BaseError`. `Common::Exceptions::BaseError` is used throughout `vets-api` as a parent class which provides support for custom messaging via `i18n` keys in `exceptions.en.yml`. This key-value mapping allows developers to normalize the messaging sent when disparate backend service errors are encountered, as the consistency in quality of ""original"" messages is low. ## Goal `ApplicationController` includes a module that extends class w/ error handling concerns ## Acceptance Criteria - [ ] Error coercion logic is encapsulated into its own class - [ ] Sentry logging and tagging is extracted into `SentryLogging` module ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Exception coercion logic is extracted from the `ApplicationController` - ## User Story or Problem Statement As a VSP engineer, I need to clean up the `ApplicationController` error handling so I can more easily understand the logic involved. #### Background We should address some of the complexities in `ApplicationController`, related to rescuing and coercing error classes. The purpose of transforming an error class is so that `vets-api` can exercise finer-grained control over the specific responses the client consumes. E.g., if the `ApplicationController` rescues an `ActionController::ParameterMissing` exception, we expect it to transform into a `Common::Exceptions::ParameterMissing` object, which inherits from `Common::Exceptions::BaseError`. `Common::Exceptions::BaseError` is used throughout `vets-api` as a parent class which provides support for custom messaging via `i18n` keys in `exceptions.en.yml`. This key-value mapping allows developers to normalize the messaging sent when disparate backend service errors are encountered, as the consistency in quality of ""original"" messages is low. ## Goal `ApplicationController` includes a module that extends class w/ error handling concerns ## Acceptance Criteria - [ ] Error coercion logic is encapsulated into its own class - [ ] Sentry logging and tagging is extracted into `SentryLogging` module ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `triage`, `tools-improvements`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `call center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",0,exception coercion logic is extracted from the applicationcontroller user story or problem statement as a vsp engineer i need to clean up the applicationcontroller error handling so i can more easily understand the logic involved background we should address some of the complexities in applicationcontroller related to rescuing and coercing error classes the purpose of transforming an error class is so that vets api can exercise finer grained control over the specific responses the client consumes e g if the applicationcontroller rescues an actioncontroller parametermissing exception we expect it to transform into a common exceptions parametermissing object which inherits from common exceptions baseerror common exceptions baseerror is used throughout vets api as a parent class which provides support for custom messaging via keys in exceptions en yml this key value mapping allows developers to normalize the messaging sent when disparate backend service errors are encountered as the consistency in quality of original messages is low goal applicationcontroller includes a module that extends class w error handling concerns acceptance criteria error coercion logic is encapsulated into its own class sentry logging and tagging is extracted into sentrylogging module how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,0 126762,17106193494.0,IssuesEvent,2021-07-09 18:09:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,BDD Content Change - Supporting Language,BDD design external-request vsa vsa-claims-appeals,"## Issue Description Revise BDD content --- ## Tasks - Step 3 of 5 page; recommend revising ""Step 3 of 5: Supporting evidence"" to read ""Step 3 of 5: Submitting supporting evidence, such as additional VA Forms, medical records, separation documents (DD Form 214) etc. ## Acceptance Criteria - [ ] Revised content --- ",1.0,"BDD Content Change - Supporting Language - ## Issue Description Revise BDD content --- ## Tasks - Step 3 of 5 page; recommend revising ""Step 3 of 5: Supporting evidence"" to read ""Step 3 of 5: Submitting supporting evidence, such as additional VA Forms, medical records, separation documents (DD Form 214) etc. ## Acceptance Criteria - [ ] Revised content --- ",1,bdd content change supporting language issue description revise bdd content tasks step of page recommend revising step of supporting evidence to read step of submitting supporting evidence such as additional va forms medical records separation documents dd form etc acceptance criteria revised content ,1 134190,19097102572.0,IssuesEvent,2021-11-29 17:50:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,"[Design, PM] Notifications: Schedule & prep for Design Intent",design product my-va-dashboard vsa-authenticated-exp planned-work,"## Background We need to prepare for the Design Intent as part of the collaboration cycle [Design Intent guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Design-intent.1782153235.html) ## Tasks - [ ] PM will schedule Design Intent - [ ] Designer prep artifacts for Design Intent (guidance linked above) with assistance from PM as needed",1.0,"[Design, PM] Notifications: Schedule & prep for Design Intent - ## Background We need to prepare for the Design Intent as part of the collaboration cycle [Design Intent guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Design-intent.1782153235.html) ## Tasks - [ ] PM will schedule Design Intent - [ ] Designer prep artifacts for Design Intent (guidance linked above) with assistance from PM as needed",1, notifications schedule prep for design intent background we need to prepare for the design intent as part of the collaboration cycle tasks pm will schedule design intent designer prep artifacts for design intent guidance linked above with assistance from pm as needed,1 121080,15836828509.0,IssuesEvent,2021-04-06 19:53:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[MCP] Veteran codesign research readout,MCP design research vsa vsa-benefits-2,"## Issue Description Once we complete initial VHA Veteran discovery research, we must create a research readout of our findings. --- ## Tasks - [ ] Create a readout for Veteran discovery research - [ ] Upload to GH ## Acceptance Criteria - [ ] Readout created and uploaded to GH",1.0,"[MCP] Veteran codesign research readout - ## Issue Description Once we complete initial VHA Veteran discovery research, we must create a research readout of our findings. --- ## Tasks - [ ] Create a readout for Veteran discovery research - [ ] Upload to GH ## Acceptance Criteria - [ ] Readout created and uploaded to GH",1, veteran codesign research readout issue description once we complete initial vha veteran discovery research we must create a research readout of our findings tasks create a readout for veteran discovery research upload to gh acceptance criteria readout created and uploaded to gh,1 123856,16542959642.0,IssuesEvent,2021-05-27 19:22:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,508-enhancement [MOBILE DESIGN]: Consider iterating typeahead UX pattern for mobile screen reader users ,508-enhancement 508-issue-mobile-design 508-issue-screenreader 508/Accessibility needs research vsa-search-discovery,"## Feedback framework - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix. ## Point of Contact **VFS Point of Contact:** _Josh, Angela, Trevor_ ## User Story or Problem Statement As a relatively new mobile screen reader user, I want suggested search results to remain on screen after I press the ""Done"" button on the iOS keypad. ## Details While testing the typeahead in iOS with VoiceOver turned on, I noticed the suggested results disappeared as soon as I pressed the Done button. I'm not sure this is a bad UX; I'm also not sure it's not. I'm opening this as a spike ticket for iterating on the UX if the team [proceeds with user research suggested in 20719](https://github.com/department-of-veterans-affairs/va.gov-team/issues/20719). I like the [Vue Autocomplete ](https://darrenjennings.github.io/vue-autosuggest/)because I can swipe right with the keypad still open to move to the suggested results. This is not meant to be prescriptive, just an example of alternative UX. **Related Issue:** https://github.com/downshift-js/downshift/issues/779 ## Acceptance Criteria - [ ] Autocomplete maintains current behavior EXCEPT - [ ] iOS users can swipe right with the keypad open and under focus, to view search results ",1.0,"508-enhancement [MOBILE DESIGN]: Consider iterating typeahead UX pattern for mobile screen reader users - ## Feedback framework - **❗️ Must** for if the feedback must be applied - **⚠️ Should** if the feedback is best practice - **✔️ Consider** for suggestions/enhancements ## Definition of done 1. Review and acknowledge feedback. 1. Fix and/or document decisions made. 1. Accessibility specialist will close ticket after reviewing documented decisions / validating fix. ## Point of Contact **VFS Point of Contact:** _Josh, Angela, Trevor_ ## User Story or Problem Statement As a relatively new mobile screen reader user, I want suggested search results to remain on screen after I press the ""Done"" button on the iOS keypad. ## Details While testing the typeahead in iOS with VoiceOver turned on, I noticed the suggested results disappeared as soon as I pressed the Done button. I'm not sure this is a bad UX; I'm also not sure it's not. I'm opening this as a spike ticket for iterating on the UX if the team [proceeds with user research suggested in 20719](https://github.com/department-of-veterans-affairs/va.gov-team/issues/20719). I like the [Vue Autocomplete ](https://darrenjennings.github.io/vue-autosuggest/)because I can swipe right with the keypad still open to move to the suggested results. This is not meant to be prescriptive, just an example of alternative UX. **Related Issue:** https://github.com/downshift-js/downshift/issues/779 ## Acceptance Criteria - [ ] Autocomplete maintains current behavior EXCEPT - [ ] iOS users can swipe right with the keypad open and under focus, to view search results ",1, enhancement consider iterating typeahead ux pattern for mobile screen reader users feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact josh angela trevor user story or problem statement as a relatively new mobile screen reader user i want suggested search results to remain on screen after i press the done button on the ios keypad details while testing the typeahead in ios with voiceover turned on i noticed the suggested results disappeared as soon as i pressed the done button i m not sure this is a bad ux i m also not sure it s not i m opening this as a spike ticket for iterating on the ux if the team i like the i can swipe right with the keypad still open to move to the suggested results this is not meant to be prescriptive just an example of alternative ux related issue acceptance criteria autocomplete maintains current behavior except ios users can swipe right with the keypad open and under focus to view search results ,1 141172,21419433789.0,IssuesEvent,2022-04-22 14:13:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Generate examples of good SD in guidelines space (Is my tool easy to find? Is it clearly named? etc),service-design,"## Issue Description Provide examples of good SD in guidelines space (Is my tool easy to find? Is it clearly named? etc) --- ## Tasks - [ ] Provide examples of good SD in guidelines space (Is my tool easy to find? Is it clearly named? etc) ## Acceptance Criteria - [ ] Preliminary list of Provide examples of good SD in guidelines space ",1.0,"Generate examples of good SD in guidelines space (Is my tool easy to find? Is it clearly named? etc) - ## Issue Description Provide examples of good SD in guidelines space (Is my tool easy to find? Is it clearly named? etc) --- ## Tasks - [ ] Provide examples of good SD in guidelines space (Is my tool easy to find? Is it clearly named? etc) ## Acceptance Criteria - [ ] Preliminary list of Provide examples of good SD in guidelines space ",1,generate examples of good sd in guidelines space is my tool easy to find is it clearly named etc issue description provide examples of good sd in guidelines space is my tool easy to find is it clearly named etc tasks provide examples of good sd in guidelines space is my tool easy to find is it clearly named etc acceptance criteria preliminary list of provide examples of good sd in guidelines space ,1 120101,15703576714.0,IssuesEvent,2021-03-26 14:01:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,"Inconsistent/buggy focus for ""Search this area"" button",508/Accessibility Q121-priority bug facilities-design-review frontend vsa vsa-facilities,"## What happened? During his validation for [#6911], Josh observed the inconsistent focus management between zoom in/out and ""search this area"". Engineers have addressed the announcement of the button and change in context in a way that is appropriate for users who may need to adjust the zoom level by interacting with the controls more than once. one additional tweak - we need to provide Voiceover instructions for how the button can be reached (ie: _you can reach the ""Search this area"" button by tabbing..._) ## Desired behavior Veterans using voiceover should how to access the button when it receives focus ## Acceptance Criteria - [ ] A Veteran using Safari/Voiceover can use the space or enter keys to move focus to the ""search this area"" button. ",1.0,"Inconsistent/buggy focus for ""Search this area"" button - ## What happened? During his validation for [#6911], Josh observed the inconsistent focus management between zoom in/out and ""search this area"". Engineers have addressed the announcement of the button and change in context in a way that is appropriate for users who may need to adjust the zoom level by interacting with the controls more than once. one additional tweak - we need to provide Voiceover instructions for how the button can be reached (ie: _you can reach the ""Search this area"" button by tabbing..._) ## Desired behavior Veterans using voiceover should how to access the button when it receives focus ## Acceptance Criteria - [ ] A Veteran using Safari/Voiceover can use the space or enter keys to move focus to the ""search this area"" button. ",1,inconsistent buggy focus for search this area button what happened during his validation for josh observed the inconsistent focus management between zoom in out and search this area engineers have addressed the announcement of the button and change in context in a way that is appropriate for users who may need to adjust the zoom level by interacting with the controls more than once one additional tweak we need to provide voiceover instructions for how the button can be reached ie you can reach the search this area button by tabbing desired behavior veterans using voiceover should how to access the button when it receives focus acceptance criteria a veteran using safari voiceover can use the space or enter keys to move focus to the search this area button ,1 143248,21965602957.0,IssuesEvent,2022-05-24 19:57:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[508] Add page info to Pagination documentation,508/Accessibility 508-issue-focus-mgmt vsp-design-system-team 508-issue-screenreader,"## Description To provide optimal screenreader usability, the pagination documentation needs to include a section on adding a page info block above the content. When the page is changed, focus should be moved to this paragraph. Example: ``` Showing 21 through 30 of 50 items, Page 3 of 5 ------ card 21 ------ card 22 ------ ... ------ card 30 ------ < Prev 1 [2] 3 4 5 Next > ```
Example from Facilities locator
cc: @joshkimux ## Tasks - [ ] Add documentation on adding a pager information block that receives focus after changing pages - [ ] Provide examples - [ ] Accessibility review of content ## Definition of done - [ ] All tasks complete ",1.0,"[508] Add page info to Pagination documentation - ## Description To provide optimal screenreader usability, the pagination documentation needs to include a section on adding a page info block above the content. When the page is changed, focus should be moved to this paragraph. Example: ``` Showing 21 through 30 of 50 items, Page 3 of 5 ------ card 21 ------ card 22 ------ ... ------ card 30 ------ < Prev 1 [2] 3 4 5 Next > ```
Example from Facilities locator
cc: @joshkimux ## Tasks - [ ] Add documentation on adding a pager information block that receives focus after changing pages - [ ] Provide examples - [ ] Accessibility review of content ## Definition of done - [ ] All tasks complete ",1, add page info to pagination documentation description to provide optimal screenreader usability the pagination documentation needs to include a section on adding a page info block above the content when the page is changed focus should be moved to this paragraph example showing through of items page of card card card example from facilities locator img width alt showing through of results for filtered items in the facility location page src cc joshkimux tasks add documentation on adding a pager information block that receives focus after changing pages provide examples accessibility review of content definition of done all tasks complete ,1 105842,13223565479.0,IssuesEvent,2020-08-17 17:27:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Scale display of large number of disabilities (step 2 of 6),design research vsa-benefits vsa-decision-reviews,"## User Story or Problem Statement As a designer, I need to identify a way to display multiple number of disabilities so the Veteran can locate the needed disabilities without confusion. ## Goal _Create a user-friendly view of a large number of disabilities_ ## Acceptance Criteria - _As a system user, I want to avoid being confused by a large number of items in a single view._ ## Definition of Done - [ ] Identify current issue of large number of disabilities displayed - [ ] Identify design of proposed solution for displaying large number of disabilities - [ ] Request content review from VSP (Yana create a ticket and assign Peggy Gannon) - [ ] _*This relates to epic ticket #1053 *Check the box below when this has been completed and comment ""done""._ ## Screen Shots",1.0,"[Design] Scale display of large number of disabilities (step 2 of 6) - ## User Story or Problem Statement As a designer, I need to identify a way to display multiple number of disabilities so the Veteran can locate the needed disabilities without confusion. ## Goal _Create a user-friendly view of a large number of disabilities_ ## Acceptance Criteria - _As a system user, I want to avoid being confused by a large number of items in a single view._ ## Definition of Done - [ ] Identify current issue of large number of disabilities displayed - [ ] Identify design of proposed solution for displaying large number of disabilities - [ ] Request content review from VSP (Yana create a ticket and assign Peggy Gannon) - [ ] _*This relates to epic ticket #1053 *Check the box below when this has been completed and comment ""done""._ ## Screen Shots",1, scale display of large number of disabilities step of user story or problem statement as a designer i need to identify a way to display multiple number of disabilities so the veteran can locate the needed disabilities without confusion goal create a user friendly view of a large number of disabilities acceptance criteria as a system user i want to avoid being confused by a large number of items in a single view definition of done identify current issue of large number of disabilities displayed identify design of proposed solution for displaying large number of disabilities request content review from vsp yana create a ticket and assign peggy gannon this relates to epic ticket check the box below when this has been completed and comment done screen shots,1 107354,13452570339.0,IssuesEvent,2020-09-08 22:30:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Prepare for Research: Facility Locator Redesign,design research vsa vsa-facilities,"## Issue Description How might we test a first iteration of the Facility Locator redesign? ## Goals -Learn how Veterans and Caregivers may use the new filter feature as well as the addition of the quick links. Answer the following: - Is it more intuitive to have two search fields instead of three? - How are people filtering services for each facility type? - Is there a need for a Google-like open search --- ## Tasks - [ ] Review [card sort readout](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/facilities/facility-locator/research/user-research/redesign/filter-categorization) - [ ] Review and complete draft [research plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/facilities/facility-locator/research/user-research/redesign/prototype-testing/prototype-v1/research-plan.md) - [ ] Create conversation guide - [ ] Ensure prototype supports research plan and conversation guide ## Acceptance Criteria - [ ] Approved research plan and conversation guide - [ ] Prototype can support research plan and conversation guide and is available for user research sessions --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Prepare for Research: Facility Locator Redesign - ## Issue Description How might we test a first iteration of the Facility Locator redesign? ## Goals -Learn how Veterans and Caregivers may use the new filter feature as well as the addition of the quick links. Answer the following: - Is it more intuitive to have two search fields instead of three? - How are people filtering services for each facility type? - Is there a need for a Google-like open search --- ## Tasks - [ ] Review [card sort readout](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/facilities/facility-locator/research/user-research/redesign/filter-categorization) - [ ] Review and complete draft [research plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/facilities/facility-locator/research/user-research/redesign/prototype-testing/prototype-v1/research-plan.md) - [ ] Create conversation guide - [ ] Ensure prototype supports research plan and conversation guide ## Acceptance Criteria - [ ] Approved research plan and conversation guide - [ ] Prototype can support research plan and conversation guide and is available for user research sessions --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,prepare for research facility locator redesign issue description how might we test a first iteration of the facility locator redesign goals learn how veterans and caregivers may use the new filter feature as well as the addition of the quick links answer the following is it more intuitive to have two search fields instead of three how are people filtering services for each facility type is there a need for a google like open search tasks review review and complete draft create conversation guide ensure prototype supports research plan and conversation guide acceptance criteria approved research plan and conversation guide prototype can support research plan and conversation guide and is available for user research sessions how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 111964,14174994757.0,IssuesEvent,2020-11-12 20:49:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Put VA Banner on the component document Storybook link,design-system-team frontend,"## Issue Description Put a VA banner on the component document Storybook link so that users know that they are looking at VSP design system. --- ## Tasks - [ ] Put VA Banner on the component document Storybook link ## Acceptance Criteria - [ ] When I go to the component page on design.va.gov, I see a VA banner --- ",1.0,"Put VA Banner on the component document Storybook link - ## Issue Description Put a VA banner on the component document Storybook link so that users know that they are looking at VSP design system. --- ## Tasks - [ ] Put VA Banner on the component document Storybook link ## Acceptance Criteria - [ ] When I go to the component page on design.va.gov, I see a VA banner --- ",1,put va banner on the component document storybook link issue description put a va banner on the component document storybook link so that users know that they are looking at vsp design system tasks put va banner on the component document storybook link acceptance criteria when i go to the component page on design va gov i see a va banner ,1 149245,23447920428.0,IssuesEvent,2022-08-15 21:46:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design | Profile | Personal info revisions | UAT | Hint Text,design vsa vsa-authenticated-exp profile personal-information,"## Background Confirm that Preferred name hint text is sufficient and dropdown is not needed. ## Tasks - [x] Determine if Preferred name should include a dropdown instead of the current hint text - [x] Review research feedback - [x] Consider accessibility questions ## Acceptance Criteria - [x] Check on accessibility guidance - [x] Determine approach and share with PM and PO ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1.0,"Design | Profile | Personal info revisions | UAT | Hint Text - ## Background Confirm that Preferred name hint text is sufficient and dropdown is not needed. ## Tasks - [x] Determine if Preferred name should include a dropdown instead of the current hint text - [x] Review research feedback - [x] Consider accessibility questions ## Acceptance Criteria - [x] Check on accessibility guidance - [x] Determine approach and share with PM and PO ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1,design profile personal info revisions uat hint text background confirm that preferred name hint text is sufficient and dropdown is not needed tasks determine if preferred name should include a dropdown instead of the current hint text review research feedback consider accessibility questions acceptance criteria check on accessibility guidance determine approach and share with pm and po how to configure this issue include practice area in title e g include project initiative name e g auth profile address change messaging add label for practice area frontend backend design add label for project if applicable assign to a profile team member associate with an epic if applicable if creating for yourself estimate work if enough info exists to do so ,1 122675,16196887363.0,IssuesEvent,2021-05-04 15:34:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design expandable alert for Vet Center operating status,design frontend vet-center vsa vsa-facilities,"## Issue Description The VAMC product has an [Operating Status page](https://www.va.gov/pittsburgh-health-care/operating-status/) which provides details on facility access. The Facility Locator provides the details on the [Facility Detail page](https://www.va.gov/find-locations/facility/vc_0434V). The Vet Center product does not have an equivalent experience to connect to the operating status displayed on the Locations page. We identified a component that is being used on [Suicide Prevention pages](https://www.va.gov/health-care/health-needs-conditions/mental-health/suicide-prevention/) ![image](https://user-images.githubusercontent.com/55411834/114786347-30113f00-9d3b-11eb-8593-238897e60e73.png) --- ## Tasks - [x] Design an expandable alert that can be used to display the operating status details for a Vet Center location. ## Acceptance Criteria - [ ] Design spec ready for FE engineers to implement ",1.0,"Design expandable alert for Vet Center operating status - ## Issue Description The VAMC product has an [Operating Status page](https://www.va.gov/pittsburgh-health-care/operating-status/) which provides details on facility access. The Facility Locator provides the details on the [Facility Detail page](https://www.va.gov/find-locations/facility/vc_0434V). The Vet Center product does not have an equivalent experience to connect to the operating status displayed on the Locations page. We identified a component that is being used on [Suicide Prevention pages](https://www.va.gov/health-care/health-needs-conditions/mental-health/suicide-prevention/) ![image](https://user-images.githubusercontent.com/55411834/114786347-30113f00-9d3b-11eb-8593-238897e60e73.png) --- ## Tasks - [x] Design an expandable alert that can be used to display the operating status details for a Vet Center location. ## Acceptance Criteria - [ ] Design spec ready for FE engineers to implement ",1,design expandable alert for vet center operating status issue description the vamc product has an which provides details on facility access the facility locator provides the details on the the vet center product does not have an equivalent experience to connect to the operating status displayed on the locations page we identified a component that is being used on tasks design an expandable alert that can be used to display the operating status details for a vet center location acceptance criteria design spec ready for fe engineers to implement ,1 105049,13159417664.0,IssuesEvent,2020-08-10 15:48:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Social Listening of Veteran Concerns around CST,Claim Status Tool design discovery vsa-benefits,"We need to gather information as to what pain points may exist in the claim status tool. Specifically, we are looking for general usability issues that we can turn into bug tickets. We will do this via a website where veterans seek help on navigating va.gov - called hadit.com. ### Tasks - [x] Create a Mural board with notes of issues voiced by veterans - [x] Categorize issues in Mural board - [x] Create list of QA issues to test on the claim status tool ### Acceptance Criteria - [x] QA issue list has been generated",1.0,"[Design] Social Listening of Veteran Concerns around CST - We need to gather information as to what pain points may exist in the claim status tool. Specifically, we are looking for general usability issues that we can turn into bug tickets. We will do this via a website where veterans seek help on navigating va.gov - called hadit.com. ### Tasks - [x] Create a Mural board with notes of issues voiced by veterans - [x] Categorize issues in Mural board - [x] Create list of QA issues to test on the claim status tool ### Acceptance Criteria - [x] QA issue list has been generated",1, social listening of veteran concerns around cst we need to gather information as to what pain points may exist in the claim status tool specifically we are looking for general usability issues that we can turn into bug tickets we will do this via a website where veterans seek help on navigating va gov called hadit com tasks create a mural board with notes of issues voiced by veterans categorize issues in mural board create list of qa issues to test on the claim status tool acceptance criteria qa issue list has been generated,1 99208,12406255771.0,IssuesEvent,2020-05-21 18:47:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] Create an alert for if a user tries to edit multiple sections in the profile,design needs-grooming profile vsa-authenticated-exp,"##User Story With us moving away from modals to edit contact info, it opens the possibility of users being able to be edit multiple pieces of contact info data at the same time. Users should not be able to edit multiple pieces of contact info and need to be alerted if they are switching from one form to another they will lose their information or need to save. (Maybe a modal, maybe something on the page?) [Slack Conversation](https://dsva.slack.com/archives/C909ZG2BB/p1590079754288900) Epic #2086 ## Tasks - [ ] Design alert - [ ] Work with Peggy to get correct copy ## Acceptance criteria - [ ] Design and copy is approved",1.0,"[Design] Create an alert for if a user tries to edit multiple sections in the profile - ##User Story With us moving away from modals to edit contact info, it opens the possibility of users being able to be edit multiple pieces of contact info data at the same time. Users should not be able to edit multiple pieces of contact info and need to be alerted if they are switching from one form to another they will lose their information or need to save. (Maybe a modal, maybe something on the page?) [Slack Conversation](https://dsva.slack.com/archives/C909ZG2BB/p1590079754288900) Epic #2086 ## Tasks - [ ] Design alert - [ ] Work with Peggy to get correct copy ## Acceptance criteria - [ ] Design and copy is approved",1, create an alert for if a user tries to edit multiple sections in the profile user story with us moving away from modals to edit contact info it opens the possibility of users being able to be edit multiple pieces of contact info data at the same time users should not be able to edit multiple pieces of contact info and need to be alerted if they are switching from one form to another they will lose their information or need to save maybe a modal maybe something on the page epic tasks design alert work with peggy to get correct copy acceptance criteria design and copy is approved,1 152465,23979515463.0,IssuesEvent,2022-09-13 14:06:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Improve Communications Playbook via Streamlining of Workflow and Clarification of steps,Epic service-design platform-initiative crew-platform team-platform-service-design PO Endorsed platform-okrs FY22-Q3,"## Problem Statement The MVP of the Communications Playbook established some primary guidance on how and where to communicate information across the Platform. However, it remains somewhat confusing in format and steps. We intend to improve upon its clarity, add a step-by-step template, and perform additional research to inform recommendations. ## High Level User Stories As a Platform team member, I want to know what steps to follow to communicate important information to Platform and VFS teams. As an OCTODE lead, I want to know what channel(s) are to be used for communication of important information ## Hypothesis or Bet By improving the clarity of the recommended paths, and providing a communication template, Platform teams will more successfully be able to utilize the playbook. ## Known Blockers/Dependencies There are various opinions on the optimal communication channels for specific information. We will need to research these and justify the resultant choice(s). ## Definition of Done - [x] The existing form of the playbook will be modified to streamline instructions and clarify steps. - [x] A new communication template will be created to aid in these steps. - [x] The proper communication channels will be incorporated and clearly explained. - [x] The playbook is added to the [Platform Initiative Template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/.github/ISSUE_TEMPLATE/platform-initiative.md) ## Projected Launch Date Thursday, 8/4/22 ## Launch Checklist ### Is this service / tool / feature... ### ... tested? - [x] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [x] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [x] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [x] New documentation is written pursuant to our [documentation style guide](https://vfs.atlassian.net/wiki/spaces/AP/pages/622264362/Style+guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [x] Internal-facing: there's a [Product Outline](https://vfs.atlassian.net/wiki/spaces/PMCP/pages/1924628490/Product+Outline+Template) - [ ] External-facing: a [User Guide on Platform Website](https://vfs.atlassian.net/wiki/spaces/AP/pages/1477017691/Platform+website+guidelines) exists for this product/feature tool ### ... measurable - [x] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://depo-platform-documentation.scrollhelp.site/analytics-monitoring/Analytics-customer-support-guide.1586823275.html) - [x] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ### When you're ready to launch... - [x] Conduct a [go/no-go] (https://vfs.atlassian.net/wiki/spaces/AP/pages/1670938648/Platform+Crew+Office+Hours#Go%2FNo-Go) when you're almost ready to launch. ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: Change Communication Playbook * **[Product Outline](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1956020286/Product+Outline+-+Platform+Communications+Playbook)**: * **[User Guide](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2277277697/Welcome+to+the+Change+Communication+Playbook)**: ### Testing * **Usability test**: N/A * **Manual QA**: N/A * **Automated tests**: N/A ### Measurement * **[Success metrics](https://vfs.atlassian.net/wiki/spaces/AP/pages/2226356277/Q3+2022+Crew+Teams+-+OKR+Tracking#Service-Design-Team)**: * **[Release plan](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1956020286/Product+Outline+-+Platform+Communications+Playbook#Release-Plan)**: ",2.0,"Improve Communications Playbook via Streamlining of Workflow and Clarification of steps - ## Problem Statement The MVP of the Communications Playbook established some primary guidance on how and where to communicate information across the Platform. However, it remains somewhat confusing in format and steps. We intend to improve upon its clarity, add a step-by-step template, and perform additional research to inform recommendations. ## High Level User Stories As a Platform team member, I want to know what steps to follow to communicate important information to Platform and VFS teams. As an OCTODE lead, I want to know what channel(s) are to be used for communication of important information ## Hypothesis or Bet By improving the clarity of the recommended paths, and providing a communication template, Platform teams will more successfully be able to utilize the playbook. ## Known Blockers/Dependencies There are various opinions on the optimal communication channels for specific information. We will need to research these and justify the resultant choice(s). ## Definition of Done - [x] The existing form of the playbook will be modified to streamline instructions and clarify steps. - [x] A new communication template will be created to aid in these steps. - [x] The proper communication channels will be incorporated and clearly explained. - [x] The playbook is added to the [Platform Initiative Template](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/.github/ISSUE_TEMPLATE/platform-initiative.md) ## Projected Launch Date Thursday, 8/4/22 ## Launch Checklist ### Is this service / tool / feature... ### ... tested? - [x] Usability test (_TODO: link_) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it. - [x] ... and issues discovered in usability testing have been addressed. * _Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing._ - [x] End-to-end [manual QA](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/quality-assurance/README.md) or [UAT](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/research/planning/what-is-uat.md) is complete, to validate there are no high-severity issues before launching - [ ] _(if applicable)_ New functionality has thorough, automated tests running in CI/CD ### ... documented? - [x] New documentation is written pursuant to our [documentation style guide](https://vfs.atlassian.net/wiki/spaces/AP/pages/622264362/Style+guide) - [ ] Product is included in the [List of VSP Products](https://docs.google.com/spreadsheets/d/1Fn2lD419WE3sTZJtN2Ensrjqaz0jH3WvLaBtn812Wjo/edit#gid=0) * _List the existing product that this initiative fits within, or add a new product to this list._ - [x] Internal-facing: there's a [Product Outline](https://vfs.atlassian.net/wiki/spaces/PMCP/pages/1924628490/Product+Outline+Template) - [ ] External-facing: a [User Guide on Platform Website](https://vfs.atlassian.net/wiki/spaces/AP/pages/1477017691/Platform+website+guidelines) exists for this product/feature tool ### ... measurable - [x] _(if applicable)_ This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it. * For help, see: [Analytics team](https://depo-platform-documentation.scrollhelp.site/analytics-monitoring/Analytics-customer-support-guide.1586823275.html) - [x] This change has an accompanying [VSP Initiative Release Plan](https://github.com/department-of-veterans-affairs/va.gov-team/issues/new/choose). ### When you're ready to launch... - [x] Conduct a [go/no-go] (https://vfs.atlassian.net/wiki/spaces/AP/pages/1670938648/Platform+Crew+Office+Hours#Go%2FNo-Go) when you're almost ready to launch. ## Required Artifacts ### Documentation * **`PRODUCT_NAME`**: Change Communication Playbook * **[Product Outline](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1956020286/Product+Outline+-+Platform+Communications+Playbook)**: * **[User Guide](https://vfs.atlassian.net/wiki/spaces/SDT/pages/2277277697/Welcome+to+the+Change+Communication+Playbook)**: ### Testing * **Usability test**: N/A * **Manual QA**: N/A * **Automated tests**: N/A ### Measurement * **[Success metrics](https://vfs.atlassian.net/wiki/spaces/AP/pages/2226356277/Q3+2022+Crew+Teams+-+OKR+Tracking#Service-Design-Team)**: * **[Release plan](https://vfs.atlassian.net/wiki/spaces/SDT/pages/1956020286/Product+Outline+-+Platform+Communications+Playbook#Release-Plan)**: ",1,improve communications playbook via streamlining of workflow and clarification of steps problem statement the mvp of the communications playbook established some primary guidance on how and where to communicate information across the platform however it remains somewhat confusing in format and steps we intend to improve upon its clarity add a step by step template and perform additional research to inform recommendations high level user stories as a platform team member i want to know what steps to follow to communicate important information to platform and vfs teams as an octode lead i want to know what channel s are to be used for communication of important information hypothesis or bet by improving the clarity of the recommended paths and providing a communication template platform teams will more successfully be able to utilize the playbook known blockers dependencies there are various opinions on the optimal communication channels for specific information we will need to research these and justify the resultant choice s definition of done the existing form of the playbook will be modified to streamline instructions and clarify steps a new communication template will be created to aid in these steps the proper communication channels will be incorporated and clearly explained the playbook is added to the projected launch date thursday launch checklist is this service tool feature tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a external facing a exists for this product feature tool measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying when you re ready to launch conduct a when you re almost ready to launch required artifacts documentation product name change communication playbook testing usability test n a manual qa n a automated tests n a measurement ,1 151137,23768775733.0,IssuesEvent,2022-09-01 14:42:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Design | Personal Info | Product Outline Design Documentation ,design vsa authenticated-experience profile personal-information,"## Background We need to audit, update and/or create design documentation for Personal information. Good examples can be found within Direct deposit or Contact info features which have recently been updated. ## Tasks - [x] Update and/or create use cases for this feature - [x] Create user flows - [ ] Create/update screen mocks and text ## Acceptance Criteria - [ ] Post to appropriate sections of GitHub and sketch - [ ] Check that links from product outline are up to date ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1.0,"Design | Personal Info | Product Outline Design Documentation - ## Background We need to audit, update and/or create design documentation for Personal information. Good examples can be found within Direct deposit or Contact info features which have recently been updated. ## Tasks - [x] Update and/or create use cases for this feature - [x] Create user flows - [ ] Create/update screen mocks and text ## Acceptance Criteria - [ ] Post to appropriate sections of GitHub and sketch - [ ] Check that links from product outline are up to date ## How to configure this issue - Include practice area in title -- e.g., [Design], [FE], [BE] - Include project/initiative name - e.g., Auth Profile: Address Change Messaging - Add label for practice area (frontend, backend, design) - Add label for project if applicable - Assign to a Profile team member - Associate with an Epic if applicable - If creating for yourself: estimate work if enough info exists to do so ",1,design personal info product outline design documentation background we need to audit update and or create design documentation for personal information good examples can be found within direct deposit or contact info features which have recently been updated tasks update and or create use cases for this feature create user flows create update screen mocks and text acceptance criteria post to appropriate sections of github and sketch check that links from product outline are up to date how to configure this issue include practice area in title e g include project initiative name e g auth profile address change messaging add label for practice area frontend backend design add label for project if applicable assign to a profile team member associate with an epic if applicable if creating for yourself estimate work if enough info exists to do so ,1 263505,28036868724.0,IssuesEvent,2023-03-28 15:36:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Datadog] Consult w/ Datadog SMEs to inform RBAC approach ,monitoring security platform-tech-team-2,"## Description Before we can [Develop custom roles that allow write access for VFS teams](https://app.zenhub.com/workspaces/platform-tech-team-2-633efe4ca5a428e5294d7ade/issues/gh/department-of-veterans-affairs/va.gov-team/47066), we need to understand the best approach given the Platform's current Datadog setup and configuration. There are a number of options available for Role Based Access Control (RBAC) that help to define permissions and restrict access to individual resources, based on pre-defined or custom roles. We can consult w/ Datadog SMEs directly to gain their recommendations. ## Resources - [Datadog Documentation: Role Based Access Control ](https://docs.datadoghq.com/account_management/rbac/?tab=datadogapplication) ## Acceptance Criteria - [ ] We will meet with Datadog SMEs to decide the path forward ## Refinement Guidance - Check the following before working on this issue: - [x] _Team label assigned (""platform-tech-team-2"")_ - [x] _Epic assigned (if needed)_ - [x] _Estimated (points assigned)_ - [ ] _Sprint assigned (once planned)_ - [ ] _Team member(s) assigned_ ",True,"[Datadog] Consult w/ Datadog SMEs to inform RBAC approach - ## Description Before we can [Develop custom roles that allow write access for VFS teams](https://app.zenhub.com/workspaces/platform-tech-team-2-633efe4ca5a428e5294d7ade/issues/gh/department-of-veterans-affairs/va.gov-team/47066), we need to understand the best approach given the Platform's current Datadog setup and configuration. There are a number of options available for Role Based Access Control (RBAC) that help to define permissions and restrict access to individual resources, based on pre-defined or custom roles. We can consult w/ Datadog SMEs directly to gain their recommendations. ## Resources - [Datadog Documentation: Role Based Access Control ](https://docs.datadoghq.com/account_management/rbac/?tab=datadogapplication) ## Acceptance Criteria - [ ] We will meet with Datadog SMEs to decide the path forward ## Refinement Guidance - Check the following before working on this issue: - [x] _Team label assigned (""platform-tech-team-2"")_ - [x] _Epic assigned (if needed)_ - [x] _Estimated (points assigned)_ - [ ] _Sprint assigned (once planned)_ - [ ] _Team member(s) assigned_ ",0, consult w datadog smes to inform rbac approach description before we can we need to understand the best approach given the platform s current datadog setup and configuration there are a number of options available for role based access control rbac that help to define permissions and restrict access to individual resources based on pre defined or custom roles we can consult w datadog smes directly to gain their recommendations resources acceptance criteria we will meet with datadog smes to decide the path forward refinement guidance check the following before working on this issue team label assigned platform tech team epic assigned if needed estimated points assigned sprint assigned once planned team member s assigned ,0 111932,14172852694.0,IssuesEvent,2020-11-12 17:30:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Write stories for HelpMenu,design-system-team frontend,"## Issue Description Using the documentation found in [the markdown file for `HelpMenu`](https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/tree/master/packages/formation-react/src/components/HelpMenu/HelpMenu.mdx), write Storybook stories for the component. ## Acceptance Criteria - [ ] All the ""stories"" found in `HelpMenu.mdx` are written as Storybook stories - [ ] These stories are found in `packages/formation-react/src/components/HelpMenu/HelpMenu.stories.jsx`",1.0,"Write stories for HelpMenu - ## Issue Description Using the documentation found in [the markdown file for `HelpMenu`](https://github.com/department-of-veterans-affairs/veteran-facing-services-tools/tree/master/packages/formation-react/src/components/HelpMenu/HelpMenu.mdx), write Storybook stories for the component. ## Acceptance Criteria - [ ] All the ""stories"" found in `HelpMenu.mdx` are written as Storybook stories - [ ] These stories are found in `packages/formation-react/src/components/HelpMenu/HelpMenu.stories.jsx`",1,write stories for helpmenu issue description using the documentation found in write storybook stories for the component acceptance criteria all the stories found in helpmenu mdx are written as storybook stories these stories are found in packages formation react src components helpmenu helpmenu stories jsx ,1 166690,26395820550.0,IssuesEvent,2023-01-12 19:18:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,FY23 Tasks Planning - Volume 2,service-design,"## Purpose Discuss and identify the tasks to accomplish FY2023 Initiatives ## Tasks - [x] Schedule session - [x] host workshop ## Acceptance Criteria - [x] Initiatives are broken into stories",1.0,"FY23 Tasks Planning - Volume 2 - ## Purpose Discuss and identify the tasks to accomplish FY2023 Initiatives ## Tasks - [x] Schedule session - [x] host workshop ## Acceptance Criteria - [x] Initiatives are broken into stories",1, tasks planning volume purpose discuss and identify the tasks to accomplish initiatives tasks schedule session host workshop acceptance criteria initiatives are broken into stories,1 102858,12827491452.0,IssuesEvent,2020-07-06 18:35:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Produce Flowchart for CH31 Wizard,design vsa vsa-ebenefits,"## Goal Per the stakeholders input from Steve, develop a flowchart that describes what is intended. ## Considerations [Convo with screens](https://dsva.slack.com/archives/CLY6Q69RV/p1593469644404100) ## Tasks - [x] Develop a flowchart of the CH31 wizard ## Acceptance Criteria - [x] A flowchart has been shared for feedback from stakeholders/ Steve `Next steps` - mockups - prototype as approved",1.0,"Produce Flowchart for CH31 Wizard - ## Goal Per the stakeholders input from Steve, develop a flowchart that describes what is intended. ## Considerations [Convo with screens](https://dsva.slack.com/archives/CLY6Q69RV/p1593469644404100) ## Tasks - [x] Develop a flowchart of the CH31 wizard ## Acceptance Criteria - [x] A flowchart has been shared for feedback from stakeholders/ Steve `Next steps` - mockups - prototype as approved",1,produce flowchart for wizard goal per the stakeholders input from steve develop a flowchart that describes what is intended considerations tasks develop a flowchart of the wizard acceptance criteria a flowchart has been shared for feedback from stakeholders steve next steps mockups prototype as approved,1 100397,12519783554.0,IssuesEvent,2020-06-03 14:55:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[Design] DL - Drupal content page designs,design vsa vsa-benefits-2,"## Issue Description We need to create a design for the modernized VA.gov content page to replace the debtman content pages. --- ## Tasks - [ ] Create mockup for unauthenticated content page - [ ] Create mockup for authenticated content page - [ ] Upload to UXPin - [ ] Update documentation ## Acceptance Criteria - [ ] Documentation linked to this ticket ",1.0,"[Design] DL - Drupal content page designs - ## Issue Description We need to create a design for the modernized VA.gov content page to replace the debtman content pages. --- ## Tasks - [ ] Create mockup for unauthenticated content page - [ ] Create mockup for authenticated content page - [ ] Upload to UXPin - [ ] Update documentation ## Acceptance Criteria - [ ] Documentation linked to this ticket ",1, dl drupal content page designs issue description we need to create a design for the modernized va gov content page to replace the debtman content pages tasks create mockup for unauthenticated content page create mockup for authenticated content page upload to uxpin update documentation acceptance criteria documentation linked to this ticket ,1 130173,18045138353.0,IssuesEvent,2021-09-18 19:15:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Build modal web component ,vsp-design-system-team,"- [ ] Build a modal web component - [ ] Identify existing modal REACT components that need to be migrated - [ ] Announce the new modal web component to all teams",1.0,"Build modal web component - - [ ] Build a modal web component - [ ] Identify existing modal REACT components that need to be migrated - [ ] Announce the new modal web component to all teams",1,build modal web component build a modal web component identify existing modal react components that need to be migrated announce the new modal web component to all teams,1 179627,30275839999.0,IssuesEvent,2023-07-07 19:33:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Va-memorable-date property issues,vsp-design-system-team,"## Issue Description A support request came in for a user who is having issues with the `invalid-day`, `invalid-month`, and `invalid-year` properties in the `va-memorable-date` web component. He has linked a demo where the issue can be seen here: https://codesandbox.io/s/bold-browser-xyct72?file=/src/App.js Original support request: https://dsva.slack.com/archives/CBU0KDSB1/p1688756886472779 --- ## Tasks - [ ] Fix the issue experienced in `va-memorable-date` ## Acceptance Criteria - [ ] The properties within `va-memorable-date` function properly --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Va-memorable-date property issues - ## Issue Description A support request came in for a user who is having issues with the `invalid-day`, `invalid-month`, and `invalid-year` properties in the `va-memorable-date` web component. He has linked a demo where the issue can be seen here: https://codesandbox.io/s/bold-browser-xyct72?file=/src/App.js Original support request: https://dsva.slack.com/archives/CBU0KDSB1/p1688756886472779 --- ## Tasks - [ ] Fix the issue experienced in `va-memorable-date` ## Acceptance Criteria - [ ] The properties within `va-memorable-date` function properly --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,va memorable date property issues issue description a support request came in for a user who is having issues with the invalid day invalid month and invalid year properties in the va memorable date web component he has linked a demo where the issue can be seen here original support request tasks fix the issue experienced in va memorable date acceptance criteria the properties within va memorable date function properly how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 184084,31817076109.0,IssuesEvent,2023-09-13 21:24:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[UX][Design] DS v3 #5: Update buttons,design ux HCE-Checkin,"## Background Buttons also need to be updated as part of the v3 switch. Design System v3 Components have been prioritized in the [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010). ## Tasks - [ ] Update the Design pages of the Unified check-in, Check-in, and Pre-Check-in files - [ ] Identify screens that use buttons - [ ] Update the corresponding symbols in these files with the new Component Library Sketch component (see ticket [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010) for more info on setting up the new Sketch library) - [ ] Check all Design page boards to make sure they're updated in case of detached symbols - [ ] **Sync with FE engineers** to make sure they're all set on toggling the buttons to the new version ## Acceptance Criteria - [ ] Buttons are updated in unified, Check-in, and Pre-Check-in Design page files - [ ] FE is set to toggle to v3 of this component ",1.0,"[UX][Design] DS v3 #5: Update buttons - ## Background Buttons also need to be updated as part of the v3 switch. Design System v3 Components have been prioritized in the [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010). ## Tasks - [ ] Update the Design pages of the Unified check-in, Check-in, and Pre-Check-in files - [ ] Identify screens that use buttons - [ ] Update the corresponding symbols in these files with the new Component Library Sketch component (see ticket [#64010 Design System v3 ticket](https://github.com/department-of-veterans-affairs/va.gov-team/issues/64010) for more info on setting up the new Sketch library) - [ ] Check all Design page boards to make sure they're updated in case of detached symbols - [ ] **Sync with FE engineers** to make sure they're all set on toggling the buttons to the new version ## Acceptance Criteria - [ ] Buttons are updated in unified, Check-in, and Pre-Check-in Design page files - [ ] FE is set to toggle to v3 of this component ",1, ds update buttons background buttons also need to be updated as part of the switch design system components have been prioritized in the tasks update the design pages of the unified check in check in and pre check in files identify screens that use buttons update the corresponding symbols in these files with the new component library sketch component see ticket for more info on setting up the new sketch library check all design page boards to make sure they re updated in case of detached symbols sync with fe engineers to make sure they re all set on toggling the buttons to the new version acceptance criteria buttons are updated in unified check in and pre check in design page files fe is set to toggle to of this component ,1 93025,11732695649.0,IssuesEvent,2020-03-11 04:38:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,Search improvements design,design vsa vsa-facilities,"### User Story As a Veteran, I need the Facility Locator to return meaningful results to my search so I can select a facility which will meet my need. ## Goals Iterate search ux, incorporating recommendations from recent user research sessions ## Tasks [ ] Enhance Facility Locator search functionality and presentation of results, including the search itself, user-map interactions and search results with consideration for: > Needs based on urban/rural location > Impact of facility/service type on expectations > Number of search results > Map interaction > Search refinement Acceptance Criteria [ ] Low fidelity prototype or mock-up [ ] Request for Design Collaboration meeting --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1.0,"Search improvements design - ### User Story As a Veteran, I need the Facility Locator to return meaningful results to my search so I can select a facility which will meet my need. ## Goals Iterate search ux, incorporating recommendations from recent user research sessions ## Tasks [ ] Enhance Facility Locator search functionality and presentation of results, including the search itself, user-map interactions and search results with consideration for: > Needs based on urban/rural location > Impact of facility/service type on expectations > Number of search results > Map interaction > Search refinement Acceptance Criteria [ ] Low fidelity prototype or mock-up [ ] Request for Design Collaboration meeting --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.) ",1,search improvements design user story as a veteran i need the facility locator to return meaningful results to my search so i can select a facility which will meet my need goals iterate search ux incorporating recommendations from recent user research sessions tasks enhance facility locator search functionality and presentation of results including the search itself user map interactions and search results with consideration for needs based on urban rural location impact of facility service type on expectations number of search results map interaction search refinement acceptance criteria low fidelity prototype or mock up request for design collaboration meeting how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 132474,18724633888.0,IssuesEvent,2021-11-03 15:09:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,CST - Frontend Assessment Phase 2,design vsa-claims-appeals Claim Status Tool,"## Issue Description After creating CST in a new template, we should look at the information that's on the page and understand what needs to be updated, removed or added. New proposed design: https://www.sketch.com/s/64bb337a-e31f-4a21-a92f-d89b50cba668 --- ## Tasks - [ ] Assess content in new page layout design - [ ] Determine what should be added/removed ## Acceptance Criteria - [ ] Changes have been made in design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1.0,"CST - Frontend Assessment Phase 2 - ## Issue Description After creating CST in a new template, we should look at the information that's on the page and understand what needs to be updated, removed or added. New proposed design: https://www.sketch.com/s/64bb337a-e31f-4a21-a92f-d89b50cba668 --- ## Tasks - [ ] Assess content in new page layout design - [ ] Determine what should be added/removed ## Acceptance Criteria - [ ] Changes have been made in design --- ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [ ] **Attached to an Epic** (what body of work is this a part of?) - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1,cst frontend assessment phase issue description after creating cst in a new template we should look at the information that s on the page and understand what needs to be updated removed or added new proposed design tasks assess content in new page layout design determine what should be added removed acceptance criteria changes have been made in design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 88472,11099203695.0,IssuesEvent,2019-12-16 16:34:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reopened,Create list of all benefits applications ,design vsa-authenticated-exp,"Create a list of all benefit applications and where they get address data from — note which are VA Profile (Vet360) and which are not. ## User Story: As a designer , I need to create a list of all benefit applications and where they get address data from and note which are VA Profile (Vet360) and which are not. ## Tasks _The steps that must be done by the team to complete the acceptance criteria_ - [x] Identify the forms that have an address component. - 3 hours - [x] confirm with Backend Eng what forms are running on VA Profile and being pre-filled from users profile. - 1 hour ## Acceptance Criteria: _The requirements that must be met in order to mark this user story as completed_ - [x] Have a comprehensive list of the forms on VA.gov and have an understanding on how they are being pre-filled. ## Excel Github File - [x] Create list of VA benefit applications lists in Github [Link to Github lists](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/change-address/apo-fpo-dpo/benefits-applciations-list.md)",1.0,"Create list of all benefits applications - Create a list of all benefit applications and where they get address data from — note which are VA Profile (Vet360) and which are not. ## User Story: As a designer , I need to create a list of all benefit applications and where they get address data from and note which are VA Profile (Vet360) and which are not. ## Tasks _The steps that must be done by the team to complete the acceptance criteria_ - [x] Identify the forms that have an address component. - 3 hours - [x] confirm with Backend Eng what forms are running on VA Profile and being pre-filled from users profile. - 1 hour ## Acceptance Criteria: _The requirements that must be met in order to mark this user story as completed_ - [x] Have a comprehensive list of the forms on VA.gov and have an understanding on how they are being pre-filled. ## Excel Github File - [x] Create list of VA benefit applications lists in Github [Link to Github lists](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/change-address/apo-fpo-dpo/benefits-applciations-list.md)",1,create list of all benefits applications create a list of all benefit applications and where they get address data from — note which are va profile and which are not user story as a designer i need to create a list of all benefit applications and where they get address data from and note which are va profile and which are not tasks the steps that must be done by the team to complete the acceptance criteria identify the forms that have an address component hours confirm with backend eng what forms are running on va profile and being pre filled from users profile hour acceptance criteria the requirements that must be met in order to mark this user story as completed have a comprehensive list of the forms on va gov and have an understanding on how they are being pre filled excel github file create list of va benefit applications lists in github ,1 194136,15397743835.0,IssuesEvent,2021-03-03 22:40:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,opened,[WCAG2.1]: Document affected teams and testing strategies for new success criteria,508/Accessibility VSP-testing-team documentation vsp-product-support,"## Issue Description WCAG2.1 includes 17 new success criteria. We need to meet the Level A and Level AA success criteria. AAA is not required but could be considered if accessibility specialists feel they would not be too cumbersome for teams to implement. ## Tasks - [ ] Review the new success criteria: https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/ - [ ] Document the relevant group(s) who would need to be trained on new criteria - [ ] Document proposed testing strategies for each new criteria ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",1.0,"[WCAG2.1]: Document affected teams and testing strategies for new success criteria - ## Issue Description WCAG2.1 includes 17 new success criteria. We need to meet the Level A and Level AA success criteria. AAA is not required but could be considered if accessibility specialists feel they would not be too cumbersome for teams to implement. ## Tasks - [ ] Review the new success criteria: https://www.w3.org/WAI/standards-guidelines/wcag/new-in-21/ - [ ] Document the relevant group(s) who would need to be trained on new criteria - [ ] Document proposed testing strategies for each new criteria ## How to configure this issue - [ ] **Attached to a Milestone** (when will this be completed?) - [x] **Attached to an Epic** (what body of work is this a part of?) - [x] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `tools-be`, `tools-fe`) - [x] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`) - [x] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)",0, document affected teams and testing strategies for new success criteria issue description includes new success criteria we need to meet the level a and level aa success criteria aaa is not required but could be considered if accessibility specialists feel they would not be too cumbersome for teams to implement tasks review the new success criteria document the relevant group s who would need to be trained on new criteria document proposed testing strategies for each new criteria how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,0 120106,15703945548.0,IssuesEvent,2021-03-26 14:27:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reopened,Full Accessibility & 508 Office Audit [Profile 2.0],508/Accessibility Epic collaboration-cycle design frontend vsa-authenticated-exp vsp-product-support,"## Steps to complete the Full Accessibility & 508 Audit: - [x] Product Manager: create issue and fill in feature name in the title and other bolded information appropriately - [ ] Practice area reviewers create sub-issues attached to this one with feedback for your team on *feature name* - [ ] **Requesting team** completes attached feedback tickets based on definition of done included in each practice area feedback ticket (may differ for each practice area, please refer to attached tickets for further instruction) - [ ] All requesting team attendees complete brief [VSP Collaboration Cycle Feedback](https://adhoc.optimalworkshop.com/questions/20260uu8-0-0/questions/before) survey ## Artifacts - _please provide the following artifacts when you request a full review_ - Access information for the tool or feature in staging : [Staging Credentials](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/identity-personalization/Staging%20Credentials.md) - Complete/check-off the required items here: - [x] [Axe scans in daily development](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#axe-scans-in-daily-development) - [x] [Axe scans in end-to-end tests](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#axe-scans-in-end-to-end-tests) - [x] [Color tests](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#color-tests) - [x] [Content resize check](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#content-resize-check) - [x] [Keyboard navigation check](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#keyboard-navigation-check) - [x] [Screen reader tests](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#screen-reader-tests) ## Additional Notes As part of this review, VSP will send your product to VA's 508 office for approval (as applicable) ",1.0,"Full Accessibility & 508 Office Audit [Profile 2.0] - ## Steps to complete the Full Accessibility & 508 Audit: - [x] Product Manager: create issue and fill in feature name in the title and other bolded information appropriately - [ ] Practice area reviewers create sub-issues attached to this one with feedback for your team on *feature name* - [ ] **Requesting team** completes attached feedback tickets based on definition of done included in each practice area feedback ticket (may differ for each practice area, please refer to attached tickets for further instruction) - [ ] All requesting team attendees complete brief [VSP Collaboration Cycle Feedback](https://adhoc.optimalworkshop.com/questions/20260uu8-0-0/questions/before) survey ## Artifacts - _please provide the following artifacts when you request a full review_ - Access information for the tool or feature in staging : [Staging Credentials](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/products/identity-personalization/Staging%20Credentials.md) - Complete/check-off the required items here: - [x] [Axe scans in daily development](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#axe-scans-in-daily-development) - [x] [Axe scans in end-to-end tests](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#axe-scans-in-end-to-end-tests) - [x] [Color tests](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#color-tests) - [x] [Content resize check](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#content-resize-check) - [x] [Keyboard navigation check](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#keyboard-navigation-check) - [x] [Screen reader tests](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/platform/accessibility/guidance/staging-review-processes.md#screen-reader-tests) ## Additional Notes As part of this review, VSP will send your product to VA's 508 office for approval (as applicable) ",1,full accessibility office audit steps to complete the full accessibility audit product manager create issue and fill in feature name in the title and other bolded information appropriately practice area reviewers create sub issues attached to this one with feedback for your team on feature name requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket may differ for each practice area please refer to attached tickets for further instruction all requesting team attendees complete brief survey artifacts please provide the following artifacts when you request a full review access information for the tool or feature in staging complete check off the required items here additional notes as part of this review vsp will send your product to va s office for approval as applicable ,1 175740,27968636642.0,IssuesEvent,2023-03-24 22:22:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Could platform-support channel feed it as well? Should it?,service-design,"## Purpose (Might be a good funnel due to its widespread use) or could selecting ""Provide Feedback on ---"" within the channel lead the user to the portal itself? Can we figure out a decision tree: ""when should I post in platform-support and when should I use feedback portal""? ## Tasks - [x] Review what the current intake process is for the platform-support channel (review internal/external docs, any user flows, step through actual process) - [x] Mini workshop with team - [x] Determine whether feedback should come in via the Support channel as well - [x] If yes, [what does the decision tree look like](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1679607880960/dcb763f273a49ef82a47a45b6e83cfd3fd935065?sender=u9ea6bd3ca12795949b606150)? ## Acceptance Criteria - [x] Document [decision and plan](https://app.zenhub.com/workspaces/platform-service-design-61bcbaf174a70100154e22e7/issues/gh/department-of-veterans-affairs/va.gov-team/55729) ",1.0,"Could platform-support channel feed it as well? Should it? - ## Purpose (Might be a good funnel due to its widespread use) or could selecting ""Provide Feedback on ---"" within the channel lead the user to the portal itself? Can we figure out a decision tree: ""when should I post in platform-support and when should I use feedback portal""? ## Tasks - [x] Review what the current intake process is for the platform-support channel (review internal/external docs, any user flows, step through actual process) - [x] Mini workshop with team - [x] Determine whether feedback should come in via the Support channel as well - [x] If yes, [what does the decision tree look like](https://app.mural.co/t/adhocvetsgov9623/m/adhocvetsgov9623/1679607880960/dcb763f273a49ef82a47a45b6e83cfd3fd935065?sender=u9ea6bd3ca12795949b606150)? ## Acceptance Criteria - [x] Document [decision and plan](https://app.zenhub.com/workspaces/platform-service-design-61bcbaf174a70100154e22e7/issues/gh/department-of-veterans-affairs/va.gov-team/55729) ",1,could platform support channel feed it as well should it purpose might be a good funnel due to its widespread use or could selecting provide feedback on within the channel lead the user to the portal itself can we figure out a decision tree when should i post in platform support and when should i use feedback portal tasks review what the current intake process is for the platform support channel review internal external docs any user flows step through actual process mini workshop with team determine whether feedback should come in via the support channel as well if yes acceptance criteria document ,1 118815,15367332135.0,IssuesEvent,2021-03-02 03:03:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] MyVA 2.0: Conduct research,design my-va-dashboard vsa-authenticated-exp,"## Background [Research plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/product/Research%20V2/MyVA2-research-plan.md) [Conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products[…]/2.0-redesign/product/Research%20V2/MyVA2-conversation-guide.md) ## Tasks - [ ] Conduct research",1.0,"[Design] MyVA 2.0: Conduct research - ## Background [Research plan](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/identity-personalization/my-va/2.0-redesign/product/Research%20V2/MyVA2-research-plan.md) [Conversation guide](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products[…]/2.0-redesign/product/Research%20V2/MyVA2-conversation-guide.md) ## Tasks - [ ] Conduct research",1, myva conduct research background redesign product research conversation guide md tasks conduct research,1 159244,24962194083.0,IssuesEvent,2022-11-01 16:22:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,[Design] Create Draft Wireframes using the New DS Progress Bar,design ux HCE-Checkin,"## Tasks - Collaborate with DS team on their new design for the Progress Bar component (talk to Josh Kim and Pam Hastings) - What is the DS team's vision - [DS Sketch file](https://www.sketch.com/s/09640425-48be-4019-8277-8a924eff1df7) - New design has connection to the [Sub-task pattern](https://design.va.gov/patterns/help-users-to/complete-a-sub-task) - Create draft wireframes for using the new DS stepped component in Pre-Check-in application - Create draft wireframes for using the new DS stepped component in Check-in application",1.0,"[Design] Create Draft Wireframes using the New DS Progress Bar - ## Tasks - Collaborate with DS team on their new design for the Progress Bar component (talk to Josh Kim and Pam Hastings) - What is the DS team's vision - [DS Sketch file](https://www.sketch.com/s/09640425-48be-4019-8277-8a924eff1df7) - New design has connection to the [Sub-task pattern](https://design.va.gov/patterns/help-users-to/complete-a-sub-task) - Create draft wireframes for using the new DS stepped component in Pre-Check-in application - Create draft wireframes for using the new DS stepped component in Check-in application",1, create draft wireframes using the new ds progress bar tasks collaborate with ds team on their new design for the progress bar component talk to josh kim and pam hastings what is the ds team s vision new design has connection to the create draft wireframes for using the new ds stepped component in pre check in application create draft wireframes for using the new ds stepped component in check in application,1 128821,17618822515.0,IssuesEvent,2021-08-18 13:09:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Notice of Disagreement Opt-in,design vsa vsa-claims-appeals NOD,"## Issue Description Updated opt-in language per Board request --- ## Tasks - [x] Work with Beth to adjust opt-in language ## Acceptance Criteria - [x] _What will be created or happen as a result of this story?_ --- ",1.0,"Notice of Disagreement Opt-in - ## Issue Description Updated opt-in language per Board request --- ## Tasks - [x] Work with Beth to adjust opt-in language ## Acceptance Criteria - [x] _What will be created or happen as a result of this story?_ --- ",1,notice of disagreement opt in issue description updated opt in language per board request tasks work with beth to adjust opt in language acceptance criteria what will be created or happen as a result of this story ,1 116494,14970149213.0,IssuesEvent,2021-01-27 19:11:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,closed,Chapter 31 Orientation - Research and Implement Accessibility standards for video components,508/Accessibility CH31 design frontend vsa vsa-ebenefits,"## Description As an engineer, I want the components I build to be as accessible as possible, so the broadest spectrum of users possible can utilize my applications. Components that leverage video assets should be presented in an accessible way that includes the use of captions, the provision of a transcript, and the use of progressive enhancement. ## Considerations - Use of the `