karths/binary_classification_train_design
029
1Unnamed: 0,id,type,created_at,repo,repo_url,action,title,labels,body,index,text_combine,label,text,binary_label295512,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 3Align with team4 5schedule design intent meeting (Jason)",1.0,"Take Ch 36 to Design Intent - Complete designs 6Align with team7 8schedule design intent meeting (Jason)",1,take ch to design intent complete designs align with team schedule design intent meeting jason ,1924604,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,"## Description10Make sure developers understand how we use Kubernetes in our environment.11- How to onboard a new project12- Application Manifest documentation (How to make a simple application manifest, etc)13- CI documentation (what CI needs to output to manifest)14- ArgoCD documentation (logging in, interacting with applications)15- How to use Kubernetes secrets in your application repo (external-secrets, parameter store)16 17 18## Background/context/resources19_Any additional context for the reader to know, if applicable_ 20 21## Technical notes22_Notes around work that is happening, if applicable_23 24---25## Tasks26- [ ] _Write documentation_27- [ ] Peer review / Edits28 29## Definition of Done30- [ ] _Developer documentation for EKS is written and available to developers_31 32---33### Reminders34- [ ] Please attach your team label and any other appropriate label(s) 35- [ ] Please attach the needs grooming tag if needed36- [ ] Please connect to an epic37",1.0,"Documentation - EKS - ## Description38Make sure developers understand how we use Kubernetes in our environment.39- How to onboard a new project40- Application Manifest documentation (How to make a simple application manifest, etc)41- CI documentation (what CI needs to output to manifest)42- ArgoCD documentation (logging in, interacting with applications)43- How to use Kubernetes secrets in your application repo (external-secrets, parameter store)44 45 46## Background/context/resources47_Any additional context for the reader to know, if applicable_ 48 49## Technical notes50_Notes around work that is happening, if applicable_51 52---53## Tasks54- [ ] _Write documentation_55- [ ] Peer review / Edits56 57## Definition of Done58- [ ] _Developer documentation for EKS is written and available to developers_59 60---61### Reminders62- [ ] Please attach your team label and any other appropriate label(s) 63- [ ] Please attach the needs grooming tag if needed64- [ ] Please connect to an epic65",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 ,066178434,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 description67Work with VAOS dev and product to redesign the structure of our GitHub documentation space.68 69## References70- [VAOS documentation notes](https://docs.google.com/document/d/1tHihdzLKTD333DYKPjaoxE0skaaWRaTPqLASvmJfruE/edit#)71- [Optimal sort workshop results](https://app.optimalworkshop.com/a/dj540s05/optimalsort/results/1a920c40-accf-4693-a836-d22f82e8e4c6#/t/results/overview)72 73## Acceptance criteria74- [x] Team has reviewed synthesis from card sort exercise75- [x] Team has workshopped new structure76- [x] Team has identified final new structure",2.0,"Design VAOS' documentation space - ## Task description77Work with VAOS dev and product to redesign the structure of our GitHub documentation space.78 79## References80- [VAOS documentation notes](https://docs.google.com/document/d/1tHihdzLKTD333DYKPjaoxE0skaaWRaTPqLASvmJfruE/edit#)81- [Optimal sort workshop results](https://app.optimalworkshop.com/a/dj540s05/optimalsort/results/1a920c40-accf-4693-a836-d22f82e8e4c6#/t/results/overview)82 83## Acceptance criteria84- [x] Team has reviewed synthesis from card sort exercise85- [x] Team has workshopped new structure86- [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,187160773,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,"## Background88 89After 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.90 91## Tasks92- [ ] Update sketch files93- [ ] Update/create Git documentation94 95 96## Acceptance Criteria97- [ ] Documentation is complete for the Nametag section 98 99 100## Associated Tickets101- #48306 102 103 104",1.0,"Design | Profile | Nametag | Update Documentation - ## Background105 106After 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.107 108## Tasks109- [ ] Update sketch files110- [ ] Update/create Git documentation111 112 113## Acceptance Criteria114- [ ] Documentation is complete for the Nametag section 115 116 117## Associated Tickets118- #48306 119 120 121",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 ,1122137625,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,"## Description123We 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.124 125One 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.126 127For 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.128 129## Acceptance Criteria130- [ ] Generate list of resources available131- [ ] Evaluate how we could leverage those resources to help in building and maintaining our CSS class library132- [ ] 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 - ## Description133We 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.134 135One 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.136 137For 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.138 139## Acceptance Criteria140- [ ] Generate list of resources available141- [ ] Evaluate how we could leverage those resources to help in building and maintaining our CSS class library142- [ ] 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 ,1143132495,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 fine144use cases145some IA suggestions146kick off (Jason)147this is really to prep for design intent",1.0,"Scaffold out the SAHG Mockup - wire frame is fine148use cases149some IA suggestions150kick off (Jason)151this 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,1152123653,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!153**Should** 1541. 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. 155 156**Consider**1571. 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. 1582. 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.1593. 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.]1604. 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. 161 162**Note:** I am trying a new framework for providing input (Feedback on this is welcome!): 163- **❗️ Must** for if the feedback must be applied 164- **⚠️Should** if the feedback is best practice 165- **✔️ Consider** for suggestions/enhancements 166```diff167- ""Must"" for if the feedback must be applied 168! ""Should"" if the feedback is best practice 169+ ""Consider"" for suggestions/enhancements 170```",1.0,"VSA Accessibility Feedback for ""Submit 686"" - Definitely a complex undertaking!171**Should** 1721. 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. 173 174**Consider**1751. 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. 1762. 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.1773. 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.]1784. 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. 179 180**Note:** I am trying a new framework for providing input (Feedback on this is welcome!): 181- **❗️ Must** for if the feedback must be applied 182- **⚠️Should** if the feedback is best practice 183- **✔️ Consider** for suggestions/enhancements 184```diff185- ""Must"" for if the feedback must be applied 186! ""Should"" if the feedback is best practice 187+ ""Consider"" for suggestions/enhancements 188```",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 ,1189108552,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:190- document at what viewport width we plan to collapse columns 2–12, so that we have all the info and are in agreement.191- 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).192 193**acceptance criteria**194 195- [ ] 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:196- document at what viewport width we plan to collapse columns 2–12, so that we have all the info and are in agreement.197- 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).198 199**acceptance criteria**200 201- [ ] 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,120295077,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:**203- 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.204 205- 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 picture206 207**Solution:** 2081. Update the ReadMe’s for each practice area using this proposed template as applicable: https://docs.google.com/document/d/10kREoy1dMFS2zUg2z5CJ0OIAIQBJa2JoNootVkjx5yw/edit?usp=sharing209 2102. Pin updated ReadMe's to the vfs-platform-support slack channel.211 2123. 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.213 214**Objectives:**215O1: Any volume of simultaneous customers have a delightful, self-service, end-to-end experience using the Platform to build on VA.gov.216 217**KPIs:**218- Reduction in average volume of documentation support requests per week219- Increase in customer NPS220- Reduction in volume of “non-human-needed” support requests month over month221 222**Next Steps:**223- Does the template work for each practice area? 224- 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.225 226**Definition of Done:**227[Practice area](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform) READMEs have been updated in accordance with recommendations: 228- [x] accessibility229- [ ] analytics230- [ ] call-center231- [x] content232- [x] design233- [ ] engineering234- [x] information architecture235- [ ] operations236- [ ] product management237- [ ] quality assurance238- [ ] research239- [ ] security240- [ ] tools241- [ ] triage242- [ ] working-with-vsp243 244Additional /platform READMEs have been updated _or_ next steps identified and captured as backlog ZH items245- [ ] about-vsp246- [ ] cms247- [ ] service-design",1.0,"Documentation - Implement Recommendations from ROE Research - **Problem:**248- 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.249 250- 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 picture251 252**Solution:** 2531. Update the ReadMe’s for each practice area using this proposed template as applicable: https://docs.google.com/document/d/10kREoy1dMFS2zUg2z5CJ0OIAIQBJa2JoNootVkjx5yw/edit?usp=sharing254 2552. Pin updated ReadMe's to the vfs-platform-support slack channel.256 2573. 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.258 259**Objectives:**260O1: Any volume of simultaneous customers have a delightful, self-service, end-to-end experience using the Platform to build on VA.gov.261 262**KPIs:**263- Reduction in average volume of documentation support requests per week264- Increase in customer NPS265- Reduction in volume of “non-human-needed” support requests month over month266 267**Next Steps:**268- Does the template work for each practice area? 269- 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.270 271**Definition of Done:**272[Practice area](https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/platform) READMEs have been updated in accordance with recommendations: 273- [x] accessibility274- [ ] analytics275- [ ] call-center276- [x] content277- [x] design278- [ ] engineering279- [x] information architecture280- [ ] operations281- [ ] product management282- [ ] quality assurance283- [ ] research284- [ ] security285- [ ] tools286- [ ] triage287- [ ] working-with-vsp288 289Additional /platform READMEs have been updated _or_ next steps identified and captured as backlog ZH items290- [ ] about-vsp291- [ ] cms292- [ ] 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,1293149803,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 Description294As a secure messaging user, I need a folder page so that I can see all the folders I have created in my secure messages295 296---297## Tasks298- [x] Design folder page for desktop299- [x] Design folder page for mobile300- [x] Drop link to mockups into a comment on this ticket301- [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review302 303## Acceptance Criteria304- [ ] Folder and desktop mockups will be complete and ready for review by PO.305 306---307## How to configure this issue308- [ ] **Attached to a Milestone** (when will this be completed?)309- [ ] **Attached to an Epic** (what body of work is this a part of?)310- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`)311- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)312- [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)313",1.0,"[Design] MyHealth - Design Folders desktop page - ## Issue Description314As a secure messaging user, I need a folder page so that I can see all the folders I have created in my secure messages315 316---317## Tasks318- [x] Design folder page for desktop319- [x] Design folder page for mobile320- [x] Drop link to mockups into a comment on this ticket321- [x] Drop a note into #mhv_on_vagov in Slack when you are ready for Tracey to review322 323## Acceptance Criteria324- [ ] Folder and desktop mockups will be complete and ready for review by PO.325 326---327## How to configure this issue328- [ ] **Attached to a Milestone** (when will this be completed?)329- [ ] **Attached to an Epic** (what body of work is this a part of?)330- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`)331- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)332- [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)333",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 ,1334152155,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,"## Description335 336Build 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 .337 338Consider building two separate components: one for download & a second for video links339 340<details open><summary>Markup Examples</summary>341 342<!-- leave a blank line above -->343 344<br />345Note: This content was copy/pasted from the comment linked above, it may not exactly match if edited after July 28, 2020346 347-----348 349Collaborating with @1copenut, we reviewed the icon implementations to ensure accessibility. 350- Added `aria-hidden=""true""` to `<i>` to suppress the injected text content (that renders the icon) from screen readers351- 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.).)""_352 353**Download PDF Link Example**354```HTML355<a 356 href=""https://www.va.gov/playbook/downloads/Voices_Of_Veterans.pdf"" 357 download=""Voices_Of_Veterans.pdf"" 358 type=""application/pdf"">359 <i aria-hidden=""true"" class=""fas fa-download vads-u-padding-right--1"" role=""img""></i>360 Download the Voices of Veterans <dfn><abbr title=""Portable Document Format"">PDF</abbr> (4.9<abbr title=""Megabytes"">MB</abbr>)</dfn>361</a>362```363 364**View Video Example**365```HTML366<a 367 class=""video-link"" 368 href=""https://www.youtube.com/watch?time_continue=3&v=xE0LzeRgdAk"" 369 target=""_blank"" 370 rel=""noopener "">371 <i aria-hidden=""true"" class=""fas fa-play-circle vads-u-padding-right--1"" role=""img""></i>372 View video about VA disability compensation <dfn>on Youtube</dfn>373</a> 374```375 376**Download Graphic Link Example**377```HTML378<a 379 class=""file-download-with-icon"" 380 href=""/img/2019-07/VA-020-Web-Badges-205x175-al-1.02.jpg"" 381 download=""/img/2019-07/VA-020-Web-Badges-205x175-al-1.02.jpg"">382 <i aria-hidden=""true"" class=""fas fa-download vads-u-padding-right--1"" role=""img""></i>383 Download VA benefits to people who've served <dfn><abbr title=""graphic"">JPG</abbr> (0.11<abbr title=""Megabytes"">MB</abbr>)</dfn> 384</a>385```386 387**Download Word Document Example**388```HTML389<a 390 class=""file-download-with-icon"" 391 href=""/files/2019-07/190111-ChooseVA-Marketing-Flyer-2019.docx"" 392 download=""/files/2019-07/190111-ChooseVA-Marketing-Flyer-2019.docx"">393 <i aria-hidden=""true"" class=""fas fa-download vads-u-padding-right--1"" role=""img""></i>394 Download Learn how to apply for VA benefits <dfn><abbr title=""Word document"">DOCX</abbr> (0.49<abbr title=""Megabytes"">MB</abbr>)</dfn>395</a>396```397 398Related: https://github.com/department-of-veterans-affairs/va.gov-team/issues/12184399 400### Guidance401 402* [Proposal for a more accessible Download Link](https://accessabilly.com/proposal-for-a-more-accessible-download-link/)403 404* [CSS Tricks - Building a Good Download ""button""](https://css-tricks.com/building-good-download-button/)405 406* [I thought title text improved accessibility. I was wrong.](https://silktide.com/blog/i-thought-title-text-improved-accessibility-i-was-wrong/)407</details>408 409## Acceptance Criteria410 411- [ ] Download link follows example patterns412- [ ] Video link follows example patterns413",1.0,"[Links] [508] Create a download & video link component - ## Description414 415Build 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 .416 417Consider building two separate components: one for download & a second for video links418 419<details open><summary>Markup Examples</summary>420 421<!-- leave a blank line above -->422 423<br />424Note: This content was copy/pasted from the comment linked above, it may not exactly match if edited after July 28, 2020425 426-----427 428Collaborating with @1copenut, we reviewed the icon implementations to ensure accessibility. 429- Added `aria-hidden=""true""` to `<i>` to suppress the injected text content (that renders the icon) from screen readers430- 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.).)""_431 432**Download PDF Link Example**433```HTML434<a 435 href=""https://www.va.gov/playbook/downloads/Voices_Of_Veterans.pdf"" 436 download=""Voices_Of_Veterans.pdf"" 437 type=""application/pdf"">438 <i aria-hidden=""true"" class=""fas fa-download vads-u-padding-right--1"" role=""img""></i>439 Download the Voices of Veterans <dfn><abbr title=""Portable Document Format"">PDF</abbr> (4.9<abbr title=""Megabytes"">MB</abbr>)</dfn>440</a>441```442 443**View Video Example**444```HTML445<a 446 class=""video-link"" 447 href=""https://www.youtube.com/watch?time_continue=3&v=xE0LzeRgdAk"" 448 target=""_blank"" 449 rel=""noopener "">450 <i aria-hidden=""true"" class=""fas fa-play-circle vads-u-padding-right--1"" role=""img""></i>451 View video about VA disability compensation <dfn>on Youtube</dfn>452</a> 453```454 455**Download Graphic Link Example**456```HTML457<a 458 class=""file-download-with-icon"" 459 href=""/img/2019-07/VA-020-Web-Badges-205x175-al-1.02.jpg"" 460 download=""/img/2019-07/VA-020-Web-Badges-205x175-al-1.02.jpg"">461 <i aria-hidden=""true"" class=""fas fa-download vads-u-padding-right--1"" role=""img""></i>462 Download VA benefits to people who've served <dfn><abbr title=""graphic"">JPG</abbr> (0.11<abbr title=""Megabytes"">MB</abbr>)</dfn> 463</a>464```465 466**Download Word Document Example**467```HTML468<a 469 class=""file-download-with-icon"" 470 href=""/files/2019-07/190111-ChooseVA-Marketing-Flyer-2019.docx"" 471 download=""/files/2019-07/190111-ChooseVA-Marketing-Flyer-2019.docx"">472 <i aria-hidden=""true"" class=""fas fa-download vads-u-padding-right--1"" role=""img""></i>473 Download Learn how to apply for VA benefits <dfn><abbr title=""Word document"">DOCX</abbr> (0.49<abbr title=""Megabytes"">MB</abbr>)</dfn>474</a>475```476 477Related: https://github.com/department-of-veterans-affairs/va.gov-team/issues/12184478 479### Guidance480 481* [Proposal for a more accessible Download Link](https://accessabilly.com/proposal-for-a-more-accessible-download-link/)482 483* [CSS Tricks - Building a Good Download ""button""](https://css-tricks.com/building-good-download-button/)484 485* [I thought title text improved accessibility. I was wrong.](https://silktide.com/blog/i-thought-title-text-improved-accessibility-i-was-wrong/)486</details>487 488## Acceptance Criteria489 490- [ ] Download link follows example patterns491- [ ] Video link follows example patterns492",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 ,1493118503,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 Story494 495As 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.496 497## Expected Behavior498 499This 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.500 501## Acceptance Criteria502 503- [ ] Story is groomed and clearly defined504- [ ] Story is estimated, & broken into sprint-sized pieces of work505- [ ] Collab cycle-related tasks are created506- [ ] All work to implement, including collab cycle tasks are completed & tested507- [ ] Update is peer-reviewed and reviewed on Staging by PO, PM508- [ ] Feature flags are removed509- [ ] Change is live on Production510 511",1.0,"Yellow Ribbon: Schools near me - ## User Story512 513As 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.514 515## Expected Behavior516 517This 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.518 519## Acceptance Criteria520 521- [ ] Story is groomed and clearly defined522- [ ] Story is estimated, & broken into sprint-sized pieces of work523- [ ] Collab cycle-related tasks are created524- [ ] All work to implement, including collab cycle tasks are completed & tested525- [ ] Update is peer-reviewed and reviewed on Staging by PO, PM526- [ ] Feature flags are removed527- [ ] Change is live on Production528 529",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 ,1530144262,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,"## Background531As 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).532 533Feedback from design intent documented by practice area below:534- #40721 535- #40757 536- #40699 537 538## Tasks539- [x] Create prototype540- [ ] Review with PMs + PO541",1.0,"[Research] My VA - Payment info: Create prototype for testing - ## Background542As 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).543 544Feedback from design intent documented by practice area below:545- #40721 546- #40757 547- #40699 548 549## Tasks550- [x] Create prototype551- [ ] Review with PMs + PO552",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 ,1553125736,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. 554",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. 555",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 ,1556161718,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 Description557* Test the appointments list proof of concept with Veterans who use screen readers558 559## Resources560 561## Acceptance Criteria562- [ ] Devs have completed proof of concept. Includes dummy data and working detail pages563- [ ] Proof of concept can be accessed via a test user on staging564- [ ] Research plan and conversation guide are complete565- [ ] Test is complete566",1.0,"Test appointments list with screenreader users - ## Task Description567* Test the appointments list proof of concept with Veterans who use screen readers568 569## Resources570 571## Acceptance Criteria572- [ ] Devs have completed proof of concept. Includes dummy data and working detail pages573- [ ] Proof of concept can be accessed via a test user on staging574- [ ] Research plan and conversation guide are complete575- [ ] Test is complete576",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 ,1577174696,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 578 579Migrate all unified experience wireframes to 375 artboard in sketch. I.e., to reduce risk of issues when viewing wireframes on small screens. 580 581This 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. 582 583## Tasks584 585- [x] Convert wireframes to 375 586 587## AC588 589- [x] New sketch page is available at 375 width 590 591## Deliverable592The 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 593 594Migrate all unified experience wireframes to 375 artboard in sketch. I.e., to reduce risk of issues when viewing wireframes on small screens. 595 596This 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. 597 598## Tasks599 600- [x] Convert wireframes to 375 601 602## AC603 604- [x] New sketch page is available at 375 width 605 606## Deliverable607The 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 ,1608155309,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 ,1609138375,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,"# Description610A 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. 611- 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. 612 613# Tasks614- [ ] Create new content and designs in Sketch615- [ ] Review with content616 617# Acceptance Criteria618- [ ] Review final designs with product and UX619- [ ] Create FE ticket",1.0,"[Design] Editing Edge Cases: Time expired (after midnight)with valid link - # Description620A 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. 621- 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. 622 623# Tasks624- [ ] Create new content and designs in Sketch625- [ ] Review with content626 627# Acceptance Criteria628- [ ] Review final designs with product and UX629- [ ] 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,1630139152,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,"## Background631The ""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.632 633### Considerations634The 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.635 636- [Link to the UXPin prototype](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030)637 638### Tasks639- [x] Implement changes to UXPin screen640- [x] Connect new screen/content to prototype functionality641 642### Acceptance criteria643- [x] New prototype screen with text and layout revisions in place644- [x] New screen connected to prototype functionality645",1.0,"Implement text changes to ""Check the status of your VA home loan COE"" landing page in COE prototype - ## Background646The ""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.647 648### Considerations649The 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.650 651- [Link to the UXPin prototype](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030)652 653### Tasks654- [x] Implement changes to UXPin screen655- [x] Connect new screen/content to prototype functionality656 657### Acceptance criteria658- [x] New prototype screen with text and layout revisions in place659- [x] New screen connected to prototype functionality660",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 ,1661119049,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 Story662- As a Veteran, I want to be able to notify my VA provider of changes to my medication, allergies, and immunization history. 663 664## Related Documentation665- [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md)666- [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md)667- [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)668- [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)669- [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)670 671## Description672Continued refinement of wireframe set on immunizations, allergies, and medications within a questionnaire will be delivered, so it can be utilized:673- as a discussion guide with internal stakeholders, accessibility, and content674- within a usability test - further work will probably be needed to make the wireframes interactive for the actual test.675- within collab cycle meetings (design intent)676 677_ This is a continuation of ticket #20095.678 679## Tasks680- [ ] Create a draft set of [wireframes](link to prototype)681 682## Acceptance Criteria683- [ ] UI review meeting with product and team for feature capabilities",1.0,"[UI] Refine Immunizations, Allergies, and Medications Wireframes - ## User Story684- As a Veteran, I want to be able to notify my VA provider of changes to my medication, allergies, and immunization history. 685 686## Related Documentation687- [Questionnaires Product Outline ](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/product-outline.md)688- [HealthRecord Initiative](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/questionnaire/product/initiatives/health-record.md)689- [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)690- [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)691- [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)692 693## Description694Continued refinement of wireframe set on immunizations, allergies, and medications within a questionnaire will be delivered, so it can be utilized:695- as a discussion guide with internal stakeholders, accessibility, and content696- within a usability test - further work will probably be needed to make the wireframes interactive for the actual test.697- within collab cycle meetings (design intent)698 699_ This is a continuation of ticket #20095.700 701## Tasks702- [ ] Create a draft set of [wireframes](link to prototype)703 704## Acceptance Criteria705- [ ] 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,1706120114,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,"## Background707 708Original discussion in #21177.709 710We need an error message for the claims section if we can't load it. 711 712- If either endpoint fails, then we won't show anything. We will need a message here to say why.713- 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.714 715## Tasks716 717- [ ] Mock up design for claims error718- [ ] Review with team719- [ ] Work with copy720- [ ] Handoff to FE",1.0,"[Design] My VA: Claims error message - ## Background721 722Original discussion in #21177.723 724We need an error message for the claims section if we can't load it. 725 726- If either endpoint fails, then we won't show anything. We will need a message here to say why.727- 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.728 729## Tasks730 731- [ ] Mock up design for claims error732- [ ] Review with team733- [ ] Work with copy734- [ ] 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,1735159066,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,"## Background736Per 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._)737 738Feedback on this topic can be found in these tickets:739* #48655 -- Should section 740 741## Tasks742- [x] Update designs/sketch files to show new design system notification component (instead of ""warning alert component"") for in-line notifications743- [x] Update FE documentation to show and explain use of new design system notification component (instead of ""warning alert component"")for in-line notifications744- [x] PM's to make sure corresponding FE tickets not already in flight/complete are updated as needed to reflect updated notification component745 746 747## Acceptance Criteria748- [x] Sketch files and documentation are updated to indicate use of new notification component (instead of ""warning alert component"") for in-line notifications749 750## Validation751- **_Who can validate this ticket? (FE, BE, Design, PM)?_** any team member752- **_How can this work be validated?_** check documentation see that it's updated753 754",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 - ## Background755Per 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._)756 757Feedback on this topic can be found in these tickets:758* #48655 -- Should section 759 760## Tasks761- [x] Update designs/sketch files to show new design system notification component (instead of ""warning alert component"") for in-line notifications762- [x] Update FE documentation to show and explain use of new design system notification component (instead of ""warning alert component"")for in-line notifications763- [x] PM's to make sure corresponding FE tickets not already in flight/complete are updated as needed to reflect updated notification component764 765 766## Acceptance Criteria767- [x] Sketch files and documentation are updated to indicate use of new notification component (instead of ""warning alert component"") for in-line notifications768 769## Validation770- **_Who can validate this ticket? (FE, BE, Design, PM)?_** any team member771- **_How can this work be validated?_** check documentation see that it's updated772 773",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 ,1774181675,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 Statement775**_As a_** Veteran applying for a home loan776**_I want to_** see the documents that I shared when applying for my CoE777**_So that_** I can quickly reference them when corresponding with a loan assistant.778 779---780## Background Context781LGY 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. 782 783## Acceptance Criteria784- [ ] When a Veteran uploads a document, it appears in the appropriate section of the page.785- [ ] When a Veteran clicks on an uploaded document, they can view the contents of the document. 786 787## Designs and Build Notes788- [Link to previous UX Pin designs](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030/simulate/sitemap)789 790## Tasks791- [ ] Refine internally (Gary and Eugene to review in staging together)792- [ ] Discuss use cases with LGY 793 794## Definition of Ready 795 796- [ ] Clear value description797- [ ] Testable acceptance criteria798- [ ] Accessibility added to acceptance criteria799- [ ] Approved designs attached800- [ ] Sample data provided where appropriate801- [ ] Estimated to fit within the sprint802- [ ] Dependencies and blockers linked803 804## Definition of Done805 806- [ ] Meets acceptance criteria807- [ ] Passed E2E testing (90% coverage)808- [ ] Passed unit testing (90% coverage)809- [ ] Passed integration testing (if applicable)810- [ ] Code reviewed (internal)811- [ ] Submitted to staging812- [ ] Reviewed and approved by product and/or design813 814---815## How to configure this issue816- [ ] **Attached to a Milestone** (when will this be completed?)817- [ ] **Attached to an Epic** (what body of work is this a part of?)818- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`)819- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)820- [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)821",1.0,"Copy of Certificate of Eligibility | Display uploaded documents - ## Value Statement822**_As a_** Veteran applying for a home loan823**_I want to_** see the documents that I shared when applying for my CoE824**_So that_** I can quickly reference them when corresponding with a loan assistant.825 826---827## Background Context828LGY 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. 829 830## Acceptance Criteria831- [ ] When a Veteran uploads a document, it appears in the appropriate section of the page.832- [ ] When a Veteran clicks on an uploaded document, they can view the contents of the document. 833 834## Designs and Build Notes835- [Link to previous UX Pin designs](https://preview.uxpin.com/65c0623a799c268173fe1a3cb4375f9ce00ad820#/pages/140810030/simulate/sitemap)836 837## Tasks838- [ ] Refine internally (Gary and Eugene to review in staging together)839- [ ] Discuss use cases with LGY 840 841## Definition of Ready 842 843- [ ] Clear value description844- [ ] Testable acceptance criteria845- [ ] Accessibility added to acceptance criteria846- [ ] Approved designs attached847- [ ] Sample data provided where appropriate848- [ ] Estimated to fit within the sprint849- [ ] Dependencies and blockers linked850 851## Definition of Done852 853- [ ] Meets acceptance criteria854- [ ] Passed E2E testing (90% coverage)855- [ ] Passed unit testing (90% coverage)856- [ ] Passed integration testing (if applicable)857- [ ] Code reviewed (internal)858- [ ] Submitted to staging859- [ ] Reviewed and approved by product and/or design860 861---862## How to configure this issue863- [ ] **Attached to a Milestone** (when will this be completed?)864- [ ] **Attached to an Epic** (what body of work is this a part of?)865- [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `service-design`, `Console-Services`, `tools-fe`)866- [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)867- [ ] **Labeled with Type** (`bug`, `request`, `discovery`, `documentation`, etc.)868",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 ,1869110534,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)870 871_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. 872 873_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._874 875### Additional details/notes/links876 877Printer-friendly confirmation pages have been implemented in various ways. DST should review and create a standard for this feature. 878 879### Acceptance criteria880 881Create and document standard printer-friendly confirmation page component. 882 883### Point(s) of contact884 885- [ ] @cvalarida 886- [ ] @caw310 887 888### What type of issue is this? 889- [ ] Bug890- [X] Request new feature891- [X] Request update to existing feature892- [ ] Documentation change893- [ ] Other (please describe)894 895### How to configure this issue896- [ ] 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)897- [ ] 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 applicable898",1.0,"Create standardized approach for printer-friendly confirmation page - ### User story(ies)899 900_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. 901 902_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._903 904### Additional details/notes/links905 906Printer-friendly confirmation pages have been implemented in various ways. DST should review and create a standard for this feature. 907 908### Acceptance criteria909 910Create and document standard printer-friendly confirmation page component. 911 912### Point(s) of contact913 914- [ ] @cvalarida 915- [ ] @caw310 916 917### What type of issue is this? 918- [ ] Bug919- [X] Request new feature920- [X] Request update to existing feature921- [ ] Documentation change922- [ ] Other (please describe)923 924### How to configure this issue925- [ ] 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)926- [ ] 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 applicable927",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 ,1928137624,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,"## Description929We 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.930 931One 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.932 933For 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.934 935## Acceptance Criteria936- [ ] Generate list of resources available937- [ ] Evaluate how we could leverage those resources to help in building and maintaining our component library938- [ ] 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? - ## Description939We 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.940 941One 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.942 943For 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.944 945## Acceptance Criteria946- [ ] Generate list of resources available947- [ ] Evaluate how we could leverage those resources to help in building and maintaining our component library948- [ ] 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 ,1949182676,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 Description950There 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).951 952Research 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.)953 954## Tasks955- [ ] Redesign foreign address question in the ""Veteran's Information"" section of the 686c form956- [ ] Obtain CAIA approval of change957- [ ] Assign to PM who will draft engineering ticket958 959## Acceptance Criteria960- [ ] Wireframe of question redesign961 962## Current Design963964",1.0,"Design | 686c Foreign Address Indicator - ## Issue Description965There 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).966 967Research 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.)968 969## Tasks970- [ ] Redesign foreign address question in the ""Veteran's Information"" section of the 686c form971- [ ] Obtain CAIA approval of change972- [ ] Assign to PM who will draft engineering ticket973 974## Acceptance Criteria975- [ ] Wireframe of question redesign976 977## Current Design978979",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 ,1980103661,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:981As 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. 982 983## Goals / Outcomes984- Ensure Veterans that are registered at multiple sites and Express Care enabled understand where and why they are request Express Care through that site985 986 987---988## Hypothesis or Bet989We 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. 990 991## Definition of done992### 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)993### We handle the use case where a Veteran is registered at multiple sites and those multiple sites have Express Care enabled994 995## Issues to create within this Epic996- Design mockups for handling flows for these two scenarios997 - need to account for this on the homepage where we display the date/time window - both active and inactive states998- User story - If veteran is registered at one or more VAMC facilities, and only one facility has EC enabled and availability today --- do what?999- 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?1000",1.0,"VAOSR Express Care v1.1 - Handle multiple site registrations - # Stakeholder input:1001As 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. 1002 1003## Goals / Outcomes1004- Ensure Veterans that are registered at multiple sites and Express Care enabled understand where and why they are request Express Care through that site1005 1006 1007---1008## Hypothesis or Bet1009We 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. 1010 1011## Definition of done1012### 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)1013### We handle the use case where a Veteran is registered at multiple sites and those multiple sites have Express Care enabled1014 1015## Issues to create within this Epic1016- Design mockups for handling flows for these two scenarios1017 - need to account for this on the homepage where we display the date/time window - both active and inactive states1018- User story - If veteran is registered at one or more VAMC facilities, and only one facility has EC enabled and availability today --- do what?1019- 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?1020",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 ,11021170581,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 statement1022Veterans need to make migrate their DS Logon accounts to Login.gov through grandfathering, which allows them to defer identity proofing.1023 1024## Initiative1025 1026_Let's discuss this when we meet on Friday._1027 1028",1.0,"Share grandfathering flow with content teams for feedback - ### Problem statement1029Veterans need to make migrate their DS Logon accounts to Login.gov through grandfathering, which allows them to defer identity proofing.1030 1031## Initiative1032 1033_Let's discuss this when we meet on Friday._1034 1035",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 ,11036141167,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 Description1037Determine what form these guidelines should ultimately take:1038audience, scope, what we hope they take away1039 1040---1041## Tasks1042- [ ] Workshop to determine optimal form of guidelines1043 1044## Acceptance Criteria1045- [ ] Alignment on audience and format",1.0,"Determine what form these guidelines should ultimately take: audience, scope, what we hope they take away - ## Issue Description1046Determine what form these guidelines should ultimately take:1047audience, scope, what we hope they take away1048 1049---1050## Tasks1051- [ ] Workshop to determine optimal form of guidelines1052 1053## Acceptance Criteria1054- [ ] 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,11055131515,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,"## Background1056We have an existing modal solution, but don’t think that offers the most intuitive or accessible UX. 1057Let'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.1058 1059[Note from Kevin Hoffman on our slack thread about next steps](https://dsva.slack.com/archives/C909ZG2BB/p1625233376036200?thread_ts=1625082968.005300&cid=C909ZG2BB): 1060 1061> 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.1062 1063## Tasks1064 1065- [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 Veterans1066- [x] Learn about other profile info edit-in-place use cases (check with Kristen and Kevin RE their needs)1067",1.0,"[Design] Profile: Discovery around functionality that allows users to edit contact information without abandoning their task (Part 1) - ## Background1068We have an existing modal solution, but don’t think that offers the most intuitive or accessible UX. 1069Let'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.1070 1071[Note from Kevin Hoffman on our slack thread about next steps](https://dsva.slack.com/archives/C909ZG2BB/p1625233376036200?thread_ts=1625082968.005300&cid=C909ZG2BB): 1072 1073> 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.1074 1075## Tasks1076 1077- [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 Veterans1078- [x] Learn about other profile info edit-in-place use cases (check with Kristen and Kevin RE their needs)1079",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 ,1108091109,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: 1081As 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. 1082 1083## Tasks: 1084- Create a high fidelity mockup of the order flow introduction page 1085- Upload mockup to Invision and indicate initial focus point as a comment 1086 1087## Acceptance criteria: 1088- [x] Mockup aligns with VA.gov’s design system 1089- [x] There is an alert notifying the Veteran that they are logged in1090- [x] The subway map contains all of the steps the Veteran can expect during the order flow1091- [x] (Optional) Any additional helpful content for the Veteran is included 1092- [x] The screen’s initial focus point is incorporated1093- [x] Sketch artboards are uploaded to Invision and linked in this ticket as a comment1094 1095## Next Steps 1096- content review1097- design review1098 1099## Dependencies: 1100No currently known dependencies 1101",1.0,"MDT- Introduction page- Form introduction page - default state, v1 - ## User story: 1102As 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. 1103 1104## Tasks: 1105- Create a high fidelity mockup of the order flow introduction page 1106- Upload mockup to Invision and indicate initial focus point as a comment 1107 1108## Acceptance criteria: 1109- [x] Mockup aligns with VA.gov’s design system 1110- [x] There is an alert notifying the Veteran that they are logged in1111- [x] The subway map contains all of the steps the Veteran can expect during the order flow1112- [x] (Optional) Any additional helpful content for the Veteran is included 1113- [x] The screen’s initial focus point is incorporated1114- [x] Sketch artboards are uploaded to Invision and linked in this ticket as a comment1115 1116## Next Steps 1117- content review1118- design review1119 1120## Dependencies: 1121No currently known dependencies 1122",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 ,11123175183,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,"1124### Description 1125At 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/).1126 1127### Definition of Done1128- [ ] button does not overflow1129- [ ] follows proper style guide1130 1131### Original Support Request:1132https://dsva.slack.com/archives/CBU0KDSB1/p1678733140735639",1.0,"Fix mobile view ""Feedback"" button layout location. - 1133### Description 1134At 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/).1135 1136### Definition of Done1137- [ ] button does not overflow1138- [ ] follows proper style guide1139 1140### Original Support Request:1141https://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 ,1114290837,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 Statement1143* 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. 1144 1145## Objectives or Key Results this is meant to further1146- Improve the Veteran Search Experience (Veterans have the information they need to be prepared for an urgent care visit. )1147 1148## Goals of research1149Understand Veterans expectations for search results, including the following:1150- how many results they expect to be returned for a healthcare related search1151- how that number of search results is impacted by geographic setting (urban/rural)1152- what geographic area they would expect the map to show by default1153- how they would expect to interact with the map to change their search results1154- how facility type impacts expectations1155- if device (mobile vs desktop) impacts user expectations1156 1157## Acceptance Criteria1158- 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. 1159 1160 1161 1162 1163 1164## Acceptance Criteria1165[ ] Approved research plan1166[ ] Approved conversation guide1167 1168Conduct research [#3897]1169Synthesis follows in [#4004]",1.0,"Create plan to research user search expectations - ## User Story or Problem Statement1170* 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. 1171 1172## Objectives or Key Results this is meant to further1173- Improve the Veteran Search Experience (Veterans have the information they need to be prepared for an urgent care visit. )1174 1175## Goals of research1176Understand Veterans expectations for search results, including the following:1177- how many results they expect to be returned for a healthcare related search1178- how that number of search results is impacted by geographic setting (urban/rural)1179- what geographic area they would expect the map to show by default1180- how they would expect to interact with the map to change their search results1181- how facility type impacts expectations1182- if device (mobile vs desktop) impacts user expectations1183 1184## Acceptance Criteria1185- 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. 1186 1187 1188 1189 1190 1191## Acceptance Criteria1192[ ] Approved research plan1193[ ] Approved conversation guide1194 1195Conduct research [#3897]1196Synthesis 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 ,11197323997,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,"### Description1198 1199I 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/340771200