id,created_at,repo,repo_url,text,label 13675924808.0,2020-09-29 13:18:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr submission discovery currently the paper form is scanned into pdf goes into a queue and is attached to case in caseflow pega tool once the form is online the data needs to integrate with a backend system discovery needs to be completed on what be system the form data will flow to how to integrate with be system chosem ,1 27016722273.0,2023-02-10 20:08:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design intent note this template is being deprecated if your kickoff meeting took place after may you should be following the guidance specified in the collaboration cycle rquest per the instead if you are unsure if this applies to you please reach out to the governance team on the vfs platform support slack channel steps to complete design intent collaboration before meeting vfs product manager or designer create this issue and schedule meeting via calendly you are responsible for adding the vfs attendees notify the collaboration cycle team of this ticket with scheduled date time in vfs platform support add artifacts listed below to the ticket at least days before the scheduled meeting platform add the platform reviewers to scheduled meeting add zoom information to scheduled meeting after meeting platform create feedback tickets and link to the design intent epic if no feedback please comment stating that update vfs respond to platform feedback tickets close this ticket when review is complete and feedback has been addressed artifacts provide links or documents for the following scheduling open the select a date and time and click “confirm” add your name and email click add guests and enter the vfs meeting attendees email addresses click schedule event additional information for the design intent you ll receive feedback from design accessibility and ia only you won t receive feedback from content or qa as it s too early in the development process please refer to or the on platform website for more information about the collaboration cycle fyi shiragoodman chaseakirby ,1 28307656635.0,2023-04-10 12:40:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, resolution option content update issue description update text and design to repeat the amount of debt for the payment plan and compromise offers here are the before and after with the after being the proposed solution resolution options waiver monthly payments compromise beneifit before benefit after resolution options waiver compromise copay before copay after tasks update resolution option page content update resolution comment page content update resolution waiver page content acceptance criteria resolution pages are updated and match new design how to configure this issue attached to a milestone when will this be completed x attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24680092537.0,2022-10-18 20:29:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,provide veterans with ability to edit benefit information for their fsr submission issue description as a veteran completes an online fsr they are presented with benefit information we have heard on a few occasions that this information can be incorrect and the business would like to providing veterans with a way to edit the benefit information that is presented to them the edited information should override what is submitted on the form for that submission tasks mock up designs for editing capabilities acceptance criteria design is ready to be handed over to development how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 19683003201.0,2022-01-11 18:43:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, medical copays content anomalies what happened on staging medical copays authenticated balances and detail pages some content anomalies were found balances page in not enrolled in health care alert there s a space between phone number comma detail page in main alert there s also a space between phone number comma detail page under how do i pay section in expanded option expanded accordion there s a space between phone number period specs device browser test users vets gov user gmail com kenneth vets gov user gmail com travis steps to reproduce url landing page sign in as vets gov user gmail com kenneth on landing page click review your current copay balances cta link on balances page in not enrolled in health care alert paragraph observe that there s a space between phone number comma sign out then back in as vets gov user gmail com kenneth back on balances page click an active balance card on detail page in main alert light blue last paragraph observe that there s a space between phone number comma in how do i pay option expanded accordion last paragraph observe that there s a space between phone number period screenshots balances page not enrolled in health care alert detail page main alert detail page how do i pay option alert desired content there should be no space between phone numbers and subsequent punctuations in balances page s not enrolled in health care alert in detail page s main alert in detail page s how do i pay option alert acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 13050469426.0,2020-07-29 15:32:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, conduct remaining diary code workshops w dmc issue description conduct remaining diary code workshops w dmc tasks conduct thursday jul conduct friday jul consolidate decisions made and upload to gh acceptance criteria workshops conducted decisions documented in gh ,1 11493155073.0,2020-02-11 22:26:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,use code splitting to reduce the size of the vaos payload we should be able to use code splitting to improve the load times for vaos some options might be to split out the form from the main app so that it s loaded only after you click schedule appt we might also have components that are large within the form that we could load separately ,1 26942470343.0,2023-02-08 04:12:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, financial status report s find a form content background with the fsr s release coming up we need to ensure it s findable in multiple places on va gov i ve drafted content based on the ez s find a form page to ensure consistency let me know what thoughts you have about any of the proposed content fsr s url va gov manage va debt request debt help when to put in place tbd estimating sprints i ll remove placeholder from the title and add a comment to this ticket when i have a solidified date content title change about va form related to i m unsure what guidelines determine what we put here i looked at multiple results and some listed categories while other listed many let me know how i can help determine what would be best to list here my thoughts on what we might want to include debt management veteran’s benefits administration veteran’s health administration disability pension health care when to use this form use va form if you’re a veteran or service member who needs help with debt related to va disability compensation education or pension benefits you can use this form to request a payment plan compromise offer or waiver helpful links we d like to add the following links manage your va debt check the status of your va debt and find out what options you have to resolve it url request financial assistance for va copays if you’re struggling to pay your copays learn how to request a repayment plan debt relief or copay exemption url these two links directly relate to va debt so it s important that we provide that information to our users we likely don t want a long list in the helpful links section so we can replace the request your military records including and get your va records and documents online because documents related to va debt live in the manage your va debt tool thank you ,1 15395422586.0,2021-03-03 19:12:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, empty state for when there are no debts issue description currently an authenticated user can technically access the fsr form when they do not have an active debt however we want to prevent users from submitting general fsrs since this iteration focuses on vba debt veterans could potentially submit an fsr that was meant for a different department or debt type tasks once an authenticated veteran navigates into the form from the introduction page there s a fetch call for debts if there are no debts returned display the empty state in acceptance criteria the provided empty state displays when the api call returns no debts for the authenticated veteran the empty state has been qa tested ,1 22309416923.0,2022-06-13 15:37:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, tech debt clean up duplicate actions between day of and pre check in description actions for recording answers to demographics responses are being duplicated in day of and pre check in these can be moved to the shared actions file to reduce duplication tasks move record actions to shared actions file we have an existing shared file update import paths create or update unit tests create or update tests update relevant documentations readme use cases acceptance criteria code is reviewed and merged into master passes accessibility checks using axe deployed to staging designer has signed off on the feature product team has signed off on the feature ,1 15238375074.0,2021-02-19 01:46:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up use of mhv account audit api in mobile sm client pre existing mhv integration code was invoking mhvloggingservice login current user which invokes an audit endpoint on mhv this seems like it is a holdover from when vets gov was exposing sm and rx features i e it was a web portal equivalent to mhv and so login events needed to be audited it makes less sense from the standpoint of a mobile app api integration i checked with barry from the mhv team and he was going to confirm whether or not it was still needed there is a separate account activity log that is triggered directly by the sm api requests which makes more sense from an api ecosystem perspective assuming all clear from mhv remove this invocation of the mhvloggingservice from the mobile code path ,1 27719093684.0,2023-03-14 19:05:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, styling and text updates for fsr issue description this ticket will contain a list of small changes styling and text updates that need to be made on va gov tasks update link styling on wizard bold monthly in what s your gross monthly income at this job acceptance criteria updates are made and merged how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27744826904.0,2023-03-15 16:21:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, modify the precheckinaccordionblock to not open accordion items when there is an error user story when the veteran gets an error on an expired pre check in link the accordion assumes that the answers to the demographics questions were all no this results in the accordion opening certain drawers that might not make sense img width alt screen shot at am src for these scenarios we don t have answers to the questions but we show the accordion appointment canceled pre check in past appointment pre check in expired we could change the default to null and don t open any drawers on the accordion unless answers to demographicsuptodate emergencycontactuptodate or nextofkinuptodate are passed in tasks change the argument default to null create or update unit tests create or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 14235915316.0,2020-11-18 15:23:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update with feedback new list loop design issue description the design team has previously collaborated with vsp s accessibility team to design an accessible list loop component variation that aligns with the existing list loop s functionality we need to incorporate the modified list loop into s hi fi designs additionally we received feedback that splitting some of our questions to separate pages may ease cognitive load tasks update s hi fi prototype with the modified list loop designs split the veteran s employment history into two pages one with gating questions and current employment fields and one for additional jobs the veteran has had within the past two years split the veteran s other income into pages with one question per page update the marital status question to ask if the veteran is unmarried married separated etc split the spouse s employment history into two pages one with gating questions and current employment fields and one for additional jobs the veteran has had within the past two years split spouse s other income into pages with one question per page acceptance criteria the hi fi prototype has been updated and exported to uxpin the updated uxpin prototype has been linked to this ticket as a comment ,1 11222880031.0,2020-01-07 21:14:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,do we need the vaos facilities service the fe is only currently using the name city and state info from the vaos facilities endpoint we could get this from the regular facilities api instead of using one that maps back to vamf the only real unique info in that service is parentstationcode but we probably don t need to use that worth considering removing this service once we re comfortable with how the facilities data is being used ,1 15836097466.0,2021-04-06 18:51:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,post launch review of va debt management tool issue description now that the debt management tool launched and we re getting closer to releasing the fsr we should take a look at the manage your va debt tool to uncover areas to improve iterate on tasks review the launched debt management tool and document proposed improvements review domo analytics in relation to the debt management acceptance criteria documentation has been attached to this ticket and proposed improvements features have been discussed w the team ,1 17771756788.0,2021-08-30 14:24:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor community care detail page refactor the community care details page so that there s no longer a separate communitycaredetailspage component in confirmedappointmentdetailspage there s a detailscommunitycare component for cc confirmedappointmentdetailspage is updated to handle cc as well as va details pages there are still separate urls va and cc for va and cc details pages,1 30509504646.0,2023-07-18 19:36:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display vehicles issue description add vehicle summary vehiclessummary as view only on the final review page can likely leverage a custompagereview similar to how utilitybillsummaryreview is implemented only show the values that have been populated see for copy tasks implement read only display on final review page acceptance criteria vehicles are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25795188569.0,2022-12-10 13:28:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, bug feature flag not updating when choosing to restart form issue description feature flags for copay inclusion combined fsr and fsr enhancements are not updating when the user exits the form and selects start new application option this is causing users to engage the old experience solution identified a isstartingover flag the form system utilizes when start new application is selected using that flag to update feature flags appropriately since the initial form data is wiped when restarting tasks identify why the flags are not updating resolve issue with flags not updating acceptance criteria feature flags update appropriately when starting the application over how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11137146259.0,2019-12-20 18:30:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,implement yaml configuration for dependabot background now that the vets api repo is using dependabot we should migrate our configuration to a more specific rules file see acceptance criteria dependabot uses yml config configuration is not colliding with cms or other teams,1 23895693227.0,2022-09-08 14:38:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,certificate of eligibility remove obsolete feature flags description certificate of eligibility copied some code from platform that still has a feature flag in the code that have been removed and need to be cleaned up request locked pdf password related to tasks remove feature flag code in coe platform update tests definition of done all tasks complete all tests passing,1 15393776133.0,2021-03-03 17:06:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create test case data for test users in order to qa fsr test users need to have the following data scenarios created veteran does not have any va benefits to prefill the fsr form veteran has va benefits to prefill the fsr form veteran has one debt veteran has multiple debts definition of done create data and tie to test users provide test users to with attached scenario ,1 23112180643.0,2022-07-27 13:53:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design and research discovery issue description learn more about cfsr tasks learn more from colleagues about cfsr review uxpin prototype vs current fsr watch riley s cfsr demo acceptance criteria better understanding of cfsr ,1 25381972613.0,2022-11-21 18:19:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,isolate claims status application background in order to speed up development on vets website applications platform has started using yarn workspaces these workspaces allow us to build our app independently of the rest of the applications in vets website in order to use yarn workspaces one of the prerequisites is that we need to be added to the allowlist for single app builds to be added to the allow list we must make sure that our app is isolated from the other applications this requires us to make sure that we are not importing from other applications and other application are not importing from cst currently cst is not importing from other applications but personalization is importing from cst we need to fix this tasks update the personalization app to not import from cst acceptance criteria personalization is not importing from cst cst is ready to be added to the single app build allowlist ,1 24706561126.0,2022-10-19 19:36:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,changing contact info on veteran s profile issue description allowing veterans to update their contact information as part of their va profile instead of just for the fsr submission that does not persist background as part of the design team questioned why the experience does not transfer to the veteran s profile currently on fsr any reason not to change personal information section to something like this tasks investigate feasibility of implementing the ability for the veteran to change their contact info on the portal acceptance criteria identify and document a path forward for implementation first step connect with supplemental claims team how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21103869377.0,2022-04-04 16:46:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,link guidance to static vs dynamic in collab cycle kickoff ticket user story as a vfs team member completing a collaboration cycle kickoff ticket i want to know and understand the difference between static pages and dynamic pages ie tools and applications so that i may answer the kickoff questions correctly intended audience vfs teams desired outcome updated collaboration cycle kickoff ticket and guidance improved responses and reduced confusion in cc kickoff ticket due date description in the and in the vfs teams are asked to identify if their work will involve changes to tools and applications static pages and or both teams seem to struggle with this question as they don t have a clear understanding of what qualifies as a static page the sitewide content ia team put together guidance on and have given us permission to link it in collaboration cycle documentation artifacts confirmed needing updates tasks add link to in github template add link to on platform website page re collab cycle kickoff acceptance criteria collaboration cycle kickoff github template has been updated per guidance collaboration cycle kickoff page on platform website has been updated per guidance updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 13306239526.0,2020-08-25 19:54:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl usability testing issue description conduct usability testing on the uxpin prototype with users tasks complete usability testing with users upload scrubbed transcripts to gh acceptance criteria testing completed transcripts uploaded to gh and linked in the comments,1 12453416564.0,2020-05-27 13:49:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,upgrade gems included in gemfile bundle outdated only explicit outdated gems included in the bundle active model serializers newest installed requested in groups default activerecord postgis adapter newest installed requested in groups default awrence newest installed in groups test aws sdk newest installed requested in groups default aws sdk sns newest installed requested in groups default carrierwave newest installed requested in groups default carrierwave aws newest installed in groups default connect vbms newest installed in groups default danger newest installed in groups development test dry struct newest installed in groups default dry types newest installed in groups default faraday newest installed in groups default faraday middleware newest installed in groups default flipper active record newest installed requested in groups default flipper active support cache store newest installed requested in groups default flipper ui newest installed requested in groups default json schemer newest installed in groups default jsonapi parser newest installed in groups default nokogiri newest installed requested in groups default oj newest installed in groups default openid auth newest installed in groups default pg newest installed in groups default puma plugin statsd newest installed requested in groups default pundit newest installed in groups default rack newest installed in groups default rails newest installed requested in groups default rails semantic logger newest installed requested in groups default redis newest installed in groups default restforce newest installed in groups default rubocop newest installed in groups development test rubocop rspec newest installed in groups development test rubyzip newest installed in groups default sentry raven newest installed requested in groups default shrine newest installed in groups default shrine memory newest installed in groups test sidekiq newest installed requested in groups development test sidekiq ent newest installed in groups production sidekiq pro newest installed in groups production sidekiq scheduler newest installed requested in groups default statsd instrument newest installed in groups default cleaner newest installed in groups default vets json schema newest installed in groups default web console newest installed in groups development will paginate newest installed in groups default ,1 14886539207.0,2021-01-20 17:04:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr iteration allow vsos to fill out and submit fsr form high level user story ies as a vso representative i want the ability to fill out the fsr form on behalf of the veteran as a designated representative and submit the form hypothesis or bet by allowing vso representatives to fill out the form online there will be less errors and time to resolution should be shorter okr faster resolution times due to more accurate information and less returns for errors definition of done vso reps can fill out form without authenticating vso reps have to certify the form as legal representatives take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 12494726608.0,2020-06-01 11:49:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,other aws accounts need attention user story or problem statement as admins of all the various va aws accounts we use within our workflows we need to be more conscious of compliance security etc with the less used ones also goal ideally all the accounts would be managed in code via terraform for all resource pieces like iam users vpc s etc this may be a bit of an undertaking though so i would say the most immediate current concerns would be auditing those accounts and making sure offboarded users do not still have accounts objectives or key results this is meant to further ato compliance security better off boarding process es tasks decide as a team if we want to go ahead and try to get these accounts managed more in code or push forward for now manually remove off boarded users unused resources outdated objects etc acceptance criteria cleaner aws account management ideally in code but if nothing else the removal of old accounts resources etc should be completed within the near future how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 29499715479.0,2023-06-02 20:21:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, accessibility testing content zoom and reflow bug for dependents input page issue description on the dependents question the input is too wide from on up dependent count label dependent count usa input error message width b variables scss seems to be the issue since width is being applied as a fixed value from the variable originally posted by josephrlee in tasks change input width to be relative percentage based instead of a fixed width acceptance criteria input no longer overflows at zoom how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18734122838.0,2021-11-04 03:42:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, assure that all programs pages are published and covid vaccine page are correct story as an editor i need to have my covid vaccines page correctly placed under programs and programs published so i can associate the page correctly and so the covid page can be correctly displayed goal by publishing the programs page not enabling in on menu unless required it can have child pages tasks update approximately program pages and covid vaccine pages publish program pages but only enable menu if pao requests leave it disabled move covid vaccine page under programs in menu location and rename alias to include programs correctly publish confirm menu is updated correctly acceptance criteria all programs and covid vaccine pages have been published and menues are correct ,1 27018740953.0,2023-02-10 22:19:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,define requirements with vbs for new copay notification issue description connect with vbs to discuss requirements and next steps for the new medical copay notification tasks create some rough draft definitions for the data file that will be transferred for notifications acceptance criteria present and discuss with vbs data requirements how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 17149878145.0,2021-07-13 19:02:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,hlr switch alertbox to va alert description switch the alertbox component to use the va alert web component in the higher level review form tasks replace alertbox with va alert update unit tests update tests if applicable definition of done tasks completed all tests passing,1 16243821397.0,2021-05-07 12:43:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in datetimerequestpage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos new appointment components datetimerequestpage index jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 14971768323.0,2021-01-27 21:41:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, chapter content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to chapter tasks incorporate the global changes outlined on pages in the provided document acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 24580113166.0,2022-10-13 15:01:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl update and empty state messages issue description update the and empty states for the debt list and debt letter table pages tasks update the and empty states for the debt list and debt letter table pages acceptance criteria messages match for the following use cases ,1 12395568855.0,2020-05-20 18:54:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters interviews summary and requirements problem description in order to design a landing page for debt letters the current process and pain points for debt letter generation and process flow needs to be understood and documented goal process flow for debt generation process flow and desired outcome for displaying debt letters information to veterans online objectives or key results this is meant to further allow veterans to see the information of how debt was incurred the amount of the debt and remediation steps tehy need to take tasks summarize research findings from interviews with call center and stakeholders create process flow and suggestions for next steps acceptance criteria document summarizing what the requirements are in showing debt letters information on line how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28042384326.0,2023-03-28 19:36:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,heuristic evaluation synthesis and report issue description what details are necessary for understanding the specific work or request tracked by this issue a review and synthesis of the team s completed individual heuristic evaluations will be done a concise report will be created for the team compiling everyone s individual evaluation feedback in heuristic eval workshop part the team will have a chance to review the issues that were noted and decide what to change report deck heuristic evaluation compilation spreadsheet tasks what work is necessary for this story to be completed the review and synthesis process creation of a report as a document or a deck acceptance criteria what will be created or happen as a result of this story the review and synthesis process creation of a report as a document or a deck ,1 26244574732.0,2023-01-05 14:18:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rework user validation messaging on to be less aggressive design task according to our user the hca seems to be a little out of spec please look through the hca to confirm our user validation meets our guidelines to be less aggressive expected behavior user messaging and validation errors are more welcoming do not user verbiage like must acceptance criteria user validation on the hca meets our messaging guidelines additional context during this the verbiage was called out by a coworker ,1 14860177377.0,2021-01-18 19:58:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update content for the post gi bill waiver resolution verification issue description if a veteran submits an fsr for a waiver on a post gi bill and it s granted their remaining education benefits are reduced to resolve the debt this may not be clear to our users so we want to verify that they understand that their debt won t be completely waived if they choose this resolution tasks update the fsr s debt resolution ui to display a certification checkbox if the user has an education debt and requests a waiver ensure that other debt types don t display the checkbox when the user requests a waiver acceptance criteria fsr s ui has been updated and matches the linked designs ui has been reviewed by a designer ,1 20157152983.0,2022-02-09 17:29:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, provide a way for veterans to email dmc with technical concerns issue description currently dmc receives calls from veterans experiencing issues from the debt portal and are experiencing issues assisting them tracking the issue and forwarding the issues to our team when applicable we re exploring implementing ava but in the meantime want to update the contact information to include an email address for technical concerns tasks reach out to jill to determine when a veteran should reach out to dmc set up a call as needed review the debt portal s contact information error messaging to determine areas that could benefit from adding dmc s email address update designs acceptance criteria designs have been updated and linked in this ticket designs have been sent to jill for review ,1 25568685117.0,2022-11-30 16:02:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design for fsr review page issue description design for fsr tasks create designs for open accordions on acceptance criteria uxpin updated ,1 19319794229.0,2021-12-14 03:15:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, only show latest copay on overview page technical task we should only show one copay card per facility we should never have the same facility on overview page twice make sure only the latest copay shows on overview page expected behavior overview page only shows latest copays and no duplicates acceptance criteria facilities are not repeated on overview page only the latest copay shows on overview page ,1 13615969558.0,2020-09-23 15:03:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres integrate fsr with vets api for contact data story as a veteran who is authenticated on va gov filling out the fst form i would like my contact data to be pre filled if the contact record is incorrect i would like to see links to update my contact record acceptance criteria for a test user logged into va gov teh contact record fo rthe test user is prefilled ,1 15110452519.0,2021-02-08 19:14:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, chapter content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to chapter tasks incorporate the chapter changes outlined on pages of the provided document acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 23697652844.0,2022-08-29 15:56:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update the cypress viewport updater bot so it automatically updates the newly added default viewport values the following was recently added to cypress json to set the default cypress viewport to the top desktop viewport used by va gov users viewportwidth viewportheight tasks update these values automatically when the cypress viewport updater runs each month acceptance criteria the cypress viewport updater bot will successfully update the viewportwidth and viewportheight values in cypress json ,1 27092130881.0,2023-02-14 22:06:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, gather affected veteran identifiers issue description we need to gather uuids for affected veterans from fe issue where submissions were not being routed to the correct endpoints we need to extract the logs from grafana and run script to gather affected veterans uuids tasks extract the logs from grafana run script to gather uuid acceptance criteria uuids for affected veterans have been collected and are ready to how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24704882444.0,2022-10-19 18:10:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, checkbox to input boxes enhancements issue description add checklist to box functionality in fsr for the following pages and spouse example of functionality tasks add page jump functionality for phone number apply functionality to email and mailing addresses acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15167433845.0,2021-02-12 17:47:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, chapter content ui updates issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to chapter tasks incorporate the content changes on pages in the provided document into the fsr s staging environment it may be easier to reference the uxpin for the content updates reach out to the design team with any questions acceptance criteria the chapter changes have been incorporated into the fsr s staging environment chapter s ui matches the linked prototype work has been checked off in the ,1 11455356996.0,2020-02-06 18:56:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fix issues with direct scheduling test after some updates to the ds test to make it go through the full flow we encountered some instability in the test and turned it off we need to address those issues and turn the test back on ,1 22295782491.0,2022-06-13 01:16:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, combine debt portal copay bills overview details mismatch what happened on staging your va debt and bills page copay bill summary card s total amount and bill count didn t match current copay balances page copay bill cards s balances total and count specs device browser test user if applicable vets gov user gmail com travis steps to reproduce go to and sign in via id me as vets gov user gmail com travis doc for passwords go to page in copay bill summary card note total amount and bill count then click check your balance link on current copay balances page observe that copay bill cards balances total and count do not match figures on previous page screenshots desired behavior current debt and bills page and current copay balances page should have matching copay balance totals and bill counts acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 12496812697.0,2020-06-01 15:26:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add messages check to appointment list test in our appointment list test we should pick an appointment to fetch a message for to verify that that functionality is not broken ,1 19098931406.0,2021-11-29 19:57:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,access for scott james cor name mary o’toole vendor onboarding representative name governmentcio kimberly o west your name scott james your email scott james gcio com name of your team debt foregiveness sr back end developer governmentcio service s you want access to socks aws public ssh key ssh rsa ozo kp mdxvrrybhr wdg xlfo xiutkspgnt macbook macbooks mbp desired aws services for attachments cloudfront for logs systems manager for parameter store and to view staging instances,1 18911680872.0,2021-11-16 14:42:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add husky and lint staged to vets json schema technical task there are hundreds of linting errors on vets json schema since the lint rules are not enforced adding husky and lint staged to the vets json schmea repo so we get less unrealized errors also adding the yarn build command to husky so people dont forget to update the dist for schema changes expected behavior eslint rules will be enforced when files are staged in git yarn build and lint will run on pre commit acceptance criteria lint runs on pre commit all staged files are linted yarn build runs on pre commit ,1 25894838434.0,2022-12-14 21:21:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,🥐🥐 flaky test detected community care cypress spec js your test spec src applications vaos tests community care cypress spec js has been disallowed from running on vets website due to flakiness since please make corrections to the test spec and run it through ci to have it re enabled ,1 17020630890.0,2021-07-02 18:26:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,phone number is implicitly required on fsr description when i start the fsr there is a field to enter my phone number although the phone number is not a required field i must enter a phone number to continue through the form when left empty the value is validated against a proper phone number format causing a validation error since empty string null is not a proper format ,1 30480857420.0,2023-07-17 20:14:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, sw add feature flag for streamlined waiver issue description add new feature flag for streamlined waiver effort let s call it financial status report streamlined waiver tasks add new feature flag for streamlined waiver acceptance criteria new feature flag has been created for streamlined waiver work how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13389965820.0,2020-09-02 19:45:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,configure release tagging for the sentry brd issue description as an engineer in order to deploy and tag sentry releases should be tagged and configured as appropriate for the vsp brd cycle tasks update the ansible playbooks to tag releases for sentry builds acceptance criteria sentry builds and releasees are appropriately tagged how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14172657747.0,2020-11-12 17:14:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rename references to vapsvc the service changed its name to va profile a few of months ago we should update the fe code to prevent confusion and enhance clarity or any reference to really doesn t mean anything anymore and could really confuse someone who is new to this code or the program guiding principles we should drop or when possible replacing it with vap or vapsvc or vapsvc or vap svc or simply dropping it altogether depending on the situation we should aim to not use the phrase vaprofile in our code when possible this is ambiguous and could refer to the profile feature we develop and maintain on va gov or the va profile service that we integrate with we should aim to simply use profile when referring to the feature we are developing and maintaining and use the terser vap or some variation like vapsvc when referring to the service that we integrate with ideas rename any mentions of to vapsvc rename any mentions of to vap svc rename any files and components to vap or vap rename all references of to profile as our profile is always backed by va profile ie there is no longer a non va profile profile so we no longer need to specify which one is the va profile version rename the vaprofileapp to profileapp caveats be careful not to rename any strings that contain such as error codes for the time being we should not touch the top level vaprofile item in the redux store which is a different ball of wax,1 12960078373.0,2020-07-20 13:53:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl dlc api debt must match letter in vbms story modified issue description a veteran can have one or many debts that are passed in dmc api to be displayed on summary page a veteran will have the ability to download the debt letter that is associated with a specific debt summary tasks identify data element in dmc api that is tied to specific debt letter in vbms work with dmc to modify api if needed add variable in api get acceptance criteria as a veteran who is viewing a debt summary and clicks on download letter associated with that debt i expect to be able to download that letter for any given test user the downloaded letter matches the debt summary how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23741965234.0,2022-08-31 13:10:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,look into why the tests for on site notifications have to be skipped for the ci the from had to be skipped they worked perfectly locally but in the ci it refused to pass we tried every known tactic in the book to get it to pass but never succeeded in locally replicating the specific error in ci in ci the tests are failing to find a specific element cy findbytestid dashboard notifications in local however loops have failed to replicate this instead failing on api call intercepts removing waits on those intercepts didn t help with replication ,1 19566708528.0,2022-01-04 02:12:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, updates to the details page s content issue description craig pointed out in that we need to provide the urls for the mcp mvp s links on the details page upon further investigation there were some content changes that needed to be incorporated as well we also noticed that some of the content took into account the combined fsr but that won t be available for release tasks add comments to the uxpin prototype with the correct links update the page s content where applicable acceptance criteria the prototype is updated and linked in this ticket a ticket for frontend content changes is created and linked in this ticket ,1 31017845086.0,2023-08-10 01:02:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, sw add new chapter level depends and structures issue description once income limits back end has been implemented we can create new chapter level depends based on tasks create new chapters for streamlined waiver feature flag add depends to new chapters based on income limit requirements create new tests for different branches see mural above for branching and examples i e dan ana etc this will probably be a lot to add so we can break it out in new ticket s acceptance criteria new sw chapters are created with depends include tests for new flows how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27296216715.0,2023-02-23 20:35:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update omb information issue description omb information for fsr needs to be updated with correct code and expiration date tasks update omb information for fsr acceptance criteria omb info has been updated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15680904121.0,2021-03-25 04:02:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review at all wilmington va system pages to validate mvp and consistency user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation prod cms va gov tasks complete review of system and facility pages for the following content and flow asking these questions does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page confirm all of the facilities are reviewed wilmington va medical center atlantic county va clinic cape may county va clinic cumberland county va clinic kent county va clinic sussex county va clinic document all errors items that need update and testing on each page using spreadsheet listed above acceptance criteria all node pages have been reviewed in spreadsheet and issues found have been been documented issues have been escalated for resolution using spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 19566705527.0,2022-01-04 02:12:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the overview page s facility contact information for proper semantic heading structure issue description after incorporating angela s feedback regarding semantic structure the design team noticed the questions about your treatment or your charges section could be simplified from headings to an unordered list screen readers will read the facility list out as an x number of items tasks update the content on the overview page to list the veterans facilities in an unordered list acceptance criteria the updated uxpin has been linked in this ticket a ticket for frontend has been created and linked to this ticket,1 31780151021.0,2023-09-12 16:50:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,account for flat streamlined field in issue description in the streamlined method we should check for either flat streamlined true or the complex type streamlined type short value true since it may be possible to be of either type based on persistence order tasks account for flat field acceptance criteria we can call streamlined with confidence how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12975856613.0,2020-07-21 17:43:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl download letters from efolders user story as a veteran who is viewing my debts as were communicated in the debt letter s and on the summary page i would like the ability to download the debt letters in pdf as provided in the download link due to potential constraint on vbms all the letters will be listed on a page in reverse chronological order tasks connect to vbms endpoint download letter as provided in the link on fe page acceptance criteria for a test user with one debt but letter ability to download all letters for a test user with debt and letter for each debt ability to download all letters how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26338426790.0,2023-01-10 15:55:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint dec jan sprint goals new contract onboarding initial set up va training finalize vbms audit work identify veterans impacted by fsr submission issue prepare for usability research sessions for fsr enhancement release sprint deliverables list of deliverables completed during sprint remove unused ga planned issues coordinate url changes aggregate vbms logs since launch unplanned additions n a capacity planning pto holiday s note winter code freeze note january holiday for all denise scott brandyn andrew megan points planned points accomplished tbd points over tbd issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 22840829518.0,2022-07-12 21:39:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, mock demographics confirmation patch requests in cypress description we aren t intercepting these patch requests and causes the output log on cypress tests to look like they have errors nothing breaks and tests still pass it would be a nice to have screenshot ,1 14172749911.0,2020-11-12 17:21:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch household expenses content as a veteran filling out fsr form i want helpful content to understand what i should include in the expenses portion of the form ,1 18948886359.0,2021-11-18 13:16:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review debt resolution team tools for instances of sighted language issue description the sitewide content team is moving away from using sighted language such as the word view on va gov tasks review the following products staging environments for sighted language medical device re ordering tool debt management portal financial status report medical copay tool document changes for each tool acceptance criteria areas including sighted language in each tool have been documented and attached to this ticket tickets are created for frontend changes as needed tickets are created for the sitewide content team as needed ,1 26809751859.0,2023-02-01 21:16:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,define requirements with vbs for new copay notification issue description connect with vbs to discuss requirements and next steps for the new medical copay notification tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23445229836.0,2022-08-15 18:54:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, audit tests and add axecheck calls to non compliant files warning message viewable in my ide as of today cypress tests must include at least one axecheck call documentation for adding checks and understanding errors can be found here tasks determine if this is still an issue find what is flagging eslint and run locally add axecheck calls to any components that are missing them create or update unit tests create or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled ,1 22151402700.0,2022-06-03 17:13:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analytics kpi dashboard request for request an edge case kpi dashboard what this form is for use this template to request a kpi dashboard on domo for your product this template is for products that fall outside of our standardized dashboards if you have another va gov product please reach out to the platform analytics insights team on vfs platform support expected delivery timelines please note that these dashboards will require additional data and design discovery and will take additional time to deliver instructions for the vfs team please fill out and link it below to help define your product feature s information please request the excel sheet from the platform analytics insights team if you do not have google access the analytics team will not be able to pull this ticket into the queue until this is provided and linked if a part of your product involves any sort of linear process funnel for which you want to be able to measure conversions please include it in the forms tab of the template all other pages associated with your product for which you d want to track visits and engagement should be added to the content tab add links to product outlines feature information or any other resources you think would help us better understand your product and okrs to the vfs provided information section below add your team label to this ticket to follow progress if you do not have domo access please vfs provided information add links to product outlines feature information or any other resources you think would help us better understand your product and okrs below feel free to also type background information into this section directly the more context you re able to provide the fewer questions we ll need to ask you before getting started product resources other product info add here as needed additional resources from the platform analytics team please use the for more information on the metrics used in the standard kpi dashboards for additional info read through the please leave the following blank vsp analytics insights acceptance criteria discovery design determine appropriate product questions determine appropriate metrics charts design dashboard layout build see add the vsp analytics insights group as the dashboard owner structure funnel data for etl pipe available metrics to domo document any blocked unavailable metrics in the analytics team space update the dashboard header including google analytics links if any add for additional necessary implementation q a please see complete the share add vfs group default group to the dashboard for new vfs customers only schedule onboarding meeting host the meeting to explain how the dashboard works definition of done acceptance criteria has been completed kpi dashboard full qa checklist completed dashboard has been shared back with the vfs team,1 25729143615.0,2022-12-07 18:50:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,🥐🥐 flaky test detected audiology cypress spec js your test spec src applications vaos tests flows community care request flow audiology cypress spec js has been disallowed from running on vets website due to flakiness since please make corrections to the test spec and run it through ci to have it re enabled ,1 13768498823.0,2020-10-07 17:10:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl mid complexity hifi prototype issue description create a high fidelity prototype in uxpin for one of the following concepts or tasks create the high fidelity design in uxpin in it s own project share with designer update gh documentation and share with the team acceptance criteria designs up in gh and shared with team for feedback,1 19721571183.0,2022-01-13 15:50:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,linking to the medical copay tool on the debt portal s content page from the debt resolution team what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with content support ia support we ve launched the medical copay tool and noticed that directs veterans to call the health resource center if they have health care and prescription charges we d like to incorporate a button that links to in case veterans navigate to the debt portal instead of the medical copay tool supporting artifacts please provide supporting artifacts as available link to product outline link to or attach user flows link to prototype or mockups link to any epics issues that may be helpful will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date estimated staging review date content and ia work needed by asap do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name the debt resolution team octo de product owner product manager denisecoveyduc designer rileyorr fe engineer craigwheeler product team slack channel vsa debt next steps once you’ve submitted this ticket please post a link to this issue in the  slack channel and tag rlhecht if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 18727786523.0,2021-11-03 18:03:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add new devops config for mcp vbs endpoint technical task add new api url and key to devops repo for dev and staging enviorment expected behavior devops repo has url key for local dev and staging environments acceptance criteria devops is configured for new url and api keys ,1 13770422116.0,2020-10-07 20:12:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr hi fidelity prototypes iteration issue description once wireframes are reviewed and feedback is incorporated the design team can move into high fidelity prototyping the fsr va form tasks create hi fidelity prototypes in sketch port sketch files to uxpin and add interactive states as needed acceptance criteria uxpin prototype is linked in this ticket ,1 11492871781.0,2020-02-11 21:51:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,improve vaos action unit tests the following action files have test coverage that could be improved to cover some edge cases actions appointments js actions newappointment js,1 28008146063.0,2023-03-27 16:34:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, utility bills enhancements issue description add checklist to input list and mini summary options for utility bills checklist options exclude other tasks add the following pages checkbox page input list page mini summary page new utility input show list in final review page update efsr specific testing include item removal and addition acceptance criteria page matches design and functionality all new and existing tests are passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14004108065.0,2020-10-28 16:41:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr household expenses hifi design as a veteran i want eh ability to add my expenses when filling out the fsr form so dmc can have an accurate representation of my financial status ,1 20825778364.0,2022-03-18 20:40:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,letter design fixes description while examining the letters app i found several pages with accessibility issues service not available notice no and content doesn t match design patterns img width alt page header plus a sentence then the footer src header level problems img width alt all headers inside the accordion are s the first should have two nested src tasks add alert to no service page nest under inside benefit summary accordion update unit tests definition of done all tasks complete all tests passing ,1 30821629242.0,2023-08-01 16:45:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add streamlined waiver notification to va notify portal issue description create a new notification template in the va notify portal for veterans that complete a streamlined waiver submission for vha fsr requests with the following copy from u s department of veterans affairs subject the debt management center has approved your request dear name thank you for completing the financial status report va form to request help with your va debt your waiver request has been approved and you will also receive a letter from vha in the mail date submitted date to check the status of your va debt status at any time sign in to thank you va gov please do not reply to this email if you need to contact us please visit va gov tasks login to va notify portal via va network piv add new template to staging for testing and production retain newly created template ids acceptance criteria notification templates are available in staging and production va notify portals how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28044897405.0,2023-03-28 21:46:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add instructions for tracking components or patterns that need to be updated user story as a governance team member i want to be able to know if an experimental design component pattern is in an upcoming review so that i can provide accurate feedback assignee peer reviewer sterkenburgsara description we would like to be able to track design patterns or components that come up in design intent midpoint or staging reviews that need to be updated for example the start a new application button in the form system should be a link after speaking with dsc we need to add labels and assign the ticket to carol wong add these labels design system update vsp design system team component update experimental design assign ticket to carol wong impacted artifacts tasks confirm with allison which tickets we ll be adding labels to experimental design design system update vsp design design team component update document instructions for governance team to follow if when it is recognized that a design pattern or component is in need of updating create draft page draft is peer reviewed and approved by governance team member add instructions to and where appropriate peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria the governance team will how notify design system team when an existing component or pattern needs to be updated governance team will be able to track components or patterns that have these labels how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 24760572026.0,2022-10-21 23:19:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, lighthouse api for cdw data issue description we understand that payment data is available on the corporate data warehouse cdw and that lighthouse might be able to establish an api for the debt portal to collect this data tasks reconnect with light house team kelly lein dave mazik to define path forward to establish api they have a standing weekly meeting we can join to kick off discussions previous discussions kelly lein i started a conversation with some of our api teams that interface with cdw veteran health apis and facilities api and we confirmed that we do not currently pull this data it does sound up our alley though so please reach out to dave mazik if you’d like to talk about adding this to our roadmap dave mazik dave said i think this could be of the following requests to make sure i point you in the right direction could you help me see which one s it might be you have a team that is going to build this api somewhere in vaec but want to make it available on lighthouse you have a team that wants to build an api to onboard to lighthouse and have it live in a lighthouse vaec aws account instance you want the lighthouse team to build this api we requested option and he said the lighthouse team needed a bit more information regarding the apis we need and they would do a bit of thinking it and get back to us acceptance criteria determined next steps and identify path forward how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 32040377664.0,2023-09-22 18:47:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review submissions from vha for errors issue description mike dewey at vha has identified transaction ids that may have errors see attached list for individual transaction ids and follow up information tasks each of the transaction ids noted will be reviewed to ensure that they were vha not vba and the medical copay debt did not exceed acceptance criteria we will be able to share our findings with vha to give them confidence that the calculations are accurate how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13640901132.0,2020-09-25 13:26:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging review debt letters mvp steps to complete staging review product manager create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in in slack tag andreahewitt mandi lipka mandi to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must complete list of artifacts below vsp requesting team review meeting completed practice area reviewers create sub issues attached to this one with feedback for your team on feature name requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket may differ for each practice area please refer to attached tickets for further instruction all requesting team attendees complete brief survey artifacts please provide the following artifacts at least days before scheduled review meeting link to link to access information for the tool or feature in staging do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository please use greg anderson user link to your product test cases test plan in testrail with test execution logs please note debt letters is one page listing out the veteran s debt and a table with links to debt letters because a veteran needs to log in to see this the only way to test is moderated release with live veterans will be sitting in on a few sessions as part of qa process link to your and reports in testrail for qa practice area review required read the conduct axe browser scan and document or address issues found ensure end to end tests including the axe check pass check color pairing for proper contrast check for colorblindness issues zoom to at wide and confirm readability no info cut off etc repeat for repeat for navigate all pages and core functionality with keyboard only test all pages and core functionality happy path with macos voiceover and or nvda firefox recommended read the add keyboard end to end tests in ci cd test runs conduct axe coconut browser scan document or address issues found test with list of known issues with links to tickets when applicable meeting attendees from requesting team product manager required leah k leahkeeler depo product lead required matt self anyone else from your team who significantly contributed to the artifacts provided required brad c cameron camerontesterman scheduling please reference the times shown are et note an available time slot within a recurring review group office hours slot that works for your team and is at least business days from now write that preferred time slot here on this ticket and vsp will send you a meeting invite if no available time slots work for your team write your availability and requirements here and megan andrea will reach out as needed additional notes during this collaboration point you will receive feedback from the following practice areas design accessibility content qa and optional product analytics engineering information architecture ,1 27775863449.0,2023-03-16 17:10:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,synthesis of team heuristic evaluation issue description what details are necessary for understanding the specific work or request tracked by this issue tasks what work is necessary for this story to be completed synthesis of team individual usability evaluation spreadsheets create a concise report based on team s feedback acceptance criteria what will be created or happen as a result of this story synthesis spreadsheet or mural concise report based on team s feedback how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13769817618.0,2020-10-07 19:13:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr wireflows iteration issue description once the team completes the fsr ideation session the design team will create wireflows of the fsr va form prior to prototyping tasks create wireflows for the fsr present wireflows to the team and confirm with development team that the ui is technically feasible with the form system acceptance criteria wireflows are uploaded to gh and linked to this ticket wireflows are presented to the team and any feedback is documented in gh optional if feedback needs to be incorporated a separate ticket is created to incorporate that work ,1 14968023808.0,2021-01-27 16:21:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,abstract signature box content and test summary during the postmortem we wanted to add more friction to updating signature box content so a copy paste error is less likely so we need to make unit test to force fe developer to double check the content changed before publishing we also need to abstract content to make it easier to maintain in a separate file rather than looking through code to edit content expected behavior when updating signature box content should see line for line diff in test acceptance criteria abstract signature box content add test for update diffs ,1 26369418344.0,2023-01-11 19:18:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore additional empty states post dec fix issue description review empty states after dec fix was merged tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16772050983.0,2021-06-14 15:52:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update url to request debt help form fsr url should be updated to and the breadcrumbs should be home manage va debt request help with va debt ,1 19591742760.0,2022-01-05 13:44:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor github actions report jobs by creating reusable actions issue description github actions testing reports actions can be broken down into reusable actions to avoid repetitive steps and eliminate many lines of code in workflow files that are quite bloated tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story ,1 24558222840.0,2022-10-12 17:44:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,wizard work product outline the wizard experience at the beginning of the fsr experience needs to be updated for a few reasons better inclusion of copay paths rework of overall design format experience one question per page addition of a payment path connection with streamlined waiver definition of done team has identified a path forward to update the wizard to align with current application and design requirements how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 23443177007.0,2022-08-15 16:50:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create internal documentation for building and maintaining yaml issue forms user story as a governance team member i want clear guidance on how yaml github issue forms work so that i can edit the collaboration cycle request template and create new templates as needed assignee briandeconinck peer reviewer description the is a issue forms are defined by a yaml file yaml has its own strict syntax for structuring data and github s forms engine is looking for specific keywords when generating forms most of this is documented by github but a few details were discovered via trial and error when building the collab cycle request form documentation created should be a confluence page in the governance team space with appropriate links to github s documentation a short how to code example from the collab cycle request form a tips best practices section learned from building the collab cycle request form impacted artifacts should not require editing any artifacts just creation of new documentation the should be used as a reference tasks create documentation detailing yaml draft documentation peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria governance team members are able to update and maintain the collaboration cycle request template governance team members are able to create new yaml templates how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team and sized when brought into a sprint move to the planned pipeline when brought into a sprint add assignee and specify peer reviewer ,1 30540773564.0,2023-07-19 21:10:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,send streamlined waiver notification for eligible requests issue description when a veteran goes through the streamlined waiver flow and completes the form they should receive a streamlined waiver specific notification tasks add streamline waiver notification templates to devops and vsp infra application manifests repo settings check if submission is streamlined and if feature flag is on and replace notification template with sw specific one add rspec tests for both flows acceptance criteria when a veteran completes a streamlined waiver submission they receive the streamline fsr notification how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14545233969.0,2020-12-15 19:20:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, finalize why might i have this debt content issue description in order to finalize the debt letters mvp release we need to provide content to users explaining why they may have received a va debt there are many ways a veteran can receive a debt but we don t need to list every possible reason rather we should provide common reasons why a veteran may receive a compensation pension or education debt we have but need to ensure the content aligns with and tasks reach out to the dmc stakeholders for answers on outstanding questions bolded in the gdoc finalize the content don t hesitate to meet with riley becca if you have questions or need assistance send the finalized content to dmc for feedback as needed upload the finalized content in the frontend dev team s preferred format and attach in this ticket reach out to becca riley for help uploading to gh if needed acceptance criteria content has been finalized final deliverable has been attached to this ticket ,1 16623261837.0,2021-06-03 06:10:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take care of missing system health services and programs and links that were missed story goal task in validating caregiver support for each national health program update all missing links programs and health services for visn visn visn acceptance,1 31470260371.0,2023-08-30 07:00:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint august september sprint goals complete review page x x planned issues need to add fsr enhancements downtime dependency update pt fe navigation content update pt fe streamlined waiver sw add new chapter level depends and structures fe sw update transform and helpers fe add streamlined waiver notification to va notify portal pt be send streamlined waiver notification for eligible requests be add an indicator for sw forms be sw create example submission objects for be pts fe ongoing maintenance bug fixes determine which external services have downtimes be use vcr for unit tests be blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished xx tbd xx points over issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 23140676910.0,2022-07-28 18:10:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, consolidate pages and surface important links issue description tasks review va design system debt and copay detail pages and determine whether the other va debt link can be more prominent on debt detail page link to copay page as copay rather than other va debt acceptance criteria create wireframes,1 14952211165.0,2021-01-26 15:16:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add fsr pdf download route controller method and service method issue description completed financial status report pdfs will be available to download for the veteran s records we need to expose that in the api tasks add controller method add route add service method add tests acceptance criteria generated pdfs will be available to download ,1 24679022316.0,2022-10-18 19:32:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,research adding debt history to debts index response issue description what details are necessary for understanding the specific work or request tracked by this issue when a debt is resolved paid off or closed it won t show up in the debt letter ui is there a data source to pull historical debts for a user can we build out a ui for users to see all historical debts not just active debts tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30693270401.0,2023-07-26 16:35:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,develop method to keep benefit payments from becoming stale issue description as it stands right now the fsr autofill data only uses benefit payments from within the past days this data is mocked in vets api mockdata repo based on each user we have many use cases where our team needs this data to be populated but it s a large dependency on our team to keep this updated every days we should look to either accept all recent payments regardless of recency window or develop an approach to automatically keep these days updated within the past days tasks settle on approach to accept benefit payments implement approach acceptance criteria fsr forms can populate with benefit payments without concern over manually updating dates how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27645261969.0,2023-03-10 22:12:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, re map our cypress tests description take a look at our existing cypress tests and existing user flows look for ways to re organize our tests to more closely follow user flows the result of this ticket should be a proposed re mapping of how our tests should look from that we can make new tickets maybe one for each flow path acceptance criteria new test outline for tests represents user flow ,1 20157210670.0,2022-02-09 17:33:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr processing status issue description as a veteran who has submitted an fsr i want a way to view the processing status of that request after it has been submitted and reviewed by the dmc acceptance criteria experience described above is available on the debt portal for veterans how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21638754709.0,2022-05-05 16:30:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,hlr nod switch to use va date web component description in both the higher level review hlr and notice of disagreement nod forms the simpledate react widget is being used on the add issue page this react widget needs to be replaced with the va date web component tasks replace react date widget with va date update tests as need definition of done all tasks complete all tests passing,1 12479243728.0,2020-05-29 17:54:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, incorporate feedback into the debt letters mvp wireflows issue description the design team is working on wireflows for the debt letters mvp work we ve presented to the team and need to into the next iteration note we will be presenting the current wireflows in the vsp design intent check in and to the dmc sme s the week of june tasks incorporate feedback into second iteration of wireflows acceptance criteria second iteration wireflows are completed in miro wireflows are documented in gh and linked in this ticket wireflows are presented to team stakeholders for feedback optional if feedback needs to be incorporated create a ticket to document that work ,1 13399042361.0,2020-09-03 13:58:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters uat round issue description in order to validate that the data we re receiving from the dmc matches what we re expecting on the frontend we need to conduct uat we didn t achieve our desired number of participants with current va debts during the last round so we ve extended to recruit more participants tasks moderate uat sessions from august september complete to keep track of tested use cases acceptance criteria all uat sessions have been completed the base use cases are tested the uat spreadsheet is completed ,1 19689334772.0,2022-01-12 04:00:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, validate vamc web pages that are showing as duplicate or obsoltete w o parrent story resources listingfrom cms tasks review pages provided by cms team that do not have parent menu link and are not published validate that the page does not have a parent menu item determine if it is obsolete a duplicate or possibly in development delete duplicates or obsolete pages list all pages that maybe in development or need attention acceptance criteria all obsolete pages are deleted and documented as such on list highlight pages that need further investigation,1 22356900444.0,2022-06-15 16:25:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review alt text on governance team platform website pages user story as a vfs team member i want platform website to be accessible and have accurate image descriptors intended audience vfs teams desired outcome accessible platform website pages due date n a description platform content team reviewed our pages and requested that we add alt text to each image chase added basic alt text in the interim to allow for publishing artifacts needing reviewed getting started collaboration cycle developer docs qa and accessibility testing accessibility testing request support from the va office tasks review alt text descriptions on platform website pages update alt text descriptions if needed acceptance criteria images on platform website are accessible and accurately described updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 23115555932.0,2022-07-27 16:20:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add introductory sentence to resources page user story as a vfs team member i want to know what the various collab cycle resources are so that i understand how best to use them if when i navigate to the platform website resources page assignee jimuhh peer reviewer cherylevans description platform content blocked the launch of our revised resources page because it does not include any introductory text per laucon we feel the document needs an introductory sentence to explain what these resources are for impacted artifacts tasks create a resources draft page add an introductory sentence explaining the various cc resources submit for peer review peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria the collaboration cycle resources page on platform website has an introductory sentence explaining what these resources are for how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 23536589740.0,2022-08-19 21:42:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create a github how to page for those that are not familiar with creating managing files and folders in github user story as a vfs team member i want to be able to create manage files and folders in github so that myself and others across all practice areas can access information stored in github as a new employee i want to be able to have a link to the how to document within platform orientation guidance assignee peer reviewer description what details are necessary for understanding the specific work or request tracked by this issue impacted artifacts tasks placeholder task peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria placeholder ac how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 23371771656.0,2022-08-10 20:35:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, your content doesn t use correct and consistent labels across links entry points navigation components and general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers jim ryan jimuhh ia for more information on how to interpret this ticket please refer to the guidance on platform website platform issue your content doesn t use correct and consistent labels across links entry points navigation components and issue details current va debt breadcrumb does not match specified in design system link screenshot or steps to recreate current va debt page va gov experience standard other references wcag sc aa platform recommendation change breadcrumb to match page or vice versa vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 24758715410.0,2022-10-21 20:38:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined portal enhancements product outline combined portal enhancement for future consideration definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 18723842538.0,2021-11-03 14:30:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, increase unit test coverage to description we need to ensure unit test coverage is at current coverage sits at note that there is a test coverage report that can be run value the higher the percentage of code that is covered by unit tests the more likely we will be to find issues early ,1 27716746690.0,2023-03-14 17:26:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate and repair efsr validation cypress test what happened efsr validation test has been commented out for flakiness needs investigating and fixing desired behavior test passes and is uncommented by ci acceptance criteria test passes how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 14915448715.0,2021-01-22 16:44:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr unauthenticated review page signature design issue description for the unauthenticated fsr we will need to make some adjustments to several pages that would normally be pre filled for authenticated users tasks alternative designs created for review sync designs to uxpin create frontend ticket acceptance criteria designs synced to uxpin and linked in this ticket frontend ticket created and linked in this ticket,1 24096892236.0,2022-09-19 19:36:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cfsr create ga logs for vba and vha submissions desired behavior google analytics recordings created individually for vba and vha depending on selection acceptance criteria ga recordevent used for vba and vha how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 13452045592.0,2020-09-08 21:21:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rollback saml post tracker the is only needed for debugging the ssoe integration project after diagnosing and resolving the drop in login success rates this additional tracker both the api endpoint issuing it and the js code invoking it can be ,1 19350673048.0,2021-12-15 15:21:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design component or pattern is not functioning or working as expected general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers mikki northuis mnorthuis ia platform issue design component or pattern is not functioning or working as expected issue details title tags are not reflecting the page on the copay balances page and copay bill details page link screenshot or steps to recreate va gov experience standard other references platform recommendation make title tag match on both pages vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 27055839462.0,2023-02-13 16:06:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove use of set output in github actions in vets website description set output is set to deprecate may this message is being seen in the workflows that use it the set output command is deprecated and will be disabled soon please upgrade to using environment files for more information see that github link explains the fix this was already implemented on content build in this background context set output is used widely across the org technical notes notes around work that is happening if applicable optional please delete if unused tasks what things need to happen acceptance criteria what are the specific things that must be true in order for this to be accepted reminders please attach your team label and any other appropriate label s operations devops and needs grooming will automatically be applied as part of the template please connect to an epic this will typically be done by the platform operations pm or tl ,1 16977883858.0,2021-06-30 03:36:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, validate that react widgets are enabled in top task pages story as a veteran i need to know the reaction alerts work so i can get the resources and information in each section goal enable react widgets to work properly task validate that all enable react widgets for pharmacy medical records and suicide prevention are enabled open reach widget on page confirm that call to action widget is enabled option you can also test all published pages and widgets by going to system url and page and test widget complete for the following visns and systems visn visn visn visn visn visn visn visn visn visn acceptance criteria all listed systems have been validated that react widgets are enabled ,1 30886186456.0,2023-08-03 22:07:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, disable all debt letters fetching based on feature flag issue description due to privacy concerns the debt letters endpoint has been disabled and a feature flag was created to prevent calls while it s down it seems as if there may still be some calls being made we should leverage the debt letters show letters vbms to disable any remaining calls while we sort out a solution tasks identify the debt letters calls still being made and disable them with the feature flag acceptance criteria no debt letters calls are being made while the feature flag is disabled how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24849045083.0,2022-10-26 18:20:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, uxpin text updates issue description user flow for streamlined waiver and wizard tasks update as noted on comments danielle may add additional comments through document text updates made acceptance criteria uxpin updated list of updates is created,1 26273612400.0,2023-01-06 19:31:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review and refactor form profile spec this spec uses so many contexts and helper methods it s hard to understand any given test discovered this when a new to ruby developer wanted to add a simple test and just created a let block but that didn t test anything one approach might be to make a form profiles directory in spec to parallel the one in models and just have tests for each form this may involve a lot of repeated spec in each of the files but that would increase clarity a lot ,1 16623241721.0,2021-06-03 06:08:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, swap out current policies page with new hardened policies page for visn and save as draft user story as a vha digital media web manager the national policies need to be hardened and available to national administrators only so national content should be changed from one source to all systems goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks archive current policies page replace with cloned page and add to menu for the following systems va alexandria health care va central arkansas health care va fayetteville arkansas health care va gulf coast health care va houston health care va jackson health care va shreveport health care va southeast louisiana health care complete the follow these steps for each system open policies page in edit mode a change name to policies old b remove menu by un checking menu box c save as archive open fargo or iowa city system and find policies page a select clone from tabs and select clone b go to edit and remove cloned c change governance to match new owner and related system d select menu enable check box e type in policies in name f select from drop down about va from system you are cloning to g copy visiting hours and or security information from original policies page security information will go into other policies section save new policies page as current status of system i e published or draft acceptance criteria all original policies pages have been archived and removed from menu all new policies pages are published and link is in menu at bottom of menu items ,1 25379729412.0,2022-11-21 16:35:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add link to child pages to touchpoints page user story as a vfs team member i want to be able to easily locate the touchpoint pages so that i can find the information i am looking for assignee peer reviewer description the includes a platform practice area table that specifies which practice areas are involved in which collab cycle touchpoints vfs pms have landed on this page and not recognized that it is the parent page of the individual touchpoint pages the purpose of this ticket is to add a child page display before the platform practice area table that lists the child pages ie touchpoint pages for easy reference impacted artifacts tasks placeholder task peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria placeholder ac how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 16061344024.0,2021-04-23 13:00:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unnecessary action selector and reducer tests we have a lot of unit tests that directly test action creators selectors and reducers these tests tend to need a lot of updating during refactoring and rarely catch bugs we should remove them and add rtl tests to cover any gaps we notice general process pick an action reducer or selector unit test file find existing rtl tests that cover the same area of the app verify that logic covered in chosen action reducer selector file is covered in related rtl tests add new rtl tests to cover any missed logic remove action reducer selector test file this will end up removing a lot of code please break this work into multiple prs ,1 23140590195.0,2022-07-28 18:05:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, consolidate pages and surface important links issue description tasks review content and user flow and assess whether pages can be consolidated review design and whether important statement information and a pay link can appear sooner to users acceptance criteria create user workflow create wireframes,1 27722401042.0,2023-03-14 21:52:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint march sprint goals continue fe development of fsr enhancements onward we go prepare for design feedback sessions with veterans finalize eks testing review identifiers to progress vbs needs for mcp notifications planned issues fsr enhancements experimental design process cards design remove combined fsr enhancements feature flag pts fe your va benefits enhancement pts fe mini summary card component pts fe spouse other income pts fe vehicle page enhancements fe utility bills enhancements fe discovery research co design feedback sessions research discovery research co design feedback sessions research finalize research plan on github research update uxpin fsr project to match sketch design other assets enhancement fe carry over update css to prevent text wrapping on varadio button component pts fe addressing platform disabled test fe contact information bug fe ongoing maintenance bug fixes find cause of not found veteran identifiers in iam be carry over gather list of potential empty submission veterans that have resubmitted fsrs be discovery work to change template names in dmc notifications verify debts controller endpoints in eks mcp notification add mock mvi responses for debt users be review two id types edipi and dfn with platform identity team be blocked issues currently tracking the following blocked issues expanding group design awaiting platform team expanding group deprecation blocked by identify affected veterans from non routed forms blocked by add signature date to fsr pdf sourcing pdf editor unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 24823144575.0,2022-10-25 18:11:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, your va benefits add total amount to card screen adjustments what happened desired behavior total amount summed correctly and displayed on card acceptance criteria total amount summed correctly and displayed on card how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 14918170166.0,2021-01-22 21:10:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,user survey request for request the medallia survey what this form is for use this template to request adding the medallia survey to your product read more about medallia how to request a survey description the online fsr form will allow veterans to fill out the financial status report online when requesting debt resolution from dmc see prototypes launch date mid february staging urls tbd next sprint production urls please provide production urls please leave the following blank acceptance criteria urls added qa d with the medallia survey ,1 13894272516.0,2020-10-19 14:29:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert appointment list class components to function components convert to function components and use hooks for any state or lifecycle behavior appointmentspage appointmentrequestlistitem pastappointmentslist facilitydirectionslink,1 16396333812.0,2021-05-18 00:30:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, return to visn and replace original policies page with new page story as a vha digital media manager i need the ability to update all site policies page with national content so i need a nationalized hardened policies page loaded at each site goal swap out current policies page with new hardened page to provide vha dm the ability to update national content task update the following sites with the new policies page in the following order open up current policies page and rename it policies old remove menu link and save page as archived clone policies page from va hudson valley scaffold the page to match the site you are cloning add menu link under about va for the following systems communicate within team to complete systems va amarillo health care va central texas health care va north texas health care va south texas health care va texas valley health care va el paso health care va west texas health care acceptance criteria all systems policies pages have been updated to new hardened page all old policies pages have been renamed and archived ,1 18526690168.0,2021-10-20 21:29:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team priorities sprint october nov sprint goals priorities update all iris mentions on debt tools establish designs for short term list loop improvements create research plan and conversation guide for uat create product profile and user guide for mcp iris mentions update mentions on debt tools fsr mvp release deliver fsr training video lay out short term improvements to fsr s list loops mcp mvp release configure sentry for failed endpoint calls update the overview page s facility contact information for proper semantic heading structure troubleshoot mcp staging errors add collection status to debt letter details mvp uat conversation guide design mcp mvp uat research plan details page content updates map error codes to use cases update links add vets api feature to download mcp pdfs and serve html defect screen readers medical co pays detail page of individual debt headings nested improperly mcp historical zero debt balances backend create forward proxies for each medical copay api environment create product profile user guide for mcp mcp notifications draft content for new copay bill notifications capacity planning pto holiday s denise leah scott justin craig becca riley troy sprint demo topic tbd presenter tbd tracking collab cycle events summary of status will be added for reference unplanned additions any unplanned additions will be added as they arise new backlog tasks throughout sprint team will add any newly identified tasks that need to be added to backlog ,1 13925968661.0,2020-10-21 17:36:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up code that converts test facility ids to real ids and vice versa we convert and to and in order to pull real facility data from the facilities api this is a little bit wonky in places because we don t convert the ids in the actual facility data to the test ids we should update the transformer to convert all ids to the test ids so that we can remove a lot of the code converting between the two in the actual app code and keep that code in the api and transform layers,1 17695660928.0,2021-08-24 15:01:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, verify income values issue description during uat with the veteran it was noticed that a few of the values generated on the fsr pdf under section ii income are not being calculated correctly and need to be updated field net monthly income less expenses value is being calculated wrong field payroll deductions other should be field federal state and local income taxes tasks update section ii income values acceptance criteria section ii income should be calculated correctly how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16104674544.0,2021-04-27 13:40:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor eligibility to work better with vaos service approach we should refactor the way the eligibility checks work in vaos to fit better with the vaos service approach of one call that returns both request limits and past visits info and doesn t include the actual request limit or past visit setting ac create patient service in services folder create function that returns eligibility data use info from vats calls to generate message with past visits value,1 31031958553.0,2023-08-10 13:02:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, testing issue description complete end to end testing in preparation for streamlined waiver launch ideal release date august tasks complete tests acceptance criteria we will launch with confidence that the streamlined waiver works as expected how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26338927518.0,2023-01-10 16:14:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,hook up mocked debt letters with vbms gem issue description we ve created the infrastructure to be able to deliver mocked debt letters but since this data is gathered via an external we ll need to do further work to leverage this mock data tasks develop workaround with vbms data to deliver mock debt letters instead of live staging data acceptance criteria the frontend is able to fetch mocked debt letter data how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15836061131.0,2021-04-06 18:48:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, empty state for when there are no debts issue description currently a veteran can technically access the fsr form when they do not have an active debt investigate our options and define the design direction for this does the fsr need to be available for authenticated veterans with no debts is there any way to prevent authenticated veterans with no debts from seeing them technically should this design mimic the unauthenticated debt selection screen tasks determine design direction for authenticated fsrs with no active debts document in gh comment in this ticket create a ticket for frontend acceptance criteria direction defined in gh and commented in this ticket ticket created for front end and linked ,1 23591060380.0,2022-08-23 15:13:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create record upon fsr submission issue description once model and db structure is in place we need the functionality to create an associated record when an fsr is submitted tasks call new record once fsr submission goes through acceptance criteria we are creating records in the db with the associated model for fsr submissions how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24557735027.0,2022-10-12 17:18:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,streamlined waiver wizard design user flow draft issue description user flow for streamlined waiver and wizard tasks create user flow for streamlined waiver create user flow for wizard acceptance criteria ,1 13995820800.0,2020-10-28 04:15:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, resolve all technical debt created by upgrades changes or new features in the design and architecture of vamc vamc product outline high level user story as a vamc team member i must assure that all recent systems and pages have been updated to reflect the most recent design and architectural updates changes and modifications vamc upgrade kpi met with this epic document and suggest ways to improve the system content and links help comments and overall flow and use of the experience in prod and staging for future use tasks see below list of stories ,1 13064371883.0,2020-07-30 17:59:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update stastd tags for evss submissions non retryable error messages graph we can see in the graph we are sending long statsd tags with user guids statsd tags should not be unique so we should update the error tags example tag suggested tag submit establishclaim serviceerror this should both help us bet better stats on the kinds of errors and help prometheus storage ,1 25567989170.0,2022-11-30 15:35:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr review page updates issue description discuss path forward for the fsr review page make updates to present to platform team tasks discuss path forward with team make updates to review page sections acceptance criteria upload in progress design for fsr review page ,1 28040665679.0,2023-03-28 18:15:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create unit test coverage report description we have coverage of unit tests reported see this ticket tasks run a report on our unit test coverage analyze report and make plan to increase coverage acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 20623240175.0,2022-03-07 19:35:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, enable cypress test technical task public websites skipped test due to failing in ci cd re enable them so we have full test coverage again expected behavior all debt letters test are enabled acceptance criteria fix and re enable debt letters cypress test ,1 27712179097.0,2023-03-14 14:52:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, kickoff meeting for streamlined waiver issue description review what we know about the streamlined waiver tasks review excel and pdf paths acceptance criteria kickoff meeting ,1 14900214679.0,2021-01-21 15:10:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, chapter check cypress test integrity against migration guide description the testing team recently rolled out an upgrade to cypress bumping the package version from to though there are no breaking changes to go through in preparation for cypress upgrades that would introduce breaking changes to ensure the chapter cypress tests do not break the build pipeline in jenkins we need to go through the guide and make any necessary updates to deprecated methods considerations migration guide tasks perform an audit of all chapter cypress tests update any methods recommended by the migration guide definition of done tests run properly pull request submitted ,1 16105168968.0,2021-04-27 14:10:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,two required parameters are not being permitted by the fsr controller s create action specs device vets api server browser chrome postman user account vets gov user gmail com steps to reproduce log into va gov locally work through the fsr form and submit it to the local vets api observe the vets api log output what happened required parameters ages of other dependents and amount can be paid toward debt are not being permitted by the fsr controller desired behavior required parameters ages of other dependents and amount can be paid toward debt must be permitted by the fsr controller,1 26942511394.0,2023-02-08 04:15:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,request to review eligibility information on the debt portal from benefits team what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with content support ia support please describe your need and provide any additional documents and or links that will help us help you if we need to add a react widget to a page be sure to provide the code here dmc stakeholders have asked us to review the eligibility information on the debt portal and suggest we better highlight details that explain the portal is only for veterans could you please review and provide some recommendations for stakeholder review email from jill anderson stated a question has been raise if we can add who can manage their va debt on the site one suggestion was to add something like what is shown below when i looked at the other areas of va gov many had a list of who can use the site second example i believe for consistency sake across the sites that may be the way your team would like to go but can we look into this and get a change executed as soon as possible email also included these two screenshots will this new product be released incrementally for instance of users initially yes no note if you checked yes we ll reach out to discuss details about the content in the react widget when do you expect to launch your product to of users this is a review of what is already live today please provide an estimated date so our team can create other relevant tickets supporting artifacts please provide supporting artifacts as available link to product outline link to or attach user flows link to prototype or mockups link to any epics issues that may be helpful will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date n a live today estimated staging review date content and ia work needed by do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name benefits team octo de product owner matt self product manager denise coveyduc designer megan gayle brie pipitone fe engineer andrew rodiek brandyn sullins product team slack channel benefits team next steps once you’ve submitted this ticket please post a link to this issue in the  slack channel and tag randi hecht if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 19561467301.0,2022-01-03 16:46:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up ccp route issue description now that we have fully moved to the rails engine and confirmed no other traffic is pointed to the endpoint we can clean up uneeded code for the ccp route tasks remove unneeded code supporting the deprecated ccp route acceptance criteria facility locator functionality is maintained unneeded code supporting the ccp route is no longer present ,1 14997241277.0,2021-01-29 16:38:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, defect debt letters heading level should only increase by one enter an issue title using the format brief description of the problem edit buttons need aria label for context add another user link will not receive keyboard focus heading levels should increase by one error messages should be more specific blue button on blue background does not have sufficient contrast ratio feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact jennifer user story or problem statement as a screen reader user i would like to hear headings in a proper nesting order according to their importance when i hear heading levels skipped it makes me wonder if i missed some important content details the axe browser plugin is reporting a few heading levels being nested improperly screen reader users overwhelmingly use headings to navigate through pages so nesting these appropriately has a big human impact i ve included a few screenshots with heading levels noted and recommend the team check out a to see the same left pane i m showing in the screen shots acceptance criteria heading level best practice issues no longer appear in the axe browser plugin footer best practice items may still appear but that s an issue outside the scope of this ticket no visual changes noted screen readers announce heading level nesting appropriately wcag or vendor guidance optional screenshots or trace logs ,1 24468566047.0,2022-10-07 17:20:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update vsp api engineering focused documentation to reflect error handling practices user story or problem statement as an engineer using vets api i need to understand our approach to error handling so i can consistently implement new services interactions goal all documentation related to api error handling is identified audited and refreshed objectives or key results this is meant to further vsp bets roe lights on data acceptance criteria documentation has clear answers to following questions when is it appropriate to use a custom error middleware what does the raise error middleware give us for free when building a service when building a controller when building a job what differs between faraday middleware faraday response middleware faraday request middleware how does breakers work to short circuit degraded services update how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 14705405345.0,2021-01-04 18:04:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, why do we reject read only pdfs issue description when veterans upload documents we reject locked pdfs and we are also purposefully rejecting read only pdfs do we need to reject them for real acceptance criteria ask stakeholders if there is a policy about not accepting read only pdfs we have code tests in place that make it seem like we are specifically disallowing read only pdfs if there is no policy against read only pdfs write a ticket for allowing read only pdfs and link it to this one ,1 15680884419.0,2021-03-25 03:59:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and correct invalid content in system health services for va hampton health care story as a veteran i need to have accurate and correct system health service description so i can quickly and correctly find where to go to get my correct health care support goal accurately update health services with approved content resources task hampton has a total of system health services to replace update all system health services with html code from health service library resource assure that intro line is correct e g care we provide at va hampton health care acceptance criteria all system health services have been replaced with correct html code and the intro has been replaced with care we provide at va hampton health care ,1 15039139895.0,2021-02-02 18:16:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, fix employment sections to only ask for add l employment if employment was indicated issue description your employment history your spouse’s employment history when ‘no’ is selected for ‘has your spouse been employed within the past two years ’ the next page is still ‘has your spouse had additional jobs in the past two years required ’ we should not be asking for additional jobs within the past years if they indicated that they have not been employed within the past years tasks hide followup question for additional employment if no employment was indicated in the initial question confirm behavior with designers can be via screen recording acceptance criteria behavior fixed behavior confirmed with designers,1 16598540897.0,2021-06-01 16:08:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, correct menu errors and corrections needed for vamc systems story as a veteran and editor i need to have consistent and standardized menu items that support urls so that the urls nesting and menus are easy to understand and comply with standards across the vamc sites goal remove all human created errors and document any outstanding technical improvements that can be implemented into future cloning task review all menus and links in each system and update or correct any errors for the following visn s visn visn visn visn visn vsin acceptance criteria all visns and systems have been reviewed and menus and links have been corrected any issues have been reported and either corrected or listed in a support ticket ,1 27405573031.0,2023-03-01 06:22:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research planning refinement issue description continue refining items needed for efsr research study tasks refine conversation guide refine research plan participant guidelines refined note taking guidelines refined acceptance criteria refined conversation guide refined research plan refined google spreadsheet and mural for note taking ,1 23371618185.0,2022-08-10 20:25:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits sprint priorities sprint july aug formerly debt resolution team sprint goals populated backlog with combined debt portal usability research findings and recommendations for future consideration design team product discovery and onboarding specifically related to the finanical status report va form and intended future enhancements project kickoff for the streamlined waiver project integration of medical copay selection options for veterans vha resolution option integration create unique identifier for fsr separate vha fsr submissions per station generate rails engine for debts api trailers campers and boats page redesign authentication for mcp notifications endpoint discovery work sprint deliverables list of deliverables completed during sprint tbd planned issues combined fsr debt and copay selections update generate rails engine for debts api pts trailers campers and boats page redesign pts benefit debt resolution option update pts separate vha fsr submissions per station pts add new database table for fsr submissions pts combined fsr cfsr design discovery pts mcp notification determine best authentication approach for mcp notifications endpoint pts streamlined waiver streamlined waiver project kickoff unplanned additions copay debt resolution option update capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr streamlined waiver github epic product outline use cases flow release plan architectural diagram use cases usability testing n a dates product guide mcp product guide kickoff design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 16990588099.0,2021-06-30 19:52:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt portal add content for debt issue description add additional content for debt tasks add the following language for debts if you are a student who received a letter regarding a tuition debt please note that a deduction code identifies a debt assigned to your educational institution please communicate with your educational institution prior to making payment on their behalf in order to avoid potential duplicate billing acceptance criteria the content has been updated in alignment with the provided prototype ui has been reviewed by a designer ,1 27550916245.0,2023-03-07 14:53:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, spouse other income issue description update spouse other income page s to follow veteran other income page tasks add the following pages other income checklist other income input list add update unit tests for new page s add update end to end tests for new page s acceptance criteria new pages match design and are hidden behind efsr feature flag how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26513460826.0,2023-01-18 18:53:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the dropdown date component with the experimental design system s input date component issue description a new text date input component is being added to the experimental design system we should update the dropdown date components in the fsr to the new component so we can test it as part of the combined vha vba fsr project information about the component can be found in ticket tasks update the dropdown date components in the fsr with the text input date component acceptance criteria the fsr s uxpin has been updated and linked in this ticket ,1 21192293737.0,2022-04-08 18:55:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update platform page research and design left navigation user story as a vfs teammate i want to easily find the right page on platform so that i have quick access to the information that s important to me as a platform team member i want to be able to easily navigate to pages relevant for my practice area when i m supplying links to answer questions bet as a vfs teammate i want to set the the different practice areas on the left side navigation for the research and design section of platform so i can more easily find information needed at a given time as a new teammate it would be easier to navigate by practice area to discover what i need to know for each intended audience vfs desired outcome easier to find information and to navigate on platform s research and design section due date description current state on the section of platform the left side navigation mostly links research pages since the only way to find much of the design ia accessibility and qa information is to scroll down that section s home page it can take additional effort to find needed information also since those links are research heavy it makes this look like a section only for research suggesting change have left nav include a link to a page for each practice area this will allow each practice area to better organize their information and will be easier for vfs members to find needed information additional background for initiative additional background for initiative additional background for initiative new artifacts artifacts potentially confirmed needing updates research and design tasks consider best way to reorganize left nav could include card sorting task at least for governance team possibly including vfs team members as well acceptance criteria updated left nav organization for insert page name confluence document has been updated per guidance insert page name confluence document has been created per guidance insert github template github template has been created per guidance insert github template github template has been updated per guidance insert platform website page on platform website has been updated per guidance insert platform website page on platform website has been created per guidance updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 17935533363.0,2021-09-10 14:52:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add natural disaster messaging to debt landing page public websites banner intake request form description dmc has requested a natural disaster message be added to debt landing page what do you need url timing asap stakeholders leahkeeler jill anderson ,1 23612988199.0,2022-08-24 13:49:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, text updates to enhanced fsr uxpin issue description enhanced fsr research plan and conversation guide draft tasks make updates to uxpin acceptance criteria text updates made to uxpin,1 14665356052.0,2020-12-29 14:04:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres update installment contracts and other debts issue description updates to the installment contracts and other debts repayments section refer to the mock tasks add yes no widgets set required fields styling and formatting to match mock acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16888437672.0,2021-06-23 05:50:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, confirm and resolve system and facility health services for the below health services that did not match in migration story as a veteran i need to have accurate system and facility health services so i can confirm the correct location facility to complete my health care journey task review the following facility health services that did not have a matching system health service in the associated systeam and determine if a system health service needs to be added then add this facility health services in support of the facilyt listed vha specialty care john d dingell department of veterans affairs medical center specialty care at va detroit health care va detroit health care vha nutrition food and dietary care mcallen va clinic nutrition food and dietary care at va texas valley health care va texas valley health care vha neurology chalmers p wylie veterans outpatient clinic neurology at va central ohio health care va central ohio health care acceptance criteria system and facility health services have been either confirmed not to exist and documented in playbook if system and facility belong to system they have been added to system and a facility health service is then in place and updated ,1 16597674985.0,2021-06-01 15:12:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, move financial overview header into detail box move the financial overview header into the blue detail box on the resolution selection pages as seen here ,1 15831696267.0,2021-04-06 13:53:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,accessibility feedback for staging review debt resolution online fsr form feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact angela form josh wizard ,1 16617162295.0,2021-06-02 18:16:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update learn more about the va appeals process link in wizard issue description feedback from ia in the wizard alerts after selecting i disagree with the va decision the link label to learn more about the va appeals process should reference the new label for appeals decision reviews not fixing this will lead to user confusion due to a disconnect between the link label and the page they land on change the learn more about the va appeals process link to say learn more about decision reviews and appeals tasks change the learn more about the va appeals process link to say learn more about decision reviews and appeals acceptance criteria link text updated ,1 15885541693.0,2021-04-09 20:45:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unauth mock data issue description mock data was added to the initial state for unauth users and should be removed we also need to remove the functionality to allow unauth users to start the form without signing in more details can be found on this tasks remove mocks from initialdata found in form js remove link for start your application without signing in acceptance criteria unauth users should not so show any fields pre populated start your application without signing in link should be disabled how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16606088891.0,2021-06-02 04:07:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, swap out current suicide page with newly cloned suicide page from sot user story as a vha digital media web manager the national policies need to be hardened and available to national administrators only so national content should be changed from one source to all systems goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks rename current suicide prevention page replace with cloned page link system health service to new page and publish archive old suicide page complete the below instructions for all systems in the following visn visn visn visn visn visn visn visn visn complete the follow these steps for each system open suicide prevention page in edit mode a change name to suicide prevention old b remove menu by un checking menu box c save as published open albany system and find suicide prevention page a select clone from tabs and select clone b go to edit and remove cloned c change governance to match new owner and related system d select menu disable check box for enable e assure suicide prevention is listed in name field f select from drop down health services to new system g copy the node number from the url e g node see below g save as draft go to suicide prevention system health services a remove link from hyperlink to suicide prevention page b highlight the link content select link and use the node number saved earlier to link to the new page go back to suicide prevention old page a save as archive acceptance criteria all original suicide prevention pages have been archived and removed from menu all new suicide prevention pages are published and link from system health services are working correctly no broken links ,1 19730201543.0,2022-01-14 01:02:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,collab cycle fsr kick off design intent analytics ia staging ,1 15799053773.0,2021-04-02 20:01:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr remove days from confirmation page after much discussion with dmc we need to remove days from confirm page they have no visibility into timelines and this would be misleading in the future when they implement sf we can look into integrating the systems to expose this information on va gov cc daniellethierryusdsva for visibility provide language modification to fe craig change the content to reflect new language ,1 31844459638.0,2023-09-14 18:46:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,vbms letter audit issue description work related to vbms letter audit acceptance criteria vbms letter audit has concluded and all aspects are complete how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24508816509.0,2022-10-10 19:07:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,edit and reorganize the vfs team tasks to complete in staging review feedback template user story as a vfs team member i want to know what actions to take post staging review so that i can ensure i am doing everything that is expected of me assignee peer reviewer cherylevans description at the short form staging review there were questions from the vfs teams about the feedback reported by governance team specifically the vfs team member did not believe the issue documented was the responsibility of her team to fix the purpose of this ticket is to provide additional guidance in the staging review feedback template to the vfs team so they know what action to take if they believe the ticket is incorrectly assigned the secondary purpose of this ticket is to restructure the vfs team tasks to complete from a checklist to a bulleted list the heading should also be updated to better reflect what vfs teams need to know as it is not necessarily a task list for them to take action on impacted artifacts draftingtemplate google sheet collab cycle feedback for staging review gh template tasks collab cycle feedback for staging review gh template rename heading from vfs team tasks to complete to vfs guidance or whatever we think is appropriate i would just like to emphasize that these aren t required tasks but steps they should take if there s uncertainty change check boxes to bullets split close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket into bullets add a bullet if you do not believe that this staging review issue ticket is the responsibility of your team comment below providing an explanation and who you believe is responsible please tag the point of contact reviewers governance team will research and will follow up again or whatever we think is appropriate add a bullet governance team has been advised by our octo leadership to flag any issue we find whether it is in scope for your iteration or not it is possible that this issue may be out of scope for your iteration however it is still your responsibility to resolve the issue some feedback provided may be out of scope for your iteration of the product however platform s octo leadership has stated that all identified issues need to be documented and it is still your responsibility to resolve the issue wordsmith all bullets should be written as you and not the vfs team reorder the bullets as appropriate draftingtemplate google sheet the same changes are made to the draftingtemplate note please make changes to the collab cycle feedback for staging review gh template first have them peer reviewed and then shira will make the necessary changes to the draftingtemplate acceptance criteria vfs teams know how to escalate concerns with the identified staging review issue vfs teams are no longer asked to check off tasks they have or have not completed how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 14952755145.0,2021-01-26 15:53:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr update review page issue description update review page according to mock tasks review application confirmation acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15296685673.0,2021-02-24 07:16:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and correct invalid content in system health services for va salem health care story as a veteran i need to have accurate and correct system health service description so i can quickly and correctly find where to go to get my correct health care support goal accurately update health services with approved content resources task salem has a total of system health services to replace update all system health services with html code from health service library resource assure that intro line is correct e g care we provide at va salem health care acceptance criteria all system health services have been replaced with correct html code and the intro has been replaced with care we provide at va salem health care ,1 17020627101.0,2021-07-02 18:26:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove pre fill transformer issue description a prefill transformer was added when we created fsr but is no longer needed and should be removed tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16773317133.0,2021-06-14 17:26:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add an additional info component for your dependents screens issue description the fsr s usability study highlighted that veterans don t know why they need to include information about their dependents the content and design team collaborated on content for an additional info component to provide more information about why we re asking for dependent info the content why do i need to include my dependents we want to make sure we fully understand your financial situation if you have dependents we ask for number of dependents as well as their ages this allows us to make a more informed decision regarding your request tasks add an additional info component and the corresponding the following pages do you have any dependents page enter each dependent s age page acceptance criteria the fsr s ui has been updated to match the provided uxpin designs content the ui changes have been reviewed by a designer ,1 14952213712.0,2021-01-26 15:17:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add bad request error handling for fsr submissions issue description errors aren t being handled will need to add error handling for submissions that are malformed tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23368139012.0,2022-08-10 17:10:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, determine source of gmt threshold data and appropriate access points issue description as part of the streamlined waiver portion of the combined fsr product we will need access to gmt threshold data to calculate initial approval tasks meet with poc for ownership of data discover current access determine best location for future voda access acceptance criteria we can move forward with acquiring gmt data and sourcing it how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14146899270.0,2020-11-10 19:56:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rewrite preferreddatepage tests in react testing library we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos make sure to use the default exported component in the tests and you should remove the old export of the unconnected component,1 14108487558.0,2020-11-06 17:54:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt portal fallback messaging for unassigned diary codes issue description in the case of an unassigned diary code being sent back to us we ll need to have a fallback status and next step or alert tasks draft fallback messaging pattern for diary codes that do not have content draft and review with content create fe ticket to complete work acceptance criteria fe ticket created and linked in this ticket ,1 26195785927.0,2023-01-03 13:20:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined fsr redirects and content updates from benefits team what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with content support ia support please describe your need and provide any additional documents and or links that will help us help you if we need to add a react widget to a page be sure to provide the code here after discussion with danielle we agree we will set up redirect for the copay page at the point we go live estimated september at that time we will also update content pages future discussion is needed regarding the ia changes and wizard updates danielle and mikki will connect and then we will meet as a group to discuss future changes needed thanks for a great collaboration will this new product be released incrementally for instance of users initially yes no note if you checked yes we ll reach out to discuss details about the content in the react widget when do you expect to launch your product to of users please provide an estimated date so our team can create other relevant tickets phased roll out plan september september september supporting artifacts please provide supporting artifacts as available link to product outline link to or attach user flows link to prototype or mockups link to any epics issues that may be helpful will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date september estimated staging review date n a content and ia work needed by september do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name benefits team octo de product owner matt self product manager denise coveyduc designer megan gayle brie pipitone fe engineer andrew rodiek brandyn sullins product team slack channel benefits team next steps once you’ve submitted this ticket please post a link to this issue in the slack channel and tag randi hecht if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 14530754741.0,2020-12-14 19:44:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, cst and we have two different ways to upload files issue description we now how two ways to send files into evss but we don t reuse the same code this is a maintenance issue and adds to complexity of figuring out file upload bugs file size bugs password protection issues acceptance criteria consider using more shared code to reduce the issues how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23922591980.0,2022-09-09 18:30:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, sentry error for numeric input fix issue description sentry is picking up on an issue where a replaceall method is acting on an undefined object typeerror undefined is not an object evaluating e replaceall this is most likely due to a fix that was put in place to handle commas in number input fields tasks update transform function so replaceall has null checks to avoid the error acceptance criteria no longer receiving errors when values are null empty how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27091500979.0,2023-02-14 21:30:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr total monthly expenses not being calculated correctly issue description when a veteran is filling out the expenses portion of the fsr form the summation of these expenses for field is not being calculated correctly it appears that the value is only considering utilities and other living expenses and not taking into account rent or food tasks identify reason for miscalculation include all expenses for total expense column acceptance criteria a fix has been added to correctly calculate the monthly expenses communicate with stakeholder teams how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16487013081.0,2021-05-24 19:36:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,stop calling get messaging health folders messages if we don t need to investigate why my va calls the get messaging health folders messages endpoint in addition to the get messaging health folders endpoint on staging with user monday may pm the call to get messaging health folders returns the following json data id type folders attributes folderid name inbox count unreadcount systemfolder false links self given that the unreadcount exists and all we show on the my va dashboard is the number of unread messages i don t think we need to make the call to get messaging health folders messages which returns json data id type messages attributes messageid category test results subject your lab results body null attachment true sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category covid subject covid inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category medications subject medication inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category appointments subject your upcoming appointment body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category other subject general inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category other subject general inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category other subject general inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category other subject general inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category other subject general inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self id type messages attributes messageid category other subject general inquiry body null attachment false sentdate senderid sendername ratana narin recipientid recipientname freeman melvin v readreceipt read links self links self first prev null next last meta sort sentdate desc pagination currentpage perpage totalpages totalentries todo confirm that we do not need to make a call to get data about individual messages and stop making that call,1 27259495836.0,2023-02-22 13:58:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, installment contract enhancements issue description create new installment contract pages that match yes no input page mini summary tasks create necessary pages yes no input mini summary update tests unit update maximals minimals as necessary acceptance criteria new pages added and match design all tests passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13895489380.0,2020-10-19 15:55:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres conversation guide issue description once concluding preliminary research on the fsr va form the design team needs to write conversation guide s for the sme interviews tasks write at least one conversation guide to be used for dmc sme interviews additional conversation guides may be needed depending on interviewees roles acceptance criteria conversation guide s is uploaded to gh and linked in this ticket ,1 15287920139.0,2021-02-23 16:17:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, form submission content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to the form s confirmation screen tasks incorporate the content changes on pages in the provided document into the fsr s staging environment it may be easier to reference the uxpin for the content updates reach out to the design team with any questions acceptance criteria the form s confirmation screen changes have been incorporated into the fsr s staging environment work has been checked off in the ,1 30787775580.0,2023-07-31 14:16:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add an indicator for sw forms issue description this ticket is the result of discovery performed in as we approach the launch of the streamlined waiver we need to make adjustments to the backend to accommodate the change in fsr form schema anticipated changes adjust financial status reports controller so that fsr form will permit a boolean streamlined attribute at the root level create a new form schema based on info provided by fe team to validate sw forms based on lib debt management center schemas fsr json edit financialstatusreportservice validate form schema to recognize a sw based on the new streamlined attribute and validate against the appropriate schema confirm that the current schema will consider a form valid if it contains the streamlined attribute edit form data somewhere before pdffill filler fill ancillary form so that form mentions streamlined waiver acceptance criteria no change to fsr submitted without sw identifier fsr submitted without sw identifier can submit a sw fsr fsr submitted with sw mentions sw on pdf element ,1 16602171719.0,2021-06-01 21:09:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr moderated uat in order to qa the online fsr in production we need to have veterans who can log into va gov log in fill out and submit fsr form number of veterans veteran criteria ,1 13628914090.0,2020-09-24 14:29:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove previous functions in flow files in favor of holding data in state currently we have next and previous functions for each entry in our form flow files newappointmentflow and newexpresscarerequestflow we ve had several bugs where the previous logic wasn t in sync with the next logic and going back through the form sent users to the incorrect page a different approach for this would be to hold the previous page for each page in our redux state essentially create an object map in the redux state called previouspages each time a user clicks a continue button after the next pagekey is found an entry is created in previouspages for the new pagekey with a value set to the previous page whenever a user clicks back we look up the current pagekey in previouspages and use the pagekey from that object to choose the page to go back to so for example if i m on vafacility and the next page is clinicinfo then when i click continue on vafacility we would add clinicinfo to previouspages and set the value to vafacility ,1 17019132861.0,2021-07-02 16:03:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add unit test for src site layouts vet center locations list drupal liquid this template needs a unit test ,1 16623262251.0,2021-06-03 06:10:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, resolve tech debt of covid vaccine detail pages for all systems and link system hs story as a veteran i need to know the latest information and guidance regarding covid vaccines so i will know how when and where to schedule and get my covid vaccine goal provide a nationalized local detail page for all sites task update the source of truth to include covid detail page clone all sites previously created with the covid detail page and align this with the system update link in covid system health service to the new covid vaccines page locally visn visn visn visn visn visn acceptance criteria update the source of truth to include covid detail page all systems have a cloned and updated covid detail page and align this with the system link in covid system health service links to new covid vaccines page locally ,1 13108508185.0,2020-08-04 16:57:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analytics implementation or qa support for debt letters mvp google analytics implementation or qa request please note the mvp release will only be one page listing out the debt summary and debt letters the second iteration will provide a detail page with debt details and status what this form is for more information use this template to request google tag manager and google analytics implementation or qa for your product please fill out all brackets please see the following information for implementation timeline new teams implementation will usually be completed in sprints sprint discovery orientation sprint fe implementation sprint tagging implementation sprint qa all other teams implementation will usually be completed in sprints sprint discovery and fe implementation sprint tagging implementation and qa for more information please check out the an example of a completed request template can be found a fully completed issue can help speed up the implementation process description is this request for google analytics implementation or qa implementation who is this request for debt letters mvp leah keeler leahkeeler provide any relevant contact information and link this issue to the insights team on the dsva slack channel vfs platform support what team project is this work for debt letters provide the domain where google analytics needs to be implemented i e identify if pii is passed in url or title tag please provide any upcoming deadlines or important milestones no launch date set yet typical website interactions to track total visits bounce rate number of debt letters viewed downloaded sample users when authentication is required do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository test users to replicate the event do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository • vets gov user gmail com greg • vets gov user gmail com mark • vets gov user gmail com pauline • vets gov user gmail com jerry • vets gov user gmail com eddie certain conditions responses that need to be reviewed additional comments the debt letters download page has not been created yet please leave the following blank acceptance criteria qa has been completed vfs team completes brief survey definition of done all appropriate issue tagging is completed all ac completed ,1 22339164737.0,2022-06-14 21:54:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reserach appropriate storage option for generated fsr pdfs issue description we need a way to save the pdf files we generate for fsrs so they can be fetched tasks look for best storage options or pre existing file storage solutions acceptance criteria we know where to store fsr pdfs how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 17148709805.0,2021-07-13 17:32:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create migration plan for dmc credential changes description a c create the plan of action for conducting the production credential migration with limited website downtime and monitoring create the tickets needed to do the migration,1 22107240961.0,2022-06-01 17:58:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add indicator to differentiate between vba and vha debts issue description need a method to differentiate between the two different types of debts a veteran could have and this can be done by adding a new enum data point to separate the two or both tasks find appropriate location for data add static values and field acceptance criteria we can use the indicator to differentiate between the two debts how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16674103854.0,2021-06-07 14:18:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consider using moment ll formatting technial task during the code review of this that we were using abbreviated time formatting for accessibility purposes we might want to consider replacing moment time formats for the long form ll version so the readout for a screen reader is more descriptive and easier to understand ll format month name day of month year september expected behavior time is formatted correctly acceptance criteria rather than time being abbreviated like sept have the month spelled out like september ,1 16109933695.0,2021-04-27 19:42:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in preferreddatepage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos new appointment components preferreddatepage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 23114652831.0,2022-07-27 15:37:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits sprint priorities sprint june july formerly debt resolution team sprint goals complete user research sessions summarize and synthesize user research session findings alerts – qa test cases update icons approved letter codes resolve usability feedback combined debt portal technical refinement including debt ids and mobile styling fixes prepare for combined debt portal launch datadog backend discovery medical copay notification discovery sprint deliverables list of deliverables completed during sprint topline summary of research findings usability research session notes spreadsheet planned issues combined debt portal update existing debt letters widget for cdp and investigate staging only page pts cdp users not reaching correct state pts implement not enrolled in healthcare alert pts open privacy and security review for cdp pts cdp missing debt letter history download debt letters sections pts incorporate accessibility feedback from the midpoint review check details link pts datadog discovery pts usability sessions pts usability study synthesis pts combined fsr parse delimiter characters out of fsr json pts integrate fsr submission with vbs endpoint pts mcp notification research best approach for implementing mcp notifications pts move and test setting mock value for debts to feature flag pts unplanned additions combined debt portal content styling anomalies cypress tests failing pts intro discussion updates to icons in the cards status sections pts staging combined debt portal current copay balances how to dispute section links go to prod combine debt portal copay bills overview details mismatch pts combined debt portal overview page debt error for test user pt migrating url to manage va debt pts a user flow has repetitive or redundant steps capacity planning pto holiday s denise scott brandyn andrew megan july holiday points planned points accomplished points over issues points over issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr streamlined waiver github epic product outline use cases flow release plan architectural diagram use cases usability testing n a dates product guide mcp product guide kickoff design intent midpoint review content ia request analytics request required contact center review research plan review required staging review staging url staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes ,1 11353196092.0,2020-01-24 15:07:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,better define functionality of calendar widget we should put some thought into what generic functionality the calendar widget should have and what s ok to make specific to our needs there are some attempts in the current code to make it generic but since we didn t have a clear set of general needs to meet it hasn t been something we re able to maintain consistently this will help us come up with a clear component interface and then we can refactor to make the code simpler ,1 13894306363.0,2020-10-19 14:32:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert class components for typeof pages to function components convert these components to function components and use hooks for any state and lifecycle behavior typeofaudiologycarepage typeofeyecarepage typeoffacilitypage typeofsleepcarepage typeofvisitpage typeofcarepage,1 31144216900.0,2023-08-16 04:29:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,qa standards debt resolution financial status report fsr general information vfs team name debt resolution vfs product name financial status report fsr vfs feature name streamlined waiver point of contact reviewers ian harrison it harrison qa regression test plan standard has been met standard has not been met explanation of failure to meet standard if applicable no regression test plan included test plan standard has been met standard has not been met explanation of failure to meet standard if applicable no test plan included traceability reports standard has been met standard has not been met explanation of failure to meet standard if applicable no traceability reports included test participation standard has been met standard has not been met explanation of failure to meet standard if applicable unit test coverage standard has been met standard has not been met explanation of failure to meet standard if applicable no unit test coverage included vfs guidance close the ticket when your product owner determines that you have sufficiently met the qa standards if your team has additional questions or needs platform help validating the issue please comment on the ticket platform directions update issue title to be of the form qa standards vfs team vfs product add the vfs team product name and feature name add your name practice area and gh handle under point of contact reviewers complete the qa standards section making sure to include an explanation of failure to meet standard for every standard the product does not meet link to the collaboration cycle request epic add assignees vfs pm yourself optional add labels vfs team label vfs product label qa standards label launch blocking label if the product has failed to meet a required qa standard ,1 21885439616.0,2022-05-19 18:08:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,address having two locations for zoom use in research user story as a researcher i want clear and updated guidance for using zoom on platform so i have a single source of truth intended audience vfs desired outcome add updated guidance to platform due date description there is that hasn t been marked as deprecated there is also a information should be double check to ensure all needed guidance was migrated to platform then the gh page should be marked as deprecated new artifacts artifacts needing updates tasks compare information on the gh and platform page update the platform page if any guidance is missing mark the gh page as deprecated acceptance criteria github template has been marked as deprecated platform website has been updated if needed updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 26658439133.0,2023-01-25 18:49:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,extract external service sentry tag to base class user story as a vsp engineer i need consistent sentry tagging of external services so i can more easily find errors related to a given external service goal any service added to the vets api using the base connection class is be automatically tagged if the child class implements the service name method notes nomethoderror raised if service name isn t there or default to class name decision required here acceptance criteria spec s are added to enforce the tag is added to external services all requests to external services are tagged with external service by default ,1 26052993953.0,2022-12-22 20:54:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, intake fsr s find a form updated content review from the debt resolution team why you re here content support for unauthenticated static va gov pages apps or tools other writing or editing requests note these requests are handled by the sitewide content team how to submit your request complete each area of this intake form that applies to your team s needs provide as much detail as you can so we can fully understand your request determine if this request is for content only public website engineering support both content pw eng spt post a link to this issue in the appropriate channel for engineering only requests and in slack tag brianalloyd ncksllvn and kelsonic content only support in slack tag rlhecht in situations where both are needed post to public websites and in slack tag brianalloyd ncksllvn kelsonic and rlhecht for awareness if noted in the guidance below please schedule any relevant meetings when to submit your request content requests type of need when to submit your request new unauthenticated va gov page such as a static landing page to support a new app tool at project kickoff updates to an existing unauthenticated va gov page for significant updates like consolidating pages or reworking page content at project kickoff for smaller updates like adding a section of new info at least full sprint in advance so we can work it into our next sprint writing support for app tool at project kickoff editing support for app tool or other writing editing support for multiple screens at least full sprint in advance so we can work it into our next sprint for very small needs like an error message at least days in advance engineering requests please submit all engineering requests at least full sprint in advance so we can work it into our next sprint about your app tool functionality is this request related to a va gov tool if yes provide a brief description of the tool or functionality the financial status report is launching soon so we d like to update the content on provide links to any available collateral product briefs outlines wireframes prototypes user research synthesis about your support needs please select all that apply and follow related guidance content new unauthenticated va gov page additional info please provide any details not covered above about what app tool other need this new page will support schedule a meeting please schedule a meeting with rlhecht and brianalloyd to kick off this work we ll work with your team and the vsp ia resource to determine how best to accommodate this new page updates to an existing unauthenticated va gov page what url s do we need to review or update are updates for a small section of copy if yes please tell us what new info we need to consider and what if anything it s replacing we d like to add sections to the fsr s results page in alignment with i ve attached a word doc with proposed content below are updates related to usability testing or analytics if yes please provide details writing support for new app tool additional info please provide any details not covered above about what app tool other need this new page will support schedule a meeting please schedule a meeting with rlhecht and brianalloyd to kick off this work we ll work with your team and the vsp content resource to determine how best to support your needs editing support for app tool note we ll work with your team and the vsp content resource to determine how best to support your needs url where draft content appears if available word document with draft content if needed note if you have more than paragraphs of text to edit please provide text in a word doc design context example is this content in a user flow an in line error message tool tip field label this content is for updating to provide more context about the form in alignment with other find a form pages and update the resources links to more relevant pages scope how many screens or messages other i ve synced with the decision tools team so we re all looped in on this work i m happy to hop on a call to chat about the draft content desired target implementation date what s the eta for the app tool launch or the date when you need this request completed our team s capacity will determine which sprint the work falls into the eta for the fsr s launch is this sprint but all debt is currently on hold due to covid so we don t project an influx of fsr submissions until fall we d like to get this content up asap in accordance with with the public website team s schedule note as a best practice pw does not release new products over weekends or holidays please plan accordingly about your team team name debt resolution depo product owner matthew self product manager leah keeler designer riley orr becca walsh fe engineer craig wheeler justin linn product team slack channel vsa debt public websites internal use acceptance criteria convert this request into a zenhub epic follow up with requestor to address any lingering questions concerns create epic tickets as needed for the public websites team to implement definition of done request ticket is closed and implementation tickets created as needed ,1 19912610327.0,2022-01-25 18:45:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reevaluate octo invitees at collaboration cycle reviews issue description currently there is not consistency in which octo leads and or other team members are invited to which collaboration cycle touchpoints including only design intent midpoint review and staging review the purpose of this ticket is to evaluate currently who is invited to which reviews confirm that information with the individual and update invites per their request individuals to include martha wilkes beth potts danielle thierry mikki northuis randi hecht shawna hein vsa only kevin hoffman since he s ryan s backfill for now rachael roueche tasks confirm which events the above folks are currently invited to message them via slack stating that these are the events they re currently included in and ask if they d like to keep it as is remove touchpoints and or add touchpoints update the moderator responsibilities docs for design intent midpoint review and staging review to reflect the changes potentially add certain folks to the distribution lists acceptance criteria platform includes the right individuals at the appropriate collaboration cycle touchpoint meetings how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18110795472.0,2021-09-23 03:26:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update lgbtq and suicide pages with new updates from sot visn user story as a vha digital media web manager the national changes need to be implemented prior to dual state or full production launches so the systems are updated adequetly prior to the redirect goal remove tech debt prior to full production resources tools documentation tbd tasks update lgbt with lgbtq and suicide pages with new content and organize page correctly update suicide pages with correct format order and new content change out lgbt with newly authorized lgbtq in locations provided by content complete for the following locations va lexington health care va louisville health care va memphis health care va mountain home health care va tennessee valley health care acceptance criteria suicide pages are updated and if caregiver is not listed on page it is reported in support channel lgbtq pages are updated and if caregiver is not listed on page it is reported in support channel ,1 15613680302.0,2021-03-19 16:46:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove appeals service alert from vsp ops pageduty config issue description ops member and a front end engineer were pinged at eastern over the weekend for appeals service being down this was later discovered to be some planned maintenance but we likely should not have been woken up for this alert we should remove it from our alerting system pagerduty configurations perhaps is relevant tasks remove appeals service alert acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18950829137.0,2021-11-18 15:01:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and provide feedback of design and content of proposed clc dom facility page story resource task review page in the following areas content design and flow does it work add to word document summary pull all content into word document and turn on review track changes provide proposed suggestions acceptance criteria preview page has been reviewed for design flow and content summary and review are provided in a word document and saved in content folder on vamc sharepoint ,1 14001889684.0,2020-10-28 14:10:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr wireflows iteration issue description once the team completes the fsr ideation session the design team will create wireflows of the fsr va form prior to prototyping tasks create wireflows for the fsr present wireflows to the team and confirm with development team that the ui is technically feasible with the form system acceptance criteria wireflows are uploaded to gh and linked to this ticket wireflows are presented to the team and any feedback is documented in gh optional if feedback needs to be incorporated a separate ticket is created to incorporate that work ,1 19913514044.0,2022-01-25 19:45:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the fsr s contact information section to align with design system patterns issue description the experimental design system has a new pattern for editing contact information within forms that we should utilize in the fsr s second iteration where to find the pattern sign into hlr with tasks update fsr s contact info page to align with the provided pattern acceptance criteria the ui has been updated and linked in this ticket ,1 15086751574.0,2021-02-05 20:52:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, check cypress test integrity against migration guide description the testing team recently rolled out an upgrade to cypress bumping the package version from to though there are no breaking changes to go through in preparation for cypress upgrades that would introduce breaking changes to ensure the cypress tests do not break the build pipeline in jenkins we need to go through the guide and make any necessary updates to deprecated methods considerations migration guide tasks perform an audit of all cypress tests update any methods recommended by the migration guide definition of done tests run properly pull request submitted ,1 15836086042.0,2021-04-06 18:50:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters statuses and next steps draft issue description the categorized status codes need to be translated into statuses and next steps that will be displayed in the ui tasks create an excel sheet mapping the diary codes to statuses draft the statuses and next steps send the drafted statuses and next steps to the dmc team for review acceptance criteria an excel sheet mapping the diary codes to statuses is uploaded to gh and linked to this ticket a draft of the statuses and next steps is uploaded to gh and linked to this ticket the statuses and next steps draft is sent to the dmc team for review ,1 22834857702.0,2022-07-12 15:45:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, deprecate check in experience no demographics confirmation for unverified enabled tasks deprecate check in experience no demographics confirmation for unverified enabled feature flag confirm feature flag not used in fe code base update rspecs acceptance criteria deployed to staging tested on staging ,1 11580241666.0,2020-02-21 19:42:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert review instances to use the brd base os role user story or problem statement right now the review instance provisioning happens using the old roles base os role for getting all of the baseline os stuff done this role is no longer used by anything else and should be using the ansible build roles common base os role same name slightly different one way to validate that you got the right role is if the instance has the standard government motd thing as far as i can tell the old role never had that so it s a good sanity check to make sure you got the right thing once review instances are using the new base os role we should be able to delete the old one and any dependencies goal be able to remove the ansible roles base os role from the devops repo and still have review instances provision successfully objectives or key results this is meant to further any volume of simultaneous customers have a delightful self service end to end experience using the platform to build on va gov acceptance criteria ansible roles base os role is deleted from the repo review instance provisions successfully review instances get the government warning motd when you login how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 24123053722.0,2022-09-20 20:37:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,wireframes user scenarios for wizard and streamlined waiver draft issue description wireframes user flow for wizard and streamlined waiver with user scenarios similar to for reference tasks after user scenarios are defined create draft of wireframes user flow acceptance criteria draft created,1 15680884105.0,2021-03-25 03:59:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and correct invalid content in system health services for va richmond health care story as a veteran i need to have accurate and correct system health service description so i can quickly and correctly find where to go to get my correct health care support goal accurately update health services with approved content resources task richmond has a total of system health services to replace update all system health services with html code from health service library resource assure that intro line is correct e g care we provide at va richmond health care acceptance criteria all system health services have been replaced with correct html code and the intro has been replaced with care we provide at va richmond health care ,1 23160053363.0,2022-07-29 16:41:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add instructions to how to provide feedback guidance for removing cc request label user story as a governance team member i want to ensure that feedback tickets do not have the cc request label so that tickets do not populate on our collaboration cycle reviews zenhub board or slack notifications assignee peer reviewer description when creating feedback tickets in the collaboration cycle reviews zenhub board it will automatically add the cc request label this will cause feedback tickets to display on the zenhub board and also notify us in slack with the integrations completed in we want to add guidance to remove this label so that our board and slack only show relevant tickets impacted artifacts tasks add bullet under to remove the cc request label if and only if they create the ticket using the new issue link from the collaboration cycle reviews board add bullet under to remove the cc request label if and only if they create the ticket using the new issue link from the collaboration cycle reviews board add bullet under to remove the cc request label if and only if they create the ticket using the new issue link from the collaboration cycle reviews board peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria instructions are provided for removing the cc request label from future feedback tickets reviewers are aware of the scenario that will automatically apply the cc request label how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 12261238669.0,2020-05-06 19:43:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters frontend api integration user story or problem statement as a veteran who has incurred debt i receive debt letters in the mail i would like to be able to see the information online va gov so i can understand the source of the debt the amount of the debt and what my options are for payment or any other remediation i can take goal ability to display the information the veteran received in mail online from dmc api so the veteran can clearly see the debt owed how it was incurred and next steps tasks parse json from api to provide fe data display data per design ui acceptance criteria for any given the user the values retuned in api can be captured and displayed page design matches mock ups provided how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30320486909.0,2023-07-10 18:50:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display employment history issue description add employment history for veteran and spouse employmenthistorysummary spouseemploymenthistory as view only on the final review page can likely leverage a custompagereview similar to how utilitybillsummaryreview is implemented only show the values that have been populated can probably use same component for both veteran and spouse see for copy tasks implement read only display on final review page acceptance criteria housing expenses are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14736847063.0,2021-01-07 00:09:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up msw mocks js the personalization profile msw mocks js is nearly lines a lot of the mock calls have a lot in common and many of the mock calls are full of data that is not really required cleaning this file up could help with when we add new mocks in the future making the mocks a little more focused on providing the data that s actually needed would make it a little easier to understand the functionality that s being tested ,1 12059690605.0,2020-04-15 19:44:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add tests for single facility path we should add an test that only has one valid system and facility to choose instead of multiple ,1 13306238555.0,2020-08-25 19:53:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters conduct usability test synthesis issue description synthesize data gathered from debt letters usability test tasks synthesize data gathered from debt letters usability test create a research readout document upload research readout to gh optional if applicable create a short deck for demoing research readout acceptance criteria research readout is uploaded to gh and linked in this ticket ,1 15380551313.0,2021-03-02 21:16:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,simplify transformed format of in person va appointments currently we are transforming data from appointment related backend services into a fhir esque format this results in some confusing data in places we should attempt to simplify these areas and come up with a structure that makes some use of fhir resources but is not tied to the participant contained arrays or precisely what fields are or aren t allowed in the appointment resource object goals try to reduce nesting arrays for simple data fields keep the common location address and telecom formatting remove relevant data from participant contained arrays and put it into sub object s on the appointment resource object in this ticket we should refactor the data we put in the contained participant arrays for in person va appointments into a simpler format ac update transformers to remove in person va appointment data from contained participant arrays into a simpler easier to understand format update components and tests to use new format,1 23850199740.0,2022-09-06 17:10:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add observer process guidance for joining a research session user story as a researcher i want clear guidance on how observers should enter the session so that research participants feel safe and empowered as a research participant i want to understand the purpose of observers in research sessions so that i can give an informed response to observer related questions assignee claytonzook peer reviewer jimuhh description splitting this ticket from due to research being conducted to determine best practice for advising how observers enter sessions and advising the research participant s we want to clarify that it s not just for research that requires heightened sensitivity and not just a consideration but it s official guidance for researchers to hold observers in the waiting room for all research until after the participant agrees to have additional folks join on the va side see impacted artifacts platform pages tasks conduct research to determine recommended approach get observer research back from researchers who included as part of a study christina liz ben angela patrick onesty mct vha virtual agent research draft present to research ops group receive approval to add guidance determine what changes additions should be made to which pages templates list pages templates below with proposed changes additions per document update intro section to include new observer protocol drafted changes have been communicated in research slack channel changes have been communicated in design monday meeting ask perigean to default their zoom accounts to have waiting room turned on peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria shane and or kevin have approved the proposed changes researchers should have clear guidance to provide to observers when joining a research session how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 14981946349.0,2021-01-28 15:25:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, incorporate content specific for waiver requests on the financial overview screen issue description if a veteran requests to waive their debt they need to provide a written statement providing more information about why they re requesting that resolution path content needs to be added to that screen to clarify what information the user needs to provide when requesting a waiver additionally the content in the why do i need to explain this additional info component needs to be updated to provide more information about what dmc expects veterans to include in the text field tasks review the content under the why do i need to explain this additional info component and update as needed add clarifying content for veterans requesting to waive their debt acceptance criteria the uxpin prototype has been updated with proposed content and linked in this ticket the proposed content is reviewed by a vsp content writer a ticket for frontend implementation is created and linked in this ticket ,1 17268447273.0,2021-07-22 16:25:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cst switch alertbox to va alert description switch the alertbox component to use the va alert web component in the claim status tool tasks replace alertbox with va alert update unit tests update tests if applicable definition of done tasks completed all tests passing,1 25981121741.0,2022-12-19 18:56:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,back end documentation pop wrap up issue description ptems pop is ending on december final documentation and wrap up tasks update consider editing statements that may be out of date or incorrect or could be modified for additional clarity updating list of team contacts with any contacts the be team frequently reaches out to for assistance guidance links to architectural diagrams integration information for dmc vbs huron sharepoint how integration works how we test them who do we interact with what kinds of issues are typically seen acceptance criteria been updated as much as possible how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13223136306.0,2020-08-17 16:41:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery around submission is taking longer than expected issue description it looks like when we fail with a bad zip code it times out for the user instead of displaying a real failure message acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 19909633768.0,2022-01-25 15:58:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, list loop edit view styling issue issue description there appears to be some kind of padding issue with the edit view on the list loop component and should be updated tasks verify this isnt a platform issue and add the proper padding if necessary to the list loop component edit view acceptance criteria edit view should render the proper padding according to ui and design specifications how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20741574747.0,2022-03-14 18:12:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update to telephone web component description update react component to the new web component in form tasks replace react component with web component update tests definition of done all tasks complete all tests passing,1 26202054360.0,2023-01-03 18:27:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unused ga what happened ga logging was added without michelle s team and thus is unused does not work remove unusued code per meeting with them how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 13306235405.0,2020-08-25 19:53:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters mvp updated empty states issue description with the updated mvp including both debt summary and a list of downloadable letters on the same screen we need to create empty states for the following use cases if a veteran accesses the tool and they ve never had a debt i e no debts or debt letters on their record if a veteran accesses the tool and they don t have any current debts but they have resolved debts i e no debts but letters from past debts are available to download if a veteran received a debt after march they will have current debts but no letters to download tasks update to include empty states for the use cases mentioned above get feedback on the proposed designs from team members update gh documentation to include the updated designs create a ticket for frontend implementation acceptance criteria designs have been reviewed and accepted by the team gh documentation is updated designs are linked as a comment ticket for frontend implementation is created ,1 19908369692.0,2022-01-25 14:57:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html statement statement charges table issue description add statement charges table component to the html statement page refer to the for details tasks create statement charges table component acceptance criteria statement charges table should render on the html statement page how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14981904224.0,2021-01-28 15:22:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update installment contracts and other debts section to use inputs instead of radio selections issue description dmc has asked that we reintroduce text inputs for the date of debt and amount overdue questions on the installment contracts and other debts section of the form tasks incorporate new inputs into the design and sync to uxpin create a ticket for fe work acceptance criteria uxpin updated and attached to this ticket fe ticket created and attached to this ticket,1 21101328066.0,2022-04-04 14:43:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres sprint priorities debt resolution team priorities sprint april sprint goals priorities tbd ,1 20153913279.0,2022-02-09 14:52:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, wireflows issue description veterans expect to find all money they owe to va in one location on the site additionally congress has mandated that we provide a way for veterans to access all their debts in one spot as a result we need to create wireflows of the combined vba vha debt portal tasks create wireflows of the combined vha vba debt portal acceptance criteria the designs have been presented to the team an ia ticket has been opened and linked in this ticket ,1 14483819370.0,2020-12-10 15:36:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert breadcrumbs and tabitem tests to rtl tests tabitem breadcrumbs this could be incorporated into the appointments page tests or converted standalone we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos make sure to use the default exported component in the tests and you should remove the old export of the unconnected component,1 16104193881.0,2021-04-27 13:10:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in downtimemessage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos components vaosapp downtimemessage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 14966601687.0,2021-01-27 14:46:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr form cannot be submitted more then once story as a veteran who has submitted the fsr form i should not be able to re submit it again this was an item called out in security review tasks verify that there is error handling for multiple submits inherent in forms system if error handling is not inherent in forms system create error handling for multiple submits definition of done a veteran cannot resubmit an already submitted form ,1 14658002843.0,2020-12-28 16:51:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,finalize fsr wizard flow content issue description finalize fse wizard flow and content pending feedback from dmc in an email sent tasks incorporate changes and improvements from smes create gh page hosting finalized content create fe ticket acceptance criteria finalized content included in gh and linked in this ticket fe ticket created and linked in this ticket,1 12393285203.0,2020-05-20 15:11:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add git sha into environment for referencing in initializers app info rb background we used to have the current sha of the release available in the initializer this was broken when infra moved to docker see discussion towards end of acceptance criteria x git sha header is populated from each environment api va gov status returns the correct sha tasks add the ref to environment deployment in each env for vets api point up in each env for vets worker ,1 29173046882.0,2023-05-19 04:56:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor export format in src platform during a recent installation of yarn workspaces on a vfs app a pain point was brought up regarding using the yarn import format department of veterans affairs platform point out some inconsistencies linting errors and compilation failures the goal of this pr is to refactor exports to fix said issues experiment related prs steps being taken change export format from export from source to import from source export address webpack issue with fs address webpack issue require imports of non js types specifically ejs scss md and json review export aliases and paths to make sure they are correct and work with linter ,1 31814014879.0,2023-09-13 18:59:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging user account for usability test issue description we will need a staging user account with active copay debt for participants in our accessibility user study tasks tickets created to request test staging user apply copay to test account acceptance criteria lett ticket request user has active copay applied to account user can submit form without copay disappearing ,1 23196069464.0,2022-08-01 16:29:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate system usability score sus for va research user story as a researcher i want to investigate the system usability score sus so that i can recommend implementing for va research assignee peer reviewer description the system usability score sus was a suggestion by kevin hoffman we want to figure out if this is something we want to implement for va research before we undertake building a page for guidance impacted artifacts tasks placeholder task peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria placeholder ac how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 15611396992.0,2021-03-19 14:16:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, rework concept for value pair list loops issue description in our list loop discussions with ryan and the team last week he asked for us to all follow up with list loops concepts for our products ping accessibility then post to design slack channel once the sequential version is complete so the group can discuss i followed up with ryan and he suggests that we remove the edit save functionality for our value pair version of the list loop tasks create new value pair list loop concept and upload to sketch for teams follow up with accessibility for review post to dsva slack channel for discussion acceptance criteria concept uploaded to sft and shared to design,1 12464676558.0,2020-05-28 12:53:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,file change request in snow for dns zone delegation and await correspondence issue description change request needs to be filed in service now to delegate the vfs va gov zone to the vsp operations team tasks file ticket with service now folks via cag await correspondence further instruction update this ticket with any discrepancies issues etc acceptance criteria proper ticket is filed with proper team and the desired dns zone is delegated to vsp ops team how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12974051905.0,2020-07-21 14:53:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vsa qa test plan product feature summary mvp is one page only after landing page the veteran logs in and there is a summary of debts and links to download debt letters because this is pii we are doing testing in person aka zoom with recruited veterans product feature outline product feature epic product feature pre launch checklist product feature design artifacts product team smes camerontesterman product management leahkeeler design research rebeccawalsh rileyorr content ia mnorthuis front end back end qa tze chiu lei proposed user scenarios and staging test accounts veteran logs in and there is no debt veteran logs in and sees a debt summary and a list of debt letter they can down load please note sine this is pii data we re working with betamocks how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team vsa authenticated exp vsa benefits vsa benefits vsa caregiver vsa ebenefits vsa facilities vsa public websites etc definition of done test plan reviewed by product team test plan finalized per review feedback actual test run s completed on staging created and tracked ,1 14381313754.0,2020-12-02 05:05:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review of the register for care pages for visn user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation tasks complete review of register for care top tasks call to action across all visn systems listed below and document and report any issues that may need to be fixed use the following guidance does this content field data in this page make sense does the content field data in this page relate to this system level or specific to a facility is it in the right place based on system facility pages for the veteran to find how does this help with the focus of the page confirm the altoona va butler va coatesville va erie va lebanon va philadelphia va wilkes barre va wilmington va acceptance criteria all top task node pages have been reviewed in spreadsheet and issues found have been been documented issues have been documented and escalated for resolution using vamc support channel and spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 27290084662.0,2023-02-23 16:01:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,non combined vha submissions not being submitted issue description while tracking submission numbers it looks like the only time we are receiving vha submissions are when they are bundled with vba debts this may have been related to another fe bug that has been fixed but will continue to be tracked and worked to replicate locally tasks replicate bug locally with only vha debts identify cause create any tickets that may need to be worked acceptance criteria we can progress forward with vha only submissions how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28074436723.0,2023-03-29 21:52:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, required field label in wrong place on gross monthly income page for employment history issue description shadow root styling issue on the employment section under because of the shadow root stuff the required label is detached from the copy and looks a little funny it looks like a workaround was made and the label and hint have been hard coded outside of the va number input component currently looks like this should look like this tasks fix where the required label shows up acceptance criteria required label is in the right place next to the label question ,1 19914948056.0,2022-01-25 21:24:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debts endpoint gateway timeout errors issue description sentry reporting gateway timeout errors the the debts endpoint debts code detail did not receive a timely response from an upstream server status title gateway timeout tasks look into sentry and loki to drill into why the timeout is occuring acceptance criteria we understand the reasons behind the timeout and have created followup work to resolve the issue how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16013583283.0,2021-04-20 13:38:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore converting a page component to react redux s useselector and usedispatch hooks we re now on the latest version of react redux so we can use their useselector and usedispatch hooks instead of using connect docs are here they re very good docs highly recommend reading them generally useselector replaces what we use mapstatetoprops for and usedispatch replaces what we use mapdispatchtoprops except that it doesn t automatically wrap the actions with dispatch it just returns dispatch for you to use we can then do dispatch someaction where someaction was something we had in mapdispatchtoprops before i think any component with both mapstatetoprops and mapdispatchtoprops could be used to try this out ,1 17150686993.0,2021-07-13 20:09:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,test debt letters downtime message description on dmc will be down for a minute period see test the functionality in place for debt letter for handling errors when dmc cannot be reached a c research to see if we have maintenance windows in pager duty for dmc understand if dmc has breakers configures mock a service outage and ensure the frontend renders a tolerable experience ,1 24100350467.0,2022-09-19 23:32:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vaos code to re direct veterans to cerner iscerner flag background request public website team is updating the iscerner flag in the file they plan to deprecate the flag in goal requirements to consider tasks answer the following questions q time box hours definition of done tasks are complete research and recommendations are documented in this ticket ,1 15680869378.0,2021-03-25 03:56:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and correct invalid content in system health services for va durham health care story as a veteran i need to have accurate and correct system health service description so i can quickly and correctly find where to go to get my correct health care support goal accurately update health services with approved content resources task durham has a total of system health services to replace update all system health services with html code from health service library resource assure that intro line is correct e g care we provide at va durham health care acceptance criteria all system health services have been replaced with correct html code and the intro has been replaced with care we provide at va durham health care ,1 22758120700.0,2022-07-07 18:26:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, the content has spelling punctuation or typo errors general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers cheryl evans cherylevans content for more information on how to interpret this ticket please refer to the guidance on platform website platform issue the content has spelling punctuation or typo errors issue details test user your va debt and bills what to do if you think you have a va debt or copay bill should have colon before a bulleted list for benefit debts call the debt management center dmc at tty we’re here monday through friday a m to p m et for medical copay bills call the va health resource center at tty we’re here monday through friday a m to p m et link screenshot or steps to recreate va gov experience standard other references platform recommendation per ap stylebook edition a frequent use of a colon is at the end of a sentence or phrase to introduce bulleted lists what to do if you think you have a va debt or copay bill this phrase should have a colon at the end of it as it introduces a point bulleted list vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 20159294402.0,2022-02-09 19:39:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, show error links on review submit description form shows a generic error message when validation fails upon submission we need to enable the error links which provide a path for the veteran to the appropriate accordion entry that needs editing tasks enable error links unit tests definition of done error links showing in production all tests passing,1 30694765671.0,2023-07-26 17:41:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, feature flag routing veteran information chapter path old combined enhanced veteran information true true true available debts true false true all available debts false true false contact information true true false current contact information false false true edit mobile phone false false true edit email address false true true edit mailing address false false true household income chapter path old combined enhanced employment true true false employment records true true false employment question false false true enhanced employment records false false true gross monthly income false false true deduction checklist false false true deduction values false false true employment history false false true income index true true false benefits true true false your benefits false false true edit benefits false false true social security true true false social security records true true false additional income true true false additional income records true true false additional income checklist false false true additional income values false false true other income summary false false true add other income false false true spouse information true true true spouse name false false true enhanced spouse employment question false false true enhanced spouse employment records false false true spouse gross monthly income false false true spouse deduction checklist false false true spouse deduction values false false true spouse employment history false false true spouse employment true true false spouse employment records true true false spouse income index true true false spouse benefits true true true spouse benefit records true true true spouse social security true true false spouse social security records true true false spouse additional income true true false spouse additional income records true true false spouse additional income checklist false false true spouse additional income values false false true spouse other income summary false false true spouse add other income false false true dependents true true false dependents count false false true dependent records true true false dependent ages false false true household assets chapter path old combined enhanced monetary assets true true false monetary asset checklist false false true monetary asset values false false true real estate assets true true false real estate asset records true true false enhanced real estate assets false false true enhanced real estate asset records false false true vehicles true true true vehicle records true true false your vehicle records false false true vehicles summary false false true recreational vehicles true true true cold recreational vehicle records false true false recreational vehicle records true false true other assets true true false other asset records true true false other assets checklist false false true other assets values false false true other assets summary false false true add other asset false false true household expenses chapter path old combined enhanced expenses explainer false false true expenses true true false household expenses checklist false false true household expenses values false false true utilities true true false utility records true true false utility bill checklist false false true utility bill values false false true utility bill summary false false true add utility bill false false false repayments true true false repayment records true true false credit card bills false false true your credit card bills false false true credit card bills summary false false true installment contracts false false true your installment contracts false false true installment contracts summary false false true other expenses true true false other expense records true true false other expenses checklist false false true other expenses values false false true other expenses summary false false true add other expense false false true repayment or relief options path old combined enhanced option explainer true true true resolution options true false true resolution option index false true true resolution comment index false true true resolution waiver agreement index false true true resolution comments true true true bankruptcy history chapter path old combined enhanced bankruptcy history true true true bankruptcy history records true true false enhanced bankruptcy history records false false true ,1 16505779331.0,2021-05-25 19:06:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr single edit function userstory as a veteran when i want to modify my fsr request i would like to disable the function to allow me to edit multiple items at the same so that i can focus on edit one item at a time acceptance criteria input list loop can only allow edit for one item at a time ,1 30797110784.0,2023-07-31 20:50:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, observer notes documents issue description create documents for notetaking for sw research study tasks create mural create google spreadsheet acceptance criteria mural created spreadsheet created ,1 24121183101.0,2022-09-20 18:51:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review application page text changes with smes issue description review application page text changes with smes tasks review updates and send email to smes acceptance criteria email sent to smes list of updates this front end update was already made add tsp clarify brokerage account for stocks and bonds need help with debt related to va benefits or health care copays estimated value of all of your this includes vehicles with a loan this includes properties with a mortgage ,1 22708496632.0,2022-07-05 16:45:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update cypress tests to use dynamic dates issue description mdot cypress tests are using fixed dates for the supply lastorderdate nextavailabilitydate and prescribeddate variables since we re using the platform provided testform and packaging up the data with createtestconfig it s difficult to put in dynamic dates for the datasets investigate to see if we can feed dynamic dates something within the valid date range to the test so it doesn t need to be updated again createtestconfig uses variable datasets and cypress cy fixture to pull data from the json files and fills out the forms tasks investigate options to update the supply dates dynamically based on when the test is run implement a fix so we don t need to update the dates again acceptance criteria cypress tests use dynamic dates and pass or dates are just fixed and need to be updated every few years how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13617221184.0,2020-09-23 16:41:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,tech debt fix the facilities mock api to use paths our mock api uses in the fake api call paths we should switch these to since we ve migrated to for the real api calls this has no real impact on site functionality it is technical debt ,1 20159959329.0,2022-02-09 20:22:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, eslint depricate import loadingindicator issue description platform deprecated suggesting we use instead screenshot tasks replace with new acceptance criteria should render instead how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20119512591.0,2022-02-07 23:47:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,business intake form for debt resolution fsr leah keeler debt resolution benefits per research veterans except to be notified when they fill out fsr online this will provide veterans a record and assurance that their fsr has been submitted what is an overview of the notification use case once fsr is filled out online an email is generated letting the veterans know the fsr has been received what is the user journey during which this notification will take place is there a desired behavior change see above is this notification already being sent and if so how yes no and optional sentences no what kind of notification would this be required email text not sure email if you have a draft of the content you’d like to send please upload here please note we collaborate with all of our users on their content to ensure it meets standards optional blank not at this time have you spoken to your privacy officer about your content use case and has it been approved yes no not sure no what system will your notification be triggered from i e vets api required sentences dmc back end system do you have the business logic in that system to trigger an api request to us required sentences do you have the data or access to the data needed for your notification i e email addresses unique identifiers optional yes no not sure yes do you have a budget for this please see details on the cost of using our service here optional yes no not sure already in place what is your estimated volume of notifications per day week month optional open space after suspension is lifted about per month when does this notification need to be in production optional open space any time before august ,1 24677795434.0,2022-10-18 18:30:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,allow dependents to fill out fsr form high level user story ies as a dependent who has incurred debt with dmc i would like the ability to fill out the fsr form on line without having to authenticate on va gov as a veteran hypothesis or bet if we make this change more fsrs will be filled out online supporting original hypothesis of fewer errors and better user experience okr reduce error rate allowing veterans to resolve their debt in a timely matter definition of done a dependent must be able to fill out and certify the fsr form online the fsr form must be received by dmc in json format take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 18794626841.0,2021-11-08 20:42:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add reviewer github handles to staging review issue tickets aka feedback issue description staging review issue tickets are created via bulk upload using the draftingtemplate person on product support runs the bulk upload process and all of the feedback documented in the draftingtemplate is transformed into github tickets the person that runs the process is the opened by person on the github tickets meaning they are the one who receives notifications if when a vfs team member comments on the ticket it would be valuable if the practice area review who documented the feedback is tagged in github so they are aware when new vfs comments come in tasks research if there is a way to automatically to add platform reviewer to their staging issue ticket acceptance criteria platform reviewer who identified a staging issue is assigned to the staging ticket how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23724507061.0,2022-08-30 18:15:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, determine best practices standards for api data handling user stories as an engineer i wish to have consistently structured and pre validated data available to me so that i do not have to write defensive code throughout the application as an engineer i wish to adhere to the principle of maintaining a single source of truth so that the data presented to users remains consistent as an engineer i wish to update as little code as possible when the api we consume changes so that i may reduce technical debt defects and re work description this spike arises from let s get the engineering team together and discuss best practices for handling data validation normalization translation and what standards we wish to follow references questions to answer how might we simplify handling and validating api data knowing that it is likely to change over time what best practices and standards should we follow as a team acceptance criteria spike is held agreed upon standards are documented and or a follow on issue has been created to do so follow on issues have been created for addressing changes technical debt identified during this spike and or any items that require further research,1 15818261199.0,2021-04-05 15:46:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace moment timezone adjustments with date fns timezone helpers we should be able to replace uses of moment timezone s tz helper in our application code and switch to the date fns timezone helpers those helpers rely on polyfilled timezone data so this should result in some reduction in bundle size for most users important don t try to convert all the unit test code we can do that later be mindful of the differences between the formatting tokens of moment vs date fns use your best judgment on how much code surrounding the tz usage you re replacing to convert to use date fns it s ok to break off complicated pieces of this ticket into smaller ones ac no more imports of moment timezone in vaos application code test code is fine or a set of tickets created to accomplish this uses of tz are appropriately converted to use date fns helpers or a set of tickets created to accomplish this,1 27115200967.0,2023-02-15 18:01:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate discrepancy between vha submissions and emails sent issue description jill has brought up that the number of emails going out for fsr confirmation is more than the total submissions being delivered tasks investigate potential causes for these different numbers acceptance criteria we know a potential cause generated future work to align the numbers how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22779552066.0,2022-07-08 18:01:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html markup isn t valid general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue html markup isn t valid issue details on current copay balances summary copay balances the check details links each have both an aria describedby attribute and an aria label attribute these attributes can t be used together in that situation screen readers may give priority to the aria label attribute and ignore the aria describedby entirely since the aria label value is just the same as the visible link text check details this doesn t provide any benefit to screen reader users as the links don t have unique accessible names link screenshot or steps to recreate when logged in as test user the first check details link is coded as check details va gov experience standard other references wcag sc a platform recommendation best option here is to remove the aria describedby attribute and the hidden description entirely and make the aria label something uniquely identifiable note that the current hidden description doesn t make a ton of sense as coded now for the first copay owed for test user the description reads check details and resolve this debt for mann grandstaff department of veterans affairs medical center vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 25568968246.0,2022-11-30 16:13:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, migration product outline analytics team is working on the migration to google analytics as google will be sunsetting our current universal analytics properties this epic is to track documentation and benefits related to this work references and resources current steps current understanding analytics team meeting with vfs team to discuss the new event structure and any custom events we have set up to define requirements analytics team hopes to have migration work done by the end of september vfs team end of sept early oct will be asked to complete integration and test functionality definition of done what must be true in order for you to consider this epic complete migration is complete and team is able to extract all kpis and necessary data from or domo dashboards ,1 25892526391.0,2022-12-14 19:13:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate instances of applications importing code from other applications audit our usage of applications and applications babel aliases to determine if we have any applications that are importing code from other applications this is a bad practice any shared code should live in platform in particular we should look for instances where our code is importing other application s code and make tickets to fix those instances instances where other apps are importing our code and make tickets to fix those instances additional tickets can be created based on this spike ,1 27111545353.0,2023-02-15 15:38:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, form able to save with validation errors what happened forms can save with validation errors in fields experienced in fsr employment history when inputting invalid dates desired behavior update save logic in routedsaveableapp to handle preventing saving of invalid data acceptance criteria saving invalid data prevented how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 15732922755.0,2021-03-29 18:53:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,simplify transformed data format for video appointments currently we are transforming data from appointment related backend services into a fhir esque format this results in some confusing data in places we should attempt to simplify these areas and come up with a structure that makes some use of fhir resources but is not tied to the participant contained arrays or precisely what fields are or aren t allowed in the appointment resource object goals try to reduce nesting arrays for simple data fields keep the common location address and telecom formatting remove relevant data from participant contained arrays and put it into sub object s on the appointment resource object in this ticket we should refactor the data we put in the contained participant arrays for video appointments into a simpler format ac update transformers to remove video appointment data from contained participant arrays into a simpler easier to understand format update components and tests to use new format,1 21189979105.0,2022-04-08 16:17:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove references to axe coconut user story as a vfs team member i want to view up to date documentation from platform so that i can trust the guidance and not have to waste time going down dead end paths intended audience vfs teams desired outcome no more references to axe coconut on platform website due date description the chrome extension axe coconut is no longer available see ticket the purpose of this ticket is to remove references to axe coconut in the artifacts needing updates tasks n a acceptance criteria how to prepare for an accessibility staging review on platform website has been updated per guidance updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 31844672855.0,2023-09-14 18:56:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery issue description given the number of technical issues veterans are contacting dmc about our team is going to begin discovery on how to get on the ask va s backlog to redirect veterans to their tool tasks document questions for both dmc and ask va reach out to the ask va team to learn more about their timeline and process acceptance criteria discovery questions are documented and linked in this ticket ,1 20757233512.0,2022-03-15 13:20:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,html statement fe introductory exploration issue description currently the medical copay product has pdf statements which are inaccessible therefore we need to switch to html statements to meet compliance requirements this epic was established to do just that and the work has been broken up across the included tickets since our front end team is new to the team this ticket is meant for discovery work related to sizing and implementing this epic adding a feature flag to disable hide while new html page is being built tasks adding feature flag prior to work start to hide new changes until testing review tickets to understand scope connect with scott who has a json file related to this work acceptance criteria frontend team has a good understanding of the work required is able to size the tickets in this epic and is ready to pull the work into the sprint how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23198735466.0,2022-08-01 19:06:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,complete research documentation audit user story as a platform team member i want to make sure that all important documentation has been migrated to platform intended audience gov team desired outcome all gh documentation on research has tech debt ticket to be migrated to platform due date assignee claytonzook peer reviewer chaseakirby description an audit was begun by naomi to ensure that all important documentation from github was transferred over to platform some items of may now be complete but not marked as such on the audit additionally some items may not be complete and then need a new tech debt ticket artifacts needing updates tasks create tech debt tickets as necessary to ensure all the items from the audit are in backlog to be worked on tickets should include merging the vsa and platform gh docs on a topic as needed finding a place for this information to live on platform either updating a section page or creating a new section page marking gh docs as depreciated once the information is on platform marking the line on the audit doc green once complete acceptance criteria audit documentation has been updated tech debt tickets have been created for remaining audit items user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 19319793333.0,2021-12-14 03:15:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, sort pdf statements technical task we want to show the most recent to the oldest last sort pdfs so they show in this order expected behavior pdfs are sorted from newest to oldest acceptance criteria pdfs are sorted from newest to oldest ,1 22099071722.0,2022-06-01 12:29:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update urls and breadcrumbs issue description update cdp urls and breadcrumbs to match design and ia specifications add the new cdp path to content build repo so it s accessible for testing tasks update cdp urls update cdp breadcrumbs update content build with urls and specify testing only hide behind feature flag acceptance criteria cdp urls and breadcrumbs are available how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16597941917.0,2021-06-01 15:28:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,from cannot be restarted after submit in prod observed behavior once a form is submitted and a veteran choses to restart the form it cannot be submitted this has been observed in production only in lower environments the form can be restarted desired behavior a veteran should be able to submit a new fsr if they chose restart per requirements dmc has a method to sort based on submit date to work with the latest submitted form ,1 14001888853.0,2020-10-28 14:10:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr discovery research synthesis issue description once completing research with dmc smes and vsos the design team needs to synthesize and uncover themes learned about how veterans interact with the fsr va form tasks synthesize research sessions with dmc smes and vsos write a research readout containing the top takeaways acceptance criteria the final research readout is uploaded to gh and linked to this ticket optional a deck is created to present findings to the team and or at demo ,1 26274007371.0,2023-01-06 19:57:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,missing test coverage found that these classes have no corresponding tests accesssatisfactionclient accesswaittimeclient betaswitch backendservices,1 16460820757.0,2021-05-21 18:43:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove secondary email input on contact page after discussing it with the dsva design channel we found that the secondary email input on the fsr contact page is unnecessary and can be removed ,1 26941311673.0,2023-02-08 02:35:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update detail charge table with mock data issue description we have requested mock data from the liberty team and we will need to update our design spec with accurate mock data tasks update the table with mock data upload to uxpin update spec acceptance criteria uxpin updated and linked in this ticket spec updated and linked in this ticket ,1 27019913347.0,2023-02-10 23:59:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, work with lighthouse team to determine real time data next steps issue description we ve identified lighthouse as a valuable resource to fetch real time cdw data from need to understand how we can progress background information can be found on tasks reach out to lighthouse contact draft plan acceptance criteria we know how to move forward with lighthouse how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27011659252.0,2023-02-10 15:51:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, eslint react jsx one expression per line issue description receiving the following eslint warnings for jsx one expression per line which is enabled data must be placed on a new line eslint due a recent change by platform to enable some linting rules these warnings have been surfaced and should be addressed to ensure we adhere to best practices in our code tasks clear warnings for fsr mcp and debt letters components acceptance criteria warnings should be cleared how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24278918690.0,2022-09-28 15:44:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, make link to form more prominent issue description this pattern is used on all wizard pages but users feel the link is hidden note possibly use an tasks acceptance criteria ,1 15836097581.0,2021-04-06 18:51:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,incorporate completed form download into fsr confirmation screen issue description we ll be able to offer completed form downloads to veterans upon submission of the form with a delay of only a couple of seconds create a design to incorporate this action into the mockups tasks create designs for download create a ticket for fed acceptance criteria designs synced to uxpin and linked below fed ticket created and linked below ,1 28067777296.0,2023-03-29 16:41:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, va number input currency update issue description va number input has been updated with a currency property and we need to enable that flag throughout the form tasks update va number input with currency flag where it s applicable confirm functionality stays the same acceptance criteria va number input s in fsr have been updated accordingly all and unit tests are passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12303402404.0,2020-05-11 18:37:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update sidekiq to our sidekiq gems are mission critical for running asynchronous jobs and are two major versions out of date upgrading these gems requires thorough testing on staging as well as monitoring in production to ensure things work as expected ,1 27405545584.0,2023-03-01 06:20:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update new uxpin account issue description files from ad hoc s uxpin account will need to be transferred to our new uxpin account after they have been transferred the fsr project will need to be updated tasks work with ad hoc and uxpin to transfer files to new uxpin account acceptance criteria team is granted access to new uxpin account ,1 14358099354.0,2020-11-30 13:59:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch household assets as a veteran filling out fsr i want the ability to add household assets to the fsr form ,1 24424907953.0,2022-10-06 01:14:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update pay gov details for copays issue description update information presented to veterans when a link to pay gov is available on the debt portal details veterans can pay their copay bills online via pay gov we provide a link on the portal for veterans to link over to pay gov for their information the current state see below has limited information and doesn t provide veterans with enough information for them to clearly understand what information they will need once they log in current state on the debt portal information to consider including in updated copy veterans can pay medical care and prescription copayments billed on their monthly statements for services provided by a va medical center or clinic on pay gov incorrect information or wrong form used will delay payment posting details required to complete form and submit payment including verify veteran name the va account number and payment amount accepted payment methods bank account ach and debit or credit card information veterans need to submit on pay va gov for reference tasks mockup designs with new content acceptance criteria once approved hand over to fe for development how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23349981593.0,2022-08-09 22:14:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, pass appointment stationno property through background slack thread we d like to have the stationno property available to make unique ids with the stationno appointmentien combination having the station number available could also enable future informational displays for veterans tasks pass stationno property through to the frontend update rspec cache data code cleanup if necessary acceptance criteria deployed to staging tested on staging ,1 19958847643.0,2022-01-28 04:57:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,manage your va debt epic as a veteran i want the ability to see all my va debts debt letters and payments in one dashboard the veteran will be able to see their debts and in the future select options to manage them such as a waiver dispute compromise and they would be routed to vba and or vha allow veterans to view all va debts online and decrease time to resolution while meeting congressional mandates kpis total page views on debt portal,1 11568251905.0,2020-02-20 15:35:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, conditional rendering of the address validation form is somewhat cumbersome user story as a veteran i need to have performant and easy address validation therefore my coders to be able to maintain the code rendering decisions within the conditional section is written as a hard to maintain piece of code and we would like to clean it up to improve readability and maintainability tasks talk to kelson to do a quick code review redesign new address validation visual component form element rendering code it up regress pr and all the normal stuff acceptance criteria component behaves the way it was laid out in the ac code is cleaner and performance previous configuration attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team e g vsa authenticated exp vsa caregiver labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 15836097525.0,2021-04-06 18:51:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, chapter content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to chapter tasks incorporate the changes outlined on page to of the provided document since this is the review page make sure any changes that were made to previous chapters such as headers are reflected on this screen as well acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 31162051312.0,2023-08-16 16:42:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,setup datadog dashboard to track mcp metrics issue description statsd calls have been added to track policy success failure and vbs success failure for mcp and we need a datadog dashboard graphs in place to track these counts and ratios tasks create new dashboard graphs to track success error acceptance criteria kpis are able to be seen within datadog how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12963872056.0,2020-07-20 19:30:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, set up bucketing workshop activity for dmc issue description create a plan for the bucketing workshop activity to be done with the dmc goals of the workshop assign all letter or possibly diary codes to specific status buckets create general idea for verbiage for each of the buckets defined identify any potential blockers or outliers tasks create the plan create the miro or mural board for the activity send out the agenda for the meeting acceptance criteria plan outline and activity board linked below agenda sent to participants,1 15785546515.0,2021-04-01 16:28:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up homepage refresh code organization the homepage refresh code is mixed together with our existing list page code and it could be good to separate it out more ac separate refresh list page components into separate folder from current homepage list components make sure all homepage refresh code follows our typical conventions for file and folder structure make sure homepage refresh tests match component names and folder structure of component code,1 16519873467.0,2021-05-26 13:33:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr report failed api calls userstory as a veteran i would like to be able to report api service down when i am not able to progress with my fsr form due to bgs points in the beginning of the form not being handled properly acceptance criteria veteran can report error if he gets stuck with the form and not able to progress ,1 14394046533.0,2020-12-03 00:21:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,error message responses for fsr form peggy asked me to research error message replies for the fsr form would the following be the best option there are more than such required questions and statements in the form is your spouse currently receive va benefits required informational alert we need your help to continue working on your request please answer the spouse benefits question so we can continue helping you fill out your request ,1 17771805027.0,2021-08-30 14:27:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor cancel modal to avoid prop drilling refactor the cancelappointmentmodal such that it doesn t have the different appointment type conditions these are not used for homepage refresh update the component to use connect to redux directly using useselector rather than needing props to be passed in from the parent component unless truly necessary ,1 26273325137.0,2023-01-06 19:14:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,incorrect data presented on portal issue description veterans are reporting that they are seeing incorrect data presented on the portal and support calls are getting a handful of inquiries of the debt portal not providing correct balances within the last couple months for different debt types examples veteran stated he received his letter in the mail but when he went to his va account on the debt portal it states he doesn’t have a debt “ i have a va debt balance but when i log into the va website it says there is no debt on file i would like to be able to view my total balance before paying last response stated that due to system changed there would be times that veterans wouldn’t be able to see debt in debt management this is not due to system changes whenever i login everyday the system still says they i have no debt but i do and want to see the balance without having to make a phone call or submit an inquiry ” veteran sent an email stating his balance has not updated on the portal with the last two months’ payments of each paid via compensation benefits on and he states the debt portal balance reflects when vams shows he was concerned we were not applying the payments considerations from va representative reporting issue is it possible any updates on account balances have not been updating was it months ago when the letters were stopped i’m thinking there is a correlation with the letters being turned off and balances not updating tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24849057978.0,2022-10-26 18:21:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review application page text changes with smes issue description review application page text changes with smes tasks review updates and send email to smes acceptance criteria email sent to smes once approved create dev ticket for implementation list of updates this front end update was already made add tsp clarify brokerage account for stocks and bonds need help with debt related to va benefits or health care copays estimated value of all of your this includes vehicles with a loan this includes properties with a mortgage ,1 17936425773.0,2021-09-10 15:53:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove alert from the debt portal issue description dmc has verified the debt email notification issue has been resolved so the alert should be removed from the debt portal on manage va debt your debt slack tasks remove alert from debt portal acceptance criteria alert should be removed how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16090422916.0,2021-04-26 16:01:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in vaosapp we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos components vaosapp index jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 25335005910.0,2022-11-18 16:06:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update code to remove dependency on deprecated statsd backend method background bumps statsd instrument from to deprecates statsd backend and our codebase will need to be updated in order to upgrade the dependency from annaswims comment thread statsd backend is deprecated in and we use it offenses config initializers statsd rb c statsd singletonconfiguration singleton methods to configure statsd are deprecated the best option is to configure the library using environment variables like statsd addr statsd implementation statsd prefix and statsd default tags metric methods called on the statsd singleton e g statsd increment will by default be delegated to a client that is configured using these environment variables alternatively you can instantiate your own client using statsd instrument client new and assign it to statsd singleton client the client constructor accepts many of the same options if you have to you can call the old methods on statsd legacy singleton client note that this option will go away in the next major version statsd backend if host present port present acceptance criteria statsd instrument gem is at version ,1 15770044675.0,2021-03-31 19:00:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl debt list past debts default hifi issue description we need to create a mockup of the default state of past debts with debts populated tasks create mockups share with design team update update this ticket acceptance criteria screen created ,1 26941809668.0,2023-02-08 03:16:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, ongoing maintenance description captures ongoing maintenance for debt portal ,1 21047353532.0,2022-03-31 17:17:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, provide a way for veterans to email dmc with technical concerns issue description currently dmc receives calls from veterans experiencing issues from the debt portal and are struggling with assisting them tracking the issue and forwarding the issues to our team when applicable we re exploring implementing a tool called ask va ava but in the meantime updating error alerts to include an email address for technical concerns this ticket is for content updates to the vba debt portal debt overview page s alert to support providing a way for veterans to email dmc with technical concerns screenshot of the alert for reference tasks update the current debts alert acceptance criteria the alert has been updated ,1 26939779529.0,2023-02-08 00:37:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,portal information revamp high level user story ies as a veteran i am able to clearly and easily navigate through the information on the debt portal so that i can find what i need easily hypothesis or bet by enhancing the information across the debt portal we are establishing a better less confusing experience for veterans as they traverse the information that is presented to them on the debt portal okr which objective key result does this epic push forward definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 13222547460.0,2020-08-17 15:42:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move feature specific utils code into feature folders we need to evaluate the utils folder and move any feature specific code into the appropriate feature folder make sure to update the tests folder to reflect any changes ,1 11274643338.0,2020-01-14 19:00:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove downtime notification announcement background there was a scheduled maintenance to the vets api on and veterans caretakers family members or other users of the website will need to be notfified that va services will be down for a period of time this code should now be removed ac remove downtime notification announcement ,1 22758131829.0,2022-07-07 18:27:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design components or patterns don t align with design system guidelines general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details the va debt letter history table is misaligned in the second column link screenshot or steps to recreate debt letter table png va gov experience standard other references wcag sc aa platform recommendation the title of the debt letter should be top aligned with the date vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 17270145500.0,2021-07-22 18:38:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, my va kill user preferences api now that we are removing the my va find va benefits section we likely no longer need the apis that powered it first wait for to be closed then delete all user preferences apis including whatever it is using to persist user selections ,1 31843892677.0,2023-09-14 18:21:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove extra copy from transition page issue description remove the extra next steps list on the transition page so it s more clear this is based on tasks remove next steps list on transition page update sketch uxpin update code and create pr acceptance criteria sketch uxpin updated pr has been merged how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28034712055.0,2023-03-28 14:25:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,part heuristic evaluation workshop issue description what details are necessary for understanding the specific work or request tracked by this issue the heuristic evaluation workshop is an opportunity for the debt resolution team to collaborate creatively as a team learn about or refresh knowledge of usability heuristics and practice design thinking become familiar with the fsr form and or enhance present understanding think about possible usability improvements within current constraints must have work near completion in staging prior to this session this is related to tasks planning for part of the workshop part workshop takes place acceptance criteria part of the the heuristic evaluation workshop has taken place ,1 17150058367.0,2021-07-13 19:16:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,letters switch pure html alerts to use va alert description switch the pure html alert to use the va alert web component in the letters app tasks replace html alert usa alert with va alert update unit tests update tests if applicable definition of done tasks completed all tests passing,1 26273723027.0,2023-01-06 19:39:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,evss base service does not use common client errrors is for faraday clienterror the common client base lib common client base rb class captures these and turns them into common client errors parsingerror or common client errors clienterror the evss baseservice does not inherit from that class or generate the same clienterror to be compatible with other error handling features we have we need to better handle faraday clienterror if we cannot inherit from common client base ,1 21881454693.0,2022-05-19 14:39:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,benefits debt res sprint priorities benefits sprint priorities sprint may formerly debt resolution team sprint goals continued development of the combined portal including debt and merging address midpoint review feedback for combined portal document user scenarios json to pdf conversion sprint deliverables list of deliverables completed during sprint documented user scenarios draft release plan for combined debt portal planned issues combined debt portal merge medical copays under the new combined debt portal documenting user scenarios update the additional information component s chevron color to blue review icons in the cards status sections merge debt letters under the new combined debt portal debt debt detail page sync with accessibility regarding midpoint review feedback combined fsr sme meeting prep for fsr content adjustments tech debt hook up mocked debt letters with vbms gem unplanned additions tbd capacity planning pto holiday s denise scott brandyn andrew riley kevin points planned points accomplished tbd points over tbd issues tbd points over tbd issues 🛠️ reference section 🛠️ cc events artifacts medical co pays combined va debt portal combined fsr streamlined waiver product outline use cases flow release plan release plan release plan release plan architectural diagram use cases use cases use cases use cases use cases product guide product guide tbd product guide product guide product guide kickoff design intent midpoint review usability testing n a ia request analytics request required contact center review research plan review required staging review privacy security review helpful links ,1 24140306638.0,2022-09-21 14:23:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,continue wireframes user scenarios for wizard and streamlined waiver issue description wireframes user flow for wizard and streamlined waiver with user scenarios for reference tasks create and discuss wireframes user flow acceptance criteria wireframes user flow created,1 26805712021.0,2023-02-01 18:07:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, sprint priorities debt team debt team sprint priorities sprint jan jan note we have extended this sprint to be weeks to better align with contracting invoices sprint goals assist with onboarding new team members as needed woo hoo progress development efforts for fsr enhancements release define discuss fsr submission analytics requirements with platform analytics identify users impacted by fsr submission bug investigate reports of inaccurate data reports resolve compromise amount not seen on dmc endpoint resolve nan issue reoccurrence conduct collab cycle midpoint review update uxpin with fsr enhancements design post midpoint planned issues fsr enhancements veteran contact information enhancement fe update submission analytics to show type of submission fe real estate enhancements fe bankruptcy history enhancements fe your va benefits add total amount to card screen adjustments fe midpoint review design transfer sketch mockups to uxpin design user research study spreadsheet design tech debt discovery for bgs peopleservice vafilenumbernotfound be bug fixes veteran entered compromise amount not seen on dmc endpoint be investigate ongoing nan issue be incorrect data presented on portal be explore additional empty states post dec fix fe unplanned additions midpoint review frontend updates capacity planning pto holiday s mlk day aaron andrew brandyn possibly tbd denise heather megan scott points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review tbd details on kickoff feedback tickets design ia and content accessibility  content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 15836097543.0,2021-04-06 18:51:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, intro page content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to the form s intro screen tasks incorporate the global changes outlined on pages of the provided document acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 14172757788.0,2020-11-12 17:22:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr household assets content as a veteran filling out fsr i wan tot understand what i need to list in assets for household ,1 16019565684.0,2021-04-20 20:41:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in typeofsleepcarepage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos new appointment components typeofsleepcarepage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 14971476534.0,2021-01-27 21:12:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, wizard content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to the wizard tasks update the fsr s ui in sketch with the modified content acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 24848513144.0,2022-10-26 17:54:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,various discrepancies between huron and sharepoint fsr submissions issue description ashlie provided a list of various discrepancies between sharepoint submissions and what they ve received on huron tasks use provided ids to determine possible cause communicate with necessary teams to see source draft document response about discrepancy reasoning s acceptance criteria response about submission discrepancies has been provided to huron how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20885017940.0,2022-03-23 03:25:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, combine vet center tracking lists development chart graph story resources vamc report tasks combine reports for vet center tracking develop graph and chart for reporting acceptance criteria document that has merged data draft chart that can be used in reporting,1 13644430016.0,2020-09-25 18:52:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move express care components to express care components folder move our ec components to the express care feature folder also update the tests folder to reflect this ,1 31168191315.0,2023-08-16 21:40:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, staging review design feedback design components or patterns don t align with design system guidelines platform issue design components or patterns don t align with design system guidelines issue details on the employment list and loop when there is more than card they are stacked directly on top of each other with no margin padding link screenshot or steps to recreate screenshot va gov experience standard category number issue number other references wcag sc aa platform recommendation be sure you are using the card component with the appropraite margin padding ,1 11701659914.0,2020-03-06 20:10:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consolidate route table configuration user story or problem statement while doing the cutover for the transit gateway work i noticed that we had separate route tables in aws for some reason for each az but they all seem to be identical how might we consolidate these into a single entity so we don t have to update multiple and potentially cause conflicts between them per vpc goal de duplicated route table configuration objectives or key results this is meant to further enable agile vfs delivery of performant applications acceptance criteria route tables that are copies of one another should be consolidated into a single entity dev utility staging prod how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 24758907222.0,2022-10-21 20:51:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint october sprint goals continue to monitor and resolve issues related to the live fsr for vha in production finalize review page designs finalize other living expenses design wireframes draft streamlined waiver user flow list loop enhancements front end development lighthouse api discovery for cdw connection for veteran payment data turn vbms letter downloads back on in production after pii audit update wizard for medical copay path and inclusion sprint deliverables list of deliverables completed during sprint n a planned issues combined fsr enhancement continuous add credit card bills pt investigate removing cross app references from fsr pt research plan review for enhanced fsr pt design for fsr review page pt move fsr api submission logic to background job pt content of additional information in fsr is getting cut off pt checkbox to input boxes enhancements pt break up funding for va notify requests pt combined multiple last names for valid fsr filename current employment not populating in vha fsr updating urls that link to vha fsr define copay path uxpin text updates other income populating for veteran spouse update medical copay wizard path fsr enhancements enhancement continuous add employment history pt ia content edits to other expenses pt streamlined waiver user scenarios flow for streamlined waiver discovery mcp notification tbd view payment history work with lighthouse team to determine real time data next steps pt other toggle vbms letter downloads on unplanned additions will be added throughout the sprint as identified capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished tbd points over tbd issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 30506354661.0,2023-07-18 17:11:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create mobile friendly efsr mockups to test in streamlined waiver transparency study issue description we re working through the streamlined waiver draft copy and updated review page designs and we will be needing mobile friendly mockups of at minimum user flows automatic waiver decision and manual fsr the pages we will need are updated intro page first sections all will see work history income assets additional sections updated review page updated review page editing capability confirmation page tasks updated intro page first sections all will see work history income assets additional sections updated review page updated review page editing capability confirmation page acceptance criteria mockups have been created how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13936501478.0,2020-10-22 13:01:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,test research possibility of switching to centos for underlying ami base layer instead of amzn linux issue description test for issues possibility of moving from amazon linux base ami layer to centos due to issues found with amazon linux python ansible there would essentially no best practice compliant way to get rid of python entirely while using amazon linux and ansible this ticket is to track some testing any findings for the possibility of moving over to centos for our ami base layer tasks switch to centos base ami layer in another branch and test out some jobs to see if what issues arise acceptance criteria centos properly tested with numerous jobs and findings delivered back to team how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16604280920.0,2021-06-02 00:39:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, delete deprecated cms code while i was working through my pr to make graphql more efficient i was puzzled about some of the code i encountered and had trouble understanding what was its purpose it was complex basically it did a find and replace on certain values and i didn t understand why we didn t just use the correct value in the first place upon investigation the code was left over from a cms feature flag we should remove unnecessary complexity by delete src site utilities stringhelpers js and all references to it we ll get a graphql error if we do it wrong so it isn t high risk ,1 24282244543.0,2022-09-28 18:29:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content updates with addition of copays issue description text updates to enhanced fsr uxpin tasks compile list of text updates notes from uxpin gh discuss updates with danielle thurs make text updates acceptance criteria text updates approved by danielle text updates made on uxpin list of updates to make to be discussed in the future updates already made on uxpin ,1 23392696316.0,2022-08-11 19:30:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,improve maintainability of facility locator code we use codeclimate to perform static code analysis on our source code the following files have a grade of d or lower we should follow the suggestions here and improve our grade to at least a c ,1 12395029056.0,2020-05-20 17:55:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters create preliminary designs landing page problem description after conducting interviews designs need to be created to present relevant information to the veteran who have incurred debt goal create preliminary designs based on data gathered in interviews tasks crete designs acceptance criteria preliminary designs for landing page will be created how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30636837307.0,2023-07-24 18:27:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, product outline for streamlined waiver issue description review and make any necessary updates to product outline streamlined waiver process tasks discuss updates with team make any necessary updates acceptance criteria product outline updated and reviewed by team ,1 22099323815.0,2022-06-01 12:39:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, make styling consistent throughout app issue description update the margins styling across all three cdp apps some class name and other stylings are duplicated from the combinedportalapp down and we should probably update them to a more manageable state this should include the loading modals we have sprinkled throughout tasks loading modals are rendering in a uniform location margins styling are uniform throughout cdp still matching mock acceptance criteria cdp has uniformed styling throughout how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25280480330.0,2022-11-16 15:27:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint november sprint goals fsr background processing for successful submission update vanotify template names to better reflect integration of medical copays integrate checkbox inputs to fsr for monetary assets enable continuous add for fsr employment history section integrate platform feedback for mini summary and va benefit edits establish user flow for streamlined waiver define personas for streamlined waiver including various paths through user flow update content as part of phase updates veteran information required text placement and screen adjustments resolution option explainer for enhanced fsr refactor fsr endpoints and logic to move into debts api module investigate intermittent errors due to missing edipi values with staging copay users sprint deliverables list of deliverables completed during sprint midpoint review planned issues combined fsr refactor the fsr endpoints and logic to be moved into the debts api module backend pts move fsr api submission logic to background job monitoring currently blocked be pts fsr enhancements checkbox to input boxes enhancements monetary assets frontend checkbox to input boxes enhancements spouse other income frontend fsr review page updates design update template names for dmc notifications be pts veteran information required text placement screen adjustments enhancement continuous add employment history frontend content changes part frontend resolution option explainer enhancement frontend list loop improvement for summary and va benefits frontend allow for successful submission page with fsr background processing backend pts other intermittent with staging copays users backend pts unplanned additions will be added throughout the sprint as identified capacity planning pto holiday s denise scott brandyn andrew megan brie nov veterans day points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 27722402974.0,2023-03-14 21:52:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,uat testing with dmc api change issue description dmc is adding an api change for handling file not found responses and requires us to use a couple file number examples to test found letters no letters and no file number tasks sync with dmc engineering team to test via curl api requests take responses from api tests and test data against the portal acceptance criteria dmc can move forward with releasing their api change how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24029952797.0,2022-09-15 14:21:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove research support in vfs facing di and mpr guidance user story as a vfs team member i want to know what practice area feedback i ll receive at design intent and midpoint review so that i am able to better prepare for those touchpoints and manage my teams expectations assignee peer reviewer description due to clayton zook s departure on wednesday governance team is no longer able to provide research focused feedback at the design intent or the midpoint review because of this we need to update our vfs facing guidance on platform website so that vfs teams are not expecting to receive feedback in addition because clayton is no longer involved in the research review octo de is once again the owner of the research review touchpoint this ticket will also ensure that vfs facing guidance is updated to show that governance team is not involved in the research review touchpoint impacted artifacts touchpoints page image from others tasks review platform website collaboration cycle and identify all the areas where we specify that research feedback is provided at di and mpr note research review is still part of the collab cycle so references to research support are ok it just needs to be removed at specific touchpoints link all impacted pages above in the impacted artifacts section ensure all references to research support are removed from design intent guidance ensure all references to research support are removed from midpoint review guidance note if changes are made to either the di or mpr script the script needs to be modified on platform website and in the moderator responsibilities docs peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs teams do not expect to receive research feedback at design intent and or midpoint review vfs teams understand that octo de not governance team is the owner of the research review touchpoint how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 27238355382.0,2023-02-21 18:05:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,establish swagger doc for vbs mcp new statement notification issue description during weekly touchpoint with vbs to progress mcp notification for new statement work forward we identified the need to establish a swagger doc this doc should contain info about the endpoint such as endpoint name headers body body attributes tasks build a swagger doc and share with vbs name endpoint determine needed data for endpoint document data specify json fields within body file acceptance criteria swagger has been established and shared with vbs team how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22358028099.0,2022-06-15 17:29:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move screen reader research guidance and check list to platform user story as a vfs researcher i want all the important guidance i need in one location that i know to be source of truth so i don t have to hunt for it and so that i know that i m getting the latest guidance as platform governance team i want make sure researchers have access to important information on platform since it is source of truth for research guidance intended audience vfs teams desired outcome guidance moved to platform and marked deprecated in gh due date description this ticket and ticket shall be worked on at the same time researching with participants who use screen readers requires different considerations there is some but if this guidance is important enough for vfs researchers to reference it s important enough to be on platform as the source of truth new artifacts new page for researching with participants who use screen readers artifacts needing updates tasks decide where on platform this information should live has been created and maintained by notify josh of the intention to move to platform website verify with that all content within the existing gh page is current and up to date acceptance criteria platform website has been updated with information about screen reader participants gh page has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 27015489232.0,2023-02-10 18:57:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create backup prototype for user research issue description a backup prototype is needed for user research in case a participant is not able to access the fsr on va gov because of timing and limitation in access to prototyping software this prototype will only be available as a desktop prototype and will not include every section of the fsr form tasks discuss what to include on this simplified prototype make any necessary input field updates to prototype add interactions to prototype test prototype acceptance criteria prototype is created prototype has been tested by the team ,1 30797114290.0,2023-07-31 20:50:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, finalize conversation plan on github issue description ensure format of the conversation guide matches tasks ensure research plan contains all sections on add conversation guide to gh acceptance criteria conversation guide up on github link here ,1 14238619316.0,2020-11-18 18:53:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,content for fsr from error messaging for validated fields create content fo error state for validated fields in fsr definition of done review with peggy provide content to fe,1 16628893624.0,2021-06-03 13:17:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and correct duplicate named facilities and incorrectly associated health services story as a veteran and web maintainer multiple facilities with the same name need to be associated in a unique way so i can determine the correct facility and health service in my health care journey goal make all duplicate names unique by associating them to the correct health system task review all duplicate facility names across systems and visns and make them unique by associating their name to the correct system find duplicates and document their facility ids associate those facility ids to the correct system work with cms team to have the facilities associated to correct system so their names become unique in drop down determine if any facility health services are incorrectly associated and move them to the correct facility acceptance criteria all duplicate facility names will have associated system name in drop down so they are no longer confusing or lost re associate any incorrect health services to the correct facility ,1 20405349917.0,2022-02-23 04:15:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, menu maintenance to move all level menu items to level work with vha dm on comm story as a veteran i need all web pages to be easily searchable on the left nav so i do not have to click through more than four depths to find the page i need resources tbd tasks review and document all menu items that exceed to levels on the menu document the corresponding bread crumb path url and the proposed new url that needs to be used when moved work with pm to send out communications that depths will be changing work with ia to submit redirect urls once redirects are in place move all of the menu items to correct th level acceptance criteria document is created so redirects can be submitted separate issue ,1 13233275596.0,2020-08-18 14:34:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consider refactoring pciu and pciuaddress using the same name space when evaluating acronyms in this ticket it was identified that pciu is not being used consistently and would clear up the code if that was sorted out there s even a pciuaddresslinevalidator not using the pciuaddress namespace ,1 15836927790.0,2021-04-06 20:02:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add a request number to confirmation page issue description in usability we found that veterans expect a request number or confirmation number on the confirmation page of the fsr add these to the designs tasks add a confirmation number to the designs and sync to uxpin create a fe ticket to complete this task acceptance criteria uxpin updated and linked below fe ticket created and linked below,1 14381312481.0,2020-12-02 05:05:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review of the contact us pages for visn user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation tasks complete review of contact us top tasks call to action across all visn systems listed below and document and report any issues that may need to be fixed use the following guidance does this content field data in this page make sense does the content field data in this page relate to this system level or specific to a facility is it in the right place based on system facility pages for the veteran to find how does this help with the focus of the page confirm the altoona va butler va coatesville va erie va lebanon va philadelphia va wilkes barre va wilmington va acceptance criteria all top task node pages have been reviewed in spreadsheet and issues found have been been documented issues have been documented and escalated for resolution using vamc support channel and spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 24674460152.0,2022-10-18 15:53:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content changes issue description update content changes to reflect what the mockups show tasks confirm which feature flag this should be behind this front end update was already made add tsp clarify brokerage account for stocks and bonds need help with debt related to va benefits or health care copays estimated value of all of your this includes vehicles with a loan this includes properties with a mortgage list of updates global new breadcrumb text home  ›  manage your va debt   ›  request financial help va form global new header request help with va debt for overpayments and copay bills global need help section change va debt to va debt related to benefit overpayments make sure to include the tty in the aria label too follow these steps to request help remove with va debt or bills change take any needed next steps to resolve the debt or bill to take any needed next steps to resolve the overpayment or copay bill this form is for veterans or service members who need help with debt related to va benefit overpayments or health care copays past years change two to per style guide past years change two to per style guide change the following to these change regarding your request to on your request past years change two to per style guide past years change two to per style guide change the following to these change bill s to bill change the following expenses to these expenses change the following to these change the following to these remove below remove the around this s change one medical bill below to one medical bill here change debt below to debt here change amount debt to amount overpayment change regarding your request to on your request delete in order change we will to we ll change you re unable to to can t for simplicity and active voice change we will to we ll change you re unable to to can t for simplicity and active voice change please click on to select change to login gov id me ds logon or my healthevet change once you re signed in to after you sign in controlled by platform acceptance criteria all content changes match markup how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23032065503.0,2022-07-22 14:48:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design components or patterns don t align with design system guidelines general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers allison christman design for more information on how to interpret this ticket please refer to the guidance on platform website platform issue design components or patterns don t align with design system guidelines issue details the va debt letter history table is misaligned in the second column link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation the title of the debt letter should be top aligned with the date vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 25314110009.0,2022-11-17 20:00:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint november sprint goals • align with design intent team on the direction for card design on mini summary and va benefit pages • midpoint review for fsr enhancement release • merge streamlined waiver personas with scenario paths • define wireframe for one streamlined waiver path • submit platform request to configure redirects for legacy mcp and debt letter pages • finalize fe dev for employment history • text placement and screen adjustments in fsr • enhancements for veteran contact information • address compromise amounts not seen on dmc endpoint • resolution option explainer enhancement sprint deliverables list of deliverables completed during sprint user flow for streamlined waiver experience draft of initial wireframes streamlined waiver midpoint review planned issues combined fsr refactor the fsr endpoints and logic to be moved into the debts api module be pts fsr enhancements content changes part fe pts list loop improvement for summary and va benefits design pts fsr review page updates design pts update template names for dmc notifications be pt veteran information required text placement screen adjustments fe pt enhancement continuous add employment history fe pts card discussion with design system team design pt veteran contact information enhancement fe pts resolution option explainer enhancement fe pts other unplanned additions will be added throughout the sprint as identified capacity planning pto holiday s denise scott brandyn andrew megan brie nov thanksgiving day points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 21902401548.0,2022-05-20 14:35:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,look into why the tests for on site notifications have to be skipped for the ci the tests from had to be skipped they worked perfectly locally but in the ci it refused to pass we tried every tactic in the book we think to get it to pass but we couldn t get it to fail locally to reproduce it ,1 30320300843.0,2023-07-10 18:41:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display other income issue description add additional income for veteran and spouse otherincomesummary spouseotherincomesummary as view only on the final review page can likely leverage a custompagereview similar to how utilitybillsummaryreview is implemented only show the values that have been populated see for copy tasks implement read only display on final review page veteran values spouse values acceptance criteria additional income values are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24849297210.0,2022-10-26 18:33:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, bug combined fsr failing to submit when no debt is selected issue description fsr is failing to submit if only copay and do debt is selected tasks fill out submission object using new array when feature flag is true acceptance criteria fsr submits if only copay is selected no debt how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30700395998.0,2023-07-26 22:34:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, sw create example submission objects for be issue description since streamlined is cutting off some of the form we need to create examples of submission objects for the different routes so be can adjust the required fields let s see if we can work out specific flags for each path that way we have established expectations for each and it will hopefully make troubleshooting any problems easier tasks create example submission objects for each fsr path for streamlined waiver maximal object minimal object acceptance criteria be has submission examples for new sw flow how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 19100581224.0,2021-11-29 21:59:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,does profile need to call the get full name or get personal information endpoints investigate if the profile needs to call get full name or get personal information it seems that get user gives us that same data example response from get full name json data id type hashes attributes first wesley middle watson last ford suffix null example response from get personal information json data id type mvi models mvi profiles attributes gender m birthdate get user gives us similar info the only potential gap is the name suffix which i m not seeing as part of the get user response but i need to find an example of a user that has a suffix to confirm json data id type users scaffolds attributes profile birthdate gender m vaprofile birthdate familyname ford gender m givennames meta errors null if there is no reason to call these endpoints our code should be cleaned up to use the data from the get user instead ,1 27744819955.0,2023-03-15 16:21:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, mini summary card component issue description create a reusable react component to display edit delete items in a list to be used for the mini summary pages component needs to take in header text content and event handlers for edit and delete delete button styling may be tricky as it includes some custom stuffs functionality is more important than styling here since other tickets depend on this so we can always circle back with a styling ticket to update tasks create reusable component test functionality acceptance criteria component matches design and functionality how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14966712580.0,2021-01-27 14:53:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove was va or a mortgage company involved in this bankruptcy question from bankruptcy page issue description since we are not able to provide file upload capabilities we will be removing the question of was va or a mortgage company involved in this bankruptcy until a better solution for this requirement emerges tasks remove was va or a mortgage company involved in this bankruptcy from the ui acceptance criteria was va or a mortgage company involved in this bankruptcy removed from ui ,1 22103272595.0,2022-06-01 15:09:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, defect consider using ul and li elements for the cards list general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers josh kim joshkimux accessibility platform issue no va gov experience standard for the issue found issue details currently the list of balance cards are coded as div s with nested s as this is technically a list of cards the markup could be improved by using semantic ul and li elements instead of div elements link screenshot or steps to recreate va gov experience standard other references platform recommendation consider writing the list of balance cards using ul and li elements instead of divs for example html some screen reader users will benefit from having the list announced to them as a list as they ll receive information on how many balances exist and what balance they re currently on for example for list item of vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 23723233586.0,2022-08-30 17:06:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,stop duplicating redis data in vets api to the secondary redis the problem we are still duplicating vets api redis data for both dev production we want to undo this now that we have successfully migrated to the vagov redis elastiache extra context duplicating redis data was done as a way of migrating all of the vets api redis data from vetsgov to vagov a k a vaec we basically want to undo everything that was done in this pr this can be thought of as the clean up part of work to be done delete the duplication logic that lives in vets api see initializers redis tb remove all occurances of settings redis app data secondary url ,1 18457052189.0,2021-10-15 17:57:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,document mcp launch plan technical task we need to document a launch plan for medical copays so we know what to do when launch times comes document our launch approach what we will do if errors come up and how we might stagger release to midigate risk expected behavior launch plan for medical copays is documented acceptance criteria mcp launch plan is documented launch plan is added to security documentation launch plan is added to product documentation ,1 23394661097.0,2022-08-11 21:36:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint august august sprint goals fsr enhancement usability research discovery draft fsr enhancement usability research plan fsr streamlined waiver wizard design discovery create combined selection array and conditionally render copay debt resolution options create tests for copay resolution options benefit debt resolution option update open security review process for vha sharepoint determine source of gmt threshold data and appropriate access points use pdf functionality to create pdfs for vha fsr create record upon fsr submission create activemodel for fsr submissions sprint deliverables list of deliverables completed during sprint initial draft of research plan for fsr enhancements planned issues combined fsr open security review process for vha sharepoint benefit debt resolution option update copay debt resolution option update use pdf functionality to create pdfs for vha fsr create record upon fsr submission create activemodel for fsr submissions create combined selection array and conditionally render copay debt resolution options create tests for copay resolution options create tests for debt resolution options mcp notification n a fsr enhancements fsr enhancements research discovery streamlined waiver fsr streamlined waiver wizard design discovery determine source of gmt threshold data and appropriate access points unplanned additions tbd capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline coming soon use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff n a tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 14004603793.0,2020-10-28 17:18:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch bankruptcy hifi design as a veteran filling out the fsr form i want the ability to give dmc information about my bankruptcy ,1 20153932854.0,2022-02-09 14:53:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review sme interview and draft additional questions issue description we met with thuy to start learning about if and how cerner statements may impact mcp s ux we need to review the interview and document outstanding questions to dictate an additional interview tasks review adjust interview guide with remaining questions acceptance criteria the discovery document has been linked to this ticket after being reviewed and adjusted,1 23718621431.0,2022-08-30 13:44:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, investigate ga for payment options issue description it would be helpful to track when users jump from the combined portal to a payment page overview or deails page to see if we can put the link in a more common place to make payment easier for those accustomed to the process tasks investigate ga tracking options for payment links include new ga tagging options acceptance criteria determine if this type of tracking is already done platform pay side and if we can implement how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27643622486.0,2023-03-10 20:28:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add va gov email to slack profile guidance user story as a team member working on or in support of va gov i want to be able to access general profile information including va gov email addresses of my colleagues in slack intended audience octo de platform vfs teams desired outcome updated profiles with va gov email due date n a description related to adding va gov email address to slack profiles consensus was that va gov email address is potentially helpful information and we should add it to our orientation materials artifacts needing updates tasks add va gov email to list of information to add to slack profile in github orientation ticket general add va gov email to list of information to add to slack profile on platform website slack profile guidelines acceptance criteria github orientation ticket template has been updated platform website slack profile guidelines has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 13926526380.0,2020-10-21 18:25:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres form submit be integration once the fsr form is submitted the form data needs to be posted to dmc endpoint the json needs to contain the data fields that is currently in the paper form ,1 15836086960.0,2021-04-06 18:50:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,compile content for debt letters debt letter history section issue description compile content for debt letters debt letter history section for fe to implement for initial release assess tasks create a document with diary codes and content for the debt letter history section of debt letters create tickets for improvement work acceptance criteria document created and linked in this ticket and provided to fe improvement tickets created and linked in this ticket ,1 31844788207.0,2023-09-14 19:02:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr final review page updates product outline high level user story ies as a i need so i can hypothesis or bet if we make this change then we expect this to happen okr which objective key result does this epic push forward definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 15833995223.0,2021-04-06 16:15:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,set up google analytics for fsr analytics will not be supporting domo until june we need to set up google analytics to get data for fsr once it goes live see for google reference access to ga we need to be able to get data for all the events outlined in domo ticket from ga ,1 20120989711.0,2022-02-08 02:16:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove homepage refresh toggle item description the homepage refresh changes are live and in sustainment the non refresh code was removed in so we need to remove the flipper control in the admin tasks remove fe va online scheduling homepage refresh toggle remove be va online scheduling homepage refresh toggle acceptance criteria functionality remains the same as when the toggle is true flipper no longer appears in the admin ui definition of done all tasks are complete all acceptance criteria are met ,1 14172971289.0,2020-11-12 17:40:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch confirmation hifi desgn as a veteran who filled out the fsr form and submitted the form i would like to see a confirmation that the form was submitted and what i should expect next,1 16431630975.0,2021-05-20 02:58:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, resolve tech debt of the covid vaccine detail pages for systems listed and update shs link story as a veteran i need to know the latest information and guidance regarding covid vaccines so i will know how when and where to schedule and get my covid vaccine goal provide a nationalized local detail page for all sites task determine which source of truth to utilize for cloning the covid detail page clone covid to system missing the detail page update page to reflect new system governance on edit screen document url node to make line task easier go to covid vamc system health service and update update link use node from line two or look up using covid vaccine to point to new covid vaccine detail page complete for the following visns and systems visn va asheville health care va durham health care va fayetteville coastal health care va hampton health care va richmond health care va salem health care va salisbury health care visn va atlanta health care va augusta health care va birmingham health care va central alabama health care va charleston health care va columbia south carolina health care va dublin health care va tuscaloosa health care visn va bay pines health care va caribbean health care va miami health care va north florida south georgia health care va orlando health care va tampa health care va west palm beach health care visn va alexandria health care va central arkansas health care va fayetteville arkansas health care va gulf coast health care va houston health care va jackson health care va shreveport health care va southeast louisiana health care acceptance criteria all listed systems have an updated covid detail page and align this with the system link in covid system health service links to new covid vaccines page locally ,1 24579966510.0,2022-10-13 14:56:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,future enhancement considerations issue description capturing all future use case and enhancements that haven t boiled up to an initiative yet as they are still under consideration at the point when we are ready to dig into it an epic will be created and it will be filtered onto the roadmap ,1 15838047611.0,2021-04-06 21:45:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,content feedback fsr form prototype user story provide content feedback on mockup of financial status report form ,1 25574028843.0,2022-11-30 20:17:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, investigate how to log issues in sentry as debug vs error level user story as a cie engineer i wish to be able to search on upstream error statuses and messages from chip and lorota so that i can set up granular alerting background tasks identify the errors we want to log in sentry as debug vs error level investigate in vets api how to log issues in sentry as debug vs error level ,1 19704067131.0,2022-01-12 19:46:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, list loop redesign real estate assets issue description because list loops did not test well in the fsr we need to investigate alternative directions for the fsr s design once ideation is complete we will take the final outcomes from our presentation and compile it into a more fleshed out wireflow spec for approval by our stakeholders this ticket captures the design work for the real estate assets rework tasks create a spec for the real estate assets acceptance criteria the spec has been uploaded and linked in this ticket ,1 17266498390.0,2021-07-22 14:22:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr send signature fields to fsr on submission description be need to receive signature value from fe so we can generate the signature on the pdf and pass that payload to the dmc so they can generate pdf ,1 23591058402.0,2022-08-23 15:13:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create activemodel for fsr submissions issue description db table has been created in the api and we need a model to be associated with the table tasks create a model acceptance criteria we have a model the api can reference for forms how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12522117320.0,2020-06-03 18:35:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, back end validation errors on our end should be more descriptive issue description when our front end submits to our back end before submitting to evss fail we should provide better error messaging since this will not show up in the back end sentry logs acceptance criteria rich error messaging pre submit to evss lh etc how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20154854370.0,2022-02-09 15:35:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,pre need replace additionalinfo with va additional info description the pre need form still includes the deprecated additionalinfo component it needs to be updated to use the va additional info web component tasks replace additionalinfo with va additional info update tests definition of done all tasks complete all tests passing ,1 15596679528.0,2021-03-18 16:06:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,make helper for testing that api calls are made or not made code is repeated in a few tests js await wait const fetchcalls global fetch getcalls make sure we are fetching info expect fetchcalls some call return call args includes profile bank accounts to be true make sure we are fetching esr data expect fetchcalls some call return call args includes health care applications enrollment status to be true we should make a helper function we can use in tests to make things a little more readable maybe something like shouldcallapi health care applications enrollment status and also shouldnotcallapi messaging health folders ,1 16488226691.0,2021-05-24 21:31:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr announcement verbiage craft messaging to add to debtman home page announcing new experience ,1 30693081027.0,2023-07-26 16:27:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,upload lost vha fsr forms to sharepoint issue description what details are necessary for understanding the specific work or request tracked by this issue tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18525069634.0,2021-10-20 19:25:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,pre launch checklist for mcp checklist kick off design intent analytics i a usability prep research review mid point review privacy and security review staging office audit contact center review,1 12559234352.0,2020-06-07 18:19:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters your va debt page high level user story ies as a veteran who has incurred debt and received a debt letter i would like to be able to to see how i incurred the debt hypothesis or bet veterans only know about their debt because they get a debt letter which is hard to understand and may be misplaced or lost our bet is if we make the debt information available on line and easy to understand the veteran are more likely to resolve the debt definition of done the veteran must authenticate to reach this page the amounts displayed must match the amount provided in the mailed letters the cards must contain the name of the debt the date incurred must be displayed for each debt viewable on the cards the veterans should be able to click through to see additional details page must meet accessibility requirements ipage must provide next steps on how to resolve debt take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 25103601460.0,2022-11-08 15:11:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, checkbox to input boxes enhancements monetary assets issue description add checklist to box functionality in fsr for the monetary assets example of functionality tasks add checkbox to input functionality for pages listed above acceptance criteria new page formats are functioning as expected and match design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16061702869.0,2021-04-23 13:26:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove code switching between vsp fhir endpoints and var resources we have some code that passes a vsp feature flag around and switches services between vsp and var resources given that we re migrating to the vaos service and moving to a fhir api is very far in the future it s not useful to have this code lingering and making things more complicated ac removed all vaos vsp feature flags from featureflagnames js and vaos selectors removed usevsp parameters in services files and remove any branches that were called when usevsp was true,1 20620415645.0,2022-03-07 16:53:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update configuration of fsr confirmation email to send from dmc service issue description to separate out teams from having access to all email templates va notify has sectioned off templates by team and this template has been allocated to the dmc team tasks receive api key from va notify team over keybase add key to aws param store and devops repo update config to have entry way for va notify using key update code to initialize notification service with new dmc key acceptance criteria the template is being sent out from va notify via dmc connection how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12235894958.0,2020-05-04 15:32:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters api integration user story or problem statement as a veteran who has incurred debt i need be able to see the source of the debt and options to remediate online so i can take action on next steps goal ability to display the information the veteran received in mail online from api tasks json schema from api display values for a give test user acceptance criteria for any given the user the values retuned in api can be captured and displayed how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13261598459.0,2020-08-20 20:11:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review and refactor form profile spec this spec uses so many contexts and helper methods it s hard to understand any given test discovered this when a new to ruby developer wanted to add a simple test and just created a let block but that didn t test anything ,1 13886481864.0,2020-10-19 00:50:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove redundant profile logic after profile is launched description on september we launched profile to all users we need to clean up all unneeded components logic that are no longer needed to support profile pay extra attention to the mailingaddress and residentialaddress components as they might be used in other applications this is ticket of the steps to remove profile ticket remove profile feature flag ticket identify dead code related to profile and remove it ticket reused code of profile in profile needs to be moved to the profile folder renaming of components logic where needed tasks validate that any profile logic is not shared with other applications move any shared logic with profile underneath the profile folder remove all unused components remove all unused reducers actions constants utils assets remove all related unit and tests ,1 27709190367.0,2023-03-14 13:15:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vehicle page enhancements issue description this design should follow but include the new vehicle addition page design remove existing vehicles list loop and implement new input number of functionality tasks add the following pages mini summary page new vehicle inputs show list in final review page update efsr specific testing include item removal and addition acceptance criteria page matches design and functionality all new and existing tests are passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22099755889.0,2022-06-01 12:57:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, clean up duplicate code caused by merge issue description some functions were duplicated while developing updates in separate apps this ticket is meant to capture the effort of removing duplicated code and cleanup messy references that may have been leftover during the merge tasks move renderalert to combined folder check for other duplicate code caused by merge acceptance criteria cdp is free of duplicated code caused by merge,1 24557746760.0,2022-10-12 17:19:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, fsr enhancements research discovery issue description this ticket is for research discovery for the fsr enhancement release tasks review previous fsr research exploring how to build on that research and compare new research to issues seen and changes we have to improve the experience review and changes to guide research questions sync with other designers working on list loops draft the research plan denise will add the link watch recording of riley showing ux prototype review to understand what changes are we making review that describes why these changes are important and why original list loop implementation wasn’t successful acceptance criteria the draft research plan has been added to gh and linked in this ticket ,1 24511032293.0,2022-10-10 21:30:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add instructions to how to provide feedback guidance for removing cc request label user story as a governance team member i want to ensure that feedback tickets do not have the cc request label so that tickets do not populate on our collaboration cycle reviews zenhub board or slack notifications assignee cherylevans peer reviewer jimuhh description when creating feedback tickets in the collaboration cycle reviews zenhub board it will automatically add the cc request label this will cause feedback tickets to display on the zenhub board and also notify us in slack with the integrations completed in we want to add guidance to remove this label so that our board and slack only show relevant tickets remove governance team label as well impacted artifacts tasks add bullet under to remove the cc request label if and only if they create the ticket using the new issue link from the collaboration cycle reviews board add bullet under to remove the cc request label if and only if they create the ticket using the new issue link from the collaboration cycle reviews board add bullet under to remove the cc request label if and only if they create the ticket using the new issue link from the collaboration cycle reviews board remove governance team label as well peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria instructions are provided for removing the cc request label from future feedback tickets reviewers are aware of the scenario that will automatically apply the cc request label how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 16173854860.0,2021-05-03 00:16:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create training delivery for fsr we train all call center representatives on our products in live sessions create training presentation for minutes which will include live demo to follow along with guide training should incorporate why we built this product how we build products veteran research usability etc screenshots of pages veterans will see chapters any potential error states,1 16195156434.0,2021-05-04 13:46:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in typeoffacilitypage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos new appointment components typeoffacilitypage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 28005726670.0,2023-03-27 15:08:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, credit card bills enhancements issue description create new credit card bill pages that match yes no input page mini summary tasks create necessary pages yes no input mini summary update tests unit update maximals minimals as necessary acceptance criteria new pages added and match design all tests passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26393480879.0,2023-01-12 17:23:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,temporarily remove accessibility office hours from platform website user story as a vfs team member who needs accessibility help i want to get accurate information about where to go for informal help so that i can get useful feedback and not be stuck in a zoom meeting by myself waiting for someone to show up assignee briandeconinck peer reviewer cherylevans description as a result of contract shuffling angela fowler is currently not on a va contract and is no longer holding accessibility office hours the remaining accessibility specialists are interested in continuing office hours but we haven t figured out scheduling who will be responsible etc until we get that figured out the links to join and rsvp accessibility office hours should be removed from the platform website office hours page they should be replaced with a note indicating that the future schedule for office hours is tbd and in the meantime vfs team members should attend collab cycle office hours for accessibility help impacted artifacts tasks links to zoom and calendly have been removed for accessibility office hours tbd message pointing people to cc office hours added peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria vfs teams are informed of the current applicable office hours offered by platform how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 13221454163.0,2020-08-17 14:04:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore separating server state from ui state a lot of the redux logic in vaos especially in the new appointment flow is basically fetching the server data and appropriately caching it in the redux store for current later use some more modern react state management approaches advocate separating out server data state from ui state it s worth exploring what separating that state out from redux would look like there are libraries like swr and react query that do this through a hooks interface there are also likely plain js caching solutions we d want to know how much page weight does adding a new library for this add is the code clearer than the current action thunk based code can we access the cached data outside of react or is it easy to pass it from react components to places we need one other concern i have is this pushing us toward a model where react touches nearly all of the logic in the application and we don t really have application layers anymore ,1 18422891535.0,2021-10-13 18:11:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,log dfns of authenticated va gov users description create a logger and log the prospective dfn of users who sign into va gov this is to get a set of real world dfns that we can validate the structure of and eventually validate against vbs s data set have this run on a feature toggle so we can control the duration of logging,1 17703766777.0,2021-08-25 03:45:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update lgbtq and suicide pages with new updates from sot visn user story as a vha digital media web manager the national changes need to be implemented prior to dual state or full production launches so the systems are updated adequetly prior to the redirect goal remove tech debt prior to full production resources tools documentation tbd tasks update lgbt with lgbtq and suicide pages with new content and organize page correctly update suicide pages with correct format order and new content change out lgbt with newly authorized lgbtq in locations provided by content complete for the following locations va asheville health care va durham health care va fayetteville coastal health care va hampton health care va richmond health care va salem health care va salisbury health care acceptance criteria suicide pages are updated and if caregiver is not listed on page it is reported in support channel lgbtq pages are updated and if caregiver is not listed on page it is reported in support channel ,1 17269163437.0,2021-07-22 17:20:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,test debt letters downtime message description on dmc will be down for a minute period see test the functionality in place for debt letter for handling errors when dmc cannot be reached a c research to see if we have maintenance windows in pager duty for dmc dmc does not have maintenance windows configured we will be implementing maintenance windows and use them for the outage understand if dmc has breakers configures mock a service outage and ensure the frontend renders a tolerable experience ,1 25568948159.0,2022-11-30 16:12:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr list loop redesign issue description when veterans incur a debt with the va and cannot pay the full amount they re able to request financial help via the financial status report va form the financial status report fsr collects a snapshot of a veteran s monthly financial situation the form asks veterans to include a list of utilities assets etc to help veterans quickly add multiple items of the same category we designed a list loop component however the component tested poorly during usability research additionally the component is inaccessible to screen readers finally because the list loops are customized components they re tedious to update and contain many bugs the solution the fsr s ui has been redesigned to remove the list loop components this redesign will use patterns and components that exist in either va gov s experimental or established design systems the fsr s updated designs can be accessed in this uxpin prototype please note this is an in progress design as of the redesigned pages ,1 24051918983.0,2022-09-16 13:32:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create tests for debt resolution options desired behavior tests for debt resolution options should be created and passing for maximal and minimal acceptance criteria tests passing for maximal and minimal how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 14527699026.0,2020-12-14 15:39:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove prop spreading in contact components background there are quite a few opportunities to make our profile code more readable and maintainable we should take some time to invest in cleaning up code where we can since this will make it easier to debug and update our existing code saving us time in the long run and make us more efficient on the frontend we are passing in a large number of props to child components that are not used down the component chain using prop spreading it is also very unclear what props the component actually needs we need to remove this props and explicitly pass needed props to contactinformationeditview we need to remove this props in childprops and explicitly pass props in contactinformationfield in addition we need to remove props passed to contactinformationeditview where it makes sense to define their logic within the contactinformationeditview component itself tasks remove instances of this props reduce number of props passed to contactinformationeditview and determine what logic can live directly within that component,1 16814854178.0,2021-06-17 05:50:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, resolve tech debt of the covid vaccine detail pages for systems listed and update shs link story as a veteran i need to know the latest information and guidance regarding covid vaccines so i will know how when and where to schedule and get my covid vaccine goal provide a nationalized local detail page for all sites task determine which source of truth to utilize for cloning the covid detail page clone covid to system missing the detail page update page to reflect new system governance on edit screen document url node to make line task easier go to covid vamc system health service and update update link use node from line two or look up using covid vaccine to point to new covid vaccine detail page complete for the following visns and systems visn va bay pines health care va caribbean health care va miami health care va north florida south georgia health care va orlando health care va tampa health care va west palm beach health care visn va atlanta health care va augusta health care va birmingham health care va central alabama health care va charleston health care va columbia south carolina health care va dublin health care va tuscaloosa health care acceptance criteria all listed systems have an updated covid detail page and align this with the system link in covid system health service links to new covid vaccines page locally ,1 16015940203.0,2021-04-20 16:00:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in typeofvisitpage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos new appointment components typeofvisitpage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 19899100663.0,2022-01-25 04:55:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, menu maintenance to move all level menu items to level work with vha dm on comm story as a veteran i need all web pages to be easily searchable on the left nav so i do not have to click through more than four depths to find the page i need resources tbd tasks review and document all menu items that exceed to levels on the menu document the corresponding bread crumb path url and the proposed new url that needs to be used when moved work with pm to send out communications that depths will be changing work with ia to submit redirect urls once redirects are in place move all of the menu items to correct th level acceptance criteria communications are sent out to effected stakeholders document is created so redirects can be submitted separate issue document final urls for archive ,1 14227898558.0,2020-11-18 02:25:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters iteration vsa qa test plan please reach out to brad to turn on feature flag for product feature summary debt letters iteration builds on iteration in providing the veterans the status of their va debt the attached spreadsheet has all the debt statuses that could be encountered product team smes leave blank to implicitly refer to vsa master org chart linked above design research content ia mikki peggy front end brad back end cameron qa tze chiu lei proposed use cases and staging test accounts from vsa design lead important for authenticated experiences staging test accounts must be provided for all authenticated scenarios and staging api test data created to match the account specific scenarios how to configure this issue product manager added to assignees attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team vsa authenticated exp vsa benefits vsa benefits vsa caregiver vsa ebenefits vsa facilities vsa public websites etc definition of done actual test runs completed on staging created and tracked ,1 30694724165.0,2023-07-26 17:39:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,financial status report qa test plan test plan introduction the purpose of this test plan is to describe the necessary details to test the financial status report fsr application the application includes several features and each of them will be validated through end to end tests ├── cfsr cypress spec js ├── efsr validation cypress spec js ├── efsr cypress spec js ├── fixtures │ ├── data │ │ ├── cfsr maximal json │ │ ├── cfsr minimal json │ │ ├── efsr maximal json │ │ ├── maximal json │ │ └── minimal json │ ├── helpers │ │ └── index js │ └── mocks │ ├── copays json │ ├── debts json │ ├── mockuser json │ ├── profile status json │ ├── saveinprogress json │ ├── telephone update success json │ └── telephone update json ├── fsr alert cards combined cypress spec js ├── fsr alert cards cypress spec js ├── fsr contact loop cypress spec js ├── fsr fetchdebts fail cypress spec js ├── fsr fetchdebts filter cypress spec js ├── fsr fetchdebts success cypress spec js ├── fsr fetchfail cypress spec js ├── fsr fetchsuccess cypress spec js ├── fsr monthyear invalidyear cypress spec js ├── fsr wizard cypress spec js ├── fsr cypress spec js └── pages └── employment ├── employmentrecords js ├── enhancedemploymentrecords js ├── enhancedveteranemploymenthistory js ├── spouseemploymenthistory js └── veteranemploymenthistory js test items the application includes the following items that should be tested financial status report fsr contact loop fsr contact loop alert cards fsr alert cards fsr alert cards combined employment records employment features to be tested validation of fsr efsr efsr validation display of alert cards fetching debts success and failure scenarios validation of contact loop employment record management wizard functionality test cases the test cases will be described in the respective cypress spec js files test deliverables test plan document test cases test scripts in cypress test reports test tasks write test scripts based on the test cases defined in the respective cypress spec js files execute the test scripts analyze the results of the test execution and write test reports test environment the application will be tested in the environment where it is deployed using cypress for test automation test risks and contingencies there might be changes in the application which require the test cases and scripts to be updated it s also possible that some bugs will be found during testing the plan in such cases is to communicate with the development team get the issues resolved and retest the application approvals the test plan should be reviewed and approved by project stakeholders before test execution begins ,1 14915028505.0,2021-01-22 16:10:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, inventory metrics and alarms for sentry health checks background sentry was basically not sending any events on because of a queue overflow this has occurred in the months following without much real action to address the core issue we should ensure we have proper observability and monitoring for our utility tools such as sentry when the sentry client fails to receive event data for a suspicious period of time an alarm should trigger a page to the tools or operations team while discovering keep in mind these eventual requirements metrics are implemented based on sentry health so we can diagnose issues alarm is triggered to the triage team when sentry is not responding sentry documentation vsp facing includes details on what metrics track sentry instance health a simulated stoppage of events sent to sentry triggers alarm and page changes are documented and communicated tasks research and categorize what metrics are available for us document planned approach for implementing alarms based on historical performance create issues for the implementation of these metrics alarms and associated documentation ,1 22355657783.0,2022-06-15 15:26:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove calendly from title of orientation sessions page user story as a vfs team member i do not want encounter unfamiliar words in platform website title pages so that i can easily find the guidance that i m looking for intended audience vfs teams desired outcome remove reference to calendly in the orientation sessions page due date tbd description it has been reported that the platform website page calendly orientation sessions is confusing as not many people know what calendly is nor do they need to the page is a list of the orientation sessions with calendly being the tool used to sign up and the intent of the page should be clear from the title artifacts needing updates tasks remove calendly from title of of orientation sessions acceptance criteria title of calendly orientation sessions page has been renamed to orientation sessions updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 19908571620.0,2022-01-25 15:06:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html statement balance questions issue description add what if i have questions about my statement section to the html statement page refer to the for details tasks add what if i have questions about my statement section to the html statement page acceptance criteria what if i have questions about my statement section should render on the html statement page how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27318836369.0,2023-02-24 17:53:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update omb information issue description omb information for fsr needs to be updated with correct code and expiration date date omb tasks update omb information for fsr acceptance criteria omb info has been updated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24440099618.0,2022-10-06 14:04:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update unit tests for address edit how to configure this issue attached to an epic what body of work is this a part of related documentation description this should be an understandable description of the ticket this description should have enough context meaning that non technical team members should get the idea platform identified failing tests these tests are failing sometimes these tests should be updated to not fail tasks fix or update unit tests update relevant documentations readme use cases acceptance criteria tests are passing and merged into master,1 20623420286.0,2022-03-07 19:47:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add veteran facing alert to notify them of missing letters issue description as discovered in letters are not being sent from vbms after december as a result veterans are not able to download any letters after that date until the problem has been resolved dmc has requested that we add an alert to notify veterans who may be looking to download a letter that was sent after december this issue is for design to mock up that alert tasks mock up design for veteran facing pop up alert share with stakeholders for review acceptance criteria pop up is ready for fe development how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23450267811.0,2022-08-16 01:29:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined debt portal ptems qa test plan product feature summary providing veterans with a singular combined experience where they can see all of their financial matters in one place including va debts debt letters and health care copay statements product outline product team smes design research riley orr megan gayle content ia danielle theirry mikki northius front end andrew rodiek brandyn sullins back end scott james qa tze chiu lei proposed use cases and staging test accounts how to configure this issue product manager added to assignees attached to epic what body of work is this a part of possibly ongoing maintenance added product specific label if any definition of done product references provided by product team use cases provided for authenticated products staging test accounts and mock data set up for use cases above test cases finalized based on use cases above test runs completed on staging test reports generated these should be provided to platform at least workdays before see also relevant for details ,1 26776336114.0,2023-01-31 17:24:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,onboarding charlotte cesana background welcome we can use this ticket to track onboarding activity of new team members to the debt resolution team tasks meet your onboarding buddy set up github account if you do not already have one and share your handle with the delivery manager sign up for orientations ,1 12055509363.0,2020-04-15 13:06:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,front end behavior documentation approaches we need to come up with documentation for the behaviors implemented on the front end we have decent unit test and coverage and pretty sparse code comments it would be nice to come up with a coherent approach so that we can easily on board developers on the rest of the vaos team some possibilities our unit tests are the best documentation we have right now so perhaps a combination of some overview docs and more rigorous and descriptive test names cases write up a bunch of documentation in markdown on gh more extensive code comments,1 27110493185.0,2023-02-15 15:00:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove alert from download debt letter page issue description alert highlighting incorrect repayment plans can now be removed alert can be found on the debt balance letters page tasks remove alert component acceptance criteria alert has been removed and screen no longer appears in production how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23115548215.0,2022-07-27 16:20:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add introductory sentence to disability etiquette page user story as a vfs team member i want to know how interacting with research participants with disabilities may differ from other participants so that i understand how best to use the recommendations on the platform website disability etiquette page assignee jimuhh peer reviewer briandeconinck description platform content blocked the launch of the disability etiquette page child page of because it does not include any introductory text per laucon we feel the document needs an introductory sentence to explain what the document is about impacted artifacts tasks create a disability etiquette draft page add an introductory sentence explaining the purpose of the disability etiquette page submit for peer review peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria the disability etiquette page on platform website has an introductory sentence explaining what the page is for how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 14001890685.0,2020-10-28 14:10:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr modify conversation guide for vso conversations issue description modify the conversation guide for vso conversations so that we are asking the most relevant questions tasks modify the conversation guide upload guide to gh acceptance criteria guide uploaded in gh and linked to ticket ,1 30797120685.0,2023-07-31 20:50:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, finalize research plan on github issue description ensure format of the research plan matches tasks ensure research plan contains all sections on add research plan to gh acceptance criteria research plan up on github ,1 25281324407.0,2022-11-16 15:58:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,determine which external services have downtimes issue description determine which external services have downtimes that would apply towards tasks determine which external services have downtimes acceptance criteria understanding of which external services have downtimes and update how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11984262068.0,2020-04-07 15:36:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, errors discovery around error reporting logging user story or problem statement problem description how might we improve our use of sentry data or update our error logging to make it easier to identify when a veteran gets an error from the va gov website goal plan for greatly simplified digging and searching through error report data how do we correlate non pii data in the logs to an actual veteran ie is uuid actually pii tasks explore improvements to error reporting handling from our end explore ways to improve our sentry reporting scripts to parse through the logs weekly report generation automated etc acceptance criteria moar better logging error reporting document current error logging process tooling architecture how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24758735981.0,2022-10-21 20:40:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content changes issue description update content changes to reflect what the mockups show tasks confirm which feature flag this should be behind this front end update was already made add tsp clarify brokerage account for stocks and bonds need help with debt related to va benefits or health care copays estimated value of all of your this includes vehicles with a loan this includes properties with a mortgage acceptance criteria all content changes match markup how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25111199711.0,2022-11-08 20:42:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, react components in vaos background request the design system teams plans to deprecate the react components and will need to update any react components that is still active in vaos to the web components goal to research and see which react components still exists and needs to be upgraded to web components requirements to consider upgrading the react components with web components tasks answer the following questions time box hours definition of done tasks are complete research and recommendations are documented in this ticket ,1 27584218568.0,2023-03-08 18:24:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research plan review for enhanced fsr issue description research plan review for enhanced fsr tasks team reviews and makes updates to acceptance criteria research plan reviewed by team,1 24985571318.0,2022-11-02 14:50:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, checkbox to input boxes enhancements spouse other income issue description add checklist to box functionality in fsr for the following pages example of functionality tasks add checkbox to input functionality for pages listed above acceptance criteria new page formats are functioning as expected and match design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25383472319.0,2022-11-21 19:38:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cst add application to single app build allowlist background single app builds allow us to have much faster turnaround on builds when updating our applications because the applications that are part of the single app build allowlist are built individually as opposed to being built as part of the whole website in order to be part of the allowlist we need to ensure things our application is isolated from other apps ✅ this means that cst is not importing from any other applications and vice versa our application passes the header test ✅ this is a yarn script provided as part of vets website we have a slack group that we can receive application error messages in ✅ we have a slack group in the dsva slack called benefits apps builds helpful info the snippet below will need to be added to config changed app builds json json rootfolder claims status slackgroup benefits app builds tasks ensure that all of the requirements have been met for getting cst added to the allowlist add the json entry above to the config changed app builds json file create pr request review acceptance criteria cst meets all requirements to be added to allowlist cst has been added to allowlist config change app builds json pr has been merged,1 11758487003.0,2020-03-13 15:29:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,improve calendar unit tests the following files have coverage that could be improved calendarwidget jsx datetimerequestfield jsx datetimeselectfield jsx ,1 26776807133.0,2023-01-31 17:45:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters debt details page what happened after shipping i checked the feature in staging and looks like anything past is not configured as a route and results in a this is likely problem with the devops or backend routing configuration when navigating to user should be able to select a debt and refresh and that debt should be persisted via url id this logic works on localhost but does not work in any other environment because the client side route is not whitelisted as a valid url and results in a need to setup a whitelisted route in this and match the route of manage va debt your debt debt detail steps to reproduce test user sign in as any test user the above should work navigate to select any debt refresh application should not have debt and debt should be persisted selected debt url should look something like desired behavior when refreshing on the route in the steps to reproduce the reload should not result in a acceptance criteria reloading a selected debt does not result in a ,1 16814858327.0,2021-06-17 05:50:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create new progams research and doing business with detail pages in draft for future use story as a system pao i need a location to nest all of my specialty programs and research pages in my system website goal provide a place for future pages to be built and reside in the systems tasks create three new pages and archive them so they can be released at a later time clone programs page from source of truth and update and scaffold to match current system add programs page to menu under about va name and disable the menu items save as draft clone research page from source of truth and update and scaffold to match current system add research page to menu under about va name and disable the menu items save as draft clone doing business with us from source of truth and update scaffold to match current system add doing business with us page under work with us disable the menu items save as draft assure all pages are saved as draft archive will only be used on systems not in dual state complete for the following visns and systems visn altoona butler abie abraham va health care center hcc coatesville erie lebanon pittsburgh philadelphia wilkes barre wilmington visn va cheyenne health care va eastern colorado health care va western colorado health care va montana health care va eastern oklahoma health care va oklahoma city health care va salt lake city health care va sheridan health care visn va asheville health care va durham health care va fayetteville coastal health care va hampton health care va richmond health care va salem health care va salisbury health care visn va alexandria health care va central arkansas health care va fayetteville arkansas health care va gulf coast health care va houston health care va jackson health care va shreveport health care va southeast louisiana health care visn va central california health care va northern california health care va pacific islands health care va palo alto health care va san francisco health care va sierra nevada health care va southern nevada health care visn va black hills health care va central iowa health care va fargo health care va iowa city health care va minneapolis health care va nebraska western iowa health care va sioux falls health care va st cloud health care acceptance criteria research programs and doing business with us pages have been cloned scaffold menus created as disabled and saved as draft ,1 21780748193.0,2022-05-13 18:35:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update va business owner options in new vfs team gh ticket user story as a vfs team po or pm completing the new vfs team ticket i d like to have a choice of options when completing the va business owner question of the ticket so that i know to provide the va organization not the individual s name intended audience vfs pms and pos desired outcome checkbox options for the va business owner question of the new vfs team gh ticket due date description when new vfs pms or pos complete this ticket they often complete the va business owner section incorrectly often times vfs teams will respond with the individuals name however platform would prefer to know the va organization octo office of the cto vha veterans health administration vba veterans benefits administration nca national cemetery administration vaco veterans affairs central office other please specify if we provide checkboxes instead of space to type their own response we re more likely to get the information we re looking for artifacts needing updates tasks n a acceptance criteria github template new vfs team github ticket has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 19576831918.0,2022-01-04 16:20:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor the daily scan issue description the daily scan could be refactored to make it easier to follow the workflow tasks refactor the slack notifications in the workflow acceptance criteria slack notification jobs in the scan workflow are split up based on the outcome of the tests succeeded failed or canceled ,1 26127866175.0,2022-12-28 21:39:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint dec jan sprint goals tbd sprint deliverables list of deliverables completed during sprint none planned issues coordinate url changes unplanned additions n a capacity planning pto holiday s note winter code freeze note january holiday denise scott brandyn andrew megan points planned points accomplished tbd points over tbd issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 23341940586.0,2022-08-09 14:40:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,separate vha fsr submissions per station issue description vha wants to receive separate fsr requests per station facility to better isolate we need to take into account the selected debts statements to do this tasks assure we have access to the selected debts create multiple requests per station acceptance criteria we send a single request per station selected how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14003149465.0,2020-10-28 15:34:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr household income hifi design as a veteran filling out the fsr i want the ability to enter my household income to give an accurate representation to the dmc of my overall financial situation this section must contain the following household income veteran employment additional veteran income marital status spouse’s employment spouse’s additional income household dependents ,1 14172761401.0,2020-11-12 17:22:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr content as a veteran filling out fsr i would like content around how to update my contact information if it is incorrect if i have more then one debt i would like help around if i should chose or all ,1 26776420758.0,2023-01-31 17:28:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, veteran contact information enhancement issue description update contact information page so editing takes user to new page and back to view page when updated tasks add page jump functionality for phone number apply functionality to email and mailing addresses acceptance criteria veteran contact information page matches mockup and is functional how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16597008960.0,2021-06-01 14:33:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in confirmationpage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos project cheetah components confirmationpage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 16597007169.0,2021-06-01 14:33:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in contactfacilitiespage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos project cheetah components contactfacilitiespage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 14174585847.0,2020-11-12 20:08:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,why might i have this debt content create content to explain why a veteran has debt that is displayed in the cards ,1 31019224603.0,2023-08-10 02:55:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,implement streamlined flag in submission object description we need to set up a streamlined flag in the submission object that checks to see if the isstreamlined flags are set and passes them to the data transformer requirements check if isstreamlinedshortform and isstreamlinedlongform are true if true identify the streamlined flag and add it to the submission object in the following format json streamlined value true type short streamlined value false type long acceptance criteria implement the streamlined flag in the submission object following the requirements add relevant unit tests to ensure functionality update documentation to include this new addition possible implementation import isstreamlinedshortform isstreamlinedlongform from streamlineddepends transform js call the functions formdata const isshortstreamlined isstreamlinedshortform form data const islongstreamlined isstreamlinedlongform form data build the streamlined object let streamlineddata if isshortstreamlined streamlineddata value true type short else if islongstreamlined streamlineddata value true type long else streamlineddata value false type none not sure what we should call this const submissionobj personalidentification … streamlined streamlineddata ,1 27718124614.0,2023-03-14 18:20:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, expanding group issue description design tickets based on platform is depreciating the expanding group react component and step of repayment or relief options debt forgiveness waiver is impacted old design message and checkbox automatically appear after user selects waiver revised design user selects waiver radio button and selects the continue button the text you selected along with the waiver information is repeated on the following page along with the required checkbox component ,1 16326234751.0,2021-05-12 01:22:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analytics implementation or qa support for debtres fsr form google analytics implementation or qa request this is for implementation on fsr form prototypes we would like to discuss kpis first then implementation thanks what this form is for more information use this template to request google tag manager and google analytics implementation or qa for your product please fill out all brackets please see the following information for implementation timeline new teams implementation will usually be completed in sprints sprint discovery orientation sprint fe implementation sprint tagging implementation sprint qa all other teams implementation will usually be completed in sprints sprint discovery and fe implementation sprint tagging implementation and qa for more information please check out the an example of a completed request template can be found a fully completed issue can help speed up the implementation process description is this request for google analytics implementation or qa implementation who is this request for leah provide any relevant contact information and link this issue to the insights team on the dsva slack channel vfs platform support what team project is this work for this adds context for the data provide the domain where google analytics needs to be implemented i e identify if pii is passed in url or title tag please provide any upcoming deadlines or important milestones ex launch typical website interactions to track conversions understanding the user flow provide urls that are part of the application from introduction page to successful form completion conditional pages that are visible depending on an applicant s answer should be marker accordingly other user interactions provide details on other interactions and metrics like click to help text links that are helpful in understanding user behavior sample users when authentication is required do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository test users to replicate the event do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository certain conditions responses that need to be reviewed additional comments please leave the following blank acceptance criteria qa has been completed vfs team completes brief survey definition of done all appropriate issue tagging is completed all ac completed ,1 28059900818.0,2023-03-29 11:57:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint march sprint goals continue fe development of fsr enhancements conduct and synthesize co design feedback sessions with veterans review identifiers to progress vbs needs for mcp notifications finalize research plan for usability study add additional list loop to prototype streamlined waiver kickoff starting with design discovery efforts progress mcp notifications including review of two id types and swagger doc discussions with vbs define mock responses update template names for notifications planned issues fsr enhancements investigate and repair efsr validation cypress test fe your va benefits enhancement fe discovery research co design feedback sessions research add additional interactions to uxpin prototype design co design feedback sessions synthesis and concise report research heuristic evaluation synthesis and report research empty and endpoint failure designs design finalize conversation guide on github research part heuristic evaluation workshop research currency input box design fe utility bills enhancements fe credit card bills enhancements fe ongoing maintenance bug fixes expanding group deprecation fe investigate discrepancy between vha submissions and emails sent be update template names for dmc notifications be mcp notification add mock mvi responses for debt users be review two id types edipi and dfn with platform identity team be streamlined waiver kickoff meeting and discovery for streamlined waiver design blocked issues currently tracking the following blocked issues add signature date to fsr pdf sourcing pdf editor remove combined fsr enhancements feature flag fe unplanned additions other living expenses enhancement fe pts points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 24141728916.0,2022-09-21 15:18:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,publish modernized va gov strategy document to platform website user story as an emerging accessibility practice at va gov we want to publish our new strategy in an easily accessible and publicly linkable location to act as a north star to provide accountability and direction for all of our efforts as someone supporting va gov i want to know how accessibility is measured and strategized across va gov so that i can be part of the solution for building a more accessible va gov assignee briandeconinck peer reviewer cherylevans description we re looking to publish the to the platform website but are still uncertain as to what the process would look like where it would go we ve discussed if accessibility should be embedded as part of research design engineering sections or separate as its own section my hunch at the moment is the taco where the strategy doc could live in its own section where we can continue to add specific content like training materials and we can point to it in the embedded sections like this impacted artifacts depending on where we choose to publish this to we may look into adding links to it within the research and design section of the platform website questions should the entire document be published to platform website even the section prior to mission everything but the reviewer section we want to keep the context on the goal of this strategy doc and how it was created for transparency purposes 😄 should it remain a google doc or do we want the content embedded into a page of platform website we d like for this content to be embedded into a page of platform website so it s a little bit more sticky not in a permanent sense but in a this is published sense in the tasks below i m uncertain what create a github doc of the va gov strategy doc for editing purposes if folks leave feedback are you suggesting a duplicate github doc would this be the doc that is edited by the non platform specialists and then regular updates are made to the platform website version we re hoping to shift editing and feedback away from the google doc and into a github version so updates can be made and maintained in one location platform website includes a footer at the end of each page see image below this includes instructions for how vfs folks can suggest changes to the page this may conflict with the other editing process above we hope to use the platform website method of editing hence the transition away from google docs is there a list of other platform website pages where you d like to add a reference link to this new page i ll create a list for that will also ask the other specialists how do we want to publish comments or do we want to publish comments we don t publish comments 😄 there may be things that are currently out of date in the final draft for example sarah is no longer with dst should we fix now yes let s fix for now please leave comments on anything else that may be out of date in the google doc before we transition to github 🙏 tasks determine a location for the va gov strategy doc on the platform website reach out to platform content for recommendation publish on platform website create a github doc of the va gov strategy doc for editing purposes if folks leave feedback this isn t a great solution for folks editing since transferring changes from github to confluence will be cumbersome feedback should be left via the link in the footer and or discussed informally with brian add links to the strategy doc to other areas of the platform website pending adding links will be included in a separate ticket once the strategy doc is published on pw peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria the modernized va gov strategy document has been published to platform website and is available for vfs viewing how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 14526295229.0,2020-12-14 14:03:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch bankruptcy attestation as a veteran filling out fsr i want the ability to indicate if i am currently in the bankruptcy process ,1 19666452349.0,2022-01-10 23:16:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, name and role can t be programatically determined for ui components general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers josh kim joshkimux accessibility platform issue name and role can t be programatically determined for ui components issue details the p element s id copay balance is not unique for each of the cards this will result in all of the headings being described by only the first p element link screenshot or steps to recreate va gov experience standard other references wcag sc a platform recommendation all id s must be unique multiple p elements that contain unique facility names should not share the same id vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 14381313629.0,2020-12-02 05:05:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review billing and insurance pages for visn user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation tasks complete review of billing and insurance top tasks call to action across all visn systems listed below and document and report any issues that may need to be fixed use the following guidance does this content field data in this page make sense does the content field data in this page relate to this system level or specific to a facility is it in the right place based on system facility pages for the veteran to find how does this help with the focus of the page confirm the altoona va butler va coatesville va erie va lebanon va philadelphia va wilkes barre va wilmington va acceptance criteria all top task node pages have been reviewed in spreadsheet and issues found have been been documented issues have been documented and escalated for resolution using vamc support channel and spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 12441080187.0,2020-05-26 13:07:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review usage of activerecord import gem the activerecord import gem has a minor version upgrade but before it is upgraded its worth evaluating if it is truly needed it is used one place vets api modules veteran app workers veteran vso reloader rbl which is only referenced veteran vsoreloader perform async from lib tasks veterans tasks rake it is unclear if that is used anywhere in the app tracking down any information on this task and either upgrading or removing as appropriate likely removing is the outcome of this issue ,1 24679070728.0,2022-10-18 19:35:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,derive statementid for fe technical task when cross examining the pdf statementids with the statementids we have on the frontend we realized they did not match looks like the statementid is derived similar to vistaid with digits being required with in the middle as passing the values used are facility num on the first half and edipi on the second half maybe pass a new derived value to fe called statementid was testing this on user expected behavior returns a statement id looking like acceptance criteria be returns a statementid derived from facilitynum and edipi ,1 26985238625.0,2023-02-09 15:43:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, contact information bug issue description investigate an issue on staging where users with no address have the form crashing looking for livesoutsideus tasks identify root cause of issue add localhost mockdata for local testing purposes resolve issue with form crash acceptance criteria all staging users are able to access with enhanced flag on off how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18276526186.0,2021-10-04 19:32:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, fix breadcrumbs issue description after the content separation work it was noticed that the breadcrumb path for manage va debt is wrong and redirects to tasks manage va debt breadcrumb should redirect to the manage va debt page breadcrumbs should match the acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26127801010.0,2022-12-28 21:31:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint december dec dec note ptems contract is ending on december this sprint therefore was only days and focused on final wrap up and documentation sprint goals finalize end of contract documentation for all disciplines close out the contract as pop ends on december sprint deliverables list of deliverables completed during sprint contract end documentation planned issues contract documentation updates be fe design product pts aggregate vbms logs since launch be unplanned additions n a capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished tbd points over tbd issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 27083731556.0,2023-02-14 15:37:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,part heuristic evaluation workshop issue description what details are necessary for understanding the specific work or request tracked by this issue the heuristic evaluation workshop is an opportunity for the debt resolution team to collaborate creatively as a team learn about or refresh knowledge of usability heuristics and practice design thinking become familiar with the fsr form and or enhance present understanding think about possible usability improvements within current constraints tasks planning for part of the workshop part workshop takes place acceptance criteria part of the the heuristic evaluation workshop has taken place ,1 22754828805.0,2022-07-07 15:41:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update platform guidance for unmoderated research user story as a researcher i need to know the latest guidance about conducting unmoderated research so my research sessions can be as successful as possible while following va guidelines as a platform team member i need platform to be updated with the latest guidance so i can offer team members links to the most relevant and updated information when they seek help intended audience vfs vsp team members desired outcome update guidance specific to unmoderated research sessions due date assignee clayton peer reviewer jim description recently a vfs team conducted unmoderated research and they found we want to make sure any relevant guidance on platform is updated to take into account this work new artifacts artifacts needing updates platform page confluence page tasks look through the and note any needed updates to current platform guidance draft updates to the platform page acceptance criteria platform page has been updated with best practices change has been communicated on the research ops slack channel with clayton ooo the change will not be communicated via the research ops slack channel updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 17695658894.0,2021-08-24 15:01:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, map payroll deduction options data to the correct fields issue description all payroll deductions are captured into in a single group and placed in the other category data values should be mapped to the appropriate fields refer to tasks map the appropriate option data to the correct values listed below federal tax state tax local tax box ira and pension box fica social security and medicare box all other deductions box acceptance criteria payroll deductions data should be mapped to the appropriate fields all values including the total deductions field should be verified in the submit transformer how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16623245960.0,2021-06-03 06:08:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, swap out current policies page with new hardened policies page for visn and save as draft user story as a vha digital media web manager the national policies need to be hardened and available to national administrators only so national content should be changed from one source to all systems goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks archive current policies page replace with cloned page and add to menu for the following systems va black hills health care va central iowa health care va fargo health care va iowa city health care va minneapolis health care va nebraska western iowa health care va sioux falls health care va st cloud health care complete the follow these steps for each system open policies page in edit mode a change name to policies old b remove menu by un checking menu box c save as archive open fargo or iowa city system and find policies page a select clone from tabs and select clone b go to edit and remove cloned c change governance to match new owner and related system d select menu enable check box e type in policies in name f select from drop down about va from system you are cloning to g copy visiting hours and or security information from original policies page security information will go into other policies section save new policies page as current status of system i e published or draft acceptance criteria all original policies pages have been archived and removed from menu all new policies pages are published and link is in menu at bottom of menu items ,1 17515678236.0,2021-08-11 06:11:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, return and clone leadership pages for visn and visn systems story as a web editor the new leadership page has to be cloned and scaffold so i can validate the correct leadership profiles for our system task return to systems in visn without leadership page and clone pages from sot acceptance criteria all visn and visn already cloned now have leadership pages with correct information leadership profiles ,1 19098402665.0,2021-11-29 19:19:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace select components with vaselect web components the select component is deprecated and should be replaced by their web component counterpart vaselect the web components package now comes with react bindings that allow us to add event handlers to va web components the event handlers should be named in the following manner onvaeventname the remaining props should work just like the va select web component documented import vaselect from web components react bindings ac replace select react components with vaselect web components selects work as intended,1 30320405053.0,2023-07-10 18:46:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display monetary assets issue description add monetary assets monetaryvalues as view only on the final review page can likely leverage a custompagereview similar to how utilitybillsummaryreview is implemented only show the values that have been populated see for copy tasks implement read only display on final review page acceptance criteria monetary assets are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 32038438894.0,2023-09-22 17:11:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add cash in bank question to fsr issue description add cash in bank page to fsr and remove savings and checking account from your household assets selection page tasks cash in bank savings checking account page added cash saving checking account should not appear on your household assets checklist page acceptance criteria copy is finalized design is finalized design is passed to frontend add front end items here or create new ticket,1 25518416402.0,2022-11-28 18:15:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cst determine why last page visited is being tracked background currently the cst keeps track of the last page that has been visited within the application we need to determine what this is being used for and if it can be removed tasks determine what this functionality is used for determine if it can be removed or if it serves a useful purpose acceptance criteria the purpose of this functionality has been determined functionality has been removed if deemed unnecessary,1 28498770018.0,2023-04-18 15:48:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add signature date to fsr pdf issue description provide date of fsr submission to signature date box on fsr pdf tasks add mapping of data point to necessary pdf box in filler logic acceptance criteria date signature has been added to fsr date how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14223061999.0,2020-11-17 17:41:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,vsp content review fsr intro page and outline issue description create content specs outline for fsr form so already edited content can be used for the high fidelity mockup acceptance criteria designers share design outline form flow content writer to create form content outline peggy review s intro content and provides edits,1 19350668018.0,2021-12-15 15:20:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, page functionality isn t keyboard accessible general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers noah gelman noahgelman accessibility platform issue page functionality isn t keyboard accessible issue details headings please sign in to review your va copay balances not logged in review your va copay balances logged in and the in the on balance details are announced by nvda as clickable headings but they can t receive keyboard focus it doesn t seem like they actually have a click action so there may be some extra js event listener that s throwing nvda off in that case announcing the headings as clickable may confuse users link screenshot or steps to recreate va gov experience standard other references wcag sc a platform recommendation if there s an intended clickable action on those headings add tabindex to support keyboard focus and ensure that and are supported vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 21902928490.0,2022-05-20 15:02:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move screen reader research guidance and check list to platform user story as a vfs researcher i want all the important guidance i need in one location that i know to be source of truth so i don t have to hunt for it and so that i know that i m getting the latest guidance as platform governance team i want make sure researchers have access to important information on platform since it is source of truth for research guidance intended audience vfs teams desired outcome guidance moved to platform and marked deprecated in gh due date description researching with participants who use screen readers requires different considerations there is some but if this guidance is important enough for vfs researchers to reference it s important enough to be on platform as the source of truth this is related to and may make sense to work on at the same time as new artifacts new page for researching with participants who use screen readers artifacts needing updates tasks decide where on platform this information should live after information migrated mark the gh page as deprecated acceptance criteria platform website has been updated with information about screen reader participants gh page has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 21660335286.0,2022-05-06 18:26:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review icons in the cards status sections issue description during the combined debt portal s midpoint review we received feedback that we should review the icons used in the debt and copay bill status cards to make sure they re being properly used within the context of each status for example some statuses use a warning icon while others use an informational icon additionally we should seek accessibility guidance on alt text or screen reader only text to indicate what s being communicated tasks review meet with angela fowler to explore the current experience within mcp and gain guidance for alt text or screen reader only text add fe to this meeting acceptance criteria debt status icons have been reviewed and updated as needed guidance from the meeting with angela is documented in this ticket follow up tickets are created and linked as needed ,1 13463298707.0,2020-09-09 17:21:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters mvp vsa qa test plan product feature summary product feature epics landing page manage your va debt debt list page your va debt product feature pre launch checklist product feature design artifacts product team smes product management leahkeeler design research rebeccawalsh rileyorr content ia daniellethierryusdsva front end back end camerontesterman qa tze chiu lei proposed user scenarios and staging test accounts from vsa design lead important for authenticated experiences staging test accounts must be provided for all authenticated scenarios and staging api test data created to match the account specific scenarios landing page manage your va debt unauthenticated debt list your va debt default vets gov user gmail com greg empty states general resolved debts covid debt suspension error states vbms debts present no letters vets gov user gmail com jerry dmc no debts letters present vets gov user gmail com mark both no debts no letters vets gov user gmail com chad moderated uats on prod due to spi pii restrictions that preclude data integrity validation on staging moderate uats will be conducted on prod recruiting real veteran users to validate their debt letters via remote sessions see moderated uat spreadsheet attached below for details on what questions will be asked and eventually how each uat participant responds how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team vsa authenticated exp vsa benefits vsa benefits vsa caregiver vsa ebenefits vsa facilities vsa public websites etc definition of done test plan reviewed by product team test plan finalized per review feedback actual test run s completed on staging created and tracked ,1 19319792657.0,2021-12-14 03:15:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, zero balance details link technical task we do not want to link to details page when there are no statement details this is happening with zero balances need to check the statements behind zero balance and hide show link based on if statement exist expected behavior if there is zero balance with no statements do not show overview link acceptance criteria hide overview link on zero balance if no statement ,1 13461543407.0,2020-09-09 14:56:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,project kickoff debt letters mvp steps to complete project kickoff product manager create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in vfs platform support in slack tag megan kelley andreahewitt andrea and megan will schedule meeting with vsp reviewers and requesting team attendees as listed below vsp requesting team kickoff meeting completed all requesting team attendees complete brief survey artifacts please bring the following to the kickoff meeting link to rough draft of product outline you do not need to prepare a presentation meeting attendees from requesting team product manager required leah keeler depo product lead required matt self entire vfs team recommended amen ra mahariel rosario riley orr becca walsh cameron testerman scheduling preferred dates or times week of ,1 27423319147.0,2023-03-01 18:16:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove combined fsr references in be issue description the combined fsr has been launched since and references to the be forking logic can be removed we will want to keep the feature flag in place since fe still has uses for it tasks remove references to check if flipper enabled for combined financial status report update logic to assume flipper is enabled acceptance criteria the be assumes that cfsr is turned on the flipper still exists for fe usage how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23766659689.0,2022-09-01 13:18:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update pgd route dear api consumer we are making a change to our system to system authorization routing which uses the oauth client credentials grant ccg as a pgd api consumer these change applies to you what is the change this change updates the path to the underlying system to system oauth server by adding a new system specific authorization path the new path will support both user centric and system to system authorization flows for the pgd api current path will stop working on october new path available now when is the change being made the new path is available now in sandbox and production and we encourage you to test and verify it before promoting to production on october the previous routes will stop working who do i contact for questions lighthouse support is happy to answer any questions you have you can submit a question through our contact us page and we ll get back to you in business days or less best regards va lighthouse api support the va lighthouse team developer va govapi va gov you are receiving this message because you visited developer va gov apply and requested access to the va lighthouse apis if you have received this message in error or do not wish to receive any further communication from va lighthouse please let us know ,1 22708525570.0,2022-07-05 16:47:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update general orientation slide deck to include sitewide content ia intake request user story as a new vfs team member i want to know about the sitewide content ia intake request while going through va gov platform general orientation so that i know what to expect when i engage in the collaboration cycle intended audience vfs teams desired outcome general orientation slide deck is updated to include a new slide for the sitewide content ia intake request due date end of april next general orientation is scheduled for may description in march we added the sitewide content and ia intake request to the collaboration cycle as an official touchpoint however we did not create a slide for this touchpoint in the general orientation session for the va gov platform the purpose of this ticket is to add a new slide to the slide deck please refer to the on platform website for information to populate the slide artifacts needing updates acceptance criteria updates have been peer reviewed by governance team member user story need has been fulfilled sitewide content and ia team has reviewed the slide and given their approval beth danielle and or mikki related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 22632232228.0,2022-06-30 15:32:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move and test setting mock value for debts to feature flag issue description we want to be able to dynamically assign whether to use mock or dmc data for specified staging users tasks open pr that moves setting to feature flag test both sets of data with different users acceptance criteria we can assign to user whether to use mock or dmc data how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13249108454.0,2020-08-19 20:11:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert va facilities page tests to integration tests make sure to cover any logic mentioned in testrail as well as existing logic covered in current unit tests ac tests primarily written as integration tests preferably in react testing library tests following component action unit tests can still exist to cover any gaps that can t be tested with integration tests ,1 25033462749.0,2022-11-04 14:14:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,delete accessibility testing page user story as a vfs team member i want to be able to rely on the accuracy of the accessibility standards are for platform so that i can be sure my team is meeting those standards for our product assignee peer reviewer description unbeknownst to the governance team the page was created and published under the developer docs qa and accessibility testing accessibility testing section of platform website this page is just a duplicate of the page however it has not been maintained or updated so it may be out of date all accessibility standards are published as part of the va gov experience standards and should remain there impacted artifacts tasks placeholder task peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria placeholder ac how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 27747448058.0,2023-03-15 18:01:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,co design feedback sessions synthesis and concise report issue description what details are necessary for understanding the specific work or request tracked by this issue the co design feedback sessions on the fsr form prototype will be completed as a follow up step we have been and will continue to review and synthesize the feedback noting which areas were unclear for veterans and which ones were delightful combined with the heuristic evaluation feedback we will create a concise report to share what area s of the fsr prototype need further clarity tasks what work is necessary for this story to be completed the review and synthesis process creation of a concise report to share elicit discussion and decision making acceptance criteria what will be created or happen as a result of this story what work is necessary for this story to be completed the review and synthesis process creation of a concise report to share elicit discussion and decision making how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28034964852.0,2023-03-28 14:33:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, qa uxpin prototype issue description qa prototype to make sure interactions work as expected and make updates as needed link to prototype tasks qa prototype make updates if needed acceptance criteria prototype has been tested necessary updates have been made ,1 29892595419.0,2023-06-21 00:04:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery form navigation back to review page issue description discovery ticket to investigate loe for navigation from in form edits to review page tasks determine loe for the following adding navigation to return to review page at the end of each chapter leveraging session storage value create necessary ticket s for adding review page navigation from end of each chapter acceptance criteria loe and tickets created for tasks listed above how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13306238824.0,2020-08-25 19:54:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters mvp your va debt copy anomalies what happened on staging your va debt page the following copy anomalies were found under need help time range copy did not follow va design system content guidelines under same section subheading has typo specs device browser test user if applicable vets gov user gmail com greg steps to reproduce go to sign in as vets gov user gmail com greg in need help section a observe that in paragraph and cst do not follow va design system content guidelines b observe that in subheading s last word assitance is misspelled screenshot desired copy time range copy should be a m p m and ct following va design system content assitance should be spelled assistance acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 18727238722.0,2021-11-03 17:30:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add vbs api key in headers technical task as we are moving to more secured endpoint api keys are not a header requirement for connecting to vbs add api key to headers so we can access vsb via vets api api header key and headers can be found in fwded email expected behavior api keys are now passed in mcp vets website headers acceptance criteria endpoint can handle api key in headers ,1 23445540860.0,2022-08-15 19:13:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined va debt portal epic as a veteran i want the ability to see all my va debts debt letters and payments in one dashboard the veteran will be able to see their debts and in the future select options to manage them such as a waiver dispute compromise and they would be routed to vba and or vha allow veterans to view all va debts online and decrease time to resolution while meeting congressional mandates kpis total page views on debt portal collab cycle touchpoints kickoff design intent information architecture ia request research plan review analytics request midpoint review contact center review staging review privacy and security review post launch full accessibility and office audit post launch check in,1 26783372331.0,2023-01-31 23:31:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,configure production url shortener to use as the hostname user story as a veteran i wish check in links to work no matter what network i am on so that i may pre check in and check in for my medical appointments background users on the va internal network are unable to access va gov as opposed to and therefore cannot use the pre check in or check in apps acceptance criteria the url shortener allows shortening links for va gov and the url shortener always returns short urls and redirected urls pointing at instead of va gov rollback instructions from action in github click ‘run workflow’ drop down on the right select tag click ‘run workflow’,1 13936094088.0,2020-10-22 12:29:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,project kickoff debt resolution fsr form steps to complete project kickoff product manager create this issue and fill in feature name in the title and other bolded information appropriately attach all relevent artifacts to the ticket link to this issue once created in in slack tag shira goodman and andreahewitt shira will schedule meeting with vsp reviewers and requesting team attendees as listed below vsp requesting team kickoff meeting completed and is updated all requesting team attendees complete brief survey artifacts please bring the following to the kickoff meeting link to rough draft of explanation of the problem space any other artifacts you have so far you do not need to prepare a presentation meeting attendees from product manager required leah keeler depo product lead required matt self entire vfs team recommended names do you anticipate this initiative requiring updates to and or creation of unauthenticated static content pages yes and lots scheduling please reference the times shown are et note an available time slot within a recurring review group office hours slot that works for your team and is at least business days from now write that preferred time slot here on this ticket and vsp will send you a meeting invite wednesday if no available time slots work for your team write your availability and requirements here and shira andrea will reach out as needed ,1 24644991750.0,2022-10-17 14:17:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined multiple last names for valid fsr filename issue description bug where veteran has multiple space separated last names produced an invalid filename for sharepoint tasks combine the multiple last names with an underscore acceptance criteria the api produces a valid sharepoint filename for this edge case how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23351356052.0,2022-08-10 00:32:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update the button pair web component in the vaos application platform design system team created the button pair web component we should replace the existing button pair react component to the updated button pair web component known differences tasks try out replacing the button pair react component with button pair web component and document any differences that appear acceptance criteria replace button pair react components with button pair web component ,1 15836047855.0,2021-04-06 18:47:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr usability topline debriefing issue description to quickly share our findings i e demo we should compile our debrief discussions into a list of notable trends tasks hold debrief sessions at the end of each research day create a document or deliverable that highlights major takeaways from session attendees acceptance criteria topline summary deliverable uploaded to gh and linked in this ticket,1 25159137521.0,2022-11-10 15:34:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,allow for successful submission page with fsr background processing issue description the submission page right now is coupled with the statuses we get back from vha and vba for ga events since this processing is being moved to the backend we need to account for these statuses not being available tasks strip references to vha and vba status assure that ga events will still be triggered acceptance criteria page remains working as intended but with events happening asynchronously how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27391496532.0,2023-02-28 16:32:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,incorrect data presented on portal issue description veterans are reporting that they are seeing incorrect data presented on the portal and support calls are getting a handful of inquiries of the debt portal not providing correct balances within the last couple months for different debt types examples veteran stated he received his letter in the mail but when he went to his va account on the debt portal it states he doesn’t have a debt “ i have a va debt balance but when i log into the va website it says there is no debt on file i would like to be able to view my total balance before paying last response stated that due to system changed there would be times that veterans wouldn’t be able to see debt in debt management this is not due to system changes whenever i login everyday the system still says they i have no debt but i do and want to see the balance without having to make a phone call or submit an inquiry ” veteran sent an email stating his balance has not updated on the portal with the last two months’ payments of each paid via compensation benefits on and he states the debt portal balance reflects when vams shows he was concerned we were not applying the payments considerations from va representative reporting issue is it possible any updates on account balances have not been updating was it months ago when the letters were stopped i’m thinking there is a correlation with the letters being turned off and balances not updating tasks look into the affected data points of the va gov portal determine possible cause from api or ui reach out to dmc about data discrepancies acceptance criteria we gain an understanding of why these values are not accurately represented how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11455357174.0,2020-02-06 18:56:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,failing unit tests at certain time of day we have some date related unit tests that fail at specific times we need to investigate why this is happening and fix the problem ,1 22838992955.0,2022-07-12 19:40:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, determine if cdp is eligible for datadog access and next steps issue description we would like to setup a datadog dashboard to track our services related to the combined debt portal debts medical copays we have heard before platform was restricting datadog usage for certain products but we would like to revisit check with necessary contacts within platform to establish use case for datadog and how to proceed with setting up the dashboard tasks followup with platform to discuss datadog connections if applicable detail next steps acceptance criteria we know whether we can continue with setting up datadog and how to proceed how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24447303495.0,2022-10-06 19:09:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,run coverband in production so we understand what codepaths are unused background code rot is the process of legacy code becoming defunct while remaining in the repository a useful way to analyze what codepaths are unused is to run coverage tools in production can provide us with details on what code is actively used in our application and what code is candidate for removal goals this will help us further reduce technical debt in the codebase and illustrate high volume codepaths that may warrant closer inspection acceptance criteria coverband ui is available at api va gov coverage coverband ui is protected with authorization authentication somehow tasks add gem coverband to gemfile configure a standalone redis instance in the utility environment set a web admin ui password in credstash or use in app logic like we do w flipper auth it either way modify files to pull details for redis avoiding adding a container to docker compose here because it doesn t need to be there maybe more discovery needs to happen ,1 31162051873.0,2023-08-16 16:42:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update and test debts api module issue description a few sprints ago we duplicated the fsr workflow inside the debts api module with the intention of migrating all fsr endpoints and functionality over to this module since the initial release of the module code changes have been made to the original code that need to be copied over once the module has been brought up to date it should be manually tested from the front end in a staging env tasks bring debts api files up to date with primary app counterparts add a feature flipper to point the front end at either debts api module routes or regular routes test fsr functionality in staging env acceptance criteria the debts api module is up to date and tested ,1 12067640231.0,2020-04-16 13:41:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,upgrade sentry raven gem background the sentry raven gem is currently locked to it could be upgraded to the latest x version or possibly up to with all the additional work that s going on with sentry this is a good time includes some bugfixes goal sentry raven gem dependency is at latest version acceptance criteria ci passes sentry events are sent without issue in review instance sentry raven is at latest version how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26391453452.0,2023-01-12 15:58:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, checkbox to input boxes enhancements housing expenses issue description add checklist to box functionality in fsr for the following pages confirm expenses explainer is up to date example of functionality tasks add checkbox to input functionality for pages listed above acceptance criteria new page formats are functioning as expected and match design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24123278529.0,2022-09-20 20:50:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,vbms letter debt portal audit issue description on september it was identified when vbms updated the third demand letter form additional veteran data was shared on some letters from to this is one of a few letters veterans can access when they have a vba overpayment in the debt portal a toggle switch has been added to production which enables the team to turn off access to the letters until the issue is resolved to understand the impact this issue has caused an audit needs to be done to provide estimates of the number of veterans who accessed their letters during the time period determine the identities for those veterans that accessed and identify the number of veterans who downloaded the form document tasks provide estimates for the following the of veterans that have accessed their letters during the time period estimated completion identities for those veterans that accessed estimated completion identify number of veterans who downloaded the form document estimated completion tbd still under evaluation acceptance criteria summarize and report on findings how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24848983158.0,2022-10-26 18:17:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, bug installment contract values calculations issue description investigate and fix required inconsistencies with installment contracts on current form we had multiple submissions that were missing the originalamount key from their installment contract some that were missing creditorname and one submission where the only thing that was filled out was purpose we need to either make these fields required or handle when they are not complete incorrectly filled out tasks investigate if these installment contracts should be required update requirements and include additional error handling so good data is being received acceptance criteria installment contracts no longer receive blank or nan values where appropriate how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 19907912114.0,2022-01-25 14:34:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html statement issue description add statement header to html statement page refer to the for details tasks update statement header acceptance criteria statement header should render the date and facility name how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14381313328.0,2020-12-02 05:05:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review of the make an appointment pages for visn user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation tasks complete review of make an appointment top tasks call to action across all visn systems listed below and document and report any issues that may need to be fixed use the following guidance does this content field data in this page make sense does the content field data in this page relate to this system level or specific to a facility is it in the right place based on system facility pages for the veteran to find how does this help with the focus of the page confirm the altoona va butler va coatesville va erie va lebanon va philadelphia va wilkes barre va wilmington va acceptance criteria all top task node pages have been reviewed in spreadsheet and issues found have been been documented issues have been documented and escalated for resolution using vamc support channel and spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 14264109163.0,2020-11-20 15:18:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr household income veteran income as a veteran filling out the fsr form i need the ability to list my employment ,1 22959900949.0,2022-07-19 14:35:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cfsr discovery estimation of timeline and work effort desired behavior read through vafs design system current fsr code and requested updates to come up with rough idea of timeline and estimation of work effort combined fsr links main epic use cases product guide uxpin extra work in fsr acceptance criteria rough timeline established to completion of combined fsr how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 17272026869.0,2021-07-22 21:16:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt portal add content for debt issue description veterans are mistakenly receiving notifications about owing debts represented as chapter tuition fees yellow ribbon – school liable in the dmc s deduction code spreadsheet while the dmc troubleshoots why veterans are receiving these notifications we need to provide content in the portal letting veterans know that they need too check with their school and that they cannot view the debt in our portal the content if you got an email about chapter tuition debt with code this is a debt assigned to your school you won t find it listed here before you make a payment on this debt check with your school they may have already paid the alert view the uxpin for reference on the alert s placement tasks add the alert in alignment with the provided prototype acceptance criteria the content has been updated in alignment with the provided prototype ui has been reviewed by a designer ,1 17103370088.0,2021-07-09 14:19:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,pass signature values to be on fsr technical task currently we are just using signatures to validate that the form is signed before submission we need to pass this signature value to the be now so we can generate the signature on the pdf and pass that payload to the dmc so they can generate pdf expected behavior signature values are being passed to be via payload on submission acceptance criteria signature values on the fsr are being passed to be via submission payload ,1 21478266967.0,2022-04-26 15:20:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update platform with guidance for what to do with research findings outside of the digital experience user story as a vfs researcher i may be have findings that aren t related to the digital experience if there is a pattern and especial if it s data that could improve the veterans interactions with va i want to know how to present these findings to folks who can actually do something with them as the octo team our purview is to enhance the digital experience so when a vfs research crosses over into areas that are service experience we want to make sure researchers understand how to properly present those findings intended audience vfs researchers desired outcome added guidance on platform due date tbd description while vfs researchers should be focused on researching the digital experience for va gov occasionally they may uncover important actionable findings for service design outside of the purview of octo octo would prefer this not be a major part of research presentations made in vfs vsp meetings since service experience areas conduct their own research and are the owners of actions taken at the same time it s important to get this information to the proper channel so that important modifications that enhance the veteran s non digital experience can be made by the teams in charge of those in a meeting with kevin shane and clayton a preferred outcome is add guidance to an appropriate platform research page addressing the following information when you learn about something that isn t digital experience related but could improve lives of veterans share with your po if it is actionable and you d like to present your findings outside of your team or practice area your po should first discuss it with their portfolio lead add a slide to the research findings deck template for non digital experience related findings to make it more clear to researchers presenting that they should focus their energy on digital experience findings new artifacts artifacts needing updates relevant platfom page research findings presentation slide deck template tasks kevin shane clayton discuss issue and ideate solution figure out with platform page s should host this information acceptance criteria slide deck template has been updated platform website page name has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 26941301070.0,2023-02-08 02:35:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ehrm cerner statement integration description integrate ehrm cerner statements high level user story ies as a veteran i want to receive copay statements from ehrm in the medical copay portal definition of done ehrm statements are available in the medical copay experience on va gov how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 26542354796.0,2023-01-19 20:23:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review and groom security team backlog description platform has recently lost their dedicated security team the backlog they had needs to be reviewed updated and groomed based on current needs and requirements we want to ensure items that need attention are updated accordingly and pushed to the platform team that makes most sense to drive the work the security backlog can be found additionally there was a spreadsheet that had some issues associated with it that were being tracked a little more closely that spreadsheet has been attached to be reviewed and reconciled as well note this may be duplicated w the security board but want to make sure schedule meeting w joe and thomas to work through items and make determinations make list create issues for items recognized as missing acceptance criteria all items in security backlog are reviewed and groomed as necessary all items in security team backlog have some resolution assigned to cop or deemed no longer needed subject areas product design engineering octo de,1 31836543206.0,2023-09-14 13:51:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,wireframes user scenarios for wizard draft issue description wireframes user flow for wizard and streamlined waiver with user scenarios tasks create draft of wireframes user flow acceptance criteria draft created,1 13097317547.0,2020-08-03 17:14:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging review debt letters mvp steps to complete staging review product manager create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in in slack tag andreahewitt mandi lipka mandi to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must complete list of artifacts below vsp requesting team review meeting completed practice area reviewers create sub issues attached to this one with feedback for your team on feature name requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket may differ for each practice area please refer to attached tickets for further instruction all requesting team attendees complete brief survey artifacts please provide the following artifacts at least days before scheduled review meeting link to link to access information for the tool or feature in staging do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository link to your product test cases test plan in testrail with test execution logs please note debt letters is one page listing out the veteran s debt and a table with links to debt letters because a veteran needs to log in to see this the only way to test is moderated release with live veterans will be sitting in on a few sessions as part of qa process link to your and reports in testrail for qa practice area review link to verification that accessibility checks are complete preferred link to your or link to a doc in your product folder that indicates all required checks from the accessibility doc are complete list of known issues with links to tickets when applicable meeting attendees from requesting team product manager required leah k leahkeeler depo product lead required matt self anyone else from your team who significantly contributed to the artifacts provided required brad c cameron camerontesterman scheduling please reference the times shown are et note an available time slot within a recurring review group office hours slot that works for your team and is at least business days from now write that preferred time slot here on this ticket and vsp will send you a meeting invite if no available time slots work for your team write your availability and requirements here and megan andrea will reach out as needed additional notes during this collaboration point you will receive feedback from the following practice areas design accessibility content qa and optional product analytics engineering information architecture ,1 25281195786.0,2022-11-16 15:53:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,establish graphana metric tracking issue description establish metric tracking in graphana to track successful counts failures dmc etc tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26658423246.0,2023-01-25 18:48:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,audit factorybot factories and traits with factory trace gem and remove unused instances background running gem on our test suite reveals unused factories and traits we can install this gem to make sure our factories are all used somewhere acceptance criteria all unused factories are removed,1 27016459373.0,2023-02-10 19:53:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,finalize research plan on github issue description ensure format of the research plan matches add research plan to tasks finalize research plan so it matches research plan template acceptance criteria research plan is finalized and up on github ,1 24558767392.0,2022-10-12 18:13:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, define copay path issue description define copay path for wizard tasks define path for veterans to use wizard for copays acceptance criteria path defined,1 27742985374.0,2023-03-15 15:22:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update uxpin fsr project to match sketch issue description we now have access to our new uxpin account and the fsr prototype is out of date because a bug preventing sketch s uxpin plugin from working new mockups need to manually be added to the prototype tasks upload mockups from sketch to uxpin acceptance criteria mockups have been added to fsr project on our new uxpin account ,1 26781400584.0,2023-01-31 21:31:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, cards mini summary add midpoint review updates issue description midpoint review feedback from design ia and content tasks design update how card is styled to back button chevrons should be primary blue we have recently updated the multiple responses guidelines use the actionlink for adding another item instead of a question put the list of values in the same order as previous list and add “value” to all items content step of household assets your other assets select any other item of value called assets you own not including heirlooms clarify to the user what constitutes an heirloom i recommend clarifying to the user what constitutes and heirloom or simply don t use the word heirloom and instead use the definition of heirloom the same verbiage should apply to the entire list the items in the list are all somewhat subjective i recommend using a threshold for instance you could say anything valued at over or something similar updated to select any other items of value called assets you own not including items passed down in your family for generations step of household assets you have added these assets precious metals and coins value is the first entry for added items the next added item simply says antiques this is incongruent formatting i recommend using the same formatting and verbiage for each asset entry i recommend removing value from precious metals and coins value and changing the verbiage from how much is each of your assets worth to what is the value of each of your assets acceptance criteria changes discussed with design system team files updates files updates files updates fe ticket created ,1 23589398839.0,2022-08-23 14:07:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr streamlined waiver wizard design user flow draft issue description user flow for streamlined waiver and wizard tasks acceptance criteria ,1 13924721942.0,2020-10-21 15:54:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update datetimeselectpage tests to set slots from fetch call instead mocking store we should update all the tests in the datetimeselectpage tests to populate time slots from a fetch call instead of mocking them in the redux store since it s a more realistic test ,1 24958001486.0,2022-11-01 13:27:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move research synthesis guidance to platform user story as a vfs researcher i want all the important guidance i need in one location that i know to be source of truth so i don t have to hunt for it and so that i know that i m getting the latest guidance as platform governance team i want make sure researchers have access to important information on platform since it is source of truth for research guidance assignee it harrison peer reviewer cherylevans description there is but if this guidance is important enough for vfs researchers to reference it s important enough to be on platform as the source of truth impacted artifacts tasks decide where on platform this information should live likely a new page naomimarcussen can help mark gh page as deprecated validate that all links on new platform website page point to other platform website pages if applicable and not gh pages validate that all content within guidance is up to date and accurate for anything that is outdated if it is a simple fix work with naomimarcussen to make the change before publishing if the fix requires rewriting reorganizing of the content create a follow up ticket using the governance team issue template and document the necessary changes we will publish the guidance to platform website as is work with naomimarcussen to determine if a this guidance may not be up to date warning message should be added to the platform website page naomimarcussen should the new synthesis page be integrated into the research checklist acceptance criteria vfs teams are able to find guidance on research synthesis on the platform website research vfs teams are redirected to the platform website when they encounter deprecated research synthesis guidance on gh how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 15304345936.0,2021-02-24 16:48:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters downtime alert issue description dmc api will be down between the hours of and a m et every night we need to display an error alert when we are not getting a response between those two times mockup tasks develop an alert for when the dmc api fails between and et every night acceptance criteria alert displays when api is not responding,1 23388221365.0,2022-08-11 15:23:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, github action runners contain lifecycle ignore description recently i tried to update the instance type for vets website github runners and did not have initial success upon looking into it with john we discovered that we are along with a few other things in terraform this may be an intended purpose and if so we may want to document comment it s reference somewhere presumably in the file background context technical notes it may be working as intended but for all intent and purpose perhaps documentation comment above line references should be provded tasks discover if ignore changes is intended or if we can improve upon it ensure terraform has not drifted if ami is up to date acceptance criteria code changes if applicable documentation ,1 14887687841.0,2021-01-20 18:42:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres dsr iteration allow veterans to edit fsr form after submit high level user story ies as a veteran who filled out the fsr form and submitted it i would like the ability to edit the form if my financial situation changes after i submitted it hypothesis or bet giving the veteran the ability to edit fsr form instead of as is which is filling out a new one will be a much better user experience as well as provide the dmc with most up to date information for resolution determination okr faster resolution times due to having correct information on fsr definition of done determine time period a veteran can update information back end retrieval of previously submitted fsr from dmc data identifier marking the submit as an edit business rules for number of times a form can be edited take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 17107508837.0,2021-07-09 20:27:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor class components in debt letters to be functional technical story it s better for the codebase if we maintain one way of doing things especially in side the same application one thing that i noticed when going through the code style of the debt letters application is that we are mixing both class based components with functional components with hooks in order to keep a more consistent code base refactor all class based components to functional components with hooks expected behavior the behavior and visual repetition should be the same acceptance criteria all classed based components in debt letters are refactored to functional components all pre existing test pass ui and ux are the same as before ,1 19726850385.0,2022-01-13 20:53:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update labels for midpoint review and design intent issue description the design intent gh template and the midpoint review gh template have incorrect labels tasks add the design intent label to the add the midpoint review label to the remove the content ia team label from the midpoint review gh template update the design intent url link on the following pages update the midpoint review url link on the following pages acceptance criteria vfs teams draft design intent and midpoint review requests with the correct labels how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25981223207.0,2022-12-19 19:02:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, continue discovery for user journey paths issue description continue conversations to understand the streamlined waiver tasks discuss what we understand based on user journeys and wireframes and the pdf and excel files provided by smes acceptance criteria better understanding and path forward ,1 31780543687.0,2023-09-12 17:06:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add state metadata to issue description as far as i know we don t make any meaningful record when a submission fails given the importance of these submissions processing correctly we should be able to tell at a glance if a submission failed to actually submit tasks add a field to use this field to record when a submission succeeds or fails to actually submit acceptance criteria it should be reasonably guaranteed that a submission will record success or failure state after it has been created ,1 13306238131.0,2020-08-25 19:53:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters uat issue description in order to validate that the data we re receiving from the dmc matches what we re expecting on the frontend we need to conduct uat tasks moderate uat sessions from august complete to keep track of tested use cases acceptance criteria all uat sessions have been completed the base use cases are tested the uat spreadsheet is completed ,1 28004758098.0,2023-03-27 14:38:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review two id types edipi and dfn with platform identity team issue description discuss with platform identity team the current existence of fetching an mpi profile from the two user identifiers we will work with mcp notifications edipi and dfn tasks connect with platform id team research existing or editable areas for getting profile from identifier determine next steps for allowing profile to be fetched if needed acceptance criteria understanding if both id types will work for purposes of identifying veterans for new mcp notification how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16539133112.0,2021-05-27 14:50:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove organization service and move code into location we have a separate organization resource and service that s only used for pulling parent sites for the cc check and old facility page we should fold this into the location service since the resource formats are very similar and the vaos service doesn t have this distinction tasks move parent sites service function into location resource move transformer into location transformers file update transformer to transform parent site into the location format will have some missing data update cc check and old facility page to handle new data format,1 13767597618.0,2020-10-07 15:56:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate lazy load re renders investigate whether we can still lazy load profile components in routes while preventing re renders from profileswrapper,1 20158740546.0,2022-02-09 19:04:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add content of fsr email template to va notify portal issue description take content of fsr email template and add to staging notifications va gov notifications va gov prod tasks login to portal over va network and add email copy acceptance criteria email copy and uuid is available through va notify how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26908025009.0,2023-02-06 20:50:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,define playbooks for critical incident scenarios description the incident response plan needs playbooks for each of the following scenarios aws outage aws tic outage aws forward proxy service error aws reverse proxy service error backend vets api outage backend vets api denial of service coding error application frontend backend security issue aws bucket outage security pii data leakage security unauthorized user security unauthorized transactions security zero day cve application vulnerability ops deployment issue security ops admin user compromised security ops admin token compromised application external service issue datadog slack pagerduty grafana loki acceptance criteria the is updated with detailed steps to follow ,1 12372319815.0,2020-05-18 20:11:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create an endpoint for get debts id debts show user story or problem statement as a backend developer i need to provide the frontend an endpoint that will return the details of a particular debt goal an endpoint is created that utilizes the dmc service to show a veteran the details of a particular debt tasks acceptance criteria ,1 24760616801.0,2022-10-21 23:25:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,vbms letters data issue issue description october we received notice from our stakeholders that there was a potential data breach on one of the vbms letter that were downloaded on the debt portal while the case is being investigated we have turned the feature off tasks toggle vbms letter download off while incident is being investigated upon stakeholder approve toggle vbms letter download back on acceptance criteria issue has been resolved and feature has been turned back on how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25285557006.0,2022-11-16 18:59:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content changes part issue description extracting content changes still outstanding from tasks update content changes to reflect what the mockups show content changes include add tsp clarify brokerage account for stocks and bonds change the following to these change to login gov id me ds logon or my healthevet change once you re signed in to after you sign in controlled by platform change note text to match uxpin change info text to match pending new fe ticket for implementation change one medical bill below to one medical bill here change debt below to debt here effort covered in other tickets change the following to these included in this includes vehicles with a loan included in this includes properties with a mortgage included in change the following to these included in change bill s to bill included in change the following expenses to these expenses included in change the following to these included in change regarding your request to on your request delete in order included in global content changes include want to ensure they are handled everywhere global new breadcrumb text home  ›  manage your va debt   ›  request financial help va form global new header request help with va debt for overpayments and copay bills global need help section change va debt to va debt related to benefit overpayments make sure to include the tty in the aria label too acceptance criteria all content changes match markup how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12395568316.0,2020-05-20 18:54:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters mvp call center employee interviews user story or problem statement as a designer working on the debt letters mvp i need to interview call center employees so i can take user feedback into account when designing without user discovery tasks interview call center employees upload interview notes and executive summaries to gh acceptance criteria interview notes and executive summaries in gh and linked to this ticket,1 15020103388.0,2021-02-01 14:20:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr make additional employment end dade not required as a veteran filling out fsr form i may have several jobs so having an end date on additional jobs would prevent me from listing them out definition of done end date is not required ,1 27020022784.0,2023-02-11 00:09:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update on this page component issue description update on this page component styling and add as a landmark for screen readers during review it was identified that the on the page component is not emerging as a landmark and therefore confusing for screenreader users as we reviewed we realized that there are some styling updates that also need to take place tasks add on this page as a landmark update styling acceptance criteria on this page component styling has been updated on this page component has been added as a landmark how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22832027137.0,2022-07-12 13:42:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, page transitions not announced by screen readers general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue no va gov experience standard for the issue found issue details when navigating from your va debt and bills summary to current copay balances or current va debt via the check your balance and check the status links focus is not set to the and the heading is not announced by screen readers the same behavior occurs when viewing copay details however everything is properly announced when viewing debt details when the heading of the new page isn t announced screen reader users don t receive any feedback on whether following the link worked or where they are now link screenshot or steps to recreate log into staging as test user navigate to manage debt and bills summary activate a screen reader recommend voiceover on mac or nvda on windows for testing press to move to the check your balance and resolve your bill link press note that you have navigated to the new page but nothing is announced by the screen reader press to move to the first check details link press note that you have navigated to the new page but nothing is announced by the screen reader go back to your va debt and bills press to move to the check the status and resolve your debt link press press to move to the first check details and resolve this debt link note that the new page title is announced by the screen reader va gov experience standard other references platform recommendation when moving to the new page focus should be programmatically set to the element using a tabindex attribute the behavior when following the check details and resolve this debt link should be a good template vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 21005288243.0,2022-03-29 21:54:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,streamlined waiver process high level user story ies what is the pathway you’re creating for vfs or vsp teams through this initiative problem statement in a couple of sentences describe the who what why and where of the challenge pain point you seek to address follow your problem description up with a how might we statement re framing that challenge as an opportunity don t hint too much at what the solution might be you should have enough of a focal point here to guide your ideas but plenty of freedom to think laterally and innovatively as you experiment and prototype later hypothesis or bet how will this pathway impact the quality of vfs or vsp teams’ work how will this pathway be easy for vfs or vsp teams or how will it be easier than what they did before okr which objective key result does this epic push forward success metrics how will you track this pathway’s impact on performance of the platform’s systems and services how will you track adoption of this pathway how will you track the vfs or vsp experience using this pathway we will know we re done when what requirements does this project need to meet for you to close this super epic additional details notes optional any other relevent information about this project not already listed above artifacts link to product outline communication team that owns this super epic e g product support teams contributing to this super epic e g fe tools be tools ops ,1 16614054879.0,2021-06-02 14:43:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update emails in wizard to be lower case issue description emails in the wizard terminus for vet tec and rogers stem are currently all caps change these to lowercase tasks change emails in wizard to be lower case acceptance criteria emails lower case,1 14532989306.0,2020-12-14 23:31:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, defect debt letters debt detail notice and balance information must have a programmatic relationship enter an issue title using the format brief description of the problem edit buttons need aria label for context add another user link will not receive keyboard focus heading levels should increase by one error messages should be more specific blue button on blue background does not have sufficient contrast ratio feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix vfs point of contact jennifer user story or problem statement as a screen reader user i need to understand the relationship between my debt notice starting amount and current amount data right now the labels are read then the values instead of a label then its related value details the introductory data for the following items need to be coded as a list possibly a description list date of first notice original debt amount current balance screenshot and proposed code snippet below acceptance criteria data is presented correctly to screen readers and assistive technology this can be tested by confirming users hear text like date of first notice colon december or original debt amount colon dollar sign one hundred dot zero zero no axe browser violations reported html for description list is well formed and validates no visual change to the layout environment test user solution if known html date of first notice december original debt amount current balance wcag or vendor guidance optional screenshots or trace logs ,1 23414820224.0,2022-08-12 22:27:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,tree test revised left navigation for research and design page on platform website user story as a researcher designer or team stakeholder on the va platform i want to easily identify the guidelines resources practical tips and va specific constraints that may affect my team s research and design practice on va platform assignee jimuhh peer reviewer claytonzook description this revised navigation is based on results from an unmoderated card sort ticket along with feedback from va platform team stakeholders it includes proposed new content revisions to existing content and new categories for both the purpose of this tree test is to evaluate the findability and discoverability of the actionable information that va researchers and their team colleagues need to succeed at research with va participants impacted artifacts tasks convert to csv formatted for optimal workshop create new tree test in optimal generate testable navigation tree from csv data write findability tasks share test with researchers analyze results against success criteria write and share top line summary of results identify well performing categories and areas for improvement peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria ia assigns the navigation schema a pass or fail grade based on kpis including overall success rate direct success rate time on task ia presents findings how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 30590032069.0,2023-07-21 16:13:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,determine which external services have downtimes issue description determine which external services have downtimes that would apply towards tasks determine which external services have downtimes acceptance criteria understanding of which external services have downtimes and update how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13450974513.0,2020-09-08 19:26:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters feedback issue description this ticket contains ui feedback on debt letters as it appears in staging i tried to categorize by page but let me know if you have questions about anything general across all pages all the pages are missing the covid alert the breadcrumbs don t match for example when i click on a debt details button the breadcrumbs don t change from home manage your va debt your va debt to home manage your va debt your va debt details your va debt page remove “home loan” from the subtitle “check the details of va debt you might have related to your education disability compensation pension or home loan benefits “ home loan debts aren’t currently included in the tool “on this page” should be utility bitter bold it’s currently bitter bold current debts padding between the debt name ex post gi bill debt for books and supplies and “updated on ” should be “what if i don’t see a debt” should be an utility bitter bold it’s currently bitter bold padding between “for medical co payment debt please go to pay your va copay bill to learn about your payment options ” and “download debt letters” header should be “download debt letters” should be an it’s currently an faqs “how do i pay my va debt ” should be an it’s currently an “how do i get financial help ” should be an it’s currently an “how do i dispute a debt ” should be an it’s currently an debt details page is “updated on september ” in bitter regular looks kinda bold but could just be me need margin between “date of first notice” “original debt amount” and “current balance” “on this page” should be utility bitter bold it’s currently bitter bold debt letter history is “debt letter history” an it looks the same as “download debt letters” but the latter is an it should be padding looks a little funky between “debt letter history” and “you can view the status or download the letters for this debt ” should be padding between “note the content of the debt letters below may…” paragraph and the letter history table should be padding between the debt letter history table and “download debt letters” should be this was a mistake in the prototype my bad faqs “how do i pay my va debt” should be padding between “how do i pay my va debt” and “you can pay your debt online by phone …” should be padding between the paragraph under “by mail” and “how do i get financial help ” should be download debt letters page the breadcrumbs are missing should be home mange your va debt current va debt download debt letters is “download your debt letters learn your payment…” subtitle in bitter regular looks kinda bold but could just be me the container width for everything on the page looks off compared to the other pages looks way too wide should be consistent with the other pages missing “your debt letters” above the letter table is there still work to be done updating the letter file names still says “letter ” when i download a letter there’s no way for me to tell if it’s in reverse chronological order because all the dates are the same the sorting by date and type aren’t working was there a limitation preventing us from adding that feature to the table padding between the table and “what if i don’t see the letter i’m looking for ” should be content under “what if i don’t see the letter i’m looking for ” is incorrect and is displaying strangely it should read if you’ve received a letter about a va debt but don’t see the letter listed here call the debt management center at you can also call the debt management center to get information about your resolved debts for medical copay debt please go to pay your va copay bill to learn about your payment options the “return to your list of debts ” link is missing table isn’t turning into a list when in mobile view please refer to the responsive table design the ebenefits team uses for the correct styling on mobile tasks split this ticket into additional tickets as needed optional work with design team to incorporate feedback review incorporated feedback with design team acceptance criteria feedback has been discussed and incorporated ,1 11183616321.0,2019-12-31 14:11:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,optimize vets api build time background our vets api builds are painfully slow for how little changes other variables such as dependabot or other automatic builds also slow things down we should identify work paths to improve this build time thereby improving the data driven happiness of those devs working on this codebase this epic needs grooming and further issue definition opening as placeholder for discussion ,1 14229080543.0,2020-11-18 05:26:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and cleanup correct menu section titles to assure they are enabled visn story as a veteran web user i have to be able to see the sections on the left nave menu so i can better understand the sections and areas i want to go in my health care journey resource prod cms va gov task review all system s menus to assure that the following menu sections services and locations news and events and about va… are enabled and have nolink in link field va asheville health care va durham health care va fayetteville coastal health care va hampton health care va richmond health care va salem health care va salisbury health care acceptance criteria all system menu sections are enabled all link fields show nolink ,1 27091496942.0,2023-02-14 21:30:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr facility discrepancy issue description dmc has reported conflicting information for a veteran who was serviced by both orlando and houston it is believed that when the veteran tried to submit a waiver for the orlando debt it came up with the houston facility the veteran added a note on the waiver but it was routed to houston where the veteran currently does not have any debts the last statement from houston was in the last statement from orlando was november and december facilities orlando and houston tasks scott plans to validate the information on the voda end and reach out to vbs if needed acceptance criteria determine cause of issue or route issue to vbs for continued investigation if routed to vbs communicate back to dmc with update for awareness how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21886114016.0,2022-05-19 18:49:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,address having two locations for mobile research guidance user story as a researcher i want clear and updated guidance for mobile research on platform so i have a single source of truth intended audience vfs desired outcome add updated guidance to platform due date description there is that hasn t been marked as deprecated there is also a information should be double check to ensure all needed guidance was migrated to platform or if additional guidance needs to be added once completed the gh page should be marked as deprecated new artifacts possibly a new platform page for mobile research artifacts needing updates tasks compare information on the gh and platform page if there is any information missing decide if there needs to be a new page or if the current section for mobile should be updated mark the gh page as deprecated acceptance criteria github template has been marked as deprecated platform website has been updated if needed updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 22309200748.0,2022-06-13 15:27:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add analytics request label to platform orientation template user story as a analytics insights team member i want proper labeling on the orientation template so that we can track request for our reporting intended audience analytics insights team desired outcome updated labeling for reporting due date n a description michelle dooley reached out requesting that we add the analytics request label to the platform orientation template so that they can track and automate their reporting of requests artifacts needing updates platform orientation template tasks add analytics request label to platform orientation template acceptance criteria github template platform orientation has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 13234216863.0,2020-08-18 15:56:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, better translate evss errors to human readable issue description take another look at what is retryable on evss side translate the error message to human veteran readable acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 32001269955.0,2023-09-21 12:26:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update form routers to be compatible with description platform is planning on updating react router to and done app route definitions additional deprecations ❌ appeals old form indexroute childroutes withrouter old import ❌ burials old form indexroute childroutes ☑️ claims status new indexredirect indexlink nested child routes withrouter old import ❌ disability benefits old form indexroute childroutes old import ❌ disability benefits all claims old form indexroute childroutes old import ☑️ letters new indexredirect nested child routes old import ❌ pre need old form indexroute childroutes note apps marked as old form use deprecated route definitions generated by the forms library these apps cannot be updated to use the new react router until the design system team modifies the forms library route generation logic this covers the required updates apps marked as new already define their routes using the new component approach they do not require route definition changes tasks update old form forms once the design system team has completed their update update tests definition of done all tasks complete all tests passing,1 30793671132.0,2023-07-31 18:06:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,small changes to sw indicator logic follow on for in light of feedback at the vbs voda sync it became clear that some minor changes to the sw logic are required the streamlined indicator should be a flat boolean we re going to pass it in as a hash and then replace that value with a boolean before submission fsrreasons should be preserved not wiped out with automatically approved ,1 30726272011.0,2023-07-27 19:57:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,deliver json of resubmitted fsr forms issue description we have submitted lost forms to the vbs api and ashlie has requested that we also send the json of the forms to her va email to confirm their validity tasks develop script to get json pass script to platform send results to ashlie acceptance criteria ashlie has received json of recovered forms how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30217467859.0,2023-07-05 16:36:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,implement copay notification retry logic issue description mcp notifications run on a daisy chain of workers which collect data from external sources and then use that data to email veterans currently these workers will not retry if they fail which leaves us vulnerable to temporary outages from our external partners this ticket intends to implement retry logic on the relevant workers so that they can retry only on specific errors from external services case specific worker retry logic is demonstrated in mcpnotificationemailjob relies on a response from vaprofile contactinformation service get person which has several possible failure cases see va profile contact information service spec for details returns nil person returns nil person returns common exceptions backendserviceexception newstatementnotificationjob relies on mpi service find profile by edipi and find profile by facility see connection errors constant and mpi service spec rb for details faraday connectionfailed common client errors clienterror common exceptions gatewaytimeout breakers outageexception tasks implement a sidekiq retry in block for mcpnotificationemailjob that only retries on implement a sidekiq retry in block for newstatementnotificationjob that only retries on relevant errors generate new specs to corroborate this behavior ,1 22958606978.0,2022-07-19 13:41:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move accessibility focused research guidance and check list to platform website user story as a vfs researcher i want all the important guidance i need in one location that i know to be source of truth so i don t have to hunt for it and so that i know that i m getting the latest guidance as platform governance team i want make sure researchers have access to important information on platform since it is source of truth for research guidance intended audience vfs teams desired outcome guidance available on platform website and deprecation message in github due date n a description ticket has been merged into this ticket this ticket is to move the two github pages from github to platform website and notify josh of the new process for updating researching with assistive tech at participants requires different considerations than for participants who don t use at there is some but if this guidance is important enough for vfs researchers to reference it s important enough to be on platform as the source of truth researching with participants who use screen readers requires different considerations there is some but if this guidance is important enough for vfs researchers to reference it s important enough to be on platform as the source of truth new artifacts child pages under new page for researching with at participants new page for researching with participants who use screen readers tasks guidance has been created and maintained by joshkimux notify josh of the intention to move to platform website verify with joshkimux that all content within the existing github pages is current and up to date create guidance as separate child pages under add to new pages notify josh how he can suggest changes to the page once on platform website using the create an issue ticket to suggest changes to this page bullet in the footer add deprecation message to each github page with link to platform website once page is created update link on under methods add l resources once page is created update link on under methods add l resources acceptance criteria platform website research with assistive technology users has been created platform website screen reader checklist has been created platform website disability etiquette has been created josh understands the new location and how to suggest edits to the pages documents are linked under additional resources in the research plan template users are aware that the github pages have been deprecated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 19577554928.0,2022-01-04 16:56:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove the va health care facility s contact information on the overview and details pages issue description we received feedback from stakeholders that veterans should contact the hrc for all questions this will improve the veteran s experience and reduce confusion about which number to call depending on the question updated content refer to the prototypes here tasks update the content for all applicable use cases acceptance criteria the ui has been updated to only direct veterans to contact hrc ,1 15836050444.0,2021-04-06 18:47:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and update the usability research plan and conversation guide issue description prior to recruiting for the fsr s usability study we need to review the research plan and conversation guide to ensure it aligns with the form additionally we received feedback that we shouldn t ask veterans for their personal financial information during the session we need to reevaluate the conversation guide to determine a more empathetic way to test the form tasks review and update the and send the research plan and conversation guide to shawna for feedback acceptance criteria the research plan and conversation guide have been updated in gh and linked in this ticket both documents have been sent to shawna for review ,1 30021361653.0,2023-06-26 23:57:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,expand facility locator test coverage problem statement limited testing can negatively impact veterans by delaying the delivery of value due to the need to revert code interrupting service returning incorrect or confusing information creating a negative user experience or perception hypothesis or bet if we expand our test coverage for facilities applications then we expect higher quality code releases how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 13782116297.0,2020-10-08 17:09:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add phone number to schema issue description phone number will need to be prefilled for the save in progress form will need to add this to the schema as well as the backend prefill code tasks add phone number to schema add phone number to prefill acceptance criteria phone number added to form ,1 16107706537.0,2021-04-27 16:51:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design the interaction between fsr confirmation and debt portal issue description as a veteran submitting an fsr i want a way to view my debt request s status after i ve completed my request tasks work with be to define the possible interactions between fsr submissions and debt portal create a design and upload to uxpin create fe and be tickets then attach them to this ticket acceptance criteria designs created and uploaded to uxpin fe and be tickets linked in this ticket,1 21656948521.0,2022-05-06 14:58:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt and bill overview alert messages issue description create alert error messages for debt and bill overview section in combined debt portal mockup links listed in task section mockup screenshots debt and bill api error click to expand debt api error click to expand bill api error click to expand empty state no debts or bills click to expand bills no debts click to expand debts no bills click to expand tasks acceptance criteria alerts are populating appropriately how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23237377465.0,2022-08-03 12:59:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,integrate must should and consider framework for feedback into platform website user story as a vfs team member i want to understand how to interpret feedback received in the collaboration cycle design intent and midpoint review so i can make educated decisions for the success of my teams product on va gov assignee peer reviewer cherylevans description in ticket the must should and consider framework for feedback was drafted approved by governance team and approved by octo de practice area leads now we must integrate that feedback into vfs facing guidance on platform website and into the feedback templates the purpose of this ticket is to ensure vfs teams are aware of the must should and consider framework for feedback and can easily access it on platform website impacted artifacts new page for must should and consider framework for feedback tasks identify where the must should and consider framework for feedback should live on platform website collaboration cycle shira s cents i liken this to be similar to the va gov experience standards may the must should and consider and the va gov exp stds page can live on level with an appropriate level heading or maybe the must should and consider is important enough to be it s own level in the left nav note all tasks following are dependent on the must should and consider framework for feedback being published on platform website we must publish on platform website before we can complete any of the other tasks as we need the url to link correctly create draft pages to update the outcome section of both the design intent touchpoint page and midpoint review touchpoint page to link out to the must should and consider framework for feedback ensure both pages referenced the guidance consistently create a pr to update the collaboration cycle feedback gh template remove the existing definitions for must should and consider include link to must should and consider framework for feedback instructing vfs teams to review link for guidance on how to interpret feedback included within the ticket wordsmith as needed create draft page for change history log shiragoodman can help with this if needed once all of the above is published shared post on vfs all teams slack channel shiragoodman can help with this peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs teams know how to interpret feedback received in the design intent and midpoint review vfs teams can easily reference the must should and consider framework for feedback in their feedback tickets received at design intent and midpoint review vfs teams are aware that must feedback if not addressed could result in a launch blocking issue at staging review vfs teams have been notified of the the new must should consider guidance per how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 26955574070.0,2023-02-08 14:42:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,huron reported submission issues issue description tracking work related to huron reported vha fsr submission issues acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28035276509.0,2023-03-28 14:43:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, kickoff meeting and discovery for streamlined waiver issue description review what we know about the streamlined waiver tasks review excel and pdf paths acceptance criteria kickoff meeting scheduled for wednesday and we will plan to meet on a weekly basis ,1 11789013575.0,2020-03-17 16:27:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rspec performance audit fix the problem our ci takes a long time specifically our specs take approximately minutes to complete more context none work to be done audit our existing spec runs to find long runners fix biggest offender s ,1 31844651212.0,2023-09-14 18:55:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,feedback technical issues high level user story ies enhance pathway for veterans to veterans to submit feedback on the debt portal or highlight issues to the dmc problem statement in a couple of sentences describe the who what why and where of the challenge pain point you seek to address follow your problem description up with a how might we statement re framing that challenge as an opportunity don t hint too much at what the solution might be you should have enough of a focal point here to guide your ideas but plenty of freedom to think laterally and innovatively as you experiment and prototype later hypothesis or bet how will this pathway impact the quality of vfs or vsp teams’ work how will this pathway be easy for vfs or vsp teams or how will it be easier than what they did before okr which objective key result does this epic push forward success metrics how will you track this pathway’s impact on performance of the platform’s systems and services how will you track adoption of this pathway how will you track the vfs or vsp experience using this pathway we will know we re done when what requirements does this project need to meet for you to close this super epic additional details notes optional any other relevent information about this project not already listed above artifacts link to product outline communication team that owns this super epic e g product support teams contributing to this super epic e g fe tools be tools ops ,1 27092190457.0,2023-02-14 22:09:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, spouse employment information loop issue description spouse employment history needs to be updated to match veteran employment history loop adding history flow should match veteran history along with design similar to below the cards and radio button will likely change after design review tasks add the following pages employment mini summary employment history information current employment income current employment deductions checklist current employment deductions input add update necessary unit tests for these page additions add update necessary end to end tests for these page additions acceptance criteria spouse employment history loop matches veteran history loop spouse employment history is hidden behind efsr feature flag how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27271510706.0,2023-02-22 22:51:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, spouse benefit information page issue description update spouse benefit information page to good news is that we can use standard vafs functionality without any super custom logic tasks add spouse benefit information radio option page add spouse benefit information page with inputs add update unit tests for new page add update end to end tests for new page acceptance criteria spouse benefit information page matches design and is hidden behind efsr feature flag how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14001587656.0,2020-10-28 13:50:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch signatures as a veteran i want the ability to esign the fsr form and submit electronically to dmc ,1 26839118641.0,2023-02-02 22:16:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, real estate enhancements issue description update real estate pages to match tasks update real estate pages to match new design acceptance criteria new real estate pages are implemented behind feature flag how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23443199201.0,2022-08-15 16:52:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging review benefits combined debt portal note this template is being deprecated if your kickoff meeting took place after may you should be following the guidance specified in the collaboration cycle rquest per the instead if you are unsure if this applies to you please reach out to the governance team on the vfs platform support slack channel steps to complete staging review before meeting vfs product manager create this issue and schedule meeting via calendly you are responsible for adding the vfs attendees notify the collaboration cycle team of this ticket and scheduled date time in vfs platform support add artifacts listed below to the ticket at least days before scheduled meeting ensure you ve provided staging access information for the tool or feature don t put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository if this product contains any add the experimental design label and schedule a meeting with dsc to present the research findings platform add the platform reviewers to scheduled meeting add zoom information to scheduled meeting create feedback tickets and link them to the staging review epic after meeting vfs respond to platform feedback tickets close individual feedback tickets when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket update staging review ticket with the product’s launch date after it has gone live close staging review ticket when the review is complete and the product has launched communicate any and all known accessibility issues that are not addressed prior to launch to the va office via platform artifacts provide links or documents for the following staging url and staging test user information staging users staginguser has both a copay bill and benefit debt best to see full experience staginguser has only benefit debts staginguser has only medical copay bills staginguser has neither benefit debt nor copay bills do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository use this accessible staging account template to do so release plan template content artifacts your product’s content source of truth phase debt portal content and ia strategy combined debt portal github ticket for any relevant static content page and entry point updates for tool or feature if applicable qa artifacts product test cases test plan in testrail with test execution logs accessibility artifacts preferred or list of known issues • issue • issue • issue scheduling open the select a date and time and click “confirm” add your name and email click add guests and enter the vfs meeting attendees email addresses click schedule event please note you are responsible for adding the vfs attendees if you have more than vfs attendees you can forward the invite after it is scheduled platform will add the platform reviewers you will receive an email and the meeting will be automatically added to your calendar please note staging reviews are scheduled on thursdays all times are shown in et available time slots are indicated with when you reserve a time slot the reserved meeting will show up alongside the please select a time slot at least business days from request date additional information please refer to or the on platform website for more information about the collaboration cycle fyi shiragoodman chaseakirby ,1 14004960269.0,2020-10-28 17:47:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch signatures as a veteran filling out the fsr form i was the ability to electronically sign the form ,1 15597946555.0,2021-03-18 17:30:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consolidate duplicate contact info util code there is duplicate or nearly duplicate code in src applications personalization profile util contact information formvalues js and src applications personalization profile util contact information js we should consolidate it remove any duplication ,1 20995218183.0,2022-03-29 12:59:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor standard react select component to the new vaselect component in va designs vaos application has a select component based off of the react select component that needs to be refactored to the new vaselect component ,1 30320839493.0,2023-07-10 19:06:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display employment questions issue description i think has ui options hideonreview set to true so easy fix just want to make sure that the edit for these is definitely hidden bc it could cause validation issues if the radio options get changed on final review with that in mind this change should probably come in after has been completed see for copy tasks implement read only display on final review page acceptance criteria employment questions are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21656942727.0,2022-05-06 14:58:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create debt and bill overview sections and card components issue description create debt and bill overview sections and card components tasks create card component to display individual debts and bills create debt and bill overview section populated by debt bill card component acceptance criteria debt and bill overview section is created and correctly populated by available debts and bills how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14703857292.0,2021-01-04 15:38:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for va eastern oklahoma health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field to include is a referral required are walk ins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems va eastern oklahoma health care ernest childers va outpatient clinic jack c montgomery va medical center jack c montgomery east va clinic mcalester va clinic mccurtain county va clinic tulsa eleventh street va clinic vinita va clinic yale avenue va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 20142431392.0,2022-02-09 01:33:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research and update all campus map locations for ur and naming story as a veteran i need to have campus map direct under the facility so i can easily find it in the system and utilize the correct bread crumbs to return resources cms report area tasks after confirming with ia and po update all campus maps under each main facility and update the name and meta data to comply determine page locations and if they will need redirects update page name to campus map and meta description to system name campus map upon approval and comms to stakeholder move campus map to new parent link acceptance criteria,1 23114547325.0,2022-07-27 15:32:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor the fsr endpoints and logic to be moved into the debts api module issue description once we have a debts api module available to add code we have ownership over it makes to start this refactor with the fsr endpoints tasks create fsr services add fsr controllers update business logic acceptance criteria we have exposed fsr endpoints within the debts api module how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25281450493.0,2022-11-16 16:03:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add additional debt letter types to debt letter downloader issue description what details are necessary for understanding the specific work or request tracked by this issue tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14546066448.0,2020-12-15 20:38:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,break global selectors js file into feature specific selectors files all our selectors are in one global file but many of them are very specific to functionality in each feature so we should move them into feature specific files where it makes sense ,1 15106450717.0,2021-02-08 14:19:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove the progressive disclosure components from issue description the va design system is moving towards splitting our form’s pages into smaller chunks to reduce cognitive load so we need to remove the fsr s progressive disclosure components and create additional pages to spread those input fields across this ticket encompasses the changes for tasks remove all the progressive disclosures from the fsr evaluate the questions inputs that were in the original progressive disclosures and create additional pages as necessary acceptance criteria the fsr s ui has been updated and exported to uxpin the updated uxpin is linked in this ticket ,1 15396437822.0,2021-03-03 20:38:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, rated disabilities write new cypress tests that adhere to migration guide description the testing team recently rolled out an upgrade to cypress bumping the package version from to though there are no breaking changes to go through in preparation for cypress upgrades that would introduce breaking changes rated disabilities currently has old tests that run using nightwatch a deprecated technology for va gov new cypress tests should be written and they should adhere to the latest standards set forth in the migration guide considerations migration guide tasks write cypress tests for rated disabilities that adhere to the recommended standards prescribed in the migration guide definition of done tests run properly pull request submitted ,1 16194735461.0,2021-05-04 13:19:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update list loop component to render add item by default on review page issue description for the list loop component on the review page when a user updates the yes no question from no yes it should display the add item by default tasks update list loop to show add item by default verify correct item titles acceptance criteria list loop should show add item by default on the review page item titles should render correctly ,1 19350670472.0,2021-12-15 15:20:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html markup isn t valid general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers noah gelman noahgelman accessibility platform issue html markup isn t valid issue details the value of an aria id must be unique to prevent other instances from being overlooked by assistive technologies failing elements my vamy healthprofilesign out sarah koomson link screenshot or steps to recreate va gov experience standard other references wcag sc a platform recommendation in order to prevent invalid markup a unique id must be implemented so jaws nvda does not overlook the second instance could possibly use id myva account menu id myhealth account menu etc vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 17017356075.0,2021-07-02 13:51:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,edit cards do not open when they hit error state user story as a veteran it is confusing when i press the continue button and it does not let me navigate at the same time of not receiving any validation feedback update the edit card ui to go into edit mode it error exist under neath so when there is an error the veteran knows what to fix and does not need to press the edit button to see the error underneath i expected behavior veterans can see error when blocked by continue button acceptance criteria edit cards open into edit mode when there is an error underneath video ,1 15394596647.0,2021-03-03 18:06:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,calendarwidget refactor simplify loading state functionality we d like to simplify the way the calendar widget handles loading states the calendar doesn t really need to have a concept of loading since it does fetch anything all we really need is a disabled state where all calendar actions are disabled this state should also have a customizable message so that consumers of the widget could pass a loading message or whatever makes the most sense for them changes remove the loadingstatus and loadingerrormessage props add new disabled and disabledmessage props when disabled is true you should get the ui that shows now for the loading state instead of a loadingindicator use the value from disabledmessage for the message in datetimeselectpage handle loading errors by display an error message instead of the calendar ,1 17193197702.0,2021-07-16 13:52:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore ways to make mock data set up easier for unit tests it can be complicated to set up mock data for unit tests you have to know a lot about the properties needed and the way the service calls are made in some ways it s useful to have to know that info because it helps make sure we fully understand what s being tested but i think we could at least streamline both the mock data generation and the helper functions that set up the mock fetch calls some ideas rename helper functions that set up the fetch calls to better reflect what page they go with create higher level mock data functions that cover different variations of appointments or locations update mock data functions to allow more data to be passed as params so we don t have to fiddle with setting data in attributes objects anything else that we can think of that s helpful this should probably be timeboxed and follow up tickets created after the initial work is done ,1 23389239528.0,2022-08-11 16:11:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,quality check research repo cards in the complete column user story as octo and platform we want research to be consistent so that past findings are easier to sort through in order to find relevant data making it more likely that researchers utilize relevant past findings as vfs researcher i want looking through past research to be as easy as possible so it takes less time to look up relevant past findings that may be useful to my team s product assignee claytonzook peer reviewer description currently there is not qa for completed research in order to ensure standardization and to correct potential issues with research repo cards we must qc the repo cards that are presently there to ensure labels are applied properly findings are added in a standardized way and that other relevant information like links to research folders have been added problem statements impacted artifacts tasks decide what the standardized repo card in the completed column should look like are labels checked by what metric order of content in the card findings first check links to artifacts anything else who corrects what to do if a card is majorly deficient not enough information etc what if the researcher is not currently available or no longer with va clayton and kaylen contact through kevin split the qc work look through and standardize the cards presently in the complete column of the research repo by the metrics decided in the first task here peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria research repo qc round complete researchers have an easier time looking through past research how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 13995956672.0,2020-10-28 04:37:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for wilmington va health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field wilmington has facility health services total to include is a referral required are walkins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems wilmington va medical center atlantic county va clinic cape may county va clinic cumberland county va clinic kent county va clinic sussex county va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 16617326108.0,2021-06-02 18:29:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add multiple current jobs user story as a veteran i might have a full time and part time job that are both current update fsr so veteran can add more than one current job this way form can accurately report the most current information solution after we add a page to if yes we just show them another ‘tell us about your current job’ page and loop until they say no to the question asking if they currently have another job tasks update the fsr s ui to reflect the outlined solution above reach out to becca or riley to review the ui updates acceptance criteria employment history list loop can accept more than one current job ,1 21783024517.0,2022-05-13 21:17:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debug connection to vbs prod endpoint issue description receiving general error when using new va network vbs endpoint working to reproduce in staging environment tasks reproduce bug and find resolution acceptance criteria stable deploy in production how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16829919758.0,2021-06-18 02:01:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,use the same template for vamc locations pages in preview vs full build currently we use src site layouts health care region locations page drupal liquid to render vamc locations pages e g cheyenne health care locations in the full build and src site layouts locations listing drupal liquid to render them in the preview server we should use the same template for both to avoid having to maintain code in places ,1 26806211255.0,2023-02-01 18:29:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, user research study spreadsheet issue description spreadsheet for fsr user research study tasks create a spreadsheet for fsr user research study acceptance criteria ,1 12499919133.0,2020-06-01 21:06:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design intent collaboration debt letters mvp steps to complete design intent collaboration product manager or designer create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in design in slack tag crystabel reiter emily crystabel and emily to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must provide list of artifacts below vsp design intent collaboration meeting completed design experts leave feedback and relevant resources on this ticket vfs designer acknowledge receipt of feedback resources vfs designer and all other requesting team attendees complete brief survey artifacts please provide the following at least days before the scheduled meeting meeting attendees from requesting team designer s required rebecca walsh riley orr product manager optional leah keeler depo design lead required as applicable matt self scheduling preferred dates or times monday june all day additional notes design experts will provide a list of relevant design components and patterns with urls a list of existing applications or pages with similar execution or patterns with urls in staging during this collaboration point you will receive feedback from the following practice areas design accessibility content ia ,1 30693590642.0,2023-07-26 16:49:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, platform research approval issue description add research plan and conversation guide to for approval tasks review research plan and conversation guide add research plan and conversation guide to make any necessary updates based on feedback acceptance criteria research submitted to platform ,1 13232873270.0,2020-08-18 14:00:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, conduct pt diary code workshops w dmc issue description conduct diary code workshops w dmc tasks conduct thursday jul conduct friday jul consolidate decisions made and upload to gh make a ticket for the final parts of the workshop acceptance criteria workshops conducted decisions documented in gh ticket made and linked in this ticket ,1 23599328055.0,2022-08-23 23:07:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,open security review process for vha sharepoint issue description since sharepoint is a new integration with possible security concerns we need to open the security review process soon to authenticate the workflow va gov portal vha sharepoint tasks acquire ato boundary from vha build architecture diagram of sp interaction open security review ticket with desired info acceptance criteria the review process is underway for our sharepoint upload feature how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25981110000.0,2022-12-19 18:56:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,front end documentation pop wrap up issue description ptems pop is ending on december final documentation and wrap up tasks update with knowledge and understanding from front end team consider editing statements that may be out of date or incorrect or could be modified for additional clarity updating list of team contacts with any contacts the fe team frequently reaches out to for assistance guidance “gotchas” not sure what format this may take but you guy have intimate knowledge of the form system and the portal itself if there are any tips tricks or ‘watch out fors’ you want to share acceptance criteria been updated as much as possible how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24525956236.0,2022-10-11 13:09:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update problem statement on collaboration cycle product outline user story as a governance team member i understand the problem statement for the collaboration cycle better apply my area of experti assignee peer reviewer description the problem statement on the collaboration cycle product outline has been outdated for some time now and needs to be reviewed impacted artifacts tasks review the current problem statement write a new problem statement reach out to shira ray on platform governance team channel for approval peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria governance team members have a clear vision of the current problem and pain points in the collaboration cycle governance team members understand how they can contribute to help the collaboration cycle how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 27744827386.0,2023-03-15 16:21:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add the banner official government web component in the vaos platform design system team built a banner official government web component we should add the new web component in vaos known differences tasks add the web component va official gov banner acceptance criteria add va official gov banner component ,1 27015432368.0,2023-02-10 18:54:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,establish swagger doc for vbs mcp new statement notification issue description during weekly touchpoint with vbs to progress mcp notification for new statement work forward we identified the need to establish a swagger doc tasks build a swagger doc and share with vbs acceptance criteria swagger has been established and shared with vbs team how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20917018152.0,2022-03-24 14:15:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add lead time to midpoint review and staging review user story as a vfs team member i want to know how many days in advance i need to schedule a design intent so that i can plan accordingly intended audience vfs teams desired outcome platform website is updated to specify lead time on midpoint review and staging review due date tbd description recently updated the to specify that the design intent requires a day lead time the lead time information is missing from midpoint review and staging review this ticket will be for updating those pages to reflect the lead time artifacts needing updates tasks use the as a reference on the midpoint review page under timing add the sentence midpoint review requires a day lead time on the staging review page under timing add the sentence staging review requires a day lead time acceptance criteria midpoint review page on platform website has been updated per guidance staging review page on platform website has been updated per guidance updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 22306761660.0,2022-06-13 13:40:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cdp staging review content updates what happened content needs to be updated to match design requirements per staging review from riley below tasks your va debt and bills ‘your va debt and bill’ to ‘your va debt and bills’ the chevron in the cards differ between ‘your va debt and bills’ and ‘current debts’ current debts add periods in the sentences under ‘pay by phone’ and ‘pay by mail’ debt details add periods in the sentences under ‘pay by phone’ and ‘pay by mail debt letter download when expanding to view older letters the letters are indented they should be flush with the demand letter links under ‘latest debt letters’ current copay balances remove ‘account number ’ from ‘pay by phone’ accordion change ‘your account number ’ to ‘your account number’ under the ‘pay by mail’ accordion remove ‘account number ’ and ‘your facility’s address’ from ‘pay in person’ accordion global benefit debt overview details pay va gov should open in a new tab,1 25981071564.0,2022-12-19 18:54:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint november dec sprint goals end of contract documentation for all disciplines vbms logs for stakeholder audit update contact information linked to veteran profile continued discovery for streamlined waiver user journey paths card mock up for enhanced fsr tests and navigation testing refactor the fsr endpoint address fsr veteran submitted compromise issue discovery for va file number not found resolution option explainer enhancement sprint deliverables list of deliverables completed during sprint contract end documentation planned issues fsr enhancements veteran contact information enhancement fe pts card mockups design pts continue discovery for user journey paths design pts add navigation testing to efsr tests fe pts refactor the fsr endpoints and logic to be moved into the debts api module be pts veteran entered compromise amount not seen on dmc endpoint fe pts resolution option explainer enhancement fe pts other aggregate vbms logs since launch be pts discovery for bgs peopleservice vafilenumbernotfound be pts contract end documentation back end documentation pop wrap up be pts front end documentation pop wrap up fe pts design documentation wrap up design pts unplanned additions will be added throughout the sprint as identified capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 12498454191.0,2020-06-01 18:18:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create dmc backend service scaffolding user story or problem statement as a backend developer i need to provide a backend service for connecting with the dmc to extract relevant data to generate a debt letter for the veteran goal documentation that explains the dmc backend service code objectives or key results this is meant to further the dmc backend service will allow for the creation of api endpoints that will allow users to get information related to debt letters when they are released tasks create service class create config class faraday connection create breakers initializer create response class update settings yml acceptance criteria dmc service will be created ,1 23906812898.0,2022-09-09 02:17:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint september sprint goals review streamlined waiver user flow and discovery questions with vha smes draft design wireframes and user for streamlined waiver and wizard initiate phased roll out of combined fsr for vha monitor combined fsr roll out review application page text changes with smes move fsr api submission logic to background job return pdf details upon fsr submission create tests for copay resolution options upload pdf versions of fsr vha requests to create design for other living expenses implement checkbox to input boxes on fsr integrate continuous add credit card bills resolve sentry error for numeric input define three user scenarios for wizard and streamlined waiver generate staging api key for vbs authenticate vbs on new statement route sprint deliverables list of deliverables completed during sprint streamlined waiver user scenarios design wireframes for streamlined waiver fsr enhancement collaboration cycle kickoff streamlined waiver collaboration cycle kickoff planned issues combined fsr review application page text changes with smes pt move fsr api submission logic to background job pts return pdf details upon fsr submission upload pdf versions of fsr vha requests to pts create tests for copay resolution options create tests for debt resolution options fsr enhancements design for other living expenses pts investigate removing cross app references from fsr pt checkbox to input boxes enhancements pts enhancement continuous add credit card bills pts streamlined waiver wireframes user scenarios for wizard and streamlined waiver draft pts define three user scenarios for wizard and streamlined waiver pts mcp notification generate staging api key for vbs pt authenticate vbs on new statement route pt unplanned additions sentry error for numeric input fix pt capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline coming soon use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff n a tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 22776945810.0,2022-07-08 15:18:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html markup isn t valid general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue html markup isn t valid issue details when viewing current debts summary debt balances the check details and resolve this debt links have invalid values for aria describedby the id provided has an extra in it that doesn t parse correctly i m guessing it s just a typo that snuck in but as currently coded the screen reader friendly description isn t announced at all i would also recommend using aria label instead of aria describedby or else re phrasing the hidden description text that s used for these links explanation provided below link screenshot or steps to recreate when logged in as test user the link and referenced description element are coded as check details and resolve this post gi bill debt for housing check details and resolve this debt va gov experience standard other references wcag sc a platform recommendation removing the extra should resolve the issue if it makes sense i would also recommend removing the description span entirely and just inserting that text as an aria label on the link itself eg check details and resolve this debt aria describedby and aria label result in slightly different screen reader behavior aria describedby will cause the screen reader to announce the description after announcing the link text on nvda with the example included here that would sound like check details and resolve this debt link check details and resolve this post gi bill debt for housing aria label will cause the screen reader to announce the label instead of the link text on nvda that would sound like check details and resolve this post gi bill debt for housing i think aria label better matches the intention here and it keeps the screen reader version of the text closer to the link which is helpful for code readability if you keep the aria describedby you could probably rephrase the text to make it less wordy and grammatically cleaner vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 26969492668.0,2023-02-09 02:42:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove practice area check boxes for staging review user story as a governance team member i don t want to have to check a separate box in the staging review section of the collaboration cycle request template confirming that i completed by practice area review assignee sterkenburgsara peer reviewer description the practice area checkboxes under staging review in the collaboration cycle request template feel a bit redundant we should remove the checkboxes which are often overlooked and forgotten and explore new ways of communicating to the vfs team that each practice area completed their review note team decided that no replacement solution was necessary impacted artifacts staging review template tasks remove practice area specific checkboxes from in the collaboration cycle kickoff moderator responsibilities guidance peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria governance team knows that submitting their feedback to the drafting template and checking the box within the template is sufficient for communication completion of review internally vfs teams no longer see individual practice area review checkboxes in their staging review codeblock how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 11610422294.0,2020-02-26 03:00:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add unit tests for the paymentinformation component we should make sure that the component does not render anything unless the required control information data flags are true ,1 13249107684.0,2020-08-19 20:11:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert cc contained resources to location and practitioner resources right now our contained resources for cc provider and practice data are in a weird not really fhir format we should structure those as actual resources ,1 25548938621.0,2022-11-29 21:30:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, enhancement continuous add employment history desired behavior update user interface to match new spec and rewrite logic to no longer use list loop in favor of manual looping based on continuation question acceptance criteria ui updated and list loop replaced with continue question how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 23112306933.0,2022-07-27 13:58:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits sprint priorities sprint july july formerly debt resolution team sprint goals summarize and synthesize user research session findings present key research findings and recommendations establish api for vbs to enable mcp notifications architect fsr refactor finalize lower environment testing for huron workstream connect to sharepoint api launch combined debt portal discovery work for combined financial status report sprint deliverables list of deliverables completed during sprint usability research session findings and recommendations planned issues combined debt portal usability study synthesis research findings pts almost match between visible text and screen reader only text recommend review for redundant aria the content isn t written in plain language and contains excess words and modifiers design components or patterns don t align with design system guidelines combined fsr architect new structure of fsr generate and submit mock fsr requests to vbs staging design and research discovery cfsr discovery estimation of timeline and work effort discovery estimation of timeline and work effort authenticate and test integration with vha sharepoint mcp notification create mcp endpoint for vbs to submit new statement data pts unplanned additions your content doesn t use correct and consistent labels across links entry points navigation components and pt capacity planning pto holiday s denise scott brandyn andrew megan brie start points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr streamlined waiver github epic product outline use cases flow release plan architectural diagram use cases usability testing n a dates product guide mcp product guide kickoff design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 30832564141.0,2023-08-02 03:47:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint july august sprint goals identify all sw mvp work and create tickets for all mvp development complete desktop mobile prototypes complete research plan guide for sw secure approval for sw content complete all be work for sw update review page for sw planned issues fsr enhancements downtime dependency update pt fe navigation content update pt fe streamlined waiver product outline for streamlined waiver pt mobile prototype uxpin design sw implement income limit back end fe streamlined waiver prep fe organization of folders fe front end discovery form navigation back to review page pts fe review display employment questions pts fe review display installment contracts fe look into possible approaches for adding an indicator for sw forms be observer notes documents design sw add new chapter level depends and structures fe sw update transform and helpers fe add streamlined waiver notification to va notify portal pt be send streamlined waiver notification for eligible requests be add an indicator for sw forms be sw release plan finalize transparency content design sw create example submission objects for be pts fe finalize conversation plan on github research finalize research plan on github research pilot session design ongoing maintenance bug fixes determine which external services have downtimes be develop method to keep benefit payments from becoming stale be use vcr for unit tests be blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint update sharepoint credentials and resubmit missed submissions be review display cleanup titles and spacing design points planned points accomplished xx tbd xx points over issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 18948850450.0,2021-11-18 13:14:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, designs for html statements issue description once initial technical discovery is completed we need to incorporate html statements into the detail pages of mcp tasks create mockups of the new html statement designs detail page html statement page and upload to uxpin acceptance criteria designs uploaded to uxpin designs shared with fe fe tickets created ,1 15168720515.0,2021-02-12 19:53:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, unauthenticated issue description as we move towards releasing an unauthenticated fsr we need to adjust some of the ui to gather information that would be populated in an authenticated experience this work encompasses the ui updates to tasks update the unauthenticated fsr s ui to match acceptance criteria the unauthenticated has been updated to match the uxpin mockups the ui has been reviewed by a designer ,1 30676687607.0,2023-07-26 06:04:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,copy of review display employment questions issue description i think has ui options hideonreview set to true so easy fix just want to make sure that the edit for these is definitely hidden bc it could cause validation issues if the radio options get changed on final review with that in mind this change should probably come in after has been completed see for copy tasks implement read only display on final review page acceptance criteria employment questions are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14952682971.0,2021-01-26 15:48:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,document design changes for list loop error states issue description when there is an error on the list loop inputs the card distorts document the intended design pattern with the feedback given in the dsva design channel tasks document intended design create a ticket for fe to make changes to existing form acceptance criteria design synced to uxpin and linked in this ticket fe ticket created and linked to this ticket,1 21579588631.0,2022-05-02 17:13:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,letters replace e benefits link description if no records are found in the letters app a link to ebenefits download letters remove this link as the ebenefits destination no longer exists additionally there are links to ebenefits apply for coe and download dd pages that need to be updated tasks remove link to ebenefits update tests as needed definition of done all tasks complete all tests passing,1 16004968675.0,2021-04-20 00:59:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cheetah code reference clean up item description user facing references to cheetah are being updated in make relevant updates in the code this would be things like function names redux state names component names etc acceptance criteria replace non user facing cheetah and cheetah project references feature flag name is not updated event names are not updated unless cleared with lauren,1 30217161453.0,2023-07-05 16:22:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,record vcr cassette for sharepoint integrations issue description sharepoint api calls are being manually mocked right now and need vcr recordings to more accurately represent their interactions tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24416790169.0,2022-10-05 16:35:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, upgrade refactor cypress testrail integration for cypress upgrade and or refactor integration scripts libraries to keep working between cypress automated testing framework testrail test case management system platform qa is upgrading cypress from to with breaking changes definition of done what must be true in order for you to consider this epic complete cy tr reporter party open source integration library works with cypress how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 13232872152.0,2020-08-18 14:00:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters uat qa study issue description in order to qa integration between dmc endpoint and vbms we need to test with real users the have debt and have received debt letters since there is no concept of test accounts in prod environment they uat process will validate authenticated user will see debt summary authenticated user will see the debt letters that they received in the mail and have ability to download and confirm tasks research plan conversation guide acceptance criteria research plan and conversation guide have been uploaded to gh and attached to this ticket research plan and conversation guide have been sent to shawna for review how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14019661436.0,2020-10-29 18:30:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, why do we reject read only pdfs issue description although we reject locked pdfs we are also purposefully rejecting read only pdfs do we need to reject them for real acceptance criteria find out why we can t accept a read only pdf allow them if we don t find a good reason to reject how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22838239517.0,2022-07-12 18:53:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,parse delimiter characters out of fsr json issue description the characters and are used as delimiters for the eventual csv version of fsr requests and need to be parsed out of the initial json so as not to disrupt the format tasks parse characters out of json fields before vbs submission acceptance criteria vbs submissions will not include or how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15614932623.0,2021-03-19 18:29:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor fl mobile desktop rendering into one responsive view issue description the facility locator code src applications facility locator needs some refactoring we should convert the separate rendering for mobile and desktop views into one responsive view such as show tabs at mobile width toggle map hide tabs at desktop width and always show map tasks refactor the separate desktop and mobile rendering code into one responsive view acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21636230900.0,2022-05-05 14:27:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, list loop redesign flow issue description this issue captures migrating the fsr s list loop redesign flow from miro to mural so the wider team has access and we can share it with stakeholders and platform as needed tasks recreate the fsr s list loop redesign flow in mural document the flow in gh acceptance criteria the flow has been added to gh and linked in this ticket ,1 14529963001.0,2020-12-14 18:33:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consider caching provider list on the front end typically when we fetch a list of data on the front end we will cache it in redux so that we don t have to fetch it again for the same parameters currently we re not doing this for the cc providers even though they query could take a while we should consider doing so we d have to store it in redux with some kind of composite type of care and location key or we could take this opportunity to explore using swr or react query for this page ,1 25335894149.0,2022-11-18 16:48:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update zoom info for future accessibility orientations user story as an accessibility orientation host i want a scheduled reoccurring zoom meeting so that i do not need to email participants a new zoom invite intended audience accessibility orientation host desired outcome a reoccurring scheduled zoom meeting due date n a description with the introduction of calendly and monthly scheduled orientation meetings we identified that having each host provide their zoom for ease would provide the best experience with noah s departure we have updated it in the interim with chase s zoom this ticket is to update the zoom with a host s information artifacts needing updates calendly tasks n a acceptance criteria calendly zoom information has been updated potentially blocked until calendly adds functionality currently in their backlog confluence orientation sessions has been updated platform website calendly orientation sessions has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 14960072565.0,2021-01-27 04:52:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for va eastern oklahoma health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field coatesville va has a total of facility health services to include is a referral required are walkins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems va eastern oklahoma health care ernest childers va outpatient clinic jack c montgomery va medical center jack c montgomery east va clinic mcalester va clinic mccurtain county va clinic tulsa eleventh street va clinic vinita va clinic yale avenue va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 15680872086.0,2021-03-25 03:57:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and correct invalid content in system health services for va fayetteville coastal health care story as a veteran i need to have accurate and correct system health service description so i can quickly and correctly find where to go to get my correct health care support goal accurately update health services with approved content resources task fayetteville coastal has a total of system health services to replace update all system health services with html code from health service library resource assure that intro line is correct e g care we provide at va fayetteville coastal health care acceptance criteria all system health services have been replaced with correct html code and the intro has been replaced with care we provide at va fayetteville coastal health care ,1 24557969405.0,2022-10-12 17:30:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr future consideration product outline the online financial status report fsr has been live since november as time goes on we are collecting feedback from various sources veterans stakeholders vsp platform vfs team etc outlining various ways to potentially improve the overall experience this epic is a consolidation of feedback that isn t currently slated for development but capturing for future consideration how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 14941712264.0,2021-01-25 20:10:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, the cancel buttons in the list loop component isn t working correctly issue description there are multiple bugs occurring with the cancel buttons in the list loop component how to recreate the bugs in staging navigate to step your employment history select yes for have you been employed within the past two years select yes for are you currently employed select the add payroll deduction button bug selecting the cancel button on the second payroll deduction card doesn t close the card ideal experience selecting the cancel button should remove the card bug selecting the cancel button on the default payroll deduction card breaks the form ideal experience there shouldn t be a cancel button on the default card unless the user has already saved inputted values and is in the edit mode in this case the cancel button s action would cancel the action and close the card with the original inputted values please refer to this video for more info tasks update the list loops so that selecting the cancel button on subsequently added cards removes the card remove the cancel button on the default card ensure that the cancel button only displays on the default card if the user is editing previously inputted values acceptance criteria updates have been pushed to staging and sent to a designer for review ,1 15110402104.0,2021-02-08 19:10:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr income content needed fo rgross monthly income story as a veteran filling out fsr i would like to understand what gross income means so i can put the right amount into the field tasks write content provide content to fe dev ,1 12396552653.0,2020-05-20 20:45:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters create mock response functions to supply mock data to new components create mock responses to supply mock data to frontend prior to api integration is complete ,1 14971543553.0,2021-01-27 21:19:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, global content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to the entire form tasks incorporate the global changes outlined on page and of the provided document acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 20737992656.0,2022-03-14 15:14:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, prototype issue description veterans expect to find all money they owe to va in one location on the site additionally congress has mandated that we provide a way for veterans to access all their debts in one spot as a result we need to create a finalized prototype of the combined vba vha debt portal this work should be completed once the wireframes have been reviewed and approved by stakeholders and early ia recommendations are incorporated we should also kick off the collab cycle if we haven t already tasks create hi fi prototypes of the combined debt portal acceptance criteria prototypes have been linked in this ticket ,1 13171498699.0,2020-08-11 16:46:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore converting local mocking to msw the msw library was added to vets website a while back and could be a good replacement for our custom mocking solution used when running vaos locally we could also potentially use this for integration tests but i think it s worth exploring the local mocking first ,1 27117524111.0,2023-02-15 19:49:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,define prototype requirements issue description what details are necessary for understanding the specific work or request tracked by this issue tasks meet as a group to define prototype requirements acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23439530257.0,2022-08-15 13:38:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create combined selection array and conditionally render copay debt resolution options desired behavior combined fsr updates add copays to the selectable options for resolution as well as allow them a different set of resolutions options to select from the form config needs to be updated to combine and utilize the array of both selected debts and copays now and depending on which type each is show their respective resolution options acceptance criteria combined array being used conditionally rendering resolution options how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 19596957879.0,2022-01-05 19:05:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content updates to the balance cards issue description we received feedback from stakeholders to adjust the verbiage on the copay overview and details pages balance cards because balances can change between the time a veteran receives a statement it s important for them to know the last time the balance was updated so they don t make duplicate payments tasks update the balance card content on both the overview details pages acceptance criteria the updated designs have been linked in this ticket ,1 19350671112.0,2021-12-15 15:20:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, button and link language isn t descriptive and or their purpose isn t clear general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers angela fowler accessibility platform issue button and link language isn t descriptive and or their purpose isn t clear issue details the links check details and resolve this bill provide purpose but not a target link screenshot or steps to recreate va gov experience standard other references wcag sc a platform recommendation we recommend using an aria label to replace the generic this bill with the specific target for example check details and resolve this bill this will allow the specific bill name to be read out on a screen reader s links list more details on aria and link text at level access vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 19350673715.0,2021-12-15 15:21:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design component or pattern is not functioning or working as expected general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers mikki northuis mnorthuis ia platform issue design component or pattern is not functioning or working as expected issue details breadcrumb segments must match the corresponding page the current page segment of the breadcrumb on the copay details page does not match that page s link screenshot or steps to recreate va gov experience standard other references platform recommendation make breadcrumb match on copay details page vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 16601844025.0,2021-06-01 20:39:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, implement redesigned employment sections issue description we redesigned the employment sections of the form to allow for multiple current jobs by having a single list loop for employment and subsequent income pages for each current job we need to replace the current pattern for both the veteran and their spouse with the redesign tasks update employment sections for both the veteran and their spouse review with designers acceptance criteria employment sections implemented reviewed by designers,1 26032979614.0,2022-12-21 23:59:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace expandinggroup react component to additional info web component description design systems team plans to deprecate the react components on january we will need to ensure the vaos application uses the web components currently the app uses expandinggroup react component which will need to be updated to the additional info web component acceptance criteria given when then and page content matches the and page design matches the design spec given when then design assets all spec copy is fpo use copy in copy doc definition of done all acceptance criteria are met documentation is updated ,1 14705741346.0,2021-01-04 18:39:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr update spouse information issue description update spouse sections according to mock tasks what is your spouse s name’ should have a refer to mock type of employment should be a standard dropdown with the following options part time full time seasonal temporary payroll deduction list loop should be populating a table rather than cards verify required fields should be marked so veteran employment details are pre filling into spouse employment acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26543613589.0,2023-01-19 21:33:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, replace soon to be deprecated radio button components issue description is being deprecated and needs to be replaced in the fsr va radio appears to be the most up to date and tasks replace the react component in the following locations src applications financial status report components resolutiondebtcards jsx src applications financial status report wizard pages decision jsx src applications financial status report wizard pages recipients jsx src applications financial status report wizard pages reconsider jsx src applications financial status report wizard pages repayment jsx src applications financial status report wizard pages request jsx src applications financial status report wizard pages start jsx confirm these changes do not affect unit tests acceptance criteria all radiobuttons instances have been replaced all tests continue passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26939810299.0,2023-02-08 00:39:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,document storage transition high level user story ies as a i need so i can hypothesis or bet if we make this change then we expect this to happen okr which objective key result does this epic push forward definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 15494965747.0,2021-03-11 00:02:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consolidate my va dashboard date time helpers we are using similar date and time helpers in multiple places for my va tests search for or inms we should standardize and consolidate those in a common helper file maybe src applications personalization profile tests helpers js ,1 12963116011.0,2020-07-20 18:15:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl incorporate current debt api data into the debt table page for issue description incorporate api data for current debt into of the debt table page and adjust the content on the page to reflect these changes tasks update the uxpin prototype to include debt information share with designer team create a ticket for front end work acceptance criteria prototype updated and linked in comments ticket for fe linked in comments ,1 24389559850.0,2022-10-04 14:17:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,return pdf details upon fsr submission issue description to support the feature of a veteran being able to download their pdf we need to change the response value for the create route the api can either immediately return a file object or the id of the submission to fetch later tasks decide what s best approach for api return add pdf details to return acceptance criteria the pdf download feature is maintained for the combined experience how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16623235200.0,2021-06-03 06:07:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, swap out current policies page with new hardened policies page for visn and save in draft user story as a vha digital media web manager the national policies need to be hardened and available to national administrators only so national content should be changed from one source to all systems goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks archive current policies page replace with cloned page and add to menu for the following systems va cheyenne health care va eastern colorado health care va western colorado health care va montana health care va eastern oklahoma health care va oklahoma city health care va salt lake city health care va sheridan health care complete the follow these steps for each system open policies page in edit mode a change name to policies old b remove menu by un checking menu box c save as archive open fargo or iowa city system and find policies page a select clone from tabs and select clone b go to edit and remove cloned c change governance to match new owner and related system d select menu enable check box e type in policies in name f select from drop down about va from system you are cloning to g copy visiting hours and or security information from original policies page security information will go into other policies section save new policies page as current status of system i e published or draft acceptance criteria all original policies pages have been archived and removed from menu all new policies pages are published and link is in menu at bottom of menu items ,1 27405560566.0,2023-03-01 06:21:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,define prototype requirements issue description as a team we need to discuss the various prototypes that our team needs and what would be helpful moving forward tasks meet as a group to define prototype requirements acceptance criteria requirements and next steps have been identified and future work has been documented to address prototype needs how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12394861546.0,2020-05-20 17:38:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, download debt letters from vbms efolders u user story as a veteran who received a debt letter in the mail i would like the ability to see and download the letter online goal give veterans the ability to see debt letters online and have the ability to download them to print etc tasks connect to vbms efolders authenticate user identify letters to be downloaded viewed view download letter by type acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24557817502.0,2022-10-12 17:22:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,toggle vbms letter downloads on issue description vbms letter incident resulted is the team adding a feature toggle and turning the download feature off on the debt portal feature can be turned back on once the audit has been completed and dmc leadership approves related audit issue tasks get approval from dmc leadership to toggle download feature back on toggle download feature back on for veterans to access letter downloads acceptance criteria letters are available for veterans to download on the debt portal ,1 23851578619.0,2022-09-06 18:27:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, enhancement continuous add credit card bills desired behavior update form to no longer use list loop in favor of new logic and render all in a row like current behavior acceptance criteria list loop replaced with new manual looping behavior based on answering if they have another how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 12216274321.0,2020-05-01 14:48:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design intent collaboration debt letters mvp steps to complete design intent collaboration product manager or designer create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in design in slack tag crystabel reiter emily crystabel and emily to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must provide list of artifacts below vsp requesting team design intent collaboration meeting completed design experts leave feedback and relevant resources on this ticket vfs designer acknowledge receipt of feedback resources vfs designer and all other requesting team attendees complete brief survey artifacts please provide the following at least days before the scheduled meeting link to product outline sketches lo fi mockups meeting attendees from requesting team designer s required name s product manager optional name depo design lead required as applicable name scheduling preferred dates or times additional notes design experts will provide a list of relevant design components and patterns with urls a list of existing applications or pages with similar execution or patterns with urls in staging during this collaboration point you will receive feedback from the following practice areas design accessibility ,1 27747159051.0,2023-03-15 17:49:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,heuristic evaluation synthesis and report issue description what details are necessary for understanding the specific work or request tracked by this issue a review and synthesis of the team s completed individual heuristic evaluations will be done a concise report will be created for the team compiling everyone s individual evaluation feedback in heuristic eval workshop part the team will have a chance to review the issues that were noted and decide what to change tasks what work is necessary for this story to be completed the review and synthesis process creation of a report as a document or a deck acceptance criteria what will be created or happen as a result of this story the review and synthesis process creation of a report as a document or a deck how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23393160673.0,2022-08-11 19:59:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unpublished vet center check issue description during vet center pilot phase we added logic to check to see if a vet center location added as a nearby location is published to determine data source cms or lighthouse this logic was necessary so that unpublished content within cms would not be displayed on the front end see for details once vet center pages are rolled out nationally all locations will be published and this duplicate code will not longer be needed tasks prune out published check for nearby vet centers acceptance criteria cleaner code base no unnecessary logic ,1 22710197435.0,2022-07-05 18:30:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create domo dashboard view of open issues by product user story as a governance team member i want to see the number of issues by product so that i understand known issues as an octo de lead i want to see number of issues by product so that i can fully understand the scope of issues across products brought through collaboration cycle intended audience governance team and octo de leads desired outcome shared understanding of product health across va gov due date tbd description we currently have a with our move to product focus we will need new boards and cards providing data on the product labels added to staging reviews in ticket additional background for initiative new artifacts new domo board for product views total issues by product card total issues by status tasks create domo board for product views add total issues by product card change name to total open issues by product change pie chart to bar graph map labels to an official product name request support from insight analytics ticket opened for support meeting with analytics insights on add total issues by status document queries used and other information for updating maintenance delete archive the total issues by team card acceptance criteria total issues by status card should be editable and able to be maintained by sarah labels should be mapped to an official product name dashboard should display all open staging review issues by product related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 23851561139.0,2022-09-06 18:26:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move fsr api submission logic to background job issue description the increased amount of api requests vbs sharepoint have increased the latency once an fsr is submitted for the combined experience ideally these operations will run in the background while what the client needs pdf url is provided right away tasks move api submissions to worker call worker from model acceptance criteria fsr submission requests have reduced latency how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14171056389.0,2020-11-12 15:16:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,address test flakiness caused by schema pattern we use we have a pattern in some pages where we use the initial unprocessed schema to render schemaform before we actually update the redux store with it this appears to lead in some cases to rtl rendering a form and inputing form data before the redux store is updated i suspect this because in the full error log where this test failure occurs in jenkins there s an error where the schema we pulled from redux is null ,1 25568674861.0,2022-11-30 16:01:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,provide veterans with ability to edit benefit information for their fsr submission issue description as a veteran completes an online fsr they are presented with benefit information we have heard on a few occasions that this information can be incorrect and the business would like to providing veterans with a way to edit the benefit information that is presented to them the edited information should override what is submitted on the form for that submission tasks mock up designs for editing capabilities acceptance criteria design has been reviewed by platform ,1 31809857868.0,2023-09-13 16:04:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint august september sprint goals complete review page complete staging review should do feedback explore opportunities for pair programming prepare for sw usability study research findings presentation planned issues need to add fsr enhancements team qa for fsr enhancements downtime dependency update pt fe navigation content update pt fe move values for pdf fields pts fe installment contract date for fsr enhancements fe review page navigation pts fe streamlined waiver update transform and helpers part expenses fe add new chapter level depends and structures fe ongoing maintenance bug fixes determine which external services have downtimes be use vcr for unit tests be blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished xx tbd xx points over issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 15836079269.0,2021-04-06 18:50:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, wizard content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to the wizard additionally some of the wizard screens haven t been reviewed by the content team yet so this ticket will encompass that work as well tasks send the full wizard flow for content review update the wizard section of the fsr s ui in sketch with the modified content acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 17194962913.0,2021-07-16 15:58:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,schedule vsp support for migration time description on at pm ct the dmc service will be down for a system upgrade after that time a new set of production credentials will go into effect more details here ensure that we have someone available from vsp ops to update the credentials and trigger a production deployment to apply the changes ,1 13531627699.0,2020-09-15 22:02:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove sso redirect logic from url service cerner redirects we re originally facilitated by the api however this logic was duplicated on the front end thus it is no longer needed in the api anymore and can be removed ,1 16173879401.0,2021-05-03 00:21:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,discovery research epic debtres fsr form high level user story as a veteran i want to be able to fill out the fsr on line in order to start the debt resolution process goals we would like to know how to make it easier for the veteran to fill out the fsr form on line in order to start the debt resolution process issues to create within this epic create research plan recruit for research sessions schedule research sessions create conversation guide conduct discovery research sessions at a minimum the team lead pm designer content person should join these sessions discovery synthesis should be conducted as a team led by designer discovery research readout at minimum it is expected that the designer should do a readout at design meetings for their team if stakeholder readouts are needed the team lead pm are responsible for scheduling those designers should also plan to do research readouts at the end of sprint demo how to configure this issue labeled with discovery and research and team name ,1 11425892773.0,2020-02-03 20:46:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove old git branches from github there are well over branches in github for the vets api repository as of this moment many of them are over year old and even more predate the may contract renewal these branches add extra effort to some automated scripts that scan the repository and are long overdue for cleanup the parameters for this cleanup are branch does not have a corresponding active pull request branch predates may the move has been announced in vfs engineers on slack and in the biweekly engineering meeting at worst old branches of value should still be on individual user machines ,1 13935864528.0,2020-10-22 12:10:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres veteran information as a veteran who has been authenticated on va gov by logging in my personal information is refilled from the vets profile service i want the option to review my information and change if it is incorrect ,1 16415237596.0,2021-05-19 05:28:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, validate that react widgets are enabled in top task pages story as a veteran i need to know the reaction alerts work so i can get the resources and information in each section goal enable react widgets to work properly task validate that all enable react widgets for pharmacy medical records and suicide prevention are enabled open reach widget on page confirm that call to action widget is enabled option you can also test all published pages and widgets by going to system url and page and test widget complete for the following visns and systems visn visn visn visn visn visn visn visn visn acceptance criteria all listed systems have been validated that react widgets are enabled ,1 25896736475.0,2022-12-14 23:25:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add octo reviewer s gh handle to collab cycle feedback ticket if feedback came directly from them user story as a vfs team member i want to know which individuals from governance and octo were involved when documenting design intent and midpoint review feedback tickets so that i can follow up with the correct individual if needed assignee cherylevans peer reviewer description for the the design feedback ticket had must should and consider feedback from both and humancompanion usds however it was written in a way where the auth exp team interpreted the feedback to only be from allison the purpose of this ticket is to modify our design intent and midpoint review operational guidance so that if when octo provides feedback to the vfs team the governance team member is mentioning them in the feedback ticket so the vfs team member can see who all was involved impacted artifacts there are no actual changes to this document however the draftingtemplate outline link is located in this document and that document will change tasks for di and mpr add a step for tagging the octo reviewers gh handle in your feedback ticket if the feedback came directly from them for example octohandle use this design element instead for staging review add a note to the additional information column of the issue details and recommendation sections of the individual feedback worksheet of the draftingtemplate outline guidance the notes should say to tag the octo reviewer s github handle if the feedback came directly from them peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria vfs teams are notified if when octo provides direct feedback at the di mpr and sr feedback tickets how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 22156901396.0,2022-06-04 00:36:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analytics implementation or qa support for benefits combined debt portal google analytics implementation or qa request what this form is for more information use this template to request google analytics implementation or qa for your product please fill out all brackets please see the following information for implementation timeline new teams implementation will usually be completed in sprints sprint discovery orientation sprint fe implementation sprint tagging implementation sprint qa all other teams implementation will usually be completed in sprints sprint discovery and fe implementation sprint tagging implementation and qa description required is this request for google analytics implementation or qa google analytics implementation qa who is this request for benefits team formerly debt resolution provide the link s for google analytics implementation or qa looking to set up analytics for the combined debt portal currently not implemented when is the launch date approximately june what interactions need to be tracked kpis for combined debt portal include all pageviews to manage debt and bills all pageviews to manage debt and bills summary ctr from manage debt and bills summary to manage debt and bills summary copay balances ctr from manage debt and bills summary to manage debt and bills summary debt balances total bounces on manage debt and bills summary total clicks to fsr total clicks to pay va gov total clicks to pay gov optional if applicable what test users are needed staging url without content pages with content pages as of content pages have not be added yet staging user staging user can be used for a veteran who has both a copay bill and debt are outlined here if needed any additional comments additional documents if needed please leave the following blank acceptance criteria all appropriate issue tagging is completed qa has been completed events have been added to product and benefit hub content groups additional information please refer to or the on platform website for more information about the collaboration cycle ,1 23789647907.0,2022-09-02 13:27:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, identify text updates for the addition of copays issue description tasks acceptance criteria ,1 18110793502.0,2021-09-23 03:26:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove pittsburgh webmaster e mail phone numbers and other references from contact us story the contact us page should be unique to the system page so that information goes to the correct webmaster or goal remove pittsburgh references and information from visn and visn where the original template was used task review contact us page for any references of pittsburgh or in this case vhapth contact remove vhapthwebteam va gov from contact page contact pao for each system and confirm their correct webmaster e mail check gal e g to report a technical issue or give us feedback about this site email our web team at vhapthwebteam va gov quickly audit visn systems to see if the template was continued acceptance criteria contact page has either correct webmaster or full line removed from page ,1 15836097566.0,2021-04-06 18:51:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, chapter content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to chapter tasks incorporate the changes outlined on page to of the provided document acceptance criteria uxpin has been updated and linked in this ticket work has been checked off in the ,1 26419309234.0,2023-01-13 18:46:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore additional empty states post dec fix issue description fsr submission bug was resolved on december a safety net has been established to catch any submissions so they are routed to vba appropriately since dec we have seen submissions come in see data chart additional testing is required to track down any remaining issues tasks conduct additional testing to identify remaining issues and define next steps acceptance criteria issue has either been resolved or next steps are identified and documented for future implementation how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12369556983.0,2020-05-18 15:25:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design intent collaboration debt letters mvp steps to complete design intent collaboration product manager or designer create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in design in slack tag crystabel reiter emily crystabel and emily to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must provide list of artifacts below vsp requesting team design intent collaboration meeting completed design experts leave feedback and relevant resources on this ticket vfs designer acknowledge receipt of feedback resources vfs designer and all other requesting team attendees complete brief survey artifacts please provide the following at least days before the scheduled meeting sketches lo fi mockups meeting attendees from requesting team designer s required riley rebecca product manager optional leah depo design lead required as applicable matt scheduling preferred dates or times additional notes design experts will provide a list of relevant design components and patterns with urls a list of existing applications or pages with similar execution or patterns with urls in staging during this collaboration point you will receive feedback from the following practice areas design accessibility ,1 23790950288.0,2022-09-02 14:29:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, electronic signature veteran frustrations what happened multiple vets have complained that when they fill out the fsr on the debt portal get to the signing section that it says their name isn’t recognized and doesn’t let them put their name in it fsr statement of truth currently requires the veteran to type their full name which will serve as their electronic signature for the request the assumption is that a veteran was required to enter their name exactly as it appears on their account and if they do not then they are not able to complete the statement of truth discovery tasks investigate what are the current requirements for the statement of truth talk to the dmc smes to determine if there is any flexibility determine next steps and define desired behavior statement of truth screenshot desired behavior tbd acceptance criteria describe the desired working behavior how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 30819204189.0,2023-08-01 15:14:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,establish graphana metric tracking issue description establish metric tracking in grafana to track successful counts failures dmc etc tasks add counts for tracking statistics configure grafana dashboard for those stats acceptance criteria metrics have been established and are ready for use how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14660310316.0,2020-12-28 23:12:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, defect debt letters the debt download table should not have sorting icons if they re not actionable enter an issue title using the format brief description of the problem edit buttons need aria label for context add another user link will not receive keyboard focus heading levels should increase by one error messages should be more specific blue button on blue background does not have sufficient contrast ratio feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact jennifer user story or problem statement as a screen reader user i am confused when the download debt letters table headers announce themselves as clickable but when i press enter or space nothing happens details the download debt letters table columns and have icons that would suggest the columns are sortable if these will not be sortable these icons should be removed screenshot attached below acceptance criteria table columns are either wired to be sortable or the icons are removed if the table is made sortable it s done so in an accessible manner any sorting function has been discussed and collaborated with the accessibility specialist environment test user wcag or vendor guidance optional screenshots or trace logs ,1 11579740600.0,2020-02-21 18:36:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor newappointmentflow js unit tests the unit test coverage of newappointmentflow js is pretty good but i think we could be more organized and precise with a file that s really important to the overall application logic each page should have tests for next and previous if a function tests for each possible outcome in a next previous,1 24963662658.0,2022-11-01 17:31:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update faith owusu sekere to faith arthur user story as a vfs team member i want to be able to find the correct person for ato orientation so that i don t have to reach out for help assistance assignee peer reviewer it harrison description faith owusu sekere has changed her name to faith arthur the purpose of this ticket is to update faith s name in all of the vfs facing guidance she is mentioned in impacted artifacts tasks change faith s last name from owusu sekere to arthur on the ato orientation page change faith s last name from owusu sekere to arthur in the new vfs team gh template peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs teams know to look for faith arthur re ato orientation how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 22762470922.0,2022-07-07 22:48:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, reset validation attempts in session storage user story as a user my validate attempts in session storage should reset each time a new uuid is set for the session my validate attempts should also reset after a successful login on the validate page related documentation fill in description update the usesessionstorage hook to be able to reset validateattempts and reset them after a successful validate attempt and when a new uuid is set tasks update usesessionstorage to include a reset for validate attempts reset validation attempts after a successful validation reset validation attempts when a new uuid is set create or update unit tests create or update tests acceptance criteria when is the ticket done error pages only show a visually red box for validation errors and not for other errors currently there is a bug where other errors can be displayed in the red box if the app is still in a maxvalidationattempts state users can no longer log in when the app is in a maxvalidationattempts state for a specific uuid i e if you reload the page with the same uuid it will not allow login with successful credentials passes accessibility checks using axe deployed to staging designer has signed off on the feature product team has signed off on the feature ,1 17149845150.0,2021-07-13 18:59:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,nod switch alertbox to va alert description switch the alertbox component to use the va alert web component in the notice of disagreement form tasks replace alertbox with va alert update unit tests update tests if applicable definition of done tasks completed all tests passing,1 18734119249.0,2021-11-04 03:42:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and investigate correct location of orphan facilities and associated facility health services story as a veteran and web maintainer multiple facilities need a home in the correct system and need correctly associated facility health services goal move all orphaned facilities to the correct system or document it for removal associate possible health services for review of paos task review all orphaned facilities in parent cms systems and associate them to the correct system investigate and document correct facility health services associate facility to correct system save as draft inform pao that facility is in draft and can be published once health services are validated and determine if any facility health services are incorrectly associated and move them to the correct facility acceptance criteria all facilities are associated to correct system and initially saved in draft pao has been informed and facility health services have been provided so they can confirm if they need to be added answer pao questions and support,1 24642277058.0,2022-10-17 12:34:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,current employment not populating in vha fsr issue description vha has found a case where they can see two employment histories but only the past was present within the fsr pdf tasks replicate use case fix to fill current employment acceptance criteria we show all employment history on pdf how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 32010416920.0,2023-09-21 17:35:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,resolve nil fsr records sent from newline error issue description a code change was merged on that updated the fsr logic for removing new line characters as well as potential delimiters this functioned on values of type string but boolean values i e true false were transformed to nil this only affected vha submissions tasks we voda discovered issue when prying into an example record vbs sent email informing us about the presence of nil records we rolled back the causing commit that went out at the standard deploy est tracked affected form ids in total once deploy went out vbs deleted the affected records and sent over the ids we cross matched to make sure the ids lined up updated nil boolean fields with accurate true false on the records re processed the records to be submitted to the vbs api again acceptance criteria records have been updated and resent to vbs api how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20618646365.0,2022-03-07 15:26:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, refactor alerts to use va alert issue description the majority of alerts used by debt letters are custom components and should be refactored to use to ensure consistency throughout the portal tasks refactor all alerts to use the va alert design system component consider rendering alerts using refer to mcp for details acceptance criteria all alerts should render using va alert how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26836596486.0,2023-02-02 20:03:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr facility discrepancy issue description dmc has reported conflicting information for a veteran who was serviced by both orlando and houston it is believed that when the veteran tried to submit a waiver for the orlando debt it came up with the houston facility the veteran added a note on the waiver but it was routed to houston where the veteran currently does not have any debts the last statement from houston was in the last statement from orlando was november and december facilities orlando and houston tasks scott plans to validate the information on the voda end and reach out to vbs if needed acceptance criteria determine cause of issue or route issue to vbs for continued investigation if routed to vbs communicate back to dmc with update for awareness how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23134621922.0,2022-07-28 13:24:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits sprint priorities sprint july aug formerly debt resolution team sprint goals tbd sprint deliverables list of deliverables completed during sprint tbd planned issues combined fsr debt and copay selections update generate rails engine for debts api pts trailers campers and boats page redesign pts benefit debt resolution option update pts separate vha fsr submissions per station pts add new database table for fsr submissions pts combined fsr cfsr design discovery pts mcp notification determine best authentication approach for mcp notifications endpoint pts unplanned additions tbd capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr streamlined waiver github epic product outline use cases flow release plan architectural diagram use cases usability testing n a dates product guide mcp product guide kickoff design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 21639947105.0,2022-05-05 17:41:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reexamine ebenefits links in claim status tool as part of we learned that active users are being logged out after viewing ebenefits that is a bug that should be addressed but it also seems like we re directing users to ebenefits for features that we d now expect users to complete on va gov we should reexamine the additional services section img width alt screen shot at am src ,1 15167117040.0,2021-02-12 17:18:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, form introduction content changes issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to the form s intro screen tasks incorporate the global changes on pages in the provided document into the fsr s staging environment it may be easier to reference the uxpin for the content updates reach out to the design team with any questions acceptance criteria the into page s changes have been incorporated into the fsr s staging environment work has been checked off in the ,1 30218437942.0,2023-07-05 17:20:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint june july sprint goals launch the new efsr form refine the design for the updated efsr review page front end analysis for sw work complete the streamlined waiver design code clean up planned issues fsr enhancements use cases for testing add employment move dates to another screen see comments pts fe bug employment history required not triggering error pts fe bug required field inputs for spouse additional income and deductions list for spouse veteran pt fe required accessibility update from staging review statement of truth text pts fe bug required field spouse employment history monthly income pt fe collab cycle staging review semantic html pts fe analytics add efsr feature flag to submission event for tracking pt fe downtime dependency update pt fe navigation content update pt fe mcp notifications implement minimization of copay notification external service dependencies pts be implement copay notification retry logic pts be setup datadog dashboard for copay notifications pts be streamlined waiver streamlined waiver discovery research framing design product outline for streamlined waiver pt design streamlined waiver discovery fe transparency discovery mockups for streamlined waiver design ongoing maintenance bug fixes medallia satisfaction survey data review pts reasearch on hold this sprint due to user research blocked issues conditionally disable month year in employment history pts fe unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished xx tbd xx points over xx issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 14675315053.0,2020-12-30 17:17:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr add contact page to fsr issue description add contact page to fsr refer to the mock tasks create page for contact information page add edit functionality acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 17103418187.0,2021-07-09 14:22:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,pass signature values from fe to dmc technical task once signature values are being passed from the fe to the be payloads we need to relay that data so the dmc can generate a pdf with the veterans signature expected behavior veteran s signature is being passed to dmc via be payload so dmc can generate a pdf with a signature acceptance criteria dmc is retrieving the veteran s signature via be payload ,1 21710866692.0,2022-05-10 13:46:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,launch fsr notification copy in production issue description once copy for fsr notification submission has been approved we need to update the copy in va notify portal and set it up for production tasks update template in va notify dmc portal flip the fsr notification feature to on acceptance criteria when a veteran submits an fsr in production they will receive a notification how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30253102168.0,2023-07-06 22:36:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,confirmation page contact information updates issue description what details are necessary for understanding the specific work or request tracked by this issue updates to blue information component remove this information your request was sent to
 debt management center 
p o box 
 st paul mn updates to step remove this information if you have a question about the status of your request call us at or from overseas we’re here monday through friday a m to p m et tasks remove the above information on the confirmation page acceptance criteria confirmation page has been updated ,1 17694072366.0,2021-08-24 13:32:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,resolve event listing page discrepancies between full build and preview description there are some discrepancies between preview and full build on the system events page vs preview still shows a past event and shows the upcoming past toggle it looks like the issue with showing past events might be unique to pittsburgh wilmington does not have this issue acceptance criteria experience is consistent between between preview and prod as it relates to published content only published draft and in review events are visible on event listing pages in preview archived events are not visible on event listing pages in preview display the upcoming past event toggle consistently past events don t display as a spotlight spotlight events published draft and in review must be current or upcoming and only display on upcoming events page navigation between pages is not possible in preview ,1 27777287944.0,2023-03-16 18:07:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery research co design feedback sessions issue description we are planning to host co design feedback sessions with veteran employees to get early feedback on enhanced fsr designs before launching them in a formal usability study estimated timeline monday tuesday and wednesday per day tasks what work is necessary for this story to be completed facilitate sessions record sessions with permission take notes acceptance criteria what will be created or happen as a result of this story sessions take place notes taken and organized ,1 15836097465.0,2021-04-06 18:51:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr unauthenticated your va benefits designs issue description for the unauthenticated fsr we will need to make some adjustments to several pages that would normally be pre filled for authenticated users tasks alternative designs created for your va benefits sync designs to uxpin create frontend ticket acceptance criteria designs synced to uxpin and linked in this ticket frontend ticket created and linked in this ticket,1 15614976018.0,2021-03-19 18:32:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,customize facilitiesmap hooks issue description the facility locator code src applications facility locator needs refactoring this task will make facilitiesmap hooks easier to understand tasks change generic hooks in facilitiesmap to custom hooks acceptance criteria facilitiesmap hooks are self documenting and easier to understand how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18538923523.0,2021-10-21 14:16:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create alert for pdf downloads issue description dmc is uploading the wrong letters to vbms so we need an alert informing users of incorrect information about their debts implement an alert on the download page for debt letters according to the slack tasks implement alert on debt letter downloads page should match acceptance criteria alert should render on the download page how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 19704529715.0,2022-01-12 20:18:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, pre discovery issue description our team is going to work on a new product that allows veterans to set up payment plans that they can repay within years we need to do some pre discovery work to uncover what repayment plan form s currently exist and draft a list of questions to ask our smes about this initiative tasks conduct pre discovery research about payment plans that can be repaid within years acceptance criteria link document containing notes and questions to this ticket ,1 21885170171.0,2022-05-19 17:52:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add information to platform about uat as a researcher i want clear and updated guidance on observers to keep research participants safe and empowered intended audience vfs desired outcome add updated guidance to relevant documentation due date description there is a that hasn t been migrated to platform that information needs to be added to platform and the gh page marked as deprecated new artifacts maybe a new platform page for uat artifacts needing updates tasks determine where this uat information needs to live on platform acceptance criteria github template has been marked as deprecated platform website page name has been updated platform website page name has been created updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 22636779169.0,2022-06-30 19:52:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research best approach for implementing mcp notifications issue description we need to have functionality that notifies a veteran when they have a new medical copay statement available to them in the portal in the past we ve discussed and aws approach real time data from cdw and pinging vbs service tasks draw pros and cons of each potential implementation and come to conclusion what makes most sense from a technology team and product standpoint acceptance criteria we know how to progress with implementing mcp notifications how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20924046417.0,2022-03-24 20:27:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,retire full accessibility office audit from collaboration cycle user story as a vfs team member i want to have an updated list of required collaboration cycle touchpoints so that i can prepare properly as a governance team member i want to remove all guidance and references to the full accessibility office audit so that vfs teams receive correct and current guidance intended audience vfs teams desired outcome no more full accessibility office audit due date description governance team drafted a the proposal was sent to the va office for their review and the request was approved via martha wilkes octo de accessibility lead and pat sheehan on march artifacts needing to be archived platform website page confluence github template artifacts needing updates platform website confluence shira will update tasks update artifacts needing updates pages to remove referenced to the full accessibility and office audit archive all artifacts needing to be archived for the github template the template can be deleted for the remove in the collaboration cycle full accessibility and office audit touchpoint the sentence should start with teams are required acceptance criteria artifacts needing to be archived have all been successfully archived or deleted artifacts needing updates no longer make any reference to the full accessibility office audit related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate initiative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 13767961270.0,2020-10-07 16:24:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr discretionary income assets as a veteran i want to fill out these sections correctly and make sure everythign is included ,1 15086391631.0,2021-02-05 20:15:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, prepare lebanon health care vamc for dual state story as a web user i need to confirm all broken links updates and content has been updated prior to dual state publishing so i can be assured the latest and best system input is loaded to dual state resources tasks validate that each page update any last minute changes provided by pao and approved for input confirm or resolve active and true broken or redirected link update pages specified in content review with updated material tech debt validate there are no additional detail pages or list page duplicates that have not been removed acceptance criteria all pages in check list have been tested all additional pages that are not duplicates have been added to list and have been checked updates suggested from staging have been input into system ,1 19913590178.0,2022-01-25 19:50:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,prepare for react router background we need to get our teams apps ready for the upgrade to react router there is a thread describing what needs to be done to our applications to get us ready for this transition considerations tasks update our apps to get ready for transition acceptance criteria ebenefits apps are ready for upgrade to react router a pr has been requested for merging if applicable,1 15035502921.0,2021-02-02 14:13:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, ensure list loop cards are closed by default when stepping backwards in the form issue description currently there is some weird behavior surrounding the list loops and stepping backwards in the form when stepping back the cards should not be open by default fill in the list loop card save continue to next page step back to find the card in an edit open state if there are multiple cards previously saved you will see something like this tasks ensure list loop cards are closed by default when stepping backwards in the form confirm behavior with designers can send a screen recording acceptance criteria behavior fixed behavior confirmed with designers,1 16104476305.0,2021-04-27 13:28:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move cancel logic into appointment service file we have our cancel logic appointments and requests in an action creator but we could put it in the appointment service since it s application specific logic independent on the ui ac cancel api calls and related logic are in cancelappointment and cancelrequest functions in appointment service redux related dispatch logic and error handling is still in action creator analytics are in appointment service,1 15821373004.0,2021-04-05 20:25:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore converting a page component to react redux s useselector and usedispatch hooks we re now on the latest version of react redux so we can use their useselector and usedispatch hooks instead of using connect docs are here they re very good docs highly recommend reading them generally useselector replaces what we use mapstatetoprops for and usedispatch replaces what we use mapdispatchtoprops except that it doesn t automatically wrap the actions with dispatch it just returns dispatch for you to use we can then do dispatch someaction where someaction was something we had in mapdispatchtoprops before i think any component with both mapstatetoprops and mapdispatchtoprops could be used to try this out ,1 30729121805.0,2023-07-27 22:46:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, mobile prototype uxpin issue description what details are necessary for understanding the specific work or request tracked by this issue continuation of tasks create uxpin prototype for mobile add interactions to uxpin prototype test prototype acceptance criteria uxpin created and linked here uxpine tested by team ,1 24654850412.0,2022-10-17 22:08:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, refactor skipped test to work more consistently background we received a pr review request to skip one of our tests that often fails ci we have asked in the pr as part of our review for more information to help troubleshoot we should refactor the test in question based on this feedback so that it passes consistently blocked until we receive a response pr tasks determine if the test needs to be refactored fix test if necessary update relevant documentations readme and use cases acceptance criteria test passes ci consistently code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 20623453148.0,2022-03-07 19:49:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create product profile for mcp description create product profile and user guide for release of medical co pays mcp acceptance criteria create product profile for mcp create user guide for mcp ,1 13222522118.0,2020-08-17 15:40:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,break sass into feature folders we should break our sass file into feature specific files and include those in the relevant feature folders there s not much of this but might take some time to disentagle ,1 14001890166.0,2020-10-28 14:10:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr ideation workshop issue description the team needs to come together to discuss ideas for how we might present the form to users and discuss technical complexity and any technical limitations with proposed ui ideas tasks set up a mural board with necessary activities for ideation conduct ideation session s with team members as needed acceptance criteria a mural board containing workshop activities team members sketches and notes about limitations and or functionality to research is linked to this ticket ,1 15084522354.0,2021-02-05 17:17:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, view payments remove feature toggle code description now that view payments has been in production for a while it makes sense to remove the feature toggle code we have in place we do this because the feature toggle has served its purpose and the code is no longer needed in the code base considerations the view payments feature toggle renders code on va gov va payment history screenshot of rendered widget tasks remove all feature toggle checks from the remove entry from run through app and unit tests to make sure nothing relies on feature toggles definition of done feature toggle removed in vets api feature toggle removed in vets website prs submitted ,1 13935975303.0,2020-10-22 12:19:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres veteran information available debts as a veteran who is logged into debt portal i would like to see a list of resolution options and a list of debts i have with the anilty to select the debt i am seeking resolution for ,1 14541872971.0,2020-12-15 15:03:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ia feedback staging review debt letters iteration feedback framework must for if the feedback must be applied should if the feedback is best practice consider for suggestions enhancements description must the breadcrumb on the download debt letters page is incorrect it should be home manage your va debt your va debt download debt letters should on mobile the content on the download debt letters page is missing a left margin consider i noticed that when clicking on the link within the content of the page to return to your list of debts the page refreshes quite quickly however if you return to the your va debt page via the breadcrumb there is a significant difference in load time not sure what is causing that difference definition of done must feedback is implemented decisions on should and consider feedback and question responses documented in issue issue is closed by vfs team once above items are complete ,1 13895488676.0,2020-10-19 15:55:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr preliminary research issue description prior to conducting interviews with smes from the dmc who are familiar with the fsr va form the design team needs to research the form and document questions notes tasks create an inventory of the fsr va form document questions notes about the form acceptance criteria a link to a document containing the fsr s inventory and questions notes ,1 15680876923.0,2021-03-25 03:58:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and correct invalid content in system health services for va salem health care story as a veteran i need to have accurate and correct system health service description so i can quickly and correctly find where to go to get my correct health care support goal accurately update health services with approved content resources task salem has a total of system health services to replace do not update covid vaccine health service update all system health services with html code from health service library resource assure that intro line is correct e g care we provide at va salem health care acceptance criteria all system health services have been replaced with correct html code and the intro has been replaced with care we provide at va salem health care ,1 23790959301.0,2022-09-02 14:30:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vehicle cost displaying incorrectly with comma issue description when a comma is entered for a dollar amount the value being displayed shows incorrectly entered values for above tasks identify issue with currency display identify other locations where currency is being incorrectly displayed acceptance criteria currency is displaying accurately when user enters a comma how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24280941140.0,2022-09-28 17:20:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add expandable alert for hurricane debt relief issue description dmc would like to add a pop up on the debt portal alerting veterans that they are offering debt suspension for benefit debts for days tasks add expandable alert to summary page add content shown in screenshot acceptance criteria we have an alert available to veterans detailing hurricane relief how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22108895082.0,2022-06-01 19:20:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits debtres team benefits sprint priorities sprint june formerly debt resolution team sprint goals 🎉 welcome megan gayle to the team 🎉 combined debt portal continue development team qa test in staging submit research plan review combined fsr vba vha prepare prototype collab cycle design intent pdf generation add indicator to fsr to distinguish between vba vha sprint deliverables list of deliverables completed during sprint release plan for combined debt portal fsr prototype design intent artifacts for combined fsr planned issues combined debt portal review icons in the cards status sections part of by sync with accessibility regarding midpoint review feedback carry over from blocked defect consider using ul and li elements for the cards list update urls and breadcrumbs add engineers to staging flipper documenting user scenarios update medical copays cypress tests under cdp review icons in the cards status sections usability prep pre staging review spot check defect download link for statements should have download attribute and should not open in a new tab clean up duplicate code caused by merge make styling consistent throughout app combined fsr generate pdf form carry over from open up rfc process for sharepoint integration carry over from research appropriate storage option for generated fsr pdfs add indicator to differentiate between vba and vha debts prototype iteration combined fsr content adjustments unplanned additions tbd capacity planning pto holiday s denise scott brandyn andrew riley megan points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ cc events artifacts medical co pays combined va debt portal combined fsr streamlined waiver product outline use cases flow release plan release plan release plan release plan architectural diagram use cases use cases use cases use cases use cases product guide product guide tbd product guide product guide product guide kickoff design intent midpoint review usability testing n a ia request analytics request required contact center review research plan review required staging review privacy security review helpful links incl code freezes ,1 22271601451.0,2022-06-10 12:54:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add widget for manage debt and bills issue description once static pages are complete we ll need widgets to navigate to the new combined debt portal manage debt and bills summary page tasks add widgets for cdp and to localhost acceptance criteria when navigating to manage debt and bills on localhost the page should load button for combined debt portal how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30529510897.0,2023-07-19 13:29:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, look into possible approaches for adding an indicator for sw forms issue description as we approach closer to streamlined waiver rollout the fsr submissions that come in based on sw approved veterans will need to be identifier by downstream services we will need a way for this to be identified via the pdf and json data that gets sent to vbs tasks determine indicator placement in pdf generation develop or repurpose field in json to contain indicator status acceptance criteria we are able to develop an indicator for both pdf and json versions for streamlined waiver submissions how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20204425589.0,2022-02-11 18:34:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, list loop edit view styling issue issue description there appears to be some kind of padding issue with the edit view on the list loop component and should be updated styling also seems to be affected for available debts refer to mock list loop available debts tasks verify this isn t a platform issue and add the proper padding if necessary to the list loop component edit view acceptance criteria edit view should render the proper padding according to ui and design specifications how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23115341287.0,2022-07-27 16:09:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove mikki from collaboration cycle documentation user story as a vfs team member i want to be able to rely on the point of contacts listed on platform website so that i know i m contacting the right people assignee peer reviewer seanasewell description mikki northuis will have a new position with octo starting in july and won t be supporting collaboration cycle the same way that she was previously we need to remove her name from our guidance known instances of mikki s name draftingtemplate impacted artifacts tasks remove mikki from known instances review other platform website and or confluence documentation to see if mikki s name is listed elsewhere if identified elsewhere document artifact above and ensure mikki s name is removed peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria mikki northuis has been removed from collaboration cycle documentation how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 20156286018.0,2022-02-09 16:44:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging prod env prep technical task as we get ready for launch we need to have staging environment working for qa with as little mocked data as possible so we will know if something breaks or is fixed we also need uat testing on friday dec so we need to have production ready and configured for all external systems expected behavior staging environment should use with all whitelisted users with as little mock data as possible acceptance criteria staging environment works with all staging users prod is working and connected and ready for uat as little mock data as possible is being used,1 21660252038.0,2022-05-06 18:20:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,mcp request help for medical copay wizard high level user story ies as a veteran who needs help with my copay bills i need to see a list of options of help i can request so i can decide what to request hypothesis or bet if allow veterans to see a list of options to resolve their copay bills and let them send request through the portal then we expect more veterans to take actions of their copay bills okr veterans can see all the debt resolving options and send appropriate request from the portal more debt action can be taken due to veterans spend less time trying to investigate how to request help for their copay bills definition of done once veterans click request help for your copay bill link they can see a list of options for help they can request and select the most appropriate one take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 15880326765.0,2021-04-09 13:34:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,simplify transformed data format for community care appointments currently we are transforming data from appointment related backend services into a fhir esque format this results in some confusing data in places we should attempt to simplify these areas and come up with a structure that makes some use of fhir resources but is not tied to the participant contained arrays or precisely what fields are or aren t allowed in the appointment resource object goals try to reduce nesting arrays for simple data fields keep the common location address and telecom formatting remove relevant data from participant contained arrays and put it into sub object s on the appointment resource object in this ticket we should refactor the data we put in the contained participant arrays for community care appointments into a simpler format ac update transformers to remove community care appointment data from contained participant arrays into a simpler easier to understand format update components and tests to use new format,1 15831689913.0,2021-04-06 13:53:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,full accessibility office audit debt resolution team debt letters steps to complete the full accessibility audit vfs verify all accessibility defects that were identified at staging review have been fixed before requesting a full audit vsp understands that other teams may be accountable for fixing the defects identified at staging review these defects are exempt and will not block a team from scheduling this touchpoint vfs product manager create this issue and fill in your team and feature name in the title vfs link to this issue once created in in slack tag trevor pierce vsp create sub issues attached to this epic with findings audits are performed on a first come first serve basis and are scheduled with each biweekly sprint vfs coordinate with the va office to address accessibility findings vsp update artifacts staging manage va debt link to verification that accessibility checks are complete preferred link to your template or link to a doc in your product folder that indicates all required checks from the accessibility doc are complete list of known issues with links to tickets when applicable additional information as part of this review vsp will send your product to va s office for approval as applicable please refer to the on github for more information about the collaboration cycle ,1 25892302185.0,2022-12-14 19:01:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, deprecate check in experience lorota deletion enabled feature flag description deprecate feature flag check in experience lorota deletion enabled tasks remove feature flag check in experience lorota deletion enabled confirm check in experience lorota deletion enabled not used in front end remove feature flag code reference acceptance criteria deployed to staging tested on staging ,1 27743878039.0,2023-03-15 15:50:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, currency input box design issue description va number input doesn t currently support including a to represent currency input so we will need a temporary styling update to apply until it has been added there is currently a currency input class defined in the fsr that can probably be modified to target the shadow root input component of the va number input tasks implement a style update that targets va number input so a is visible and the input boxes match designs acceptance criteria currency inputs on the fsr that use va number input show a how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25568635908.0,2022-11-30 16:00:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create personas for user flow paths issue description create personas for user flow paths on miro board tasks create acceptance criteria personas created ,1 16065091511.0,2021-04-23 17:46:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove express care section of application remove express care folder in vaos and any express care references in app wide code ac express care flow is removed actions reducers selectors for ec flow are removed tests are removed,1 19350672234.0,2021-12-15 15:20:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, button and link language isn t descriptive and or their purpose isn t clear general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers jim ryan jimuhh ia platform issue button and link language isn t descriptive and or their purpose isn t clear issue details some users may interpret learn how to pay your bill as a link to tutorial content link screenshot or steps to recreate va gov experience standard other references platform recommendation consider changing label to pay your bill vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 23765521850.0,2022-09-01 12:30:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,use pdf functionality to create pdfs for vha fsr issue description we have already added the ability to create fsr pdf forms but need to hook up this feature when vha requests are submitted tasks call pdf filler for form with form json to create pdf file acceptance criteria we have accessible pdfs for every fsr vha submission how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26273986842.0,2023-01-06 19:56:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sm client review specs the specs for sm client are here in spec lib sm client but not structured typically a class these should be reviewed and a plan made for restructuring them,1 12258038189.0,2020-05-06 14:33:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, stakeholder interviews prep user story or problem statement as a designer i need to prepare for stakeholder interviews so i can ask valuable consistent questions to debt letter stakeholders in a timely manner goal what outcome s do we want to see a solid plan for stakeholder interviews tasks determine list of stakeholders we want to get more data from create a general conversation guide for stakeholder interviews upload stakeholder conversation guide to gh schedule stakeholder interviews acceptance criteria stakeholder conversation guide in gh scheduled stakeholder interviews,1 27782192269.0,2023-03-16 22:11:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, your va benefits enhancement issue description update va benefit information page with the ability to edit listed benefits note be sure to use mural for up to date mocks the following screenshots are just for quick reference overview page click to expand edit page click to expand tasks add the following pages overview page edit page update efsr specific testing include edit loop acceptance criteria page matches design and functionality all new and existing tests are passing how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 13642682902.0,2020-09-25 15:53:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters iteration vsa qa test plan p lease reach out to brad to turn feature flag on for product feature summary debt letters iteration builds on iteration in providing the veterans the status of their va debt the attached spreadsheet has all the debt statuses that could be encountered product team smes leave blank to implicitly refer to vsa master org chart linked above design research content ia mikki peggy front end brad back end cameron qa tze chiu lei proposed use cases and staging test accounts from vsa design lead important for authenticated experiences staging test accounts must be provided for all authenticated scenarios and staging api test data created to match the account specific scenarios how to configure this issue product manager added to assignees attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team vsa authenticated exp vsa benefits vsa benefits vsa caregiver vsa ebenefits vsa facilities vsa public websites etc definition of done test plan reviewed by product team test plan finalized per review feedback actual test runs completed on staging created and tracked ,1 17150487486.0,2021-07-13 19:53:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ensure debt letters api endpoints are up to date description dmc has two versions of debt letters url endpoints running side by side they need confirmation from us that we have migrated to the new url format api digital services a c ensure no changes have been made to the host name ensure that all calls to dmc are being made with the new url vets api settings reference the new value vets api fwd proxy does not reference the url make updates where needed the fwd proxy for all env still reference old urls the dmc team confirmed that the health checkpoint should be api digital services health updates ,1 19594264997.0,2022-01-05 16:06:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, facility phone numbers not always showing technical task on medical copays we have to interact with a ton of facilities for some reason some facilities do not show their phone number we need to figure out which facilities don t show phone number and figure out why we use a global vsp resource to lookup facility phone number maybe more need to be added or there is a key mismatch expected behavior all facilities show phone number on overview page acceptance criteria all facilities show phon e number on overview page ,1 30504292863.0,2023-07-18 15:46:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update cta widget to redirect after login issue description auth experience updated the sign in cta widget so it redirects to the correct destination after login we need to update the redirect property to true so the navigation will function correctly noticed we have two references to manage va debt while poking around in there one is named manage va debt and looks like it was originally in place for the legacy debt portal and can likely be removed i believe we re using combined debt portal now but let s use this ticket to confirm that notes og discussion on inconsistencies discussion on updating cta widget widget location src applications static pages cta widget ctawidgets js tasks update cta widget so redirect is true check to see if we can remove any deprecated widgets acceptance criteria widget had been updated and login is redirecting as anticipated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18110794889.0,2021-09-23 03:26:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update lgbtq and suicide pages with new updates from sot visn user story as a vha digital media web manager the national changes need to be implemented prior to dual state or full production launches so the systems are updated adequetly prior to the redirect goal remove tech debt prior to full production resources tools documentation tbd tasks update lgbt with lgbtq and suicide pages with new content and organize page correctly update suicide pages with correct format order and new content change out lgbt with newly authorized lgbtq in locations provided by content complete for the following locations va alexandria health care va central arkansas health care va fayetteville arkansas health care va gulf coast health care va houston health care va jackson health care va shreveport health care va southeast louisiana health care acceptance criteria suicide pages are updated and if caregiver is not listed on page it is reported in support channel lgbtq pages are updated and if caregiver is not listed on page it is reported in support channel ,1 26268319622.0,2023-01-06 14:40:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,aggregate vbms logs since launch issue description we need to provide vbms and leadership teams with the logs va gov has tracked since debt letters has launched tasks aggregate logs in aws aggregate logs in grafana create script to extract desired information hand over to appropriate contact acceptance criteria leadership has received the data they need from voda how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27397696761.0,2023-02-28 21:08:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, expanding group issue description design tickets based on platform is depreciating the expanding group react component and step of repayment or relief options debt forgiveness waiver is impacted old design message and checkbox automatically appear after user selects waiver revised design user selects waiver radio button and selects the continue button the waiver information is repeated on the following page along with the checkbox component how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13249123536.0,2020-08-19 20:13:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,come up with more effective organization vaos application folder the vaos application folder follows the typical structure of our other applications which is an older react redux style actions reducers components containers some kind of utilities folder sass tests in our case we have a giant components folder and small actions reducer folders while we shouldn t create deep folder structures better top level organization might be useful ,1 17091153373.0,2021-07-08 17:38:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,dry out the two bankinfo components src applications personalization profile components direct deposit bankinfoedu jsx and src applications personalization profile components direct deposit bankinfocnp jsx have a ton of duplicate content we should refactor these two components to dry them out the main difference between the two is that has a different state when the user is not currently signed up for and you cannot sign up for if you are not already signed up because we have know way to know if they are currently getting education benefits via paper check however does allow users to sign up for dd if they aren t already fortunately we already have very solid cypress test coverage to make sure both and work well src applications personalization profile tests direct deposit update flow cypress spec js ,1 28065333743.0,2023-03-29 15:03:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,test mpi request payloads in staging issue description iam team has said we can use any identifier to get profile from mpi we need to do some testing to view what these requests look like and how we can use the vista identifier to get the profile we need tasks use test users identifiers in staging to get mpi payload record request and response of these payloads detail what a vista id request might look like acceptance criteria we know how to work with mpi data requests and responses how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14001412519.0,2020-10-28 13:37:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr bankruptcy signatures review submit as a veteran filling out the fsr form i would like to complete the form by indicating if i have ever had a bankruptcy review the information i entered on the form electronically sign the form and submit the form thus concluding my fsr process ,1 24420681555.0,2022-10-05 20:00:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add quick reference guide for income and assets issue description vha sme david adcock suggested we add a link to the on the fsr online experience to provide veterans with additional clarity on what types of income and assets the va is looking for when reviewing an fsr submission tasks design team to review and mock up potential location to share with stakeholders share with denisecoveyduc and if approved we will integrate it into the experience acceptance criteria design mockup including link how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24826247803.0,2022-10-25 20:55:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vaos code to re direct veterans to cerner iscerner flag background request public website team plans to deprecate the that has iscerner flag hardcoded vaos fe code uses the iscerner flag to determine if the veteran is associated with a vamc facility that uses cerner or vista when the facility uses cerner the name of the facility is listed in the file the veteran will be routed to the cerner portal from the vaos static homepage when the facility uses vista the veteran will be directed to vaos to book or request an appointment goal to review the updated logic of the iscerner flag in drupal as the source of truth vaos team will need to do research to see if it will have any impact to the current vaos code requirements to consider has provided documentation of the proposed changes tasks answer the following questions do we need to update the fe and or be code what is the recommendation plan for the initiative please provide a comparison of current code versus proposed code time box hours definition of done tasks are complete research and recommendations are documented in this ticket ,1 16601592506.0,2021-06-01 20:17:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content to update fsr s find a form results page issue description with the fsr s release coming up we need to ensure it s findable in multiple places on va gov one area we need to request an update is on we should provide content that aligns with tasks draft the content per marci s instructions all we need is a description of what the tool is used for the url for the new tool and when that should be put into place have the content reviewed by troy to verify it aligns with the style guide draft up ticket including finalized content and assign it to marci acceptance criteria ticket containing finalized content is drafted for marci and linked in this ticket ,1 26809918111.0,2023-02-01 21:25:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt team debt team sprint priorities sprint feb sprint goals continue fe development of fsr enhancements prepare for user research of fsr enhancements address bug fixes and maintenance issues recently identified define new copay statement requirements with vbs resolve recent issues and bugs identified being worked update designs for additional card and mini summary sections planned issues fsr enhancements real estate enhancements fe rolled over from sprint research planning design research pts cards add mini summary for additional sections design research efsr dependents page enhancements fe spouse employment information loop fe other assets enhancement fe mini summary card component fe ongoing maintenance bug fixes provide debt letter user data to stakeholders vbms letter audit be multiple fsr submissions pts be identify affected veterans from non routed forms fe gather affected veteran identifiers be verify debts controller endpoints in eks be add signature date to fsr pdf be replace soon to be deprecated radio button components fe mcp notification define requirements with vbs for new copay notification be team onboarding heuristic evaluation workshop planning monitoring blocked issues incorrect data presented on portal fe unplanned additions if applicable added throughout sprint capacity planning pto holiday s aaron andrew brandyn denise heather megan scott points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review tbd details on kickoff feedback tickets design ia and content accessibility content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 24097434881.0,2022-09-19 20:07:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,efsr create ga logs for vba and vha submissions desired behavior google analytics recordings created individually for vba and vha depending on selection acceptance criteria ga record event used for vba and vha how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 24413036810.0,2022-10-05 13:53:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,always use ssn for file no field in fsr for vha issue description vha has requested to use ssn for the file number field as they do not use va file numbers tasks update vha submission to contain ssn for every request keep va file number for dmc acceptance criteria vha submissions always contain ssn in file number section how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13306075295.0,2020-08-25 19:37:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, grafana charting for sub forms issue description currently we do not really track the failure of the sub jobs we are retrying them when it makes sense but we would not know unless we are digging through sentry having this in a dashboard in grafana would allow us to to see trends and patterns and work towards reducing actual bugs acceptance criteria charts updated with our sub jobs how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20622551428.0,2022-03-07 18:54:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add veteran facing alert to notify them of missing letters issue description as discovered in letters are not being sent from vbms after december as a result veterans are not able to download any letters after that date until the problem has been resolved dmc has requested that we add an alert to notify veterans who may be looking to download a letter that was sent after december this issue is for adding the designed alert to the portal s debt letter download page an alert currently exists on that page so this alert will replace it please reach out to riley with any questions about this work tasks update the download debt letters page s ui to replace the existing alert with the warning alert displayed in this uxpin prototype acceptance criteria the ui has been updated with the new alert please ping rileyorr and denisecoveyduc when the alert is in prod so we can notify our stakeholders ,1 13893595365.0,2020-10-19 13:43:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ia request debt letters mvp issue description ia review request for the debt letters mvp product project progress talk to customer service leadership reps at the dmc to get an understanding of business process and what veterans call to do ideation workshop w team sketch a design solution discuss design and get feedback in design intent get more guidance from ia about product placement build a prototype in uxpin do hybrid generative research usability test research round important notes tool will include debts for education comp pension and loan guaranty the site should be replaced with this launch required planned estimated launch date tbd ,1 23905995760.0,2022-09-09 00:52:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the domain to platform api va gov background the cloud isolation team will be updating the vets api and lighthouse api endpoints by creating routes necessary for each to have its own unique endpoint the current domains api va gov dev api va gov staging api va gov sandbox api va gov the following domains will be changed to platform api va gov dev platform api va gov staging platform api va gov sandbox platform api va gov goal to understand how much work is needed to support the initiative requirements to consider tasks answer the following questions list out all the test files that display the api va gov and requires an update list out all the test files that display the staging va gov and requires an update check if we need to update any code in vets wesbite or vets api check how many tests in vet api that we need to update time box hours definition of done tasks are complete research and recommendations are documented in this ticket ,1 18294152333.0,2021-10-05 18:34:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analyze all locations capitalizeeachword is used and remove from places that modify json problem statement capitalizeeachword is manipulating the json data for disability names this is not as expected as capitalizeeachword should be used for display purposes only remove all uses of capitalizeeachword where json data is manipulated and potentially try to still title case the disabilities outside of json manipulation display purposes only expected behavior capitalizeeachword should not modify json data for disability names acceptance criteria capitalizeeachword does not modify json data for disability names ,1 16109509612.0,2021-04-27 19:08:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove parent sites endpoint call if possible we make a call to vaos facilities to get a list of parent sites in the regular new appointment flow this seems unnecessary now that we have a flat facility list it s still necessary in the new appointment flow when a user is registered at a cerner site but it probably shouldn t be called for non cerner patients ac remove the vaos facilities call from the regular new appointment flow,1 24558313330.0,2022-10-12 17:49:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,accessibility feedback — project kickoff — pw feedback framework ❗️ must for if the feedback must be applied ⚠️should if the feedback is best practice ✔️ consider for suggestions enhancements point of contact vfs point of contact jennifer vsa trevor vsp description this ticket houses accessibility feedback for the project kickoff for pw move how to apply wizards must must use semantic markup why this ensures the screen reader user clearly understands the questions and available answers sample markup diff for what type of claim are you requesting a higher level review disability compensation claim a benefit claim other than disability compensation should accessibility should review any content updates consider consider using a mobile first design approach why this allows the solution to meet those with in the greatest need and ensure we deliver a streamlined hierarchy and maximize touch experience we often treat mobile as a fluid delivery of the desktop experience but the mobile experience has small font sizes desktop contrast and small interaction touch points if there is time and appetite consider how the mobile experience might be improved why same as for mobile first approach for example font size could be increased on mobile for the questions and input labels the radio inputs could use radio input buttons the benefits and memorials team has a radio input that enhances the clickable area affordance with what looks more like a button there is a case to be made for this toggle type of ui element to be added to the va design system yet it would require clear guidance for usage unselected selected definition of done review and acknowledge feedback document decisions made accessibility specialist will close ticket after reviewing documented decisions cc — ready for your review ,1 31809448643.0,2023-09-13 15:49:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate potential pii issue with name and address fields summary veteran called dmc call center stating that when they logged into the debt portal when pulling up her information she was presented with the name and address for a different veteran steps to reproduce test user go to url actual result describe what happened that was unexpected or undesired including screenshots is encouraged desired result describe what was supposed to happen reference existing github issue that contains a solution if possible definition of done issue has been identified and resolved or it has been determined that there is no issue relevant documentation is updated how to configure this issue labeled with practice area backend frontend design product labeled with bug assigned to product for prioritization ,1 17467631625.0,2021-08-06 19:24:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor provider selection field the providerselectionfield component is pretty large and complicated it would be good to refactor it by breaking it into multiple components and making the different visual states more obvious and scannable ,1 26941294928.0,2023-02-08 02:34:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, iteration designs issue description while we don t currently have access to the new cerner statements we can begin exploring how we might show veterans both their new cerner statements as well as legacy statements tasks create designs for showing both cerner statements and legacy statements for a facility acceptance criteria the designs have been added to uxpin and linked to this ticket ,1 32013316402.0,2023-09-21 19:39:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery sending vha determination calculations for veterans who selected vba debts issue description the way the streamlined waiver experience is currently set up veterans who select a vba overpayment debt or a vha medical copayment that is over are not eligible for the streamlined process those veterans instead are required to complete va form fsr in its entirety currently voda is sending vha an fsr reason of waiver not automatically approved and when they are processing the data through the calculator they are seeing that the veteran should have been approved this discrepancy is causing them to think that there is an error can voda use the data from the completed fsr to send vha a determination for veterans who have selected vba debts not for copays over as those will still need to go through the manual review process tasks define questions next steps involved and work required for implementation acceptance criteria implementation tickets have been established to progress this work forward how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21582010599.0,2022-05-02 19:48:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,retire post launch check in touchpoint from collaboration cycle user story as a vfs team member i want to have an updated list of required collaboration cycle touchpoints so that i can prepare properly as a governance team member i want to remove all guidance and references to the post launch check in so that vfs teams receive correct and current guidance intended audience vfs teams desired outcome no references to post launch check in due date n a description we have recommended removing this touchpoint and chelen has agreed that the post launch check in should not be platform s responsibility to validate that the team s initiative has been completed and closed out artifacts needing archived artifacts needing updates shira will update tasks n a acceptance criteria has been archived has been updated has been updated has been updated has been updated has been updated has been updated create change history post updates have been peer reviewed by governance team member user story need has been fulfilled announcement has been shared on vfs all teams related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 26745026245.0,2023-01-30 15:27:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, cards add mini summary for additional sections issue description cards add mini summary for vehicles utility bills other debts installment contracts employment history tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story ,1 14995603871.0,2021-01-29 14:31:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review the overall va debt experience issue description now that the debt management tool launched we re getting closer to releasing the fsr and we re putting together a roadmap for future va debt related work we should take a look at both the debt management tool and the overall va debt experience to uncover areas of improvement and or gaps tasks review the launched debt management tool and document proposed improvements review the overall va debt experience and document proposed features acceptance criteria documentation has been uploaded to gh and proposed improvements features have been discussed w the team tickets for features improvements have been added ,1 21777892433.0,2022-05-13 15:28:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, user story as a front end developer i want a clean and easy to navigate codebase to reduce complexity and make delivery quicker unused and deprecated pages complicate the codebase list of deprecated content edit functionality demographics contact info emergency contact components pages edit all components within address email index jsx name phonenumber relationship shared folder and all components within header updatebutton editlinktext cancelbutton day of pages updateinformationquestion jsx any other unused components pages that are found while doing this work tasks remove unused components pages and code remove or update unit tests remove or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging prod validation not necessary scheduled ,1 13235830477.0,2020-08-18 18:43:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update for covid alert per peggy the covid alert was not approved it needs to be updated to suggested alert box found here please ping rileyorr rebeccawalsh one complete so they can review ,1 31470151409.0,2023-08-30 06:55:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint august sprint goals have the collaboration cycle touchpoints accounted for release sw mvp work complete veteran interviews code clean up planned issues need to update fsr enhancements downtime dependency update pt fe navigation content update pt fe streamlined waiver sw implement income limit back end fe streamlined waiver prep fe organization of folders fe front end discovery form navigation back to review page pts fe review display employment questions pts fe review display installment contracts fe look into possible approaches for adding an indicator for sw forms be sw add new chapter level depends and structures fe sw update transform and helpers fe add streamlined waiver notification to va notify portal pt be send streamlined waiver notification for eligible requests be add an indicator for sw forms be sw create example submission objects for be pts fe ongoing maintenance bug fixes determine which external services have downtimes be develop method to keep benefit payments from becoming stale be use vcr for unit tests be blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished xx tbd xx points over issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 15057464585.0,2021-02-03 21:43:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore using mockdate library to set a date when writing calendar or date based tests we often have tests fail during certain days or times during the month because we make a change that works fine on the day it s being made but not on a particular date due to proximity to weekends end of the month there s a library called that could let us set a fixed date for certain problematic tests we should explore this and see how it works tests to explore calendar page tests preferred date page tests ac test out mockdate to see if it works for vaos tests without breaking other tests identify tests with complicate date logic and set a mock date for them identify any tests that would benefit from tests being run on multiple different dates,1 17107032473.0,2021-07-09 19:34:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vamc links must have discernible text feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix issue at message the accessibility specialist when issue is resolved point of contact vfs point of contact trevor user story or problem statement accessibility specialists discovered nightwatch axe checks failing silently during a recent staging review multiple axe violations were discovered where empty link tags were on the pages these are problematic because screen readers will announce link but not what the link is this has an element in the tab order without accessible text this is a content issue the link is on a space and includes the safelinks addon tasks if there is no value or href the link should be removed ,1 30694833993.0,2023-07-26 17:44:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, usability study presentation issue description this will be completed after synthesis and after gh documents are completed tasks create ppt document schedule meeting with team and stakeholders acceptance criteria ppt document created meeting scheduled ,1 22152969333.0,2022-06-03 18:59:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, refactor fix precheckinconfirmation test suite see as of this pr the tests in this file are now being skipped as they do not pass the goal of this ticket is to have these tests run and pass tasks update unit tests acceptance criteria all tests in the precheckinconfirmation suite run and pass passes accessibility checks using axe deployed to staging tested on staging prod validation not necessary scheduled ,1 25568661777.0,2022-11-30 16:01:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design for fsr summary page mini summary issue description once a user enters a custom generated item example credit card bill they will be asked if they have another credit card bill to add we want to show the user the user the previous credit card bills that they have just entered on this screen tasks create mockup for summary pages mockups needed for the following sections of the fsr need to validate there aren t any other applications work history installment contracts and other debts other living expenses household assets acceptance criteria ,1 22775982180.0,2022-07-08 14:30:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, updates to icons in the cards status sections issue description background during the combined debt portal s midpoint review we received feedback that we should review the icons used in the debt and copay bill status cards to make sure they re being properly used within the context of each status for example some statuses use a warning icon while others use an informational icon additionally we reached out for accessibility guidance on alt text or screen reader only text to indicate what s being communicated for those icons solution has been reviewed and the icons have been changed to an informational alert for the following statuses diary codes additionally we received the following accessibility feedback the status icons need alternative text based on the icon s level of importance informational icons should say informational warning icons should say important tasks update the icons in the outlined diary codes add alt text to the icons acceptance criteria the icons have incorporated the visual and accessibility feedback outlined above ,1 20622077907.0,2022-03-07 18:25:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, write unit tests for fetch actions issue description there is a need to write unit tests for the following fetch actions fetchformstatus fetchdebts tasks write unit tests for fetch actions acceptance criteria unit tests should be passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20160277589.0,2022-02-09 20:43:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, incorporate mcp debts into fsr ixd issue description there are a few places in the fsr that need interaction updates in order to incorporate copays into the form debt selection resolution selection tasks create designs to incorporate copay debts and sync to uxpin share work to team create fe tickets if needed acceptance criteria design created and uxpin linked to this ticket shared design to team fe tickets created and linked to this ticket if needed ,1 13234103728.0,2020-08-18 15:46:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, grafana charting for sub forms issue description currently we do not really track the failure of the sub jobs we are retrying them when it makes sense but we would not know unless we are digging through sentry having this in a dashboard in grafana would allow us to to see trends and patterns and work towards reducing actual bugs tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20270746732.0,2022-02-15 15:59:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,expand instructions for how to reassign tickets or close invalid or duplicate staging review tickets issue description at the collaboration cycle staging review issue tickets are opened for the team product however it s possible that the issue found is not the responsibility of the vfs team it was assigned to examples issue tickets have been opened that should be reassigned to the design system team because the issue at hand was relevant to a design system pattern or component issue tickets have been opened that should be reassigned to sitewide content because the issue at hand was relevant to the site header the document already exists however it should be expanded upon for clearer directions in short if it is determined that the vfs team who is originally assigned the issue is not responsible for the issue the following should occur remove the vfs team label from the ticket add the label of the vfs team responsible mention the product manager of that team in the ticket and say this staging review issue ticket has been reassigned to insert team name as your team has been identified as the owner of this component product piece of va gov please do not close this ticket until the issue has been resolved if you have questions please comment on this ticket thanks if the product label has also been applied to the ticket currently not in place for most collab cycle reviews remove the product label as well tasks add instructions to mention relevant product manager and inform of the ticket acceptance criteria governance team members should understand the steps to reassign tickets to other teams other teams understand the origin of the ticket and the found issue how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14235990802.0,2020-11-18 15:28:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr incorporate content changes issue description before usability we need to update our design files with the most updated content tasks incorporate content changes provided by susan in the uxpin comments send to susan to review incorporations only where necessary major acceptance criteria content changes incorporated into sketch files and synced to uxpin all comments checked off in uxpin ,1 22710892573.0,2022-07-05 19:14:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, cypress tests failing issue description is failing out of the blue and has been skipped until the issue has been resolved it looks like the issue is that the mock data dates are now outside of the reordering period so the options the tests are expecting are not appearing tasks find root cause of failing mdot test fix issue causing failure acceptance criteria mdot cypress test is no longer failing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27091061960.0,2023-02-14 21:06:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update new uxpin account issue description once we regain access to uxpin we need to update the fsr file with updated mockups tasks update uxpin with new fsr mockups acceptance criteria uxpin has been updated ,1 19563145623.0,2022-01-03 19:14:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,allow fe teams autonomous control of revproxy redirects the problem when teams want to modify revproxy redirects they must seek a pr approval from vsp operations despite the fact that vsp operations has not real stake in these files it s an annoyance for both the fe teams who wish to modify these files and the ops team who must arbitrarily approve the prs extra context the devops ci job runs some basic automated revproxy tests such as validating that the revproxy config is valid and loads properly this runs as a pr check should keep us safe from fe devs who might introduce syntax errors work to be done identify best way to grant the relevant fe teams access to redirect files grant fe teams autonomous access to these redirect files,1 16623241148.0,2021-06-03 06:08:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, swap out current policies page with new hardened policies page for visn and save as draft user story as a vha digital media web manager the national policies need to be hardened and available to national administrators only so national content should be changed from one source to all systems goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks archive current policies page replace with cloned page and add to menu for the following systems va asheville health care va durham health care va fayetteville coastal health care va hampton health care va richmond health care va salem health care va salisbury health care complete the follow these steps for each system open policies page in edit mode a change name to policies old b remove menu by un checking menu box c save as archive open fargo or iowa city system and find policies page a select clone from tabs and select clone b go to edit and remove cloned c change governance to match new owner and related system d select menu enable check box e type in policies in name f select from drop down about va from system you are cloning to g copy visiting hours and or security information from original policies page security information will go into other policies section save new policies page as current status of system i e published or draft acceptance criteria all original policies pages have been archived and removed from menu all new policies pages are published and link is in menu at bottom of menu items ,1 27011717415.0,2023-02-10 15:54:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, overview page edits issue description edits to the copay overview page heads up we’re currently chatting with mikki about breadcrumb adjustments so stay tuned update subhead text to “check the balance of va health care and prescription charges from each of your facilities find out how to make payments or request financial help ” should also be using the intro text styling refer to for styling contact information for your va health care facilities the second facility doesn’t have a contact number tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 31780226999.0,2023-09-12 16:53:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,upload pdf versions of fsr vha requests to issue description is the standard implementation within vets api to upload and store files in this case fsr pdfs we have generated two options to look at class to be used by a to be triggered upon pdf generation we will implement a worker with the idea to move fsrs to a model based implementation in future state tasks create bucket to deliver pdfs add sidekiq worker to upload to call worker when a pdf is generated acceptance criteria when an fsr pdf is generated after submission the resulting file is upload to how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14078952268.0,2020-11-04 14:16:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr signatures review confirmation as a veteran filling out fsr form i want to understand that i am esigning the form and what i should expect to happen after submission the confirmation page ,1 12069798495.0,2020-04-16 16:35:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,get dsva vfs developers iam group managed by terraform user story or problem statement as a ops team member i need iam groups managed by terraform goal iam group dsva vfs developers managed in terraform and containing cloudwatch read access for log viewing objectives or key results this is meant to further proper management of resources tasks manage group and iam policy attachment s in terraform include cloudwatch read access acceptance criteria iam group dsva vfs developers being managed in terraform going forward how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26856632132.0,2023-02-03 15:05:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,repopulate user data from mpi in fsr submission jobs issue description user objects in redis are not guaranteed to be populated when a sidekiq job is ran so we should use the use user account id to repopulate any needed data from mpi this has caused a couple errors within the jobs for lack of email or ssn tasks pass user account id to job as parameter repopulate redis user object with mpi data acceptance criteria jobs don t rely on redis user object existence how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 10455403008.0,2019-09-19 21:13:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,upcoming deprecated react lifecycle method names when working locally since having updated to react v you will notice at least one of the following warning in the dev tools warning componentwillreceiveprops has been renamed and is not recommended for use see for details while there are long term solutions to these warnings as mentioned in the link above the following command should update all of the upcoming deprecated lifecycle method names automatically and serve as a temporary fix that will not leave the code broken when we upgrade to react v npx react codemod rename unsafe lifecycles ,1 27083569802.0,2023-02-14 15:31:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,part heuristic evaluation workshop issue description what details are necessary for understanding the specific work or request tracked by this issue the heuristic evaluation workshop is an opportunity for the debt resolution team to collaborate creatively as a team learn about or refresh knowledge of usability heuristics and practice design thinking become familiar with the fsr form and or enhance present understanding think about possible usability improvements within current constraints tasks planning for workshop workshop takes place acceptance criteria workshop has taken place ,1 18023072008.0,2021-09-16 22:24:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove non refresh appointment list code and tests we should be able to remove the non refresh version of the appointment list page this means looking for uses of the homepage refresh flag and removing code that only runs when it is false removing pages and components only used in the non homepage refresh list removing associated tests updating any cypress tests that expect the old homepage some of the appt flow tests start on the old homepage ,1 12889522609.0,2020-07-13 14:39:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create debt letters summary table ui story as a veteran i would like the ability to view the debt letters that were mailed to me in a table format per front end tasks ensure the page is styled according to design spec ensure the back end data from api is displayed in local and review instance ensure unit tests are available ensure your code changes are covered by tests run axe checks using the chrome or firefox browser plugin test for color contrast and color blindness issues zoom layouts to at width test with or screen readers navigate using the keyboard only acceptance criteria for a logged in test user the letters are displayed in reverse chronological order designers review and approve ui unit tests pass tests cover current code and regression end to end tests show violations the data returned matches api response for given user or scenario all axe checks pass all color contrast checks pass all zoom testing passes all keyboard checks pass all screenreader checks pass appendix ensure your code changes are covered by tests expand add tests if none exist for this addition change update existing tests if this code will change functionality include axe checks including hidden content run axe checks using the chrome or firefox browser plugin expand ensure no heading levels are skipped ensure all buttons and labeled inputs use semantic html elements ensure all buttons labeled elements and images are identified using html semantic markers or aria roles ensure form fields have clearly defined boundaries or outlines ensure form fields do not use placeholder text ensure form fields have highly visible and specific error states test for color contrast and color blindness issues expand all text has appropriate contrast zoom layouts to at width expand ensure readability and usability are supported when zoomed up to at browser width ensure no content gets focused offscreen or is hidden from view test with or screen readers expand ensure the page includes a skip navigation link ensure all links are properly descriptive ensure screen reader users can hear the text equivalent for each image conveying information ensure screen reader users can hear the text equivalent for each image button ensure screen reader users can hear labels and instructions for inputs ensure purely decorative images are not announced by the screenreader navigate using the keyboard only expand ensure all links navigation text and or image form controls and page functions can be reached with the tab key in a logical order ensure all links navigation text and or image form controls and page functions can be triggered with the spacebar enter key or arrow keys ensure all interactive elements can be reached with the tab key in a logical order ensure all interactive elements can be triggered with the spacebar enter key or arrow keys ensure focus is always visible and appears in logical order ensure each interactive element has visible focus state which appears in logical order how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14499182819.0,2020-12-11 16:24:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add documentation for custom form fields vsp doesn t have documentation for the props available in custom fields and widgets in the form system which is causing us trouble on vaos we can contribute documentation for this in the client documentation site ,1 21100931298.0,2022-04-04 14:26:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research plan issue description the combined debt portal s research plan was reviewed for feedback on the recruitment criteria this ticket captures the updates to the research plan based on the gathered feedback tasks create a diagram of the screener questions so perigean can visualize what answers lead to different groups update the screener questions based on the diagram update the primary and secondary demographic criteria acceptance criteria the research plan has been updated and linked in this ticket ,1 27260482765.0,2023-02-22 14:34:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove combined fsr enhancements feature flag issue description remove combined fsr feature flag and old experience from fsr now that the fsr has been live with the combined flag active we can remove the feature flag that is currently hiding the previous experience note do not remove the combined feature flag enhancments flag as that is being used to hid the currrent enhancement work tasks remove pages hidden by combined note this may not be a comprehensive list availabledebts page recreationalvehiclerecords page resolutionoptions page update remove data mocks that no longer apply update remove tests that no longer apply for previous structure test test test test test test acceptance criteria combined fsr feature flag references have been removed leaving only the new experience pages all tests unit are running and passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20145338710.0,2022-02-09 06:38:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, menu clean up part inform editors of menu parent item corrections and submit changes story as a veteran i need to have a simple and standardized location for all vamc web pages so i can quickly find and locate my vamc information resources tasks communicate with pao stakeholders of menu changes update vha dm of menu changes and upcoming redirects wait for submission of redirects for all appropriate pages update pages and test links to make sure all links are working correctly acceptance criteria artifact document for original and new url locations of menu items that need to be moved ,1 17362859537.0,2021-07-30 00:17:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,migrate dmc production credentials description create dmc maintenance window created on update the credentials in parameter store ct mydesignrocks the credentials to update are dsva vagov vets api prod dmc client id dsva vagov vets api prod dmc client secret trigger an off cycle deployment ct mydesignrocks once the credentials are in place create a deployment of the production environment of va gov so that the new credentials are applied monitor debt letters activities kevinmirc once the downtime window is removed and dmc can be reached monitor the debt letter api requests to ensure that vets api can connect to dmc monitor requests in grafana here monitor errors in sentry,1 25892305178.0,2022-12-14 19:02:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, deprecate feature flag check in experience chip error mapping enabled description deprecate feature flag check in experience chip error mapping enabled tasks remove feature flag check in experience chip error mapping enabled confirm check in experience chip error mapping enabled not used in front end remove feature flag code reference acceptance criteria deployed to staging tested on staging ,1 17703767031.0,2021-08-25 03:45:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update lgbtq and suicide pages with new updates from sot visn user story as a vha digital media web manager the national changes need to be implemented prior to dual state or full production launches so the systems are updated adequetly prior to the redirect goal remove tech debt prior to full production resources tools documentation tbd tasks update lgbt with lgbtq and suicide pages with new content and organize page correctly update suicide pages with correct format order and new content change out lgbt with newly authorized lgbtq in locations provided by content complete for the following locations va black hills health care va central iowa health care va fargo health care va iowa city health care va minneapolis health care va nebraska western iowa health care va sioux falls health care va st cloud health care acceptance criteria suicide pages are updated and if caregiver is not listed on page it is reported in support channel lgbtq pages are updated and if caregiver is not listed on page it is reported in support channel ,1 12838091049.0,2020-07-07 16:50:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,write integration tests for past appointments write integration tests for past appointments tab logic these tests should use rtl and following the existing integration test patterns ,1 13640905460.0,2020-09-25 13:26:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters discovery functional and technical product outline high level user story ies as a veteran i would like the ability to see any debt i have incurred with the va on line in a centralized page with instructions on how i can remediate the debt or next steps hypothesis or bet if this is done then a will comply with laws b will provide the veteran with a better experience and clear next steps c reduce calls asking for copies etc okr which objective key result does this epic push forward definition of done technical understand the integration points of debt letters a what apis are used what format etc b what triggers generation and how can that be tied to notification functional a process of triggers and follow up points on debt letter generation b will the debt letters need to be re written to comply with va gov language guidelines c touch points for debt generation collection process how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 26777197604.0,2023-01-31 18:03:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, midpoint review frontend updates issue description midpoint review recommended several updates to the efsr cards mini summary add item action link tasks design update how card is styled to card styles explorations we have recently updated the for adding another item instead of a question content step of household assets your other assets select any other item of value called assets you own not including heirlooms clarify to the user what constitutes an heirloom i recommend clarifying to the user what constitutes and heirloom or simply don t use the word heirloom and instead use the definition of heirloom the same verbiage should apply to the entire list the items in the list are all somewhat subjective i recommend using a threshold for instance you could say anything valued at over or something similar updated to select any other items of value called assets you own not including items passed down in your family for generations i recommend using the same formatting and verbiage for each asset entry i recommend removing value from precious metals and coins value and changing the verbiage from how much is each of your assets worth to what is the value of each of your assets acceptance criteria frontend to add ac to existing engineering tickets for this work ,1 22710998088.0,2022-07-05 19:21:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, migration product outline analytics team is working on the migration to google analytics as google will be sunsetting our current universal analytics properties as part of this they are meeting with each of the vfs team to discuss the new event structure and any custom events you may have set up to define requirements they provided this attached a deck that provides a little more detail and have asked that i complete this worksheet ahead of this meeting that’s on my list for today i know we do have some custom events that we track craig was the focal previously references and resources definition of done what must be true in order for you to consider this epic complete migration is complete and team is able to extract all kpis and necessary data from or domo dashboards ,1 14621404610.0,2020-12-22 21:35:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor facility criteria fetch to be type of care agnostic currently we have a function in the location service file that fetches facilities from the two vats criteria endpoints and combines them with the facility data from the facilities api this function takes a type of care id and marks each facility as supporting or not supporting that type of care the criteria data we get back includes info about all types of care we should be able to refactor the function in the location service file to not require a type of care id and instead update each facility with a supported flag for each types of care and then update the redux and or component logic to check those flags instead to illustrate each facility ends up with a property that looks like this via the getlocationsbytypeofcareandsiteids function legacyvar directschedulingsupported true requestsupported true those two supported properties are based on the type of care passed in to the service however the type of care is not used in the actual query to the backend and we could actually end up with data like this on each facility legacyvar directschedulingsupported false requestsupported true where is the id for primary care from the constants file we d have an id and boolean for each of our supported types of care in there and would no longer need to pass type of care to this service ,1 30788265037.0,2023-07-31 14:32:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,minor updates to sw logic follow on to based on feedback from the voda vbs sync it is clear that some minor changes need to be made to the sw backend logic the streamlined attribute is currently a hash but vbs wants a boolean we re going to keep the hash for future backend purposes and format to boolean before submission existing fsrreasons should not be overridden by the sw value automatically approved ,1 16068347591.0,2021-04-24 00:16:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos appointment list components index jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 27315796526.0,2023-02-24 15:35:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, efsr validation cypress form system custompage failure investigation what happened warning failed prop type invalid prop route pageconfig custompage supplied to formpage desired behavior investigate and fix issue causing cypress tests such as efsr validation to fail acceptance criteria efsr validation cypress test passes issue investigated and resolved regarding custompage in our form system how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 20161188623.0,2022-02-09 21:45:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, eslint import order issue description receiving following eslint warnings component library import should occur before import of custom component eslint due a recent change by platform to enable some linting rules these warnings have been surfaced and should be addressed to ensure we adhere to best practices in our code tasks verify sort order for all mcp imports acceptance criteria warnings should be cleared how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13907438448.0,2020-10-20 12:37:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres tech spike esignatures authorizations story as a veteran who filled out the fsr on line i need the ability to e sign or authorize the form before it is submitted if i have a spouse i need to have the ability for my spouse to e sign or authorize the fsr data as well tech spike to investigate options for both logged in user and spouses to sign authorize fsr before it is submitted ,1 27171186760.0,2023-02-17 19:36:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt team debt team sprint priorities sprint feb sprint goals continue fe development of fsr enhancements update uxpin account define prototype resolve submission bug non combined vha submissions not being submitted verify debts controller endpoints in eks for eks migration define requirements with vbs for new copay notification and prepare swagger doc onboard new team members welcome to the team joe and amir we are thrilled you are here planned issues fsr enhancements part heuristic evaluation workshop your va benefits enhancement research planning refinement spouse benefit information page mini summary card component other assets enhancement spouse other income efsr validation cypress form system custompage failure investigation ongoing maintenance bug fixes define prototype requirements update new uxpin account non combined vha submissions not being submitted verify debts controller endpoints in eks contact information bug mcp notification define requirements with vbs for new copay notification team onboarding va team onboarding amir nashat va team onboarding joseph lee unplanned additions tbd will be added throughout the sprint points planned points accomplished tbd points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review tbd details on kickoff feedback tickets design ia and content accessibility content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 13628915812.0,2020-09-24 14:29:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rewrite typeoffacility tests using react testing library we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details original test src applications vaos tests new appointment components typeoffacilitypage unit spec jsx general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos ,1 14005975838.0,2020-10-28 19:15:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add ssn and filenumber to form prefill issue description veterans will need to confirm their identity information which will include the last four numbers of their ssn along with their va file number tasks add va filenumber ssn to the form prefill add va filenumber ssn to the vets json schema for form acceptance criteria filenumber and ssn are available via the in the progress form endpoint for the form ,1 13675382902.0,2020-09-29 12:36:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consolidate google analytics keys in settings originally created here as the backend tools team we want to help out and make sure this tech debt is handled,1 14172640034.0,2020-11-12 17:12:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr bankruptcy content as a veteran filling out fsr i need to understand how to enter my bankruptcy case,1 20759484614.0,2022-03-15 15:01:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, combined vba vha fsr with the updated list loop designs issue description the online currently allows veterans to request financial assistance with their benefit related debts our team is now working to incorporate medical copay statements into the fsr while incorporating usability findings that replace the form s list loop components we need to consolidate and into one i think the easiest way to do this is to incorporate the combined fsr prototype pages relating to vha debts into the list loop redesign prototype because there are fewer art boards to update both of the prototype files can be found in the debt resolution sketch workspace under the names combined fsr financial status report tasks incorporate the following pages into please let riley know if you have any questions acceptance criteria the prototypes have been consolidated into the fsr prototype and the uxpin is linked in this ticket ,1 24526289103.0,2022-10-11 13:22:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update the instructions on collaboration cycle kickoff moderator responsibilities user story as a governance team member i want to be able to respond to cc kickoff requests so that i can recommend the correct touchpoints to a team assignee peer reviewer description it was discovered while working on that the instructions for the collaboration cycle kickoff moderator responsibilities need some updating impacted artifacts tasks add black out columns i though ax to step in step add a new step to comment out the “if your product is already on va gov please verify in product directory” see gh ticket as an example this will reorder the following steps read the document and confirm that the steps and process make sense and are ordered correctly peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria governance team members understand the instruction in the collaboration cycle kickoff moderator responsibilities governance team members can recommend the correct touchpoints to teams how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 13106758189.0,2020-08-04 14:18:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, conduct pt diary code workshops w dmc issue description conduct diary code workshops w dmc tasks conduct tbd conduct tbd consolidate decisions made and upload to gh acceptance criteria workshops conducted decisions documented in gh,1 30826727793.0,2023-08-01 20:43:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, finalize transparency content issue description what details are necessary for understanding the specific work or request tracked by this issue continuation of tasks make updates from stakeholders and content team for both desktop and mobile acceptance criteria updates are made on desktop updates are made on mobile content is approved by stakeholders content is approved by content team aliyah sent finalized content that we have updated content is finalized for research but will continue to be worked on ,1 20160460633.0,2022-02-09 20:55:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,general analytics request for debt resolution veteran user journey to fsr general analytics request what this form is for use this template to request support for analytics that need interpretation if you have your kpis set please instructions please fill out the following sections description timeframe for analytics requested analytics to track down which product questions are you trying to answer additional comments description who is this request for send slack message to dsva slack channel vfs platform support that includes email address es for user s requesting data link to this github issue and tag platform analytics what team project is this work for this adds context for the data debt portal what type of analytics support are you looking for analytics discussion i would like to track when veterans receive emails notifying them they have pending debt and a link to debt portal to take action how many veterans went to the debt portal from link provided in email reviewed their debt and clicked get help for your debt to fsr verses how many veterans bounced around outside the fennel and came back to fsr timeframe for analytics requested please provide the timeframe for the metrics you are requesting what timeframes are you looking to analyze e g before vs after dd mm yy analytics to track down examples metric metric metric which product questions are you trying to answer other helpful questions to think through who is your audience why do you need this data what are you hoping to find what is your hypothesis that you re hoping the data will support what area of the va are you hoping to assess how frequently do you need this data link to metrics please link your report if you are seeking verification of metrics additional comments add any comments or questions for the insights team here if applicable please leave the following blank acceptance criteria the data has been identified and documented in this ticket items that we don t have access to are noted with cannot be accessed the metrics are shared back with users definition of done all appropriate issue tagging is completed all ac completed ,1 17619668642.0,2021-08-18 13:59:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,broken debt letters cypress test user story when working on i went to go run the cypress test manually to do a quick regression test on the code i was refactoring then saw that all the test were disabled and being skipped looks like they were removed from production months ago in this we need to go back over these test so we can be safe to refactor freely without worry out application will break out from under us expected behavior cypress test pass reliably on ci and locally acceptance criteria cypress test are re enabled and run on every build and pass reliably ,1 23092854685.0,2022-07-26 16:36:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, routing corrections needed within check in workflow back to last screen scenario currently on demographics page select yes info is correct select back to last screen in top left taken back to demographics page select no info is incorrect taken to page telling me to see staff select back to last screen in top left taken back to demographics page select yes immediately taken to authentication page with last name ssn requested if i hit refresh it will take me back into the workflow scenario currently on demographics page select no info is incorrect told to see staff select back to last screen in top left taken back to demographics page select yes info is correct immediately taken to authentication page with last name ssn requested if i hit refresh it will take me back into the workflow slack that contains the details found by shawn adams tasks determine if this is still happening and create a new bug ticket if it is acceptance criteria ,1 24305093418.0,2022-09-29 16:41:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove old feature flags description form still has a few feature flags in the code that have been at or already remove and need to be cleaned up request locked pdf password evss upload limit tasks remove feature flag code in update tests definition of done all tasks complete all tests passing,1 27114893921.0,2023-02-15 17:48:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research planning issue description continue research planning tasks refine research plan create draft discussion guide create draft notetaking checklist create draft recruiting screener acceptance criteria research plan refined draft discussion guide created draft notetaking checklist created draft recruiting screener created,1 13491517069.0,2020-09-11 16:37:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unused css from facility locator scss our facility locator css file is lines long and there is a lot of “cruft” in there that makes it hard to work with let s clean it up ,1 13690430896.0,2020-09-30 14:22:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rewrite typeofvisitpage tests using react testing library we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details original test src applications vaos tests new appointment components typeofvisitpage unit spec jsx general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos ,1 27450590653.0,2023-03-02 17:05:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt resolution team onboarding amir nashat welcome to the debt resolution team this ticket is to track onboarding efforts pre onboarding delivery manager tasks access requests request access to request access to request new hire to complete va onboarding paperwork create a for getting onboarded with va gov platform onboarding new hire tasks begin va contractor onboarding paperwork sent by prime contractor onboarding contact review onboarding checklist this will be provided by your delivery manager meet with onboarding buddy set up daily check in cadence for first weeks complete platform orientation ticket tasks ,1 12068624802.0,2020-04-16 15:00:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add tests for single system path we should add an test that goes through the va new appointment flow but only has one system to choose from instead of ,1 24558860362.0,2022-10-12 18:18:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the debt portal notifications with the new combined debt portal url issue description there are plans to update the breadcrumbs as part of the combined debt portal s launch so we need to review and update the urls in the va notify notifications the following notifications will need to be updated debt notification financial status report submission tasks review and update the notifications with the new url acceptance criteria the notifications have been updated ,1 17150761545.0,2021-07-13 20:15:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,migrate dmc production credentials description update the credentials in parameter store the credentials to update are dsva vagov vets api prod dmc client id dsva vagov vets api prod dmc client secret trigger an off cycle deployment once the credentials are in place create a deployment of the production environment of va gov so that the new credentials are applied monitor debt letters activities once the downtime window is removed and dmc can be reached monitor the debt letter api requests to ensure that vets api can connect to dmc monitor requests in grafana here monitor errors in sentry,1 12262211308.0,2020-05-06 21:36:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters create redux actions reducers to wire up new component user story or problem statement as a fe dev i need to create redux actions to wire up new components to display debt data contained in api response tasks create redux actions reducers to wire up new component acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26955760992.0,2023-02-08 14:49:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,duplicate fsr submissions being seen by vha and vba issue description tracking work related to the duplicate fsr submission issue that was discovered as a result of failing retries acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24124006791.0,2022-09-20 21:35:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,generate staging api key for vbs issue description for vbs to authenticate with va gov we need to generate an api key for them to include with the request and securely transfer it to them tasks generate api key pass key to vbs team acceptance criteria vbs has new api key how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14660383597.0,2020-12-28 23:28:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, defect debt letters the debt download table sorting function must be keyboard accessible enter an issue title using the format brief description of the problem edit buttons need aria label for context add another user link will not receive keyboard focus heading levels should increase by one error messages should be more specific blue button on blue background does not have sufficient contrast ratio feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact josh user story or problem statement as a screen reader user i am confused when the download debt letters table headers announce themselves as clickable but when i press enter or space nothing happens as a keyboard user i would like to sort the table by column but the table headers will not receive keyboard focus details the download debt letters table columns and have icons that allow users to click and sort on those columns this feature must be accessible to keyboard and screen reader users we should add a button inside the th and listen for click events on that instead of the th code snippet below related issues acceptance criteria tabindex is removed from all th columns clickable column headers have a button inside the th visual styles are maintained ideally the chevron icon is added to the button as a background image instead of an element if the is maintained it must have an aria hidden true attribute applied no axe core violations any sorting function has been discussed and collaborated with the accessibility specialist fix if known diff th class vads u border scope row tabindex type environment test user wcag or vendor guidance optional screenshots or trace logs ,1 26783384441.0,2023-01-31 23:32:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,discovery for bgs peopleservice vafilenumbernotfound issue description discovery work for tasks determine what is needed to progress acceptance criteria have identified action items to resolve forward how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30472101146.0,2023-07-17 14:14:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display credit card bills issue description add credit card bills creditcardbillsummary as view only on the final review page can likely leverage a custompagereview similar to how utilitybillsummaryreview is implemented only show the values that have been populated see for copy tasks implement read only display on final review page acceptance criteria credit card bills are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21002858709.0,2022-03-29 19:15:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add va gov email to slack profile guidance user story as a team member working on or in support of va gov i want to be able to access general profile information including va gov email addresses of my colleagues in slack intended audience octo de platform vfs teams desired outcome updated profiles with va gov email due date n a description related to adding va gov email address to slack profiles artifacts needing updates tasks add va gov email to list of information to add to slack profile in github orientation ticket general add va gov email to list of information to add to slack profile on platform website slack profile guidelines acceptance criteria github orientation ticket template has been updated platform website slack profile guidelines has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 26806146985.0,2023-02-01 18:26:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,verify debts controller endpoints in eks issue description as part of our migration to eks we need to the endpoints owned by our team work as intended with the new infrastructure some instructions can be found tasks create endpoint collection add requests to collection use variables for secretes run tests acceptance criteria we ve validated the tests against our endpoints in eks communicate results with platform devops team how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18895129054.0,2021-11-15 17:02:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create html statements page issue description because the pdf statements are inaccessible we ve created html versions of the statements tasks update detail pages to include the of your statements and subsequent links found create html statement page found review pages with design for qa acceptance criteria detail pages updated html statement page created ui reviewed by design ,1 14861114536.0,2021-01-18 22:01:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,unauthenticated fsr design work issue description for the unauthenticated fsr we will need to make some adjustments to several pages that would normally be pre filled for authenticated users including personal information debt selection contact information your va benefits tasks alternative designs created for personal information debt selection contact information your va benefits sync designs to uxpin create frontend ticket acceptance criteria designs synced to uxpin and linked in this ticket frontend ticket created and linked in this ticket,1 30883659881.0,2023-08-03 19:43:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint august sprint goals identify all sw mvp work and create tickets for all mvp development complete desktop mobile prototypes complete research plan guide for sw secure approval for sw content complete all be work for sw update review page for sw planned issues fsr enhancements downtime dependency update pt fe navigation content update pt fe streamlined waiver sw implement income limit back end fe streamlined waiver prep fe organization of folders fe front end discovery form navigation back to review page pts fe review display employment questions pts fe review display installment contracts fe look into possible approaches for adding an indicator for sw forms be sw add new chapter level depends and structures fe sw update transform and helpers fe add streamlined waiver notification to va notify portal pt be send streamlined waiver notification for eligible requests be add an indicator for sw forms be sw create example submission objects for be pts fe ongoing maintenance bug fixes determine which external services have downtimes be develop method to keep benefit payments from becoming stale be use vcr for unit tests be blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint update sharepoint credentials and resubmit missed submissions be review display cleanup titles and spacing design points planned points accomplished xx tbd xx points over issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 16173906446.0,2021-05-03 00:28:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr be integration va benefits as a veteran filling out the fsr form i would like to have my va benefits pre filled since the va should have this information additionally the dmc looks at the amount eligible nto the actual amount paid having this information pre filled which will result in less errors and faster processing times benefiting both the veterans and dmc ,1 27722526630.0,2023-03-14 22:00:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, identify affected veterans from non routed forms issue description debt team identified a bug causing veterans to navigate a previous version of the fsr a version where we are not displaying copays while completing the form and resulted in the form not being submitted to the dmc a fix has been put in place so any fsr submitted will be now correctly routed we need a way to identify affected veterans so dmc can can contact them and inform them we have their uuid s but will likely need to provide emails so dmc can touch base tasks coordinate with identity team to bulk fetch data of affected veterans provide list of affected veterans acceptance criteria necessary information has been passed along to dmc how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22832024278.0,2022-07-12 13:42:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, focus state isn t visible general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue focus state isn t visible issue details when viewing a statement for a copay or debt the link to download a pdf copy of the statement does not have a visible focus indicator when it has keyboard focus and doesn t appear to have the same styling on hover either for keyboard only or keyboard first users visible focus indicators are essential for tracking where you are on the page without a visible indicator a keyboard user is left to guess whether or not pressing will actually activate the link they re trying to reach link screenshot or steps to recreate logged in as test user navigate to the press to move through the links on the page note that each tab stop has a yellow outline until the download your june statement pdf link va gov experience standard other references wcag sc aa platform recommendation i haven t dug into the css closely enough to figure out what makes this link different from the others but i m wondering if the p nested inside the a might be causing an issue that s an unusual pattern that i don t think i spotted anywhere else in my review and it might be causing some css wonkiness too vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 16110356380.0,2021-04-27 20:16:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove phone validation check issue description currently phone numbers are validated to confirm they contain digits this is no longer needed and can be removed to simplify the code tasks remove phone number digit validation acceptance criteria code no longer contains validation check for digit phone numbers ,1 15864380428.0,2021-04-08 13:45:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letters set up google analytics set up google analytics dashboard by using tags to view traffic in real time on release day ,1 24166412803.0,2022-09-22 15:21:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,revise navigation for research and design based on results of tree test user story as a researcher designer or team stakeholder on the va platform i want to easily find resources that may affect my team s research and design practices on va platform assignee jimuhh peer reviewer cherylevans description ticket was to perform quick research asking questions regarding findability on platform website for research and design this ticket is to implement the findings impacted artifacts tasks reorganize research and design pages to align to results of findability study submitting navigation request changes to platform content for review approval create tech debt tickets for potential improvements that fall outside the scope of reorganization announce changes to vfs teams following the platform communication playbook peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs team members are able to find important information quicky platform team members are able to navigate platform website and provide links to resources how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 24398589504.0,2022-10-04 21:54:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint september oct sprint goals • add copay path on fsr wizard • review and integrate content changes on fsr • update review page on fsr • finalize research plan • mock up “other” living expenses options • continue design wireframes • design intent for fsr enhancement release • monitor phased release of fsr vha • checkbox to input boxes • integrate continuous add feature • lighthouse api to cdw investigation sprint deliverables list of deliverables completed during sprint fsr enhancement collaboration cycle kickoff streamlined waiver collaboration cycle kickoff planned issues combined fsr checkbox to input boxes enhancements pts upload pdf versions of fsr vha requests to pts return pdf details upon fsr submission pts design for fsr review page pts define copay path pts uxpin text updates investigate removing cross app references from fsr pt move fsr api submission logic to background job pts break up funding for va notify requests pts fsr enhancements enhancement continuous add credit card bills pts enhancement continuous add employment history pts research plan review for enhanced fsr pts content changes pts streamlined waiver user scenarios flow for streamlined waiver discovery pts mcp notification authenticate vbs on new statement route pts view payment history work with lighthouse team to determine real time data next steps pts unplanned additions add max character length for additional info field in fsr pdf add expandable alert for hurricane debt relief optionselect is tracking analytics capacity planning pto holiday s denise scott brandyn hurricane ian andrew hurricane ian megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 20161061565.0,2022-02-09 21:36:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,contact center review for debt resolution medical copays mcp request the contact center review what this form is for use this template to request a contact center review of your product please review the self service product guide template and the contact center review how to description medical copays mvp is the next product to meet the goal of unifying veteran va debt into a modern consolidated and veteran friendly experience similar to what a consumer may experience with quicken loans or chase portals the goal of unifying all veteran debt into a single portal is to make it simple for the veteran to understand pay or settle any and all debts they may have with va without having to distinguish between different agencies and processes launch date depending on results of uat we are anticipating a december launch version number please provide the version number of the guide and or video product guide troymosher is currently working on product guide and can update when available product video troymosher is currently working on product guide and can update when available product video transcript please provide product video transcript link acceptance criteria platform contact center qa has been completed platform contact center sends artifacts to appropriate contact centers platform is updated additional information please refer to or the on platform website for more information about the collaboration cycle ,1 23371652386.0,2022-08-10 20:27:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,streamlined waiver project kickoff issue description as a product team we need a product kickoff meeting to review the most recent vha decision tree logic that will dictate the user experience for the streamlined waiver process tasks schedule product kickoff meeting with stakeholder jill anderson identify vha smes to initiate design discovery acceptance criteria product team has met to kickoff product work how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14445493048.0,2020-12-07 23:05:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, defect debt letters debt detail table must have properly formatted heading row enter an issue title using the format brief description of the problem edit buttons need aria label for context add another user link will not receive keyboard focus heading levels should increase by one error messages should be more specific blue button on blue background does not have sufficient contrast ratio feedback framework ❗️ must for if the feedback must be applied ⚠️ should if the feedback is best practice ✔️ consider for suggestions enhancements definition of done review and acknowledge feedback fix and or document decisions made accessibility specialist will close ticket after reviewing documented decisions validating fix point of contact vfs point of contact jennifer user story or problem statement as a screen reader user i want to understand the row column relationships of the debt history table details jaws is not announcing the debt history table column headers i think this is because the row needs th tags with scope attributes screenshot and code snippet below acceptance criteria table header row html updated html validates no axe browser plugin violations no change in visual display for mobile tablet desktop breakpoints environment test user solution if known diff date date letter letter december account returned from treasury cross servicing account is at top top offsets will be applied to account as federal funds become available wcag or vendor guidance optional screenshots or trace logs ,1 17145847854.0,2021-07-13 14:31:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,conduct informational interviews for domiliciaries issue description va domiciliaries are va health facilities which are included as locations under the relevant vamc they don t fit the facility pattern established by the vamc facility detail pages as they include minimal services such as extended care or none at all the information that veterans need for these types of facilities may be different than that which is expected for medical clinics problem to be solved before we can reimagine detail pages or validate potential designs with veterans we need to better understand these facilities questions how is the facility best described is the facility free standing vs a floor of a hospital for example what services are provided what is the referral process do veterans self refer what information does a veteran need for these types of facilities who is the likely audience is it a veteran caregiver or other advocates what info is meaningful for the prepare for your visit section is there specific eligibility criteria tasks conduct informational interviews with smes acceptance criteria documented information from sme conversations,1 30017833187.0,2023-06-26 20:13:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review and submit discrepancy efsr submission process issue as part of the verification process for the efsr enhanced financial status report submission i have noticed a discrepancy in the calculation of discretionary income an issue was identified with discretionary income which should be the net monthly income less expenses this calculation seems to be incorrect as it currently states whereas the correct amount should be based on the given user data below is the user data that i tested with income veteran monthly gross salary total deductions net take home pay other income total monthly net income spouse monthly gross salary total deductions net take home pay other income total monthly net income expenses rent or mortgage food utilities other living expenses expenses installment contracts and other debts total monthly expenses incorrectly computed discretionary income correct discretionary income also the amount that can be paid toward debt is incorrect as it shows while it should ideally be zero or negative since the user s net income is already in the negative expected result the discretionary income should correctly reflect the difference of the total net income and total expenses also the amount that can be paid toward debt should be adjusted to reflect the financial reality of the user especially when the user s income is in the negative reproduction steps login as a user navigate to the efsr form fill in the aforementioned data click on submit to initiate the calculation and pdf generation process download and view the generated pdf,1 25568656904.0,2022-11-30 16:01:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,continued discovery for the streamlined waiver issue description product and design both need time to understand the decision tree and spreadsheet that vha has provided it is a complicated process that has major implications on the user experience before the design team can move forward with the user scenarios flow for the experience certain questions need to be answered tasks meet with mike dewey to better understand the discrepancies between the decision tree and spreadsheet gain a better understanding of the equation used on the spreadsheet and the information needed for the decision to be made determine where that information can be collected across the portal experience is there any backend development needed to collect this information identify outstanding questions and gain a clearer understanding of next steps and requirements to move forward acceptance criteria product and design have a clear sense of what is needed to unblock the user scenarios flow design work how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11453407608.0,2020-02-06 15:21:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate support for download attribute on add to calendar link doesn t support the download attribute on links but for the add to calendar link we re adding on vaos and in other parts of va gov it s used we need to figure out if we need to do something to better support ,1 23316007278.0,2022-08-08 12:35:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,audit staging review issue tickets with other category user story as a vfs team member i want to know the complete list of va gov experience standards that i must adhere to so that i can ensure that my product is ready for staging review as a governance team member i want to make sure the va gov experience standards list is as accurate as possible so that when i find an issue during a staging review i know what va gov experience standard it is in violation of and no longer have to use the other category assignee peer reviewer cherylevans description as of the governance team has flagged with the category of other stating the issue no va gov experience standard for the issue found this category issue is used as a catch all so that governance team members can still flag their concerns at a staging review even if there isn t a va gov experience standard that fits the issue found perfectly however since issues have accumulated it would make sense that we now audit those issues to see if they could ve been mapped to a more appropriate already documented va gov experience standard or there is a gap in the va gov experience standards that must be addressed aka create a new standard impacted artifacts tasks create a to review the other issues capture the following github issue date of ticket governance team reviewer governance team reviewer practice area sentence summary of issue found possible va gov experience standard if applicable share on platform governance team slack channel and ask for team review if your practice area opened the other issue confirm the following sentence summary is accurate if there is a possible va gov experience standard confirm that the summary and possible va gov experience align if not comment on the ticket with your thoughts opinion if there is not a possible va gov experience standard review the va gov experience standards list and validate that there is not a va gov experience standard that aligns with the summary if there is a va gov experience standard that aligns comment on the ticket with your thoughts opinion if any other issues almost align to the existing va gov experience standard comment in the working document it may be best to modify the existing va gov experience standard if anything needs octo escalation share on platform collaboration cycle slack channel once team is in agreement for the issues with aligned possible va gov experience standards update the labels on the ticket remove label add the appropriate new label ccissue xx yy per update the platform issue section in the ticket with the appropriate new name per comment on the ticket this ticket has been reassigned from no va gov experience standard for the issue found to ccissuexx yy name of issue no vfs action is needed if there is no possible va gov experience standard listed for the issue then it is likely than a new va gov experience standard will be created no action is needed on the github ticket create individual issue tickets for governance team to address for each new va gov experience standard and link them all below note it is possible that there may not need to be new standard for each issue that doesn t currently have a va gov experience standard to map back to other issues may have the same summary which would mean only new issue ticket is needed for governance team peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria we have reviewed all other tickets and either reassigned them to an appropriate va gov experience standard or created a ticket in our backlog for the creation or update of a new va gov experience standard vfs teams are notified if when their existing issue tickets have been reassigned a new va gov experience standard how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 13232873937.0,2020-08-18 14:00:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, build out remaining debt detail pages issue description build out remaining detail pages for the usability test with unique content tasks create versions of the detail pages qa the prototype to ensure that it s working as intended acceptance criteria fully working usability prototype ,1 24167614831.0,2022-09-22 16:15:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove references to troy mosher and other individuals in collab cycle documentation assignee briandeconinck peer reviewer description troy mosher departed the team on he is mentioned as a resource in the page as well as the note per platform platform teams should avoid using the names of specific individuals teams or contracts use the platform and team focused pronouns like “you ” “we ” and “our” instead ” the contact us page should be the only page within the collaboration cycle that lists individuals names this ticket will also include an audit of the collaboration cycle pages to identify and remove references to other individuals impacted artifacts tasks audit collab cycle pages for individuals names minus contact us page any page with an individuals name document and link above with their name impacted artifacts remove references to troy replace troy s name with clint little on contact us page fix thomas name it should not be a link on contact us remove him from the p s page peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria troy mosher references are removed from platform website vfs teams know that clint little is the point of contact along with thomas for the p s review individuals are not mentioned by name on platform website excluding contact us how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 23987028225.0,2022-09-13 20:04:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor community care detail page refactor the community care details page so that there s no longer a separate communitycaredetailspage component in confirmedappointmentdetailspage there s a detailscommunitycare component for cc confirmedappointmentdetailspage is updated to handle cc as well as va details pages there are still separate urls va and cc for va and cc details pages the review instance for testing the review instance for testing ,1 20920651653.0,2022-03-24 17:04:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html statement account summary issue description add account summary section to the html statement page refer to the for details tasks create account summary section acceptance criteria account summary should render balance activity how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27013156971.0,2023-02-10 16:58:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design intent ia feedback benefits team adding medical copays to the financial status report va form vfs acceptance criteria let platform know when the must feedback has been incorporated leave any comments for feedback you decide not to take vfs team closes the ticket thoughts questions i know this is a lot but the design intent and the research findings you shared convinced me that your team is encountering a problem many designers face when attempting to move an offline process and its associated paperwork into an interactive online form i ve been there myself it ain t easy so anyway in her article on shawna hein va applications design lead at ad hoc writes in general our online forms should not be framed as a mapping of the paper form in other words what we are building are data collection mechanisms for the forms themselves and therefore do not need approval in the same way the forms themselves do therefore the language does not need to map to the paper forms i ve provide some external guidance on navigating the print to digital forms transformation together with va team resources in the formal feedback hope you find it helpful feel free to reach out with any questions thanks jim ryan information architect governance team feedback must the feedback must be applied should the feedback is best practice consider suggestions enhancements must move marital status question to general personal info chunk do the same for dependent children question read shawna hein s reach out to her with any questions or concerns making sure to tag for advice on best practices for a form audit should read uk governmental design guidance on work closely with va business owners to conduct a consider platform directions update issue title link to collab cycle request epic add your feedback add assignees based on collab cycle touchpoint design intent vfs designer vfs pm optional yourself optional midpoint review vfs pm yourself optional staging review qa only vfs pm yourself optional ,1 23851704479.0,2022-09-06 18:35:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,authenticate vbs on new statement route issue description once vbs has api key to include with their requests for new statements we need to authenticate them tasks store key to match against validate in controller acceptance criteria the new statements route is app authenticated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15818159978.0,2021-04-05 15:37:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update vaccine flow single facility available view to match regular appointment flow the vaccine flow facility page should have the same design as the regular appointment flow when there is one valid va facility to choose from currently it has the old info alert box style instead it should have the regular text view ac vaccine flow matches new appointment flow facility page design in one valid va facility scenario vaccine flow should still not use the facilitiesnotshown component dropdown used in the new appointment flow how to test choosing mental health in the regular appointment flow will show you the single facility view in the vaccine flow you can modify the direct booking eligibility criteria json mock so that only one facility has a covid type enabled ,1 13232872603.0,2020-08-18 14:00:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, treatment for covid debt hold issue description dmc is not collecting any outstanding debt in an alert needs to be created alerting the veteran tasks create alert to notify veterans that debt collection is suspended through end of acceptance criteria veteran will see messaging that debt collection is suspended in due to covid how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15380564888.0,2021-03-02 21:17:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,simplify transformed data format for va and cc requests currently we are transforming data from appointment related backend services into a fhir esque format this results in some confusing data in places we should attempt to simplify these areas and come up with a structure that makes some use of fhir resources but is not tied to the participant contained arrays or precisely what fields are or aren t allowed in the appointment resource object goals try to reduce nesting arrays for simple data fields keep the common location address and telecom formatting remove relevant data from participant contained arrays and put it into sub object s on the appointment resource object in this ticket we should refactor the data we put in the contained participant arrays for va and cc requests into a simpler format ac update transformers to remove in person va and cc requests from contained participant arrays into a simpler easier to understand format update components and tests to use new format,1 22336531577.0,2022-06-14 19:04:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, incorporate accessibility feedback from the midpoint review check details link issue description background we received the following feedback regarding the check details link during the combined debt portal s midpoint review on the current va debt page when there are current debts eg the no copays on record view the check details link text for current debts may be a little ambiguous two big potential impacts here are screen reader users harder to differentiate which link goes where and voice command users speaking the command click check details link will match with both links consider adding some extra text to make the link purpose a little clearer across every possible use case eg check details becomes check compensation and pension debt details if that s not a practical option then when this goes to code we may still need some helping aria label text for screen reader users we previously met with angela fowler and discovered that screen readers should be reading out the full string as the feedback specifies but it wasn t working as intended solution angela s suggestion is that we use the aria describe by label tasks use the aria describe by label for the check details link under the copay and debt pages the copay version should read out the full facility name ie check details and resolve this debt for the debt version should read out the full debt type ie check details and resolve this compensation and pension debt acceptance criteria the aria describe by label has been incorporated reach out to angela fowler to check staging to make sure it s reading out on a screen reader as intended ,1 30317341267.0,2023-07-10 16:29:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,identify unused feature flags for debt team issue description over time as features and projects are developed we ve added feature flags to begin work or launch a new item we should pinpoint which of these are still needed or have become stale or mature due to launch time tasks collect feature flags that belong to our team identify if flag still has active purpose add documentation for our team s flags acceptance criteria we have accessibility to active or unneeded feature flags how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25977141153.0,2022-12-19 15:42:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint december dec dec sprint goals finalize end of contract documentation for all disciplines close out the contract as pop ends on december sprint deliverables list of deliverables completed during sprint contract end documentation planned issues contract end documentation contract documentation updates be fe deisgn product pts unplanned additions will be added throughout the sprint as identified n a capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished tbd points over tbd issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 30640744382.0,2023-07-24 21:43:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update sharepoint credentials and resubmit missed submissions issue description the sharepoint credentials expired after a default window of year we need to be issued new credentials update our config with those and resubmit once the connection has been re established tasks gather new credentials update parameter store develop script to resubmit missed submissions pass script to platform followup with ashlie roy acceptance criteria submissions have been passed to vbs and we ve communicated with huron how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27796353598.0,2023-03-17 12:51:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate and repair efsr validation cypress test what happened efsr validation test has been commented out for flakiness needs investigating and fixing efsr validation cypress spec js desired behavior test passes and is uncommented by ci acceptance criteria test passes how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 26564004873.0,2023-01-20 18:19:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove usage of redis keys command the problem vets api makes use of the redis documentation contains a strong warning against this warning consider keys as a command that should only be used in production environments with extreme care it may ruin performance when it is executed against large databases this command is intended for debugging and special operations such as changing your keyspace layout don t use keys in your regular application code work to be done audit vets api code for places where keys is called remove refactor places where this command is used,1 21713291155.0,2022-05-10 15:31:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,complete research documentation audit user story as a platform team member i want to make sure that all important documentation has been migrated to platform intended audience gov team desired outcome all gh documentation on research has tech debt ticket to be migrated to platform due date description an audit was begun by naomi to ensure that all important documentation from github was transferred over to platform some items of may now be complete but not marked as such on the audit additionally some items may not be complete and then need a new tech debt ticket new artifacts artifacts needing updates tasks create tech debt tickets as necessary to ensure all the items from the audit are in backlog to be worked on acceptance criteria confluence page name has been updated confluence page name has been created github template page name has been created github template page name has been updated platform website page name has been updated platform website page name has been created updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 19689325388.0,2022-01-12 03:59:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update system health services descriptions with the correct wording from the health service library story as a veteran resources tasks resolve content issues in health service taxonomy for diabetes clear and replace all content for diabetes in system health services using source content from system health service library save content and check that it updates in website after next content release acceptance criteria diabetes system health services are updated,1 14010767980.0,2020-10-29 05:58:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vamc team to take second look at all previous system pages to validate mvp and consistancy user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation prod cms va gov tasks complete review of system and facility pages for the following content and flow asking these questions does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page confirm all of the facilities are reviewed altoona va medical center dubois va clinic huntingdon county va clinic indiana county va clinic johnstown va clinic state college va clinic document all errors items that need update and testing on each page using spreadsheet listed above acceptance criteria all node pages have been reviewed in spreadsheet and issues found have been been documented issues have been escalated for resolution using spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 25260848956.0,2022-11-15 22:35:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fix bullets in must should consider framework for feedback user story as a vfs team member i want to understand how to interpret feedback from governance team received at the design intent and midpoint review so that i know how to respond and or take action with my product assignee cherylevans peer reviewer it harrison background authenticated experience came to the collab cycle office hours on and challenged some of the must feedback that had been provided in the at the previous weeks midpoint review in reviewing their pm s follow up comments on the ticket we recognized that the vfs team interpreted the must feedback as launch blocking feedback this is because the current guidance on platform website states that must feedback if not addressed will likely result in a launch blocking issue this is not true description the guidance on platform website is incorrect specially for must feedback must feedback if not addressed may result in a documented issue at staging review whether that issue is launch blocking or not is dependent on the standard the issue violates the purpose of this ticket is to update the bullets under must should and consider to accurately state whether or not this will result in a documented issue at staging review if not addressed all references to launch blocking or non launch blocking should be removed from the must should and consider bullets this ticket will also add a clarifying sentence to the intro paragraph stating that this guidance will only help vfs teams determine if the identified issue will result in a documented issue at staging review whether or not the documented issue is launch blocking will depend on the severity of the va gov experience standard that the issue is in violation of impacted artifacts tasks under must delete bullet must be brought into alignment with the design principles before launching on va gov under must modify bullet if not fixed before staging review would likely be flagged as a major issue and block the release of the product to state if not fixed before staging review would likely be flagged as an issue violating the va gov experience standards under should modify bullet if not fixed before staging review could be flagged as a major issue and block the release of the product to state if not fixed before staging review could be flagged as an issue violating the va gov experience standards under consider modify bullet if not fixed before staging review likely won’t be flagged as a major issue or block release of the product but may adversely affect user experience to state if not fixed before staging review likely won’t be flagged as an issue violating the va gov experience standards but may adversely affect user experience move entire why feedback matters section after consider section this excludes the sentence starting with after the design intent and midpoint review as this is the intro paragraph to the intro paragraph add a new sentence the must should consider framework for feedback does not indicate whether an issue will be launch blocking at staging review whether or not the documented issue is launch blocking will depend on the severity of the va gov experience standard that the issue is in violation of feel free to wordsmith change section heading the three feedback categories are detailed below to the three feedback categories no colon draft a post for slack and change history peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria vfs teams understand how to interpret must should and consider feedback at the midpoint review and design intent vfs teams understand that the must should and consider feedback does not indicate whether or not the issue will be launch blocking at staging review how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 27612276308.0,2023-03-09 16:45:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging review steps to complete staging review before meeting vfs product manager create this issue and notify the collaboration cycle team of this ticket in the in vfs platform support add artifacts listed below to the ticket at least days before scheduled meeting ensure you ve provided staging access information for the tool or feature don t put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository platform schedule meeting with platform reviewers and vfs team attendees listed in ticket create feedback tickets and link them to the staging review epic if no feedback please comment stating that after meeting vfs respond to platform feedback tickets update ticket with the product’s launch date after it has gone live close ticket when the review is complete and the product has launched platform artifacts provide links or documents for the following staging url and staging test user information found in do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository use this accessible staging account template to do so with the planning sections completed content artifacts qa artifacts product test in testrail with test execution logs accessibility artifacts preferred or document in your product folder that indicates all required checks from the doc are complete list of known issues • issue • issue • issue vfs meeting attendees required product manager denise coveyduc octo de product lead matt self octo de design lead ryan thurwell team members scott james craig wheeler justin linn riley orr becca walsh troy riser vfs attendees content and ia accessibility angela fowler qa specialists tze chiu lei scheduling please select your preferred time slot from the platform collaboration meetings calendar at december please note staging reviews are scheduled on thursdays all times are shown in et available time slots are indicated with when you reserve a time slot the reserved meeting will show up alongside the please select a time slot at least business days from request date additional information please refer to or the on platform website for more information about the collaboration cycle ,1 27453789350.0,2023-03-02 19:31:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,addressing platform disabled test what happened platform disabled test efsr validation because of flakiness desired behavior fix test so platform can reenable acceptance criteria describe the desired working behavior how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 23073393128.0,2022-07-25 20:25:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create mcp endpoint for vbs to submit new statement data issue description as part of mcp notifications we need to have an exposed callback endpoint for vbs to submit to vets api to trigger events to va notify tasks new controller method to accept new data build method to handle statement data for when we know structure acceptance criteria vbs can begin testing our callback with new statements how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27722691910.0,2023-03-14 22:09:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt resolution testing in staging vets api server to eks what’s happening we are in the process of migrating vets api server to eks amazon s service which will bring us one step closer to microservices as part of the testing process for vets api server migration to eks we’ve tested healthcheck paths we also need help testing endpoints this is where you come in why is this important we want to verify expected behaviors from the endpoints so the expected behavior s translate from brd to eks testing in staging will close cob if we do not hear of any issues you are having by then we will assume your endpoints are behaving as expected testing for sandbox if applicable will begin as a vfs platform team what do i need to do what endpoints does your team app own in the comments of this ticket provide a list of endpoints your team app owns maintains we know some teams have already provided this information but we would like to verify this list again with you verify dev synthetic tests for endpoints your team app owns verify the test from the inside of tic firewall aka vfs dev if you do not have socks access please note in this ticket verify the test from the outside of tic firewall aka revproxy dev going through the check for missing tests or duplicated tests note any issues with lack of test data and or users in the comments section of this ticket per your judgement if needed perform manual testing complete necessary manual testing link documentation in the comments of this ticket showing the completion of any manual testing,1 23588183718.0,2022-08-23 13:19:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove cross app references issue description release tools is working on a script that prevents cross app imports from being added to apps so we need to remove cross app references while we work on a deprecation plan for the old medical copays and debt letters tasks remove any cross app references from medical copays remove any cross app references from debt letters remove any cross app references from combined debt portal check for any cross app references from fsr acceptance criteria no more cross app references for benefits related applications how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22317859825.0,2022-06-14 01:12:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, staging combined debt portal current copay balances how to dispute section links go to prod what happened on staging combined debt portal current copay balances page in how to dispute section links navigated to prod instead of staging mdash returning to staging page killed user session specs device browser test user if applicable vets gov user gmail com travis steps to reproduce go to and sign in via id me as vets gov user gmail com travis go to page in debt and bill overview section in copay bill summary card click check your balance link on current copay balances page scroll down to how to dispute section click find your nearest link and observe that find va locations page is in prod va gov click browser back button and observe that staging unauthenticated homepage loads instead of current copay balances video staging find your nearest link goes from to prod desired behavior find your nearest link should go to staging find va locations page not prod clicking browser back button should return to staging current copay balances page learn more link should go to staging dispute your va copay charges page not prod clicking browser back button should return to staging current copay balances page acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 16066696446.0,2021-04-23 20:22:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up community care appointment and request transform the ticket to simplify the cc appointment transform result in some code that wasn t removed when it should have been so we need to go back and clean up some of the remaining transforms for contained practitioner info ,1 27718292012.0,2023-03-14 18:28:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add interactions to fsr prototype for user research issue description a shortened prototype is needed for user research in march because of timing and limitation in access to prototyping software this prototype will only be available as a desktop prototype and will not include every section of the fsr form tasks discuss what to include on this simplified prototype make any necessary input field updates to prototype add interactions to prototype test prototype acceptance criteria interactions have been added on specific pages ,1 15109916998.0,2021-02-08 18:29:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update cypress tests for hlr description with the upgrade of cypress to the way mock data is handled needs to be updated for full details see related testing done cypress test updates screenshots n a definition of done cypress tests for hlr have been updated for cypress tests for have been updated form ,1 13159043577.0,2020-08-10 15:13:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters mvp covid debt suspension alert issue description our team recently learned that all an alert has been added to the tool s ui informing the user about this debt suspension note the content in these empty states may be updated tasks update the debt letters mvp ui to include the alert in the provided mockups review the updated ui with a designer acceptance criteria the ui has been updated to include the provided alert the ui has been approved by a designer ,1 16196904310.0,2021-05-04 15:35:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove async cg attachments feature flag and logic description this feature flag is no longer in use remove the flag and any dependent conditional logic from vets api ,1 20142434879.0,2022-02-09 01:34:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research and resolve orphaned facilities that have not been associated to systems story as a veteran i need to have accurate representation of facilities at my vamc system so i can best determine the facility that has the services i need on my health care journey resources cms top level parent listing of facilities task research all orphaned facilities and determine their associated system move facilities into the correct system and determine the following if mobile or old and not under use archive the facility and update the poc if active and correct save as draft and contact the poc to tell them they have a new facility from vast and it needs facility health services attached before it is published acceptance criteria document or artifact showing the facilities and the outcome of the resolution archive or draft ,1 16004967724.0,2021-04-20 00:59:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add cypress tests to cover both contact facilities page variations in vaccine flow we need to run axe checks on both variations of the contact facilities page in the vaccine flow we could probably work one of these into the existing test but one of them will need a new test ac cypress test covers when a user chooses yes on the have you received a dose page and the axe check is run on the contact facilities page cypress test covers when vaccine schedule is not available for that user and they are sent to the contact facilities page,1 13489285930.0,2020-09-11 13:40:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters feedback issue description this ticket contains ui feedback on debt letters as it appears in staging i tried to categorize by page but let me know if you have questions about anything general across all pages all the pages are missing the covid alert the breadcrumbs don t match for example when i click on a debt details button the breadcrumbs don t change from home manage your va debt your va debt to home manage your va debt your va debt details your va debt page remove “home loan” from the subtitle “check the details of va debt you might have related to your education disability compensation pension or home loan benefits “ home loan debts aren’t currently included in the tool subtitle should have a line height of “on this page” should be utility bitter bold it’s currently bitter bold on this page links the arrow icons should be larger on this page link padding should be increased to on both sides this is our bad but an accessibility consideration current debts padding between the debt name ex post gi bill debt for books and supplies and “updated on ” should be “what if i don’t see a debt” should be an utility bitter bold it’s currently bitter bold padding between “for medical co payment debt please go to pay your va copay bill to learn about your payment options ” and “download debt letters” header should be “download debt letters” should be an it’s currently an faqs “how do i pay my va debt ” should be an it’s currently an “how do i get financial help ” should be an it’s currently an “how do i dispute a debt ” should be an it’s currently an debt details page currently the title says debt debt is “updated on september ” in bitter regular looks kinda bold but could just be me need margin between “date of first notice” “original debt amount” and “current balance” “on this page” should be utility bitter bold it’s currently bitter bold on this page links the arrow icons should be larger on this page link padding should be increased to on both sides this is our bad but an accessibility consideration debt letter history is “debt letter history” an it looks the same as “download debt letters” but the latter is an it should be padding looks a little funky between “debt letter history” and “you can view the status or download the letters for this debt ” should be padding between “note the content of the debt letters below may…” paragraph and the letter history table should be padding between the debt letter history table and “download debt letters” should be this was a mistake in the prototype my bad faqs “how do i pay my va debt” should be padding between “how do i pay my va debt” and “you can pay your debt online by phone …” should be padding between the paragraph under “by mail” and “how do i get financial help ” should be download debt letters page the breadcrumbs are missing should be home mange your va debt current va debt download debt letters is “download your debt letters learn your payment…” subtitle in bitter regular looks kinda bold but could just be me the container width for everything on the page looks off compared to the other pages looks way too wide should be consistent with the other pages missing “your debt letters” above the letter table is there still work to be done updating the letter file names still says “letter ” when i download a letter there’s no way for me to tell if it’s in reverse chronological order because all the dates are the same the sorting by date and type aren’t working was there a limitation preventing us from adding that feature to the table padding between the table and “what if i don’t see the letter i’m looking for ” should be content under “what if i don’t see the letter i’m looking for ” is incorrect and is displaying strangely it should read if you’ve received a letter about a va debt but don’t see the letter listed here call the debt management center at you can also call the debt management center to get information about your resolved debts for medical copay debt please go to pay your va copay bill to learn about your payment options the “return to your list of debts ” link is missing table isn’t turning into a list when in mobile view please refer to the responsive table design the ebenefits team uses for the correct styling on mobile tasks split this ticket into additional tickets as needed optional work with design team to incorporate feedback review incorporated feedback with design team acceptance criteria feedback has been discussed and incorporated ,1 13628920359.0,2020-09-24 14:29:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rewrite type of care page tests using react testing library we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details we have a collection of type of care pages they could all be tested together to make sure we route properly to different pages they re all fairly simple individually general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos ,1 12225323058.0,2020-05-03 04:27:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,organize sentry teams to reflect vsp reality user story as a vsp engineer i need organized up to date sentry teams so i can understand responsibilities assignment goal all teams in sentry are current and comprised of appropriate members acceptance criteria all vsp members are on the appropriate vsp engineers team vft legacy teams krakens etc are sunset and users migrated definition of done attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 14942563695.0,2021-01-25 21:30:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, clicking the save button on the default list loop card breaks the form issue description clicking the save button on the default list loop card breaks the form how to recreate the bug in staging navigate to step your employment history select yes for have you been employed within the past two years select yes for are you currently employed bug selecting the save button on the default payroll deduction card breaks the form ideal experience selecting the save button shouldn t break the form ideally i think we ll want to have some kind of messaging like please include a type of payroll deduction and deduction amount without making it required this seems like it may have complications with the form system schema so for now we should just make sure the form isn t breaking bug repeat steps then add another payroll deduction selecting the save button on the default card breaks the form as well ideal experience please see the experience under bug please refer to this video to see a visual of the bug tasks resolve the bug that breaks the form when save is selected on the default list loop card acceptance criteria selecting save on an empty default list loop card matches the outlined ideal experience the solution has been pushed to staging and reviewed by a designer ,1 20922804069.0,2022-03-24 19:07:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create unit tests for statementaddresses desired behavior create unit tests for statementaddresses component acceptance criteria tests created and passing how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 25568282764.0,2022-11-30 15:46:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,summarize vbms data issue and historical events issue description depo po has asked for a summary of our teams involvement in the vbms letter issues tasks outline summary and historical details of vbms issue involvement acceptance criteria send summary to matt self how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23088397903.0,2022-07-26 13:24:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letter download page updates due to vbms endpoint being back up issue description the problem an alert was added to the debt letter download page when the vbms endpoint wouldn t display notification letters sent after december the alert that currently exists the solution we need to remove the alert currently displayed and replace it with the alert notifying veterans that repayment terms are incorrect in the digital letters tasks remove the existing warning alert refer to screenshot above add the alert about repayment plan terms acceptance criteria the ui has been updated reach out to denise so jill can be notified that the update is live ,1 19725445836.0,2022-01-13 19:29:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update getting started page name to collaboration cycle kickoff issue description octo de platform lead rachael roueche shared that the name of the within the collaboration cycle section of platform website is confusing because there is a on platform website she advised that we rename this section collaboration cycle kickoff as that is a more transparent and appropriate title tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30507477175.0,2023-07-18 18:01:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display hiding default edit buttons on review page issue description we re aiming to render the review and submit page as read only to accomplish this we need to eliminate the option to edit each individual section thereby aligning these sections with our updated read only design front end tasks utilize css to target and hide the edit buttons on the review and submit page acceptance criteria edit buttons are no longer visible on the review and submit page users can still submit forms all tests are successful ,1 31144533707.0,2023-08-16 04:54:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint august sprint goals identify all sw mvp work and create tickets for all mvp development done complete desktop mobile prototypes done complete research plan guide for sw done secure approval for sw content complete all be work for sw update review page for sw have the collaboration cycle touchpoints accounted for release sw mvp work complete veteran interviews planned issues fsr enhancements downtime dependency update pt fe navigation content update pt fe streamlined waiver sw implement income limit back end fe streamlined waiver prep fe organization of folders fe front end discovery form navigation back to review page pts fe review display employment questions pts fe review display installment contracts fe look into possible approaches for adding an indicator for sw forms be sw add new chapter level depends and structures fe sw update transform and helpers fe add streamlined waiver notification to va notify portal pt be send streamlined waiver notification for eligible requests be add an indicator for sw forms be sw create example submission objects for be pts fe ongoing maintenance bug fixes determine which external services have downtimes be develop method to keep benefit payments from becoming stale be use vcr for unit tests be blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint update sharepoint credentials and resubmit missed submissions be review display cleanup titles and spacing design points planned points accomplished xx tbd xx points over issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 15770045473.0,2021-03-31 19:00:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl debt list past debts empty state hifi issue description we need to create a mockup of the empty state of the past debts section of the list page tasks create mockups share with design team update update this ticket acceptance criteria screen created ,1 20160030183.0,2022-02-09 20:26:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, document outstanding items for smes issue description we need to document the outstanding items we need sme assistance with in order to move forward with finalizing the mcp s mvp tasks document the outstanding items for mcp smes present document to team acceptance criteria document has been presented to team document is linked in this ticket as a comment ,1 26141816151.0,2022-12-29 19:43:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, user research study spreadsheet issue description spreadsheet for fsr user research study tasks create a spreadsheet for fsr user research study acceptance criteria spreadsheet created and linked ,1 29495315783.0,2023-06-02 16:26:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sidekiq admin ui access for kevin suarez your name kevin suarez your github handle sidekiq admin ui access is managed through github kjsuarez your dsvagovcloud aws user name if applicable kevin suarez team role and company of the target individual benefits debt resolution backend engineer govcio cor name jennifer o day please confirm if you are on the vfs team roster or platform team roster sidekiq ui access requested for the following environments dev staging sandbox production if requesting justify prod access in additional notes section if production access is required confirm complete one of the following i have an aws username and it is listed in i currently have access to vets api production terminal via argocd i ve attached a screenshot of my e qip transmittal notice e mail drag or copy paste in additional notes section below additional notes no response ,1 26559761434.0,2023-01-20 14:58:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, bankruptcy history enhancements issue description update fsr bankruptcy page to match new design tasks update bankruptcy details page acceptance criteria bankruptcy details page matches new design behind enhancement flag how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24511014590.0,2022-10-10 21:29:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move paperwork reduction act pra guidance to platform user story as a vfs researcher i want all the important guidance i need in one location that i know to be source of truth so i don t have to hunt for it and so that i know that i m getting the latest guidance as platform governance team i want make sure researchers have access to important information on platform since it is source of truth for research guidance assignee cherylevans peer reviewer description unmoderated research requires adhering to pra a legal requirement there is but if this guidance is important enough for vfs researchers to reference it s important enough to be on platform as the source of truth impacted artifacts tasks decide where on platform this information should live naomimarcussen can help create new page on platform website research mark the gh page as deprecated validate that all links in the new page are working any links that point to gh pages should be redirected to platform website if applicable share new pra guidance in research ops channel in slack peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs teams are able to refer to platform website for pra information vfs teams are redirected to platform website research when visiting the deprecated pra gh page naomimarcussen has peer reviewed and approved this ticket how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 14403140525.0,2020-12-03 15:42:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert facility enzyme tests to use rtl tests facilityaddress facilityhours facilitydirectionslink we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos make sure to use the default exported component in the tests and you should remove the old export of the unconnected component,1 21885287199.0,2022-05-19 17:59:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add information to platform about discovery research user story as a researcher i want clear and updated guidance for discover research on platform so i have a single source of truth intended audience vfs desired outcome add updated guidance to platform due date description there is a that hasn t been migrated to platform that information needs to be added to platform and the gh page marked as deprecated new artifacts maybe a new platform page for uat artifacts needing updates tasks determine where this discovery research information needs to live on platform acceptance criteria github template has been marked as deprecated platform website page name has been updated platform website page name has been created updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 19519367436.0,2021-12-29 15:37:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add mcp services to devops downtime config technical task we need to be able to schedule downtime for a particular service but before we can use these services we need to add them to the devops config so we can use them on the fe as dependancies expected behavior all service dependancies for financial status report are int he devops config acceptance criteria mcp endpoint dependency is added to devops config ,1 16595796252.0,2021-06-01 13:22:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combine fl mobile desktop rendering into one responsive view issue description combine the separate functions for rendering mobile and desktop views into one responsive view show tabs at mobile width toggle map when tabs are clicked hide tabs at desktop width and always show map tasks refactor the separate desktop and mobile rendering code into one responsive view acceptance criteria no changes to behavior instead of sepaprate rendermobileview and renderdesktopview functions we just have one function that renders the component ,1 23324952431.0,2022-08-08 20:10:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, duplicate fsr submissions what happened it has been reported that veterans can submit a duplicate fsr submissions stakeholders report veterans who have duplicate fsrs submitted about a month apart our staff are concerned the system did something my thoughts are the veteran got another letter and then went in data was still there due to cookies and they resubmitted i have copies of the fsrs but they are full of pii how should we address should we call veterans to see if my thoughts are what happened could this have automatically occurred discovery questions does the debt portal have any tracking mechanisms for veteran submissions i e do we alert veteran if they have submitted an fsr for the same debt within a certain amount of time in our backlog i believe we have an issue to provide a space where a veteran could refer back to the fsrs they submit does this issue require us to reexamine that feature additional questions will be added by team as they process discuss this situation acceptance criteria development team has had a chance to explore the current functionality and discuss possible solutions to prevent such an issue occurring for veterans in the future solution has been documented in github and will be prioritized accordingly how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 25412703763.0,2022-11-22 20:30:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, url shortener metrics and reporting description based on a discussion around the url shortener work it was determined monitoring alerting would be needed this ticket is to add monitoring around the below metrics for the url shortener tasks create reporting metrics for the following api request volume latency time to complete api requests error reporting for end users number of active short urls number of short urls expired acceptance criteria the above metrics are being captured and viewable on dashboard for reporting,1 23394940869.0,2022-08-11 21:58:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint august sept sprint goals tbd sprint deliverables list of deliverables completed during sprint tbd planned issues combined fsr tbd fsr enhancements tbd streamlined waiver tbd mcp notification tbd unplanned additions tbd capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished tbd points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline coming soon use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff n a tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 13767999853.0,2020-10-07 16:28:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr installment contracts and other debts as a veteran i want to fill out the fsr form and have all the data in correct spot ,1 31842359913.0,2023-09-14 17:15:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, adderror sentry notification issue description sentry error is cropping up and should be investigated e adderror is not a function this is likely caused by leveraging a validator in a standard component when the validator was designed to accept a error message from the forms system that contains a function adderror tasks investigate error message and identify issue apply fix and confirm no similar errors are in place acceptance criteria sentry error listed above is no longer triggering how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25412701696.0,2022-11-22 20:30:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, veteran information required text placement screen adjustments what happened in detail what went wrong screenshots videos or gifs are strongly encouraged desired behavior move required text to correct element acceptance criteria describe the desired working behavior how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 18911713643.0,2021-11-16 14:43:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,document internal guidance for inputting staging review feedback manually issue description the platform product support team uses the draftingtemplate and bulk upload process to create issue tickets for collaboration cycle staging reviews however if a team member misses the deadline for adding feedback to the draftingtemplate and the bulk upload process has already been executed the team member will need to input their feedback manually using the there are currently no instructions or guidance for how to complete the gh ticket template this ticket will be to expand the instructions within the template itself as well as reference the template in the collab cycle space on confluence tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14229080085.0,2020-11-18 05:26:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and cleanup correct menu section titles to assure they are enabled visn story as a veteran web user i have to be able to see the sections on the left nave menu so i can better understand the sections and areas i want to go in my health care journey resource prod cms va gov task review all system s menus to assure that the following menu sections services and locations news and events and about va… are enabled and have nolink in link field va alexandria health care va central arkansas health care va fayetteville arkansas health care va gulf coast health care va houston health care va jackson health care va shreveport health care va southeast louisiana health care acceptance criteria all system menu sections are enabled all link fields show nolink ,1 19566711703.0,2022-01-04 02:13:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, make accessibility design changes for summary page issue description during a call with angela she noted that there are a few places where the summary screen is a little confusing for screen readers cards should have one link and the should read for questions about your balance should be reconfigured to show the options as headings with appropriate nesting tasks make design changes for both issues above and sync to uxpin create a fe ticket for work if necessary acceptance criteria uxpin updated and linked to this ticket fe ticket created and linked to this ticket if necessary ,1 12258037957.0,2020-05-06 14:33:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, call center interview prep user story or problem statement as a designer i need to prepare for call center interviews so i can ask valuable consistent questions to call center employees in a timely manner goal what outcome s do we want to see a solid plan for call center interviews tasks determine list of call center employees we want to get more data from create a general conversation guide for call center interviews upload call center conversation guide to gh schedule call center interviews acceptance criteria call center conversation guide in gh scheduled call center interviews,1 19564541583.0,2022-01-03 21:27:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,switch to va loading indicator from loadingindicator the loadingindicator component is deprecated in favor of the va loading indicator web component we should evaluate switching to it communication from vsp design system team known differences tasks try out replacing a few loadingindicators with va loading indicator and document any differences that appear ,1 13876705344.0,2020-10-17 00:22:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,vsp content content outline for fsr form issue description create content specs outline for fsr form so already edited content can be used for the high fidelity mockup acceptance criteria designers share design outline form flow peggy to create content specs,1 30218405414.0,2023-07-05 17:18:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr restructure formconfig into manageable chapters summary leveraging the insights gathered from the streamlined waiver functionality discovery we aim to enhance the form s usability and maintainability by restructuring it into well defined chapters this task requires breaking down the existing form into clear concise chapters making it more user friendly and easier to manage poc for the initial work on this task is provided here related issues refer to the previous ticket for more information regarding the streamlined waiver functionality discovery streamlined waiver functionality discovery va gov team proposed form structure a potential structure for the revised form is outlined below the above is just a proposed guideline however this may change once insights from the streamlined waiver functionality discovery are finalized acceptance criteria the form is divided into clearly delineated chapters each chapter is user friendly and easy to manage the proposed form structure has been taken into consideration and appropriately applied ensure any changes made maintain the integrity of the form s functionality we invite collaboration on this task all ideas and insights are welcome to make the form more efficient and user friendly ,1 26274010654.0,2023-01-06 19:57:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,mpi rename update backendexception keys renames master veteran index to master person index there are some localized exception keys in config locales exceptions en yml that are used with the backendexception class to handle issues when communicating with mpi in app swagger swagger requests profile rb they are exposed to api consumers we need to find out if they are all exposed to consumers and come up with deprecation plan to change them over to mpi ,1 25284517144.0,2022-11-16 18:09:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update problem statement on collaboration cycle product outline user story as a governance team member i understand the problem statement for the collaboration cycle better apply my area of expertise assignee shiragoodman peer reviewer description during work for it was discovered that the problem statement on the collaboration cycle product outline has been outdated for some time now and needs to be reviewed impacted artifacts tasks review the current problem statement write a new problem statement reach out to shira ray on platform governance team channel for approval peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria governance team members have a clear vision of the current problem and pain points in the collaboration cycle governance team members understand how they can contribute to help the collaboration cycle how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 26779292006.0,2023-01-31 19:43:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,investigate huron reported submission issues issue description vha stakeholders have reported issues for what they believe is happening from what voda provides to what huron pulls issue veteran possibly submit multiple times issue same form multiple submissions issue no signature on the form tasks backend team to investigate each issue acceptance criteria provide feedback to stakeholder and document any future action required how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26603581691.0,2023-01-23 17:28:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,provide debt lettter user data to stakeholders issue description dmc has determined that getting the user identifiers ssn email etc has become a requirement to their portion of the security audit regarding debt letter downloads we will need to work with identity and platform be team to extract this information from mpi using user uuids tasks extracts list of user uuids from logs connect with mpi for justification for batch processing extract user data from mpi for list pass data securely to dmc contacts acceptance criteria dmc has the user data they need to progress forward with the audit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14967086962.0,2021-01-27 15:18:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content changes issue description the vsp content team sent a page document of content changes that need to be incorporated into the fsr this work is going to be split into tickets by chapter to make the changes easier to both implement and track tickets the wizard tbd global changes tbd form introduction tbd chapter tbd chapter tbd chapter tbd chapter tbd chapter tbd chapter tbd chapter tbd form submission confirmation tbd acceptance criteria all tickets linked above have been completed ,1 19598007461.0,2022-01-05 20:26:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, replace additionalinfo with web component description all instances of additionalinfo need to be replaced with web component tasks replace react additionalinfo component with va additional info web component update unit tests definition of done all tasks complete all tests passing,1 21638380191.0,2022-05-05 16:09:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update va business owner options in new vfs team gh ticket user story as a vfs team po or pm completing the new vfs team ticket i d like to have a choice of options when completing the va business owner question of the ticket so that i know to provide the va organization not the individual s name intended audience vfs pms and pos desired outcome checkbox options for the va business owner question of the new vfs team gh ticket due date description when new vfs pms or pos complete this ticket they often complete the va business owner section incorrectly often times vfs teams will respond with the individuals name however platform would prefer to know the va organization octo office of the cto vha veterans health administration vba veterans benefits administration nca national cemetery administration vaco veterans affairs central office other please specify if we provide checkboxes instead of space to type their own response we re more likely to get the information we re looking for artifacts needing updates tasks placeholder task acceptance criteria confluence page name has been updated confluence page name has been created github template page name has been created github template page name has been updated platform website page name has been updated platform website page name has been created updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 21634447121.0,2022-05-05 13:04:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, consolidate ltr and mcp action references what happened combined portal currently has duplicated the effort of mcp and ltr to facilitate needs desired behavior eliminate debt and consolidate the calls references to the actions from the other modules to point to their new home acceptance criteria all references updated how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 17145214992.0,2021-07-13 13:58:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,deprecate alertbox react component in debt letters technical task as the new web components are rolling out on va gov i see a depreciation warning for the alertbox react component in our repo in order to maintain a clean codebase lets remove all react for its new web component counterpart expected behavior exact same behavior as before this update is made acceptance criteria all react are removed for the new web component in debt letters ,1 14861182276.0,2021-01-18 22:11:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr unauthenticated debt selection designs issue description for the unauthenticated fsr we will need to make some adjustments to several pages that would normally be pre filled for authenticated users tasks alternative designs created for debt selection sync designs to uxpin create frontend ticket acceptance criteria designs synced to uxpin and linked in this ticket frontend ticket created and linked in this ticket,1 16244073318.0,2021-05-07 12:58:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update zip code for dmc on confirmation page expected behavior update zip code for dmc on confirmation page acceptance criteria correct zip code for the dmc should be updated from ,1 13159042699.0,2020-08-10 15:13:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters mvp updated empty states issue description with the updated mvp including both debt summary and a list of downloadable letters on the same screen we need to create additional empty states i ve provided uxpin prototypes for the following empty state use cases i e no debts or debt letters on their record i e no debts but letters from past debts are available to download note the content in these empty states may be updated tasks update the ui with the provided empty states review updated ui with a designer acceptance criteria empty states have been updated to match the provided designs ui has been approved by a designer ,1 23921784924.0,2022-09-09 17:39:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor cancel modal to avoid prop drilling refactor the cancelappointmentmodal such that it doesn t have the different appointment type conditions these are not used for homepage refresh update the component to use connect to redux directly using useselector rather than needing props to be passed in from the parent component unless truly necessary this has now been deployed to the review instance ,1 21661686494.0,2022-05-06 19:59:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,migrate view payments app to va telephone web component background now that the component is being used in favor of the react component we need to swap the component out on the view payments app as the react component will be deprecated at some point tasks swap the component for the react component on view payments ensure all unit and tests still pass submit a pr for review acceptance criteria the component has been swapped out for the component a pr has been submitted for review ,1 27010553794.0,2023-02-10 15:05:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, the content has spelling punctuation or typo errors general information vfs team name debt resolution vfs product name medical copays point of contact reviewers practice area randi hecht content platform issue the content has spelling punctuation or typo errors issue details not sure why the central western massachusetts location is written in all caps and abbreviated it s also missing contact info but there s nothing stating there is no information and what to do link screenshot or steps to recreate img width alt screen shot at am src va gov experience standard other references platform recommendation can this be corrected from wherever this info is pulling from add error text to explain if there is no contact information vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket platform directions update issue title link to collab cycle touchpoint meeting epic add to the feedback pipeline on the platform product support board add your feedback add assignees vfs pm add labels vfs team label va gov experience standard issue number ccissuexx yy where xx is the category number and yy is the issue number per the va gov experience standards practice area labels accessibility ia content design per the va gov experience standards defect label if applicable defect defect defect defect defect launch blocking label if applicable ,1 31815433750.0,2023-09-13 20:04:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,portal information arrangement high level user story ies as a veteran i am able to clearly and easily navigate through the information on the debt portal so that i can find what i need easily scope review links and buttons for consistency throughout the experience we have some action links some buttons etc hypothesis or bet by enhancing the information across the debt portal we are establishing a better less confusing experience for veterans as they traverse the information that is presented to them on the debt portal okr which objective key result does this epic push forward definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 11627782807.0,2020-02-27 17:05:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rename components files to vaprofile the service was renamed to va profile a couple of months ago we should update the fe code to prevent confusing and enhance clarity or any reference to really doesn t mean anything anymore and could really confuse someone who is new to this code or the program rename any existing mentions of vaprofile to profile rename all references of to profile rename all references of or to vaprofile or vaprofile ,1 10427884910.0,2019-09-16 20:59:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,exception handling and error coercion refactor user story or problem statement as a vsp engineer i need a consistent approach to error handling in external request clients so that future developers can easily augment and extend custom error handling right now we approach exception coercion and error reporting in a smattering of various classes and mixins and middlewares the best approach would be to contain all this related logic in a singular place it should not be in private methods in the applicationcontroller goal errors are handled by client middleware and error handling processors in sentry manage custom exception coercion objectives or key results this is meant to further acceptance criteria what needs to happen or be created how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 10928433791.0,2019-11-22 19:01:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consolidate route table configuration user story or problem statement while doing the cutover for the transit gateway work i noticed that we had separate route tables in aws for some reason for each az but they all seem to be identical how might we consolidate these into a single entity so we don t have to update multiple and potentially cause conflicts between them per vpc goal de duplicated route table configuration objectives or key results this is meant to further enable agile vfs delivery of performant applications acceptance criteria route tables that are copies of one another should be consolidated into a single entity how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 25281091979.0,2022-11-16 15:49:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,discovery for bgs issue description discovery work for tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20825338170.0,2022-03-18 20:05:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,track vbms letters for download fix there is no development work for debt resolution team here this issue is to track the vbms fix and any updates we hear along the way issue description vbms stopped sending letters on december and therefore they are not available for veteran s to download through the portal we have added a pop up alert to notify users tasks monitor status of vbms fix and capture any updates for awareness jill anderson mentioned vbms timeline is may acceptance criteria debt letters are being sent from vbms and are now available in the debt portal for veterans to download how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24985039576.0,2022-11-02 14:30:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint october november sprint goals continue to monitor recent launch fsr submission errors triage and resolve fsr submission errors establish design for mini summary pages for work history installment contracts and other debts living expenses and household assets continued streamlined waiver discovery and meet with vha sme progress list loop enhancement front end implementation generate swagger doc for vbs api integration for new copay statement notification back end tech debt prepare for midpoint review sprint deliverables list of deliverables completed during sprint tbd planned issues combined fsr break up funding for va notify requests backend pts move fsr api submission logic to background job pts various discrepancies between huron and sharepoint fsr submissions backend pts content of additional information in fsr is getting cut off backend pts fsr enhancements fsr review page updates design provide veterans with ability to edit benefit information for their fsr submission design checkbox to input boxes enhancements monetary assets frontend enhancement continuous add employment history frontend checkbox to input boxes enhancements spouse other income frontend changing contact info on veteran s profile design design for fsr summary page design pt bug installment contract values calculations frontend checkbox to input boxes enhancements housing expenses frontend checkbox to input boxes enhancements other assets frontend debt notification campaign name change backend enhancement continuous add credit card bills frontend streamlined waiver continued discovery for the streamlined waiver design pts user scenarios flow for streamlined waiver discovery design pts mcp notification determine structure of new mcp statements backend pts create swagger spec document for copay notifications endpoint backend pts view payment history work with lighthouse team to determine real time data next steps backend pts feedback and technical issues tbd unplanned additions will be added throughout the sprint as identified capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 18458850707.0,2021-10-15 20:37:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update mentions of iris in the debt tools hold until october issue description iris is being replaced on october so we need to replace all mentions of iris in our team s tools tasks incorporate updates in the following tools debt portal fsr wizard acceptance criteria the content has been updated in the areas outlined in the attached document ,1 19705519753.0,2022-01-12 21:29:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design components or patterns don t align with design system guidelines general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers josh kim joshkimux accessibility platform issue design components or patterns don t align with design system guidelines issue details notice of rights and responsibilities is a button styled as a link link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation style this button as a button as it is triggering a modal to open alternatively you could write this as a link that navigates to a page about notice of rights and responsibilities instead and retain the link styling check out this presentation on buttons vs links for more on material honesty vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 27640144034.0,2023-03-10 17:20:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update platform links to the newly renamed research review page user story as a vsp team member i want to ensure that broken links are updated so that information can be found as a vfs team member i want all links to work so that i can find information intended audience vfs and vsp team members desired outcome fix broken links to the within the collaboration cycle getting started or research and design sections of platform website due date n a description after updating the it appears that some links to this page elsewhere on platform have been broken we ll want to sweep platform for these dead links and repair artifacts needing updates tasks look for other broken links to the repair any broken links update design intent link under define phase to acceptance criteria offending platform website page links have been updated links within platform website navigate within platform website or github note any pages navigating to confluence without a platform website page should be noted and reviewed related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 25981182001.0,2022-12-19 19:00:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design documentation wrap up issue description ptems pop is ending on december final documentation and wrap up tasks design documentation acceptance criteria update consider editing statements that may be out of date or incorrect adding link to design assets miro boards sketch designs other updating list of team contacts with design team contacts for streamlined waiver providing a short description of current thought process or future vision that may help new designers understand what has been done or the direction you had planned to go how to configure this issue labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 29765730873.0,2023-06-15 00:36:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,efsr and fsr routes veteran information chapter path fsr combinedfinancialstatusreport enhancedfinancialstatusreport veteran information yes yes yes available debts yes no yes all available debts yes yes no contact information yes yes no current contact information yes no yes edit mobile phone yes yes yes edit email address yes yes yes edit mailing address yes yes yes household income chapter path fsr combinedfinancialstatusreport enhancedfinancialstatusreport employment yes yes no employment records yes yes no employment question no no yes enhanced employment records no no yes gross monthly income no no yes deduction checklist no no yes deduction values no no yes employment history no no yes income index yes yes no benefits yes yes no your benefits no no yes edit benefits no no no social security yes yes no social security records yes yes no additional income yes yes no additional income records yes yes no additional income checklist no no yes additional income values no no yes other income summary no no yes add other income no no no spouse information yes yes yes spouse name no no yes enhanced spouse employment question no no yes enhanced spouse employment records no no yes spouse gross monthly income no no yes spouse deduction checklist no no yes spouse deduction values no no yes spouse employment history no no yes spouse employment yes yes no spouse employment records yes yes no spouse income index yes yes no spouse benefits yes yes yes spouse benefit records yes yes yes spouse social security yes yes no spouse social security records yes yes no spouse additional income yes yes no spouse additional income records yes yes no spouse additional income checklist no no yes spouse additional income values no no yes spouse other income summary no no yes spouse add other income no no no dependents yes yes no dependents count no no yes dependent records yes yes no dependent ages no no yes household assets chapter path fsr combinedfinancialstatusreport enhancedfinancialstatusreport monetary assets yes yes no monetary asset checklist no no yes monetary asset values no no yes if monetary assets exist real estate assets yes yes no real estate asset records yes yes no enhanced real estate assets no no yes enhanced real estate asset records no no yes vehicles vehicle records yes yes no your vehicle records no no yes vehicles summary no no yes recreational vehicles cfsr recreational vehicle records no yes no recreational vehicle records yes no no other assets yes yes no other asset records yes yes no other assets checklist no no yes other assets values no no yes if other assets exist other assets summary no no yes if other assets exist add other asset no no yes repayment or relief options chapter path fsr combinedfinancialstatusreport enhancedfinancialstatusreport option explainer yes yes no resolution options yes no no resolution option index no yes no resolution comment index no yes no resolution waiver agreement index no yes no resolution comments yes yes no bankruptcy history chapter path fsr combinedfinancialstatusreport enhancedfinancialstatusreport bankruptcy history yes yes no bankruptcy history records yes yes no enhanced bankruptcy history records no no yes household expenses chapter path fsr combinedfinancialstatusreport enhancedfinancialstatusreport expenses explainer no no yes expenses yes yes no household expenses checklist no no yes household expenses values no no yes utilities yes yes no utility records yes yes no utility bill checklist no no yes utility bill values no no yes utility bill summary no no yes add utility bill yes yes no repayments yes yes no repayment records yes yes no credit card bills no no yes your credit card bills no no yes credit card bills summary no no yes installment contracts no no yes your installment contracts no no yes installment contracts summary no no yes other expenses yes yes no other expense records yes yes no other expenses checklist no no yes other expenses values no no yes other expenses summary no no yes add other expense yes yes no ,1 20376690683.0,2022-02-21 16:17:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add sentry logging to failing vbms calls issue description vbms is frequently down for maintenance so we need to aggregate these failures via sentry tasks add log exception to sentry call upon vbms request failure acceptance criteria when vbms requests fail we are notified with more detailed info on sentry how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16814853729.0,2021-06-17 05:50:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, resolve cms menu structural issues and missing menu items so cms can run scripting story as a veteran i need clear url bread crumbs and paths to all pages hidden and enabled so i can save the location and return goal resolve all cms reporting issues related to menus and menu structure so they can run script that will harden the menus and urls using the menues resources contact kevin walsh utilize reports for both tasks utilizing reports from cms go to each menu and confirm menus are structured correctly update any missing pages that should be in menu acceptance criteria all structural and missing menu items are clear from cms airtable report ,1 19350676912.0,2021-12-15 15:21:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design components or patterns don t align with design system guidelines general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers sean sewell seansewell design platform issue design components or patterns don t align with design system guidelines issue details on the pay your va copay bill page when more than one informational and or alert box is being used on the same page there isn t any space in between the boxes forcing the boxes to appear as though they are running into one another link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation add of space in between the informational alert boxes when more than one appear on a page vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 19576322135.0,2022-01-04 15:49:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove the va health care facility s contact number from designs issue description we received feedback from stakeholders that veterans should contact the hrc for all questions this will improve the veteran s experience and reduce confusion about which number to call depending on the question tasks update the uxpin prototypes to remove the va health care facility phone number s acceptance criteria uxpin prototypes have been updated and linked in this ticket a ticket for frontend implementation has been created and linked in this ticket ,1 15836047321.0,2021-04-06 18:47:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr usability sessions issue description conduct all scheduled usability sessions for a minimum of and a maximum of tasks conduct usability sessions scrub and upload session transcripts to gh acceptance criteria scrubbed session transcripts uploaded to gh and linked in this ticket,1 11273642696.0,2020-01-14 16:55:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fix desktop first styles in vaos scss we have a few uses of max width in our vaos sass which we need to convert to use the mobile first media query helpers used on the rest of the site the va design system is written mobile first and following that pattern will make sure our app s styles are correct and less complex ,1 22659900827.0,2022-07-02 02:06:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, combined debt portal content styling anomalies what happened in staging combined debt portal the following content styling anomalies were found your va debt and bills page page title ended with bill current copay balances page how to pay section expanded option accordion account number was missing time zone format was letter est expanded option accordion account number was missing expanded option accordion account number was missing expanded option accordion visit destination was missing facility address was missing current va debt page current debts section debt cards check details link was not bold how to dispute section time zone format was letter cst specs device browser test user if applicable vets gov user gmail com travis steps to reproduce go to and sign in via id me as vets gov user gmail com travis doc for passwords go to page and observe that page title ends with bill in copay bill summary card click check your balance link on current copay balances page in how to pay section expand option accordion and observe that account number is missing and time zone format is letter est expand option accordion and observe that account number is missing back on your va debt and bills page in debt summary card click check the status link on current va debt page in current debts section observe that debt cards s check details links are not bold in how to dispute section observe that time zone format is letter cst screenshot s desired content styling overview page page title should end with bills current copay balances page how to pay section expanded option accordion account number should be displayed time zone format should be letter et expanded option accordion account number should be displayed expanded option accordion account number should be displayed expanded option accordion visit destination should be displayed facility address should be displayed current va debt page current debts section debt cards check details links should be bold how to dispute section time zone format should be letter ct acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 14528252008.0,2020-12-14 16:18:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor facility criteria fetch to be type of care agnostic currently we have a function in the location service file that fetches facilities from the two vats criteria endpoints and combines them with the facility data from the facilities api this function takes a type of care id and marks each facility as supporting or not supporting that type of care the criteria data we get back includes info about all types of care we should be able to refactor the function in the location service file to not require a type of care id and instead update each facility with a supported flag for each types of care and then update the redux and or component logic to check those flags instead ,1 13995943588.0,2020-10-28 04:35:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for wilkes barre va health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field wilkes barre has facility health services total to include is a referral required are walkins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems wilkes barre va medical center allentown va clinic columbia county va clinic northampton county va clinic sayre va clinic tobyhanna va clinic wayne county va clinic williamsport va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 27610710175.0,2023-03-09 15:48:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,gather list of potential empty submission veterans that have resubmitted fsrs issue description jill would like to know what veterans may have resubmitted fsrs who previously submitted one that contained an empty submission that did not route anywhere tasks develop script to determine if the user resubmitted provide script to platform team with production access filter out successful resubmitted users acceptance criteria we can provide list of affected veterans to dmc that have not resubmitted how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14172697524.0,2020-11-12 17:17:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr household income content as a veteran filling out fsr form i need content to guide me ot fill out the following veteran employment additional veteran income marital status spouse’s employment spouse’s additional income including when i should or should not include my spouse s income and what constitutes my own income ,1 24698995038.0,2022-10-19 14:04:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,break up funding for va notify requests issue description combined fsr submission confirmation emails need to be billed to the appropriate department vba vs vha work with department teams and va notify to configure these templates to be billed separately tasks work with teams to figure out structure update templates and submission code to match acceptance criteria cfsr submissions bill the correct department how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13232874457.0,2020-08-18 14:00:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, write content for the detail page additional info components issue description write content for the additional info components that detail why someone could have each type of debt for compensation pension debt chapter education debt chapter education debt post gi bill debt for books and supplies post gi bill debt for housing post gi bill debt for tuition post gi bill debt for tuition school liable tasks draft content for each deduction code confirm content required w dmc send revised content drafts to peggy for editing approval create ticket for fe acceptance criteria content written and approved fe ticket created and linked in this ticket ,1 19915738536.0,2022-01-25 22:23:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, eslint errors issue description vsp is trying to switch back on the jsx linting rules but they’ve been off for so long that it looks like over misc errors have cropped up and have asked us to lend a hand to update our applications steps to find errors pull latest vets website open eslintrc js search for jsx properties and update the following values to see errors jsx control has associated label jsx no static element interactions if the rule is set to set it to ignore href no hash as it has been deprecated run yarn lint js view errors related slack convo tasks verify all components pass testing and update any failing tests acceptance criteria verify all components pass testing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21002211138.0,2022-03-29 18:36:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html statement statement charges table issue description add statement charges table component to the html statement page refer to the for details tasks create statement charges table using the design system component add download your statement links below the table acceptance criteria statement charges table should render on the html statement page download your statement links should render below the table how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16542257571.0,2021-05-27 18:25:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, unbold labels in va benefit cards issue description unbold ‘total amount ’ and ‘amount received last month ’ in the va benefit cards tasks unbold ‘total amount ’ and ‘amount received last month ’ in the va benefit cards acceptance criteria thing successfully unbolded,1 16770287296.0,2021-06-14 14:04:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, convert claim status tool cypress tests description we have nightwatch tests in place but there is an issue with nightwatch not allowing us to test uploading due to a selenium bug we do have a plan in place to convert all nightwatch tests to cypress tests but we ve been delaying this on the claim status tool cst because we have a redesign in progress as we continue to fix cst bugs we need better tests in place this issue recommends we add these tests time permitting before the redesign has completed acceptance criteria cypress tests in place remove nightwatch tests after cypress tests are in place,1 20157271714.0,2022-02-09 17:36:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,technical concerns issue description as a veteran i want a way to notify the dmc there is a problem with the debt portal acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28062339845.0,2023-03-29 13:23:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refine staging review process for design system team user story as a governance team member i want to ensure that the staging review process for the design system team is clearly documented so that the process is understood by all assignee peer reviewer sterkenburgsara description governance team has completed staging review s for the design system team dst and any changes they make to web components for the va design system the staging review process for dst does not and should not follow the same process that vfs teams follow the purpose of this ticket is to improve the guidance governance team has for dst staging reviews and also to include a reference for dst so they know how we d like them to schedule and what artifacts we d like them to share note since dst is a platform team all guidance for them can be included within confluence they do not need to have a custom issue template in va gov team repo the goal should be to keep this as informal and casual as possible while still ensuring governance team has guidance to complete the review and dst has guidance to schedule and provide artifacts for the review impacted artifacts final documentation this folder contains the proposed documents proposed documentation will replace the current documentation current documentation tasks document proposed process for dst to follow when requesting a staging review confirm with governance team practice areas what artifacts they require for a ds staging review see confirm with governance team practice areas other practice area specific content is correct in the documents document process for governance team to follow for our operational process including scheduling the sr with dst testing the dst component and documenting our findings hosting the sr meeting with dst peer review to be completed by peer reviewer user story and acceptance criteria are met acceptance criteria dst knows how to request a staging review with governance team and how to complete scheduling governance team knows the operational process for completing a staging review for a design system web component how to prepare this issue refinement ticket has user story description tasks and acceptance criteria ticket has if applicable ticket has been sized once all above items are checked add the ready label planning if this ticket is picked up from the backlog mid sprint connect with shira to ensure the below items are completed correctly ticket has been discussed as a team at planning ticket has been assigned to appropriate initiative or quarterly epic ticket has been assigned to a sprint ticket has been moved to the planned pipeline in the governance team board ticket as an assignee and peer reviewer ,1 14225079865.0,2020-11-17 20:40:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,figure out why our rtl helpers don t work in beforeeach blocks we ve had some trouble running helpers like settypeofcare in beforeeach blocks for unknown reasons should investigate why this is happening ,1 22774558139.0,2022-07-08 13:19:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create a combined request help landing page for va combined debt experience launch what s needed we need to create a combined landing page to bring together information on how to request help for all va debts benefit overpayments and copays some other edge cases very early wip draft of page started here ,1 17149922350.0,2021-07-13 19:05:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, switch alertbox to va alert description switch the alertbox component to use the va alert web component in form tasks replace alertbox with va alert update unit tests update tests if applicable definition of done tasks completed all tests passing,1 24677966867.0,2022-10-18 18:38:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr review page path forward issue description discuss path forward for the fsr review page tasks discuss path forward with team make updates acceptance criteria finalize design ,1 23483997711.0,2022-08-17 13:04:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, copay debt resolution option update issue description debt resolution relief options are being updated and moving away from the radio button card components and moving to a more concise selection process and we need to include separate options for copays remove existing radio button card components and replace with standard radio button options with additional subtext information add secondary pages based on these radio button selection to collect necessary information and continue to next selected debt new selection page tasks add standard radio button options with additional subtext information add secondary pages based on these radio button selection to collect necessary information and continue to next selected debt acceptance criteria copay resolution relief options match design and function appropriately how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25404092966.0,2022-11-22 14:10:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add screenshots to capture travel path btsss errors user story as a developer i want to automate taking screenshots of the travel path error states to test run tasks update the travel unhappy path tests to take screenshots of different btsss error states acceptance criteria takes a screenshots of general error takes a screenshot of claim already exists error ,1 23226232216.0,2022-08-03 00:38:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add using assistive technology in zoom link to how to use zoom for user research user story as a researcher i want clear and updated guidance for using assistive technology in zoom on platform so i have a single source of truth intended audience vfs desired outcome add updated guidance to platform due date n a assignee cherylevans peer reviewer jimuhh description in ticket the new page was created and added to the research and design section of platform website we want to make sure that researchers know this page exists so we d like to include a link to it in the page new artifacts n a artifacts needing updates source page tasks in the things to know during a feedback session section add a bullet that says if you are planning to do research with a participant using assistive technology please review the guidance to ensure you re prepared acceptance criteria researchers who are planning to use zoom for research studies are easily able to find guidance for working with assistive technology users related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 28038293894.0,2023-03-28 16:31:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,updates to resolution options to repeat amount of debt issue description update text and design to repeat amount of debt tasks update designs for each resolution option acceptance criteria attach updated designs for each resolution option ,1 30506506750.0,2023-07-18 17:18:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr release plan step development features toggles here toggle name description combined financial status report enhancements enables users to interact with the new efsr enhancements and avoid list loops combined financial status report enables users to submit fsr forms for vha and vba debts step validation since we use a model once code is in the main branch it will be deployed that day before enabling your feature toggle in production you ll need to follow have your team perform as much validation in staging as possible validation may be challenging for some teams and systems due to downstream requirements but the staging system should mimic the production system as much as possible work any downstream or dependant systems proactively to ensure that the feature is ready for use once it hits production have a go no go meeting with the team to ensure that the feature is ready for use and signed off by each discipline and your depo octo contact during this meeting you ll need to review the plan with your depo octo representative review the release plan with your team step production rollout do i need a staged rollout yes feature type possible with feature toggles new feature in existing application yes new application no static content changes n a url redirects no depo vsp octo leads can approve other exceptions to this requirement rollback process our dev team in conjunction with our business partners will monitor site traffic and veteran communications that denote submission problems if they see a spike in errors or unexpected behavior they will contact the engineering team to get the fe engineer to disable the toggle asap phase i moderated production testing also known as user acceptance testing or uat planning desired date range or test duration completed in qa desired number of users n a how you ll recruit the right production test users random sample qa how you ll conduct the testing via canary test how you ll give the test users access to the product in production w o making it live on va gov n a results number of users number of bugs identified fixed list of tickets of bugs changes was any downstream service affected by the change yes no types of errors logged any changes necessary based on the logs feedback on user challenges or va challenges yes no if yes what with ticket numbers phase ii staged rollout also known as unmoderated production testing rollout planning desired date range how will you make the product available in production while limiting the number of users who can find access it use of feature toggles what metrics based criteria will you look at before advancing rollout to the next stage success criteria successful submissions reported contact center calls calls link to the dashboard s showing success criteria metrics who is monitoring the dashboard s be developer scott james and pm tom davis dm heather rienks stage a canary planning length of time one week percentage of users and roughly how many users do you expect this to be results number of unique users metrics at this stage per your success criteria a list that includes kpis listed in the rollout planning section was any downstream service affected by the change yes no n a types of errors logged what changes if any are necessarily based on the logs feedback on user challenges or va challenges stage b of users planning length of time days percentage of users and roughly how many users do you expect this to be results number of unique users metrics at this stage per your success criteria a list that includes kpis listed in the rollout planning section was any downstream service affected by the change yes no n a types of errors logged what changes if any are necessarily based on the logs feedback on user challenges or va challenges stage c of users planning length of time day percentage of users and roughly how many users do you expect this to be results number of unique users metrics at this stage per your success criteria a list that includes kpis listed in the rollout planning section was any downstream service affected by the change yes no n a types of errors logged what changes if any are necessarily based on the logs feedback on user challenges or va challenges stage d of users planning length of time n a percentage of users and roughly how many users do you expect this to be results number of unique users metrics at this stage per your success criteria a list that includes kpis listed in the rollout planning section was any downstream service affected by the change yes no n a types of errors logged what changes if any are necessarily based on the logs feedback on user challenges or va challenges post launch metrics continue to check in on the kpis of your feature at periodic intervals to ensure everything is working as expected we recommend one week and one month check ins but this is only minimal week results number of unique users post launch kpi actual post launch kpi actual post launch kpi actual any issues with va handling processing yes no n a types of errors logged any changes necessary based on the logs feedback on user challenges or va challenges yes no n a if yes what month results number of unique users post launch kpi actual post launch kpi actual post launch kpi actual any issues with va handling processing yes no n a types of errors logged any ux changes necessary based on the logs feedback on user challenges or va challenges yes no n a if yes what post launch questions to be completed once you have gathered your initial set of data as outlined above how do the kpis you gathered compare to your pre launch definition s of success what qualitative feedback have you gathered from users or other stakeholders which assumptions you listed in your product outline were were not validated how might your product evolve now or in the future based on these results ,1 31780837105.0,2023-09-12 17:18:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ux research process refinement research operations issue description what details are necessary for understanding the specific work or request tracked by this issue refining the process for the ux research practice goals infuse early testing research in the product cycle create a simple repository of studies and findings that are actionable and can help inform the roadmap tasks what work is necessary for this story to be completed create a new process for ux research socialize the new process repository spreadsheet acceptance criteria what will be created or happen as a result of this story a new uxr process document socialization within team repository created how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 19705272506.0,2022-01-12 21:10:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,hlr replace loadingindicator with web component description all instances of loadingindicator need to be replaced with web component tasks replace react loadingindicator component with va loading indicator web component update unit tests definition of done all tasks complete all tests passing,1 30819164464.0,2023-08-01 15:12:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,use vcr for unit tests issue description to better replicate external service interactions within our testing suite it would be ideal to use vcr recordings to play back previous responses and test off of tasks build appropriate requests that match our use cases record results of the requests replace rspec mocking of requests with using cassettes acceptance criteria our debt tests suites use vcr for http interactions how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13198094507.0,2020-08-14 01:18:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ia feedback staging review debt letters feedback framework must for if the feedback must be applied should if the feedback is best practice consider for suggestions enhancements description this issue describes ia feedback for the manage debt debt letters tool experience note given this is an mvp and not full implementation of the solution only a small portion of the ia can be reviewed will need to do an additional review once the full product is available on staging must static page breadcrumb should be manage your va debt your va debt page breadcrumb the manage your va debt component should link to staging va gov manage va debt should consider definition of done must feedback is implemented on staging decisions on should and consider feedback and question responses documented in issue issue is closed by vfs team once complete ,1 11568251710.0,2020-02-20 15:35:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, address validation flow to save validate user story as a veteran i need to have clear address validation so i do not spend a lot of time wondering why my address is not being accepted in order to do the above we have identified a technical debt item that would reduce the risk of a bad validation and simplify testing we currently have two methods to do address validation and likely can have one to reduce testing and complexity tasks investigate the two methods and determine whether a single method makes sense and doesn t break anything else regression testing checking where else this is being used code up the simplified consolidated solution acceptance criteria address validation still works but with new sexy code configuration attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team e g vsa authenticated exp vsa caregiver labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 23371637294.0,2022-08-10 20:27:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined fsr cfsr design discovery issue description design team familiarity and discovery related to the online financial status report experience tasks demo overview meeting with pm – q a review the to understand what the paper form looks like and what it contains review the and resources available about the fsr learn how to auto populate fsr experience explore fsr experience on staging using to log in understand different staging users and how to log in for each acceptance criteria above tasks are complete and designers have a fundamental understanding of what the online fsr experience is and what purpose it serves for veterans how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 19099223585.0,2021-11-29 20:17:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, replace sighted language issue description the sitewide content team is moving away from using sighted language such as the word view on va gov this ticket captures the updates to implement into the medical copay tool mcp tasks update the content in the areas outlined in not enrolled in va health care alert no history of medical copays alert acceptance criteria the content has been updated in the mcp ,1 19689453212.0,2022-01-12 04:14:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,setup financial status reports submission notification trigger issue description when a veteran submits their financial status report they should receive an email notification confirming it s submission success tasks create worker to build va notify email alert initiate worker upon fsr submission acceptance criteria veteran receives an email after successful fsr submission how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23088552076.0,2022-07-26 13:30:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, your content doesn t use correct and consistent labels across links entry points navigation components and general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers jim ryan jimuhh ia for more information on how to interpret this ticket please refer to the guidance on platform website platform issue your content doesn t use correct and consistent labels across links entry points navigation components and issue details manage debt and bills part of breadcrumb goes to a link screenshot or steps to recreate va gov experience standard other references wcag sc aa platform recommendation vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 12520754236.0,2020-06-03 16:21:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove profile show receive text notifications feature flag from fe clean up everything regarding the profile show receive text notifications feature flag treat it as true and stop fetching it entirely ,1 23112383209.0,2022-07-27 14:01:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery estimation of timeline and work effort issue description read through vafs design system current fsr code and requested updates to come up with rough idea of timeline and estimation of work effort acceptance criteria rough timeline established to completion of combined fsr how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18950896655.0,2021-11-18 15:05:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, validate and update all lgbt care coordinators to lgbtq care coordinator staff profiles story as a lgbtq coordinator i need my title and position to reflect the newest approved title representing lgbtq goal update all know lgbtq coordinator staff profiles task review and update all staff profiles for lgbtq to the new acronym review all visn systems for lgbtq staff profiles and update the titles as appropriate acceptance criteria all systems have been reviewed for lgbtq coordinator staff profiles and they have been updated with new title ,1 15832431951.0,2021-04-06 14:37:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, quickfix design for multiple current jobs issue description for the purposes of release we need to design a quick fix to account for multiple current jobs tasks create a design and upload it to uxpin create a ticket for fe acceptance criteria designs uploaded to uxpin and linked in this ticket fe ticket created and linked in this ticket ,1 21778921653.0,2022-05-13 16:29:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add references to vfs satisfaction survey to general orientation for va gov platform slide deck user story as a vfs team member i want to be made aware of the vfs satisfaction survey so that i may know of opportunities to communicate my feedback to platform teams as a platform service design team member i want to make sure vfs teams are aware of the vfs satisfaction survey early on so that we may have higher participation in the survey intended audience vfs teams platform desired outcome reference to the satisfaction survey is included in the general orientation slide deck due date description va gov platform product lead andrea hewitt asked recently if the general orientation deck made referenced to the vfs satisfaction survey currently the deck makes a reference to surveys sent to vfs teams from platform but it does not specifically call out the satisfaction survey new artifacts n a artifacts needing updates slide deck slide tasks check in with service design team to get their preference on how the survey should be communicated and possibly linked make the changes to the slide deck acceptance criteria updates have been peer reviewed by governance team member user story need has been fulfilled vfs teams are notified of the satisfaction survey in general orientation related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 18525676564.0,2021-10-20 20:10:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create product profile user guide for mcp description create product profile and user guide for release of medical co pays mcp acceptance criteria create product profile for mcp create user guide for mcp ,1 20376935415.0,2022-02-21 16:31:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, replace deprecated loadingindicator issue description platform deprecated suggesting we use instead tasks replace with new in fsr acceptance criteria should render instead in fsr how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23323288979.0,2022-08-08 18:30:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,set up documentation to track gaps in recruiting user story as a vfs researcher i want to know that where the gaps on in requested recruitment demographics and actual recruited participants so that i can better understand our research practice as a perigean recruiter i want to track gaps in requests vs actual recruitment so that i make sure that expectations are being met so that vfs studies are successful as a governance team octo research reviewer i want to make sure that we are tracking gaps in requests and actual recruitment so that we can ask perigean to adjust if needed and show vfs researchers where we are being successful assignee peer reviewer description we have previously looked back at a subset of past studies to analyze how successful vfs researcher recruitment criteria is being met we found some items that perigean can work on we also found items that either vfs or researcher reviewers can work on or clarify so that we can ensure we are successfully filling recruitment requests this ticket is to set up continued tracking so we can check in the future to see if we are increasing success impacted artifacts new tracker tasks develop a new artifact that tracks requests vs actual recruitment peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria placeholder ac how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 27961587771.0,2023-03-24 16:02:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update template names for dmc notifications issue description as we work to integrate additional vha aspects into the debt portal it is imperative that we can distinguish vba from vha notifications for communication clarity as a result we would like to update the names for our existing notifications outlined below are the current names and the desired changes which will support future growth for both vba and vha notifications tasks updated campaign names for existing va notifications related to the debt portal connect with va notify team as needed to ensure that analytics are consistent and no errors are introduced by the name change desired campaign names current notification campaign name future notification campaign name fsr confirmation debt vba fsr confirmation debt notification debt vba debt letter notification reference information melanie jones from the analytics team shared this via email adding for context this can be a little confusing because the domo dashboard is pulling the campaign from a couple different sources for notification analytics like sent open failure reasons campaign represents the email name in va notify for referral analytics e g link clicks to landing pages campaign represents the campaign value specified in the url provided in the email body if we need to add clarification to the email names that s definitely something we can do i would recommend making the email names and url campaign tags as descriptive as desired also we can track billing separately once you are ready to create those vha notifications i have an action to check if historical notification analytics will reflect updated email names i can say for certain that referrals would not once those url campaign names are tweaked it would only reflect analytics for link clicks that include the new name the old campaign name would still show up with historic data acceptance criteria campaign names have been updated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25287479268.0,2022-11-16 20:36:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, wireframes for user path persona issue description create wireframes for one user path persona tasks create wireframes for one user path persona discuss with smes acceptance criteria personas created meeting created ,1 26801177742.0,2023-02-01 15:12:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace expandinggroup react component to additional info web component description design systems team plans to start deprecating the react components starting on january we will need to ensure the vaos application uses the web components currently the app uses expanding group react component which will need to be updated to the additional info web component known differences tasks try out replacing the expanding group react component with additional info web component and document any differences that appear acceptance criteria replace expanding group react components with additional info web component design assets n a definition of done all acceptance criteria are met documentation is updated ,1 14792314769.0,2021-01-12 14:36:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch signatures as a veteran i want the ability to esign the fsr form and submit electronically to dmc ,1 12521546029.0,2020-06-03 17:34:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt detail page past debts hifi issue description we need to create mockups for the debt detail screen for past debts tasks create mockups share with design team update update this ticket acceptance criteria screen created ,1 13038492952.0,2020-07-28 15:17:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sentry configuration for facilities team goal sentry configuration for facilities team background the veteran facing services platform vsp utilizes sentry as a tool to track errors related to va gov applications sentry allows teams to discover triage and prioritize errors in real time veteran facing services vfs teams are responsible for configuring and managing their own sentry teams managing alerting rules and monitoring their application’s data these management rules give vfs teams more responsibility in relation to sentry alerting and error ownership tasks follow documentation for sentry configuration found configure the socks proxy create a new team with designated sentry administrator provide the name of designated sentry administrator in the vfs platform support slack channel to request access add team members to your sentry team determine list of ownership rules paths and urls for monitoring provide owership rules to a vsp engineer in the vfs platform support slack channel acceptance criteria new team is created based on the naming and structuring conventions sentry administrator is designated and communicated to vfs platform support slack channel ownership rules are determined and communicated to vfs platform support slack channel process is communicated to facilities team apropriate team members join vfs sentry alerts channel how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22591085277.0,2022-06-28 19:56:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add uat research tech troubleshooting to platform user story as a researcher a guide for troubleshooting research sessions with products in production would help when i run into an issue with uat intended audience vfs desired outcome add updated guidance to relevant documentation due date description researchers have found a need to draft when doing research with in production products esp for uat this is guidance that shane and kevin agree would be great to have on platform website new artifacts new page for troubleshooting tech during uat tasks determine where this information should live on platform website research and design shiragoodman s suggestion possibly in the page create guidance as new child page under add new pages determine if the should be marked as deprecated or otherwise linked to the new platform page contact since she created the existing gh page and has maintained it notify her how she can suggest changes to the page once on platform website using the create an issue ticket to suggest changes to this page bullet in the footer check for any known links to the github version update with new link to platform website acceptance criteria platform website troubleshooting for va gov research sessions in prod has been created platform website troubleshooting for va gov research sessions in prod is available for vfs teams to reference angela understands the new location and how to suggest edits to the pages any known links to github documentation is updated to platform website link if github is deprecated users are aware that the github pages have been deprecated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 19581413818.0,2022-01-04 21:54:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, change the notice of rights and responsibilities button from link styling to button styling issue description we received feedback during mcp s staging review that the notice of rights and responsibilities button should be stylized as a button instead of a link since it opens a modal the notice of rights and responsibilities button displays on a va medical facility s detail page tasks update the button s styling to a secondary button instead of a link acceptance criteria the component has been updated to a secondary button ,1 21903218982.0,2022-05-20 15:17:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move research synthesis guidance to platform user story as a vfs researcher i want all the important guidance i need in one location that i know to be source of truth so i don t have to hunt for it and so that i know that i m getting the latest guidance as platform governance team i want make sure researchers have access to important information on platform since it is source of truth for research guidance intended audience vfs teams desired outcome research synth guidance added to platform and marked deprecated on gh due date description there is but if this guidance is important enough for vfs researchers to reference it s important enough to be on platform as the source of truth new artifacts new page for research synthesis artifacts needing updates tasks decide where on platform this information should live likely a new page mark gh page as deprecated acceptance criteria new platform website research synthesis gh page updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 28376154621.0,2023-04-12 21:02:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, text copy updates for fsr issue description what details are necessary for understanding the specific work or request tracked by this issue this ticket has been created as a result of qa work that was done by the debt resolution design research team the changes relate to text copy to enhance clarity and specificity on the fsr form so that the veteran enters the correct information making the form clear and easy to fill out we also recommend additions of help sections or sub text for accessibility tasks what work is necessary for this story to be completed add specifier text how much do you pay on each of your payroll deductions is not specified in the copy and the veteran will not know what to calculate add a help section or subtext that explains how to calculate monthly income add a help section or subtext that explains how to check for payroll deductions and calculate them from paystub waiver and debt forgiveness are used interchangeably throughout the fsr and this might not be intuitive to everyone let s alway say waiver debt forgiveness on the debt resolution selection page please add you may only request one relief option in the future allowing veterans to rank first second and third choice could be desirable from a veteran perspective and from the dmc perspective to streamline follow up communications acceptance criteria what will be created or happen as a result of this story frontend team will create tickets based on these updates how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16505974769.0,2021-05-25 19:21:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr verify all input values userstory as a veteran i would like to verify all my input values before i submit my fsr request so i only submit my fsr request when i confirm all my input values are correct acceptance criteria veteran need to click confirm all values are correct before he can submit fsr request ,1 14220907864.0,2020-11-17 15:05:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch additional income as a veteran i want the ability to enter my additional income on the fsr form ,1 22635744054.0,2022-06-30 18:47:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, clean up deprecated pages functionality user story as a front end developer i want a clean and easy to navigate codebase to reduce complexity and make delivery quicker unused and deprecated pages complicate the codebase list of deprecated content edit functionality demographics contact info emergency contact components pages edit all components within address email index jsx name phonenumber relationship shared folder and all components within header updatebutton editlinktext cancelbutton day of pages updateinformationquestion jsx setveterandatahandler in check in only any other unused components pages that are found while doing this work tasks remove unused components pages and code remove or update unit tests remove or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging prod validation not necessary scheduled ,1 14170048621.0,2020-11-12 14:03:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging review debt letters iteration steps to complete staging review product manager create this issue and fill in feature name in the title and other bolded information appropriately attach all artifacts before requesting the meeting link to this issue once created in in slack tag shira goodman and andrea hewitt shira to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must complete list of artifacts below staging review meeting completed practice area reviewers create sub issues attached to this one with feedback for your team on feature name requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket may differ for each practice area please refer to attached tickets for further instruction artifacts please provide the following artifacts at least days before scheduled review meeting link to product outline link to with the planning sections completed in each section phase i phase ii go live access information for the tool or feature in staging do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository link to your product test cases test plan in testrail with test execution logs for qa practice area review link to your and reports in testrail for qa practice area review link to verification that accessibility checks are complete preferred link to your or link to a doc in your product folder that indicates all required checks from the accessibility doc are complete list of known issues with links to tickets when applicable meeting attendees from product manager required leah keeler depo product lead required matt self anyone else from your team who significantly contributed to the artifacts provided required brad craig becca riley scheduling please reference the times shown are et note an available time slot within a recurring review group office hours slot that works for your team and is at least business days from now write that preferred time slot here on this ticket and vsp will send you a meeting invite if no available time slots work for your team write your availability and requirements here and shira will reach out as needed additional notes during this collaboration point you will receive feedback from the following practice areas design accessibility content qa and optional product analytics engineering information architecture ,1 27011776717.0,2023-02-10 15:56:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery facility name formatting issue description concerns have been raised that the facility in copay details is in all caps manually fomating on the front end probably isn t a great idea since there could be abbreviations and other naming obscurities helpful links from scott all medical center names should be pulled from the schema repo using its id i e for james a haley hospital here’s the of all medical centers and their correlating ids where we’re actually setting what name to use on the card from it’s id facilitynum seems like it’s possible that the facilitynum we’re receiving from vbs isn’t aligning with the actual facility id in the schema which would then fall back to the all caps version that we get from the vbs response hopefully that helps tasks investigate if we can fetch the facility name where it may be formatted correctly acceptance criteria find if there s a formatted data point we can retrieve from or if there s an existing issue how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24557742942.0,2022-10-12 17:19:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, text updates to enhanced fsr uxpin issue description text updates to enhanced fsr uxpin tasks make updates to uxpin acceptance criteria text updates made to uxpin list of updates this front end update was already made add tsp clarify brokerage account for stocks and bonds other stocks and bonds not in your retirement accounts need help with debt related to va benefits or health care copays estimated value of all of your this includes vehicles with a loan this includes properties with a mortgage ,1 24848955745.0,2022-10-26 18:16:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, checkbox to input boxes enhancements issue description add checklist to box functionality in fsr for the following pages and spouse example of functionality tasks add checkbox to input functionality for pages listed above acceptance criteria new page formats are functioning as expected and match design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15038699344.0,2021-02-02 17:45:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update written statement to be required when a waiver is selected issue description if a veteran asks for a waiver the dmc requires a written statement to be submitted along with the request while other debt resolution options don t strictly require but greatly benefit from a written statement we must make this written statement required when waivers are requested and also make the written statement more prominent for all submissions tasks update the content and design of the written statement pages acceptance criteria fsr s ui has been updated and matches the linked designs ui has been reviewed by a designer ,1 15110486251.0,2021-02-08 19:17:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove was va or a mortgage company involved in this bankruptcy question from bankruptcy page issue description since we are not able to provide file upload capabilities we will be removing the question of was va or a mortgage company involved in this bankruptcy until a better solution for this requirement emerges tasks remove was va or a mortgage company involved in this bankruptcy from the mockups acceptance criteria sync to uxpin and link in this ticket,1 28367249443.0,2023-04-12 14:37:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,individual compromise amounts not populating issue description jill has reached out that the individual compromise amounts we re adding to the additional comments section of the fsr is neither showing the compromise amount nor the selected debt name tasks replicate issue locally identify reason behind missing values create fix to populate the values acceptance criteria individual compromise amounts are populating again how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 29658741322.0,2023-06-10 00:01:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,required accessibility update from staging review statement of truth text may be missed by screen reader users issue description in our staging review on this accessibility feedback was provided as launch blocking for our fsr enhancement work ticket issue details on step of when reviewing your information prior to submitting there s a difficult usability challenge that we identified with some other forms around the veteran s statement of truth if you re a screen reader user by the time you get to this point you ve likely gotten into the rhythm of just hitting over and over again to move between interactive elements in the workflow for the most part there s no reason you would ever have your screen reader announce the full text of the page but when you reach this review page there s a jump from the last accordion straight to the veteran s full name input if you re tabbing through the page you ll hear veteran s full name but you won t hear any of the statement of truth text that goes with it the legal fine print is essentially hidden from screen reader users it s there and technically accessible but unlikely to be noticed link screenshot tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story ,1 14010875915.0,2020-10-29 06:12:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vamc team to take second look at all previous system pages to validate mvp and consistency user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation prod cms va gov tasks complete review of system and facility pages for the following content and flow asking these questions does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page confirm all of the facilities are reviewed abie abraham va health care center hcc sergeant joseph george kusick community living center clc armstrong county va clinic clarion county va clinic cranberry township va clinic lawrence county va clinic michael a marzano department of veterans affairs outpatient clinic document all errors items that need update and testing on each page using spreadsheet listed above acceptance criteria all node pages have been reviewed in spreadsheet and issues found have been been documented issues have been escalated for resolution using spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 20177658335.0,2022-02-10 15:43:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,test fsr notification sending on staging environment issue description once the template has been created and uuid has been added to settings we need to run through staging to test the process works as desired tasks use dev user account to test fsr submission and view email acceptance criteria as a user once my fsr has been submitted on staging i have received an email how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20407146175.0,2022-02-23 07:28:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, menu clean up part inform editors of menu parent item corrections and submit changes story as a veteran i need to have a simple and standardized location for all vamc web pages so i can quickly find and locate my vamc information resources tasks wait for submission of redirects for all appropriate pages update pages and test links to make sure all links are working correctly acceptance criteria artifact document for original and new url locations of menu items that need to be moved ,1 14224121423.0,2020-11-17 19:11:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove appeals service alert from vsp ops pageduty config issue description ops member and a front end engineer were pinged at eastern over the weekend for appeals service being down this was later discovered to be some planned maintenance but we likely should not have been woken up for this alert we should remove it from our alerting system pagerduty configurations tasks remove appeals service alert acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26940475604.0,2023-02-08 01:28:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,efolders mydocuments page high level user story ies as a veteran i would like the ability to see the documents that are available to me to view download in a tabel format with the ability to filter sort search hypothesis or bet allow veterans to download needed documents definition of done as a veteran i am able to see a full list of the documents available to me and be abel to sort filter search for specific documents take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 30325608131.0,2023-07-10 23:35:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,file upload add confirmation modal when removing files value statement as a veteran that has uploaded files into a form i want to see a confirmation to remove a file so that i don t accidentally remove an upload background context prior to release of our team s supplemental claims form the collaboration cycle mentioned that this was missing in several pages of our form one of which was the removing of uploaded files acceptance criteria all tasks complete all tests passing user will see a confirmation prior to removing an already uploaded file designs and build notes out of scope add here open questions add here tasks include an approved design add confirmation action prior to removing an already uploaded file unit tests updated tests updated definition of ready clear value description testable acceptance criteria accessibility added to acceptance criteria approved designs attached sample data provided where appropriate estimated to fit within the sprint dependencies and blockers linked definition of done meets acceptance criteria passed testing coverage passed unit testing coverage passed integration testing if applicable code reviewed internal submitted to staging reviewed and approved by product and or design,1 23096563414.0,2022-07-26 20:11:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, architect new structure of fsr issue description currently fsrs are tied to both dmc and user ssn and do not have a saved state we will need to have a new architecture to refactor off of that decouples these relationships and has a long term storage solution for each fsr request tasks determine best solution to store fsrs generate new architecture diagram that represents new structure acceptance criteria we know how to move forward with refactoring fsr how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 31844857805.0,2023-09-14 19:05:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,resolved referred copay debt issue description when a debt is resolved paid off or closed it currently will not reflect in the debt portal ui because the data has not been available from the dmc we believe this data may exist potentially in the cdw acceptance criteria when a veteran has resolved their copay debt or that debt has been referred to treasury they are able to review the status on va gov through the medical copay portal how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30502641783.0,2023-07-18 14:49:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display employment history issue description add employment history for veteran and spouse employmenthistorysummary spouseemploymenthistory as view only on the final review page can likely leverage a custompagereview similar to how utilitybillsummaryreview is implemented only show the values that have been populated can probably use same component for both veteran and spouse see for copy tasks implement read only display on final review page acceptance criteria employment history is displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21960871152.0,2022-05-24 15:42:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, merge medical copays under the new combined debt portal issue description medical copays needs to move under the new combined debt portal application for the new url structure while in development and testing the production medical copays won t change and updates for the cdp effort will be made in under the combined debt portal tasks merge medical copays under combined debt portal acceptance criteria a copy of debt letters will exist within combined debt portal and behind the cdp feature flag how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27059887058.0,2023-02-13 18:53:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design ux qa for staging issue description design research teams to qa staging and document any inconsistencies tasks qa staging document issues acceptance criteria any issues are documented and shared with frontend dev team ,1 18110794187.0,2021-09-23 03:26:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update lgbtq and suicide pages with new updates from sot visn user story as a vha digital media web manager the national changes need to be implemented prior to dual state or full production launches so the systems are updated adequetly prior to the redirect goal remove tech debt prior to full production resources tools documentation tbd tasks update lgbt with lgbtq and suicide pages with new content and organize page correctly update suicide pages with correct format order and new content change out lgbt with newly authorized lgbtq in locations provided by content complete for the following locations va central california health care va northern california health care va pacific islands health care va palo alto health care va san francisco health care va sierra nevada health care va southern nevada health care acceptance criteria suicide pages are updated and if caregiver is not listed on page it is reported in support channel lgbtq pages are updated and if caregiver is not listed on page it is reported in support channel ,1 22631063721.0,2022-06-30 14:41:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cdp users not reaching correct state what happened this ticket is to capture the below work regarding the missing alerts under the described circumstances found in staging review desired behavior alert does not show for user and note guessing at implied that is the same based on wording in screenshot acceptance criteria alert does not show for user and how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 24008101291.0,2022-09-14 16:18:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,track vbms endpoint fix debt letters issue description there is no development work for debt resolution team this issue is to track the vbms fix and any updates we hear along the way vbms stopped sending letters on december and therefore they are not available for veteran s to download through the portal we have added a pop up alert to notify users and removed the cta tasks monitor status of vbms fix and capture any updates below for awareness add pdf download functionality back into ui once endpoint fix has been established acceptance criteria debt letters are being sent from vbms and are now available in the debt portal for veterans to download ℹ️ information log ℹ️ archives vbms endpoint first established jill anderson mentioned vbms timeline is may told that the vbms endpoint fix is being done by the liberty team denise has reached out to logan and mike to get a better understanding on the timing of the fix vbms has begun running dmc’s letters again they haven’t started and they will be sending us a timeline for getting the backlog added everything from december to today we can not remove pop up until all letters have been added ,1 14960074088.0,2021-01-27 04:52:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for va salt lake city health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field to include is a referral required are walk ins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems va salt lake city health care elko va clinic george e wahlen va medical center idaho falls va clinic ogden va clinic orem va clinic pocatello va clinic price va clinic roosevelt va clinic st george va clinic weber county va clinic appears that weber county va clinic is now part of ogden va clinic western salt lake va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 20996281151.0,2022-03-29 13:45:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update api key for forward proxies issue description forward proxies have been setup but an extra layer of security is being added to add back api key to header for requests tasks update aws param store with api key test endpoint with new header acceptance criteria vbs endpoints are successfully including api key with requests how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13095834646.0,2020-08-03 14:44:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, connect to prod dmc api endpoint issue description in order ot test with live users app needs to be connected to prod dml api endpoint tasks after privacy and security review connect to prod dmc api endpoint acceptance criteria veteran is able to log in and see their debt summary in prod environment how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23142258997.0,2022-07-28 19:44:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,generate rails engine for debts api issue description as part of the refactor to separate out our debt services we will add our code to a engine module microservice approach this will allow for us to isolate our code a little better and also associate code ownership tasks run generator to add new engine add boilerplate for our debt endpoints acceptance criteria we have a rails engine that we can add to for debts endpoints how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27239628873.0,2023-02-21 19:11:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, expanding group deprecation issue description deadline on friday march remove soon to be deprecated expanding group react component from debt applications fsr expandinggroup locations src applications financial status report components resolutiondebtcards jsx src applications financial status report components resolutionoptions jsx helpful links tasks replace expandinggroup in fsr components acceptance criteria expanding group react component no longer included in debt related apps tests still passing as expected how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21781010698.0,2022-05-13 18:54:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update component library imports background some of our imports to component in the component library package are incorrect we need to update these imports considerations contacts import should be import contacts from department of veterans affairs component library contacts react bindings imports should be from department of veterans affairs component library dist react bindings tasks update contacts imports update react bindings imports acceptance criteria a pr has been requested for merging,1 16814860421.0,2021-06-17 05:51:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, correct missing menu items errors as needed for vamc systems part story as a veteran and editor i need to have consistent and standardized menu items that support urls so that the urls nesting and menus are easy to understand and comply with standards across the vamc sites goal remove all human created errors and document any outstanding technical improvements that can be implemented into future cloning task review all menus and links in each system and update or correct any menu items incorrectly created by the paos updated pao menu items acceptance criteria all menu items have been reviewed and menus and links have been corrected any issues have been reported and either corrected or listed in a support ticket ,1 30505945498.0,2023-07-18 16:53:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, prep for monday design presentation issue description make updates to deck and rework presentation for larger audience meeting is on july tasks update slides add veteran journey and octo goals slides update speaker notes acceptance criteria updates made presentation made on ,1 23371719910.0,2022-08-10 20:32:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add new database table for fsr submissions issue description we need to persist and add new fields to our fsr form for individual submissions as of right now we only keep track of individual user submissions this is best done using a db table tasks run db migration with new fsr schema create activerecord model to reference table acceptance criteria we are able to store fsrs in our rails db how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14225373393.0,2020-11-17 21:08:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert tabitem test to rtl tests tabitem this could be incorporated into the appointments page tests or converted standalone we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos make sure to use the default exported component in the tests and you should remove the old export of the unconnected component,1 13195892788.0,2020-08-13 19:33:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,only fetch requests before tabs load not appointments currently we re fetching all future appointment data before the tabs on the list page load we do this so that we can conditionally show the express care tab but we really only need requests for that it would be good if we could separate those calls out and only make the request call before showing the tabs ,1 18950819475.0,2021-11-18 15:01:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and validate current active list of all clc and dom facilities in all systems story resources task review the clc dom listing and confirm if there are any new facilities removed facilities starting at start of production schedule highlight all systems that have a clc or dom update orphan list with sites that are closed still exist and what type and what is new acceptance critriea orphan list is updated with current clc dom listing that can be used to assign or track stories ,1 21880763740.0,2022-05-19 14:09:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,benefits debtres sprint priorities benefits sprint priorities sprint may formerly debt resolution team sprint goals finalize vbs aws security groups implementation launch fsr confirmation email notification further progress development of combined va debt portal connect with vha sme to determine path forward for vha resolution options fsr content and dropdown date component design updates sprint deliverables list of deliverables completed during sprint tbd planned issues tls implementation deploy and validate production api key change fsr confirmation email notification setup analytic tracking for fsr notifications launch fsr notification copy in production combined debt portal updated debt and copay alerts debt debt letter download consolidate ltr and mcp action references review the midpoint review tickets sync with accessibility regarding the status icons combined fsr update the dropdown date component with the experimental design system s input date component combined fsr content adjustments sme meeting prep for fsr content adjustments research pdf fill library and integrating with form test uploading files to sharepoint in sandbox environment mcp mvp pages require sensory characteristics to be understood or operable tech debt hook up mocked debt letters with vbms gem unplanned additions debug connection to vbs prod endpoint discovery on the experimental design system s input date component capacity planning pto holiday s denise scott brandyn andrew riley kevin points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ cc events artifacts medical co pays combined va debt portal combined fsr streamlined waiver product outline use cases flow release plan release plan release plan release plan architectural diagram use cases use cases use cases use cases use cases product guide product guide tbd product guide product guide product guide kickoff design intent midpoint review usability testing n a ia request analytics request required contact center review research plan review required staging review privacy security review helpful links ,1 16109774352.0,2021-04-27 19:29:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, back to top component issue description when the content localization team went to use the back to top widget they determine their was some technical debt around the existing component that may require a rebuild notes perceived technical debt around the back to top button the template html lives in vets website but the js is buried in a dependency here packages formation js back to top js with web components this is an anti pattern was the back to top component added to the design system front end tasks review in team grooming and determine level of tech debt and steps to correct determine if this has been added to the design system or if this needs to be taken through that process could we had this over to localization team to handle since they have bandwidth acceptance criteria tbd appendix ensure your code changes are covered by tests expand add tests if none exist for this addition change update existing tests if this code will change functionality include axe checks including hidden content run axe checks using the chrome or firefox browser plugin expand ensure no heading levels are skipped ensure all buttons and labeled inputs use semantic html elements ensure all buttons labeled elements and images are identified using html semantic markers or aria roles ensure form fields have clearly defined boundaries or outlines ensure form fields do not use placeholder text ensure form fields have highly visible and specific error states test for color contrast and color blindness issues expand all text has appropriate contrast zoom layouts to at width expand ensure readability and usability are supported when zoomed up to at browser width ensure no content gets focused offscreen or is hidden from view test with or screen readers expand ensure the page includes a skip navigation link ensure all links are properly descriptive ensure screen reader users can hear the text equivalent for each image conveying information ensure screen reader users can hear the text equivalent for each image button ensure screen reader users can hear labels and instructions for inputs ensure purely decorative images are not announced by the screenreader navigate using the keyboard only expand ensure all links navigation text and or image form controls and page functions can be reached with the tab key in a logical order ensure all links navigation text and or image form controls and page functions can be triggered with the spacebar enter key or arrow keys ensure all interactive elements can be reached with the tab key in a logical order ensure all interactive elements can be triggered with the spacebar enter key or arrow keys ensure focus is always visible and appears in logical order ensure each interactive element has visible focus state which appears in logical order how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28351837938.0,2023-04-12 03:24:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,wireframe user flows for streamlined waiver issue description build out user flows with wireframes based on tasks meeting on wed march and april create user flow documents with various scenarios ux research learning and understanding phase explore and document future research opportunities define said research opportunities define what we want to learn and what we already know acceptance criteria weekly meetings occur user flow with wireframes created ux research learning and understanding phase create a visual for ux research cycles for streamlined waiver initiative with a timeline define said research opportunities ,1 11578046307.0,2020-02-21 15:14:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,upgrade vets api to ruby version upgrade vets api to ruby version acceptance criteria make changes to vets api repo to use ruby co ordinate with the devops team to formulate a strategy for upgrading ruby in our deployed environments ,1 14010937793.0,2020-10-29 06:21:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review at all philadelphia va system pages to validate mvp and consistency user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation prod cms va gov tasks complete review of system and facility pages for the following content and flow asking these questions does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page confirm all of the facilities are reviewed corporal michael j crescenz va medical center burlington county va clinic camden va clinic gloucester county va clinic victor j saracini department of veterans affairs outpatient clinic west philadelphia va clinic document all errors items that need update and testing on each page using spreadsheet listed above acceptance criteria all node pages have been reviewed in spreadsheet and issues found have been been documented issues have been escalated for resolution using spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 20405348700.0,2022-02-23 04:15:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and archive all duplicate pages with and remove duplicates from menu story as a veteran i need to have clear page and menus so i do not get confused by duplicate pages or information on menus task review and determine the actual duplicate page update and archive the detail page remove duplicate entry from menu acceptance criteria all duplicate pages are archived menus are updated ,1 27016617046.0,2023-02-10 20:02:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research approval process from platform issue description add research plan and conversation guide to for approval tasks add research plan and conversation guide to make any necessary updates based on feedback acceptance criteria research submitted to platform ,1 16601584033.0,2021-06-01 20:16:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr create alert for submission failed create an alert for failed submit of fsr form save in progress will save the form veteran can come back at a later time to submit once alert is created a fe ticket needs to be made to implement,1 24654820551.0,2022-10-17 22:06:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add utils for unit test boiler plate description there are a lot of things that we could clean up in our unit tests below is a list of things that we should try to move to a util or helper init state there is already part of this setup for the scheduledmaintencewindow mock router provider and store provider tasks evaluate areas in unit tests to turn into helpers or utils create utils replace repeated setup and code with util create or update unit tests create or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 23851755345.0,2022-09-06 18:38:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, enhancement continuous add employment history desired behavior update user interface to match new spec and rewrite logic to no longer use list loop in favor of manual looping based on continuation question acceptance criteria ui updated and list loop replaced with continue question how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 27016692650.0,2023-02-10 20:06:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, submit research plan and conversation guide to perigean issue description submit completed research plan and conversation guide to perigean documents must be submitted week before research takes place tasks submit completed research plan and conversation guide to perigean acceptance criteria research plan and conversation guide submitted to perigean ,1 30504393722.0,2023-07-18 15:50:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, usability study synthesis issue description tasks compile organize findings on mural board create topline summary gh document create research findings gh document complete va recruitment checker for equality spreadsheet and add screenshot to research findings add findings to research repo acceptance criteria topline summary created research findings gh document completed va recruitment checker for equality spreadsheet findings added to research repo ,1 12531031559.0,2020-06-04 13:57:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters ideation workshop issue description with this issue we ll set up and host a workshop for team members to come and put their ideas on the board and share the goal of having this workshop is to align on a vision for the debt letters mvp prior to bringing the idea s to vsp tasks create workshop plans schedule workshop host workshop attach mural board here acceptance criteria workshop run mural board attached,1 22758128707.0,2022-07-07 18:26:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, no va gov experience standard for the issue found general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue no va gov experience standard for the issue found issue details when viewing details on a copay the link to view the statement includes visible text that has been hidden from screen reader users and screen reader only text that has been hidden visibly this also happens when viewing the statement itself with the link to download a pdf copy of the statement that technique should be used when the visible text alone might be ambiguous to screen reader users or when some extra information would make the link more usable eg sighted users see an icon that needs to be communicated with some alternative text in this case the two versions of the text are almost the same and the slight difference doesn t seem to add much value one unintended consequence for voice command users who speak a command like click they ll likely say the text they see on screen but their software will attempt to match against the hidden text instead since the phrasing of the two versions are a little different they might not get a match link screenshot or steps to recreate logged in as test user navigate to the the download link is coded as the visible link text is download your statement pdf and the screen reader version is download dated medical copay statement pdf va gov experience standard other references platform recommendation i don t think there s any reason to provide screen reader users a different version of this link text a around the download icon i element is appropriate but the link text should be outside the aria hidden span and the sr only span should be removed vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 26709246425.0,2023-01-27 21:28:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, multiple fsr submissions what happened stakeholders both vha and vba have reported seeing multiple and identical fsr submissions for the same veteran across multiple days to be investigated determine what is happening to cause these multiple submissions and what needs to be done to resolve determine if multiple submissions are also being added to our submission metrics determine if email notifications are being sent for each submission acceptance criteria understand resolve issue that is causing multiple fsr submissions how to configure this issue attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 15051329950.0,2021-02-03 13:59:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ia as a veteran on va gov i need the ability to easily navigate to the fsr form on teh site incorporate ia documented def of done all changes documented applied mikki reviews and approves ,1 25919947074.0,2022-12-15 20:54:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, refactor api calls to use a query builder for params description a great suggestion from mark in the data persistence pr was to use a library to manage query params this ticket is to apply that to all of our api fetching utilities appendquery is already installed and works well tasks update query param building to use appendquery create or update unit tests create or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 24505953442.0,2022-10-10 16:22:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,external service slo migration to datadog problem statement the current solution is an mvp that is not automated and takes developer time each week to run and distribute the reports changes to dependent platforms chrome safari prometheus grafana cause breakages to the generation of the report or the collection of the data that require significant work to get back in order data in the current solution only is stored for days hypothesis or bet by moving our current reporting solution we will significantly reduce the amount of time a developer will need to spend generating the report because the reports are automated fact check needed on that last part the reports in datadog will be more robust and will not break with small changes throughout the dependent platforms data will be stored for a significant longer time period we will know we re done when definition of done slo definitions are configured in datadog reports are generated for all the external services based on a decided time frame reports are scheduled to be delivered to the same user base as before launch checklist is this service tool feature service tested usability test todo link has been performed to validate that new changes enable users to do what was intended and that these changes don t worsen quality elsewhere if usability test isn t relevant for this change document the reason for skipping it and issues discovered in usability testing have been addressed note on skipping metrics that show the impact of before after can be a substitute for usability testing end to end or is complete to validate there are no high severity issues before launching if applicable new functionality has thorough automated tests running in ci cd documented new documentation is written pursuant to our product is included in the list the existing product that this initiative fits within or add a new product to this list internal facing there s a checked into note the product directory name should match with the list of vsp products external facing a exists for this product feature tool and should be located at platform product name readme md external facing a exists for this product feature tool and is updated for changes from this initiative and should be linked from the vfs facing readme for your product and should be located within platform product name unless you already have another location for it if applicable and post to about whether this should be added to the if applicable post to for external communication about this change e g vsp newsletter customer facing meetings measurable if applicable this change has clearly defined success metrics with instrumentation of those analytics where possible or a reason documented for skipping it for help see this change has an accompanying required artifacts documentation product name external service monitoring testing usability test link to github issue or provide reason for skipping manual qa link to github issue or documented results automated tests link to tests or n a measurement success metrics link to where success metrics are measured or where they re defined product outline is ok or provide reason for skipping release plan link to release plan ticket ,1 16770376937.0,2021-06-14 14:09:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,reduce error output from vaos we have a lot of error messages in the unit test debug output due to our tests not mocking facilities calls among a few others this makes our tests more concise and exercises code paths that don t require facility info but it s a lot of output and vsp asked us to clean it up generally you can remove that output by mocking the facilities fetch call with mockfacilitiesfetch vha using whatever id is necessary you can also more easily see where the test failures are coming by using the list reporter yarn test unit app folder vaos reporter list log level debug rather than adding these mocks to every single test we should try to add them in beforeeach blocks where possible so they re not cluttering up too many tests there are some tests on the list and detail pages that test that the page renders without facility info those may fail with these mocks in that case we don t want to mock the facility info or we want to mock it so that it returns an error ac error output from vaos tests is significantly reduced,1 13222478715.0,2020-08-17 15:35:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move appointment list components to appointment list folder move appointment list related components to appointment list folder also update tests folder to reflect this change ,1 26367284980.0,2023-01-11 17:32:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, transfer sketch mockups to uxpin issue description what details are necessary for understanding the specific work or request tracked by this issue tasks transfer mockups on sketch over to uxpin acceptance criteria all mockups on uxpin for dev team to reference ,1 16676203739.0,2021-06-07 16:29:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up debt letters spacing and imports technical task as i was completing this for the debt letters app i noted there was some patterns that could be implemented to make the code more clean and maintainable this ticket is being made to address that tech debt going to replace all with marking left and right classes and organize imports to have internal imports first and external second in two groups expected behavior all behavior and styling should be the same acceptance criteria all imports are organized on debt letters all are removed and margin is added instead will be opening another ticket to turn class components into functional components ,1 23587535632.0,2022-08-23 12:52:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, benefit debt resolution option update issue description debt resolution relief options are being updated and moving away from the radio button card components and moving to a more concise selection process include resolution explainer page prior to relief option selection remove existing radio button card components and replace with standard radio button options with additional subtext information add secondary pages based on these radio button selection to collect necessary information and continue to next selected debt updated selection page tasks include resolution explainer page prior to relief option selection remove existing radio button card components and replace with standard radio button options acceptance criteria debt resolution relief options match design and function appropriately how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14002139109.0,2020-10-28 14:27:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fix returnurl for fsr issue description change returnurl to veteran information tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23852013327.0,2022-09-06 18:53:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vehicles page s enhancements issue description remove existing vehicles list loop and implement new input number of functionality tasks update vehicles page with fsr enhancements acceptance criteria new vehicles page s are functioning as anticipate and match mockup how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13996041555.0,2020-10-28 04:51:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for pittsburgh va health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field pittsburgh has facility health services total to include is a referral required are walkins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems pittsburgh va medical center university drive h john heinz iii department of veterans affairs medical center beaver county va clinic belmont county va clinic fayette county va clinic washington county va clinic westmoreland county va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 31849567314.0,2023-09-14 23:37:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, usability study presentation issue description this will be completed after synthesis and after gh documents are completed tasks create ppt document schedule meeting with team and stakeholders acceptance criteria ppt document created meeting scheduled wednesday september et ,1 24871923524.0,2022-10-27 15:49:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,work with forms team to add link to wizard from form page issue description work with the forms team to add a link to the wizard from the va form page tasks identify and connect with the team responsible for adding urls to the wizard from the forms page assist with copy as needed to enhance the form page identify next steps and actions as needed validate link has been added and is live in production acceptance criteria link to the online wizard is available for veterans from the page how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27742372754.0,2023-03-15 15:02:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, employment history navigation fixes issue description back navigation in the midst of updating employment history has some unexpected results like kicking the user back to the summary page with an incomplete record and adding an additional blank record another note is the payroll deductions checkbox to input box selection pages if no checkbox is selected the input list page is empty and it should be skipped steps to recreate issue answer yes to have you had a job in the last years click continue enter employer information click continue select back on gross monthly income page this returns user to summary page with incomplete data tasks identify fix navigational issues identify fix checklist input list navigation issue update and unit tests as necessary acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25981079803.0,2022-12-19 18:54:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, card mockups issue description new mockups for va benefits and mini summary based on conversations with design system accessibility and teams tasks create mockups for va benefits and mini summary acceptance criteria mockups created ,1 23393164169.0,2022-08-11 19:59:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add weight attribute to vet center health service organization issue description vamc health services relied on weight attribute to determine sort order within parent child hierarchy this attribute was not used in the type of care implementation for vet centers we d prefer not to have two different types of logic to determine sort order of services so this issue is to return to the vet center implementation and add weight attribute option hardcoding like it was handled in vet center option cms adds a weight attribute to the type of care attributes and made available in a similar way that was used for entity field fetch subfield what is the value of having weight in the cms when we have multiple weights for different products if we add or remove a type of care the fe wouldn t be able to catch it facilities team will look at an approach to this and prioritization of cms weight value will be determined later related issue default type of care attribute ,1 14225444803.0,2020-11-17 21:15:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove remaining enzyme tests there are some outstanding enzyme tests that look like they can be removed schedulenewappointment appointmentstatus appointmentinstructions communitycareinstructions pastappointmentsdatedropdown errormessage formbuttons appunavailable noregistrationmessage novalidvafacilities singlefacilityeligibilitycheckmessage vafacilityinfomessage after removing these tests we should check for obvious gaps in our code coverage and create tickets to address them ,1 13064392711.0,2020-07-30 18:01:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, claims bdn team pif errors issue description retry the error submit save draftform pifinuse claim could not be established contact the bdn team and have them run the wipp process to delete cancelled cleared pifs tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22156888720.0,2022-06-04 00:34:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analytics edge case kpi dashboard request for benefits combined debt portal request an edge case kpi dashboard what this form is for use this ticket template to request a new edge case kpi dashboard on domo for your product edge case dashboards are for products that fall outside of the scope of our standardized kpi dashboards forms content and search if you are unsure what type of dashboard your product qualifies for please check the on domo expected delivery timelines the analytics team will notify you once this ticket has been pulled into a sprint please note that these dashboards will require additional data and design discovery and will take additional time to deliver you can also reach out for updates on this ticket instructions for the vfs team in order to pull the correct data for your product we need your help to define what pages and events to include in addition to basic product info for edge cases we also ask for product outlines or other resources that will help us understand success for your product and define metrics make a copy of or download excel version fill out product information basics if a part of your product involves any sort of linear process funnel for which you want to be able to measure conversions please include it in the forms tab of the template all other pages associated with your product for which you d want to track visits and engagement should be added to the content tab link to your completed spreadsheet here attached below check your sharing settings to make sure the analytics team will be able to access it answer the questions in the vfs provided information section below add links to the vfs provided information section below add your team label to this ticket to follow its progress vfs provided information product questions help us understand your product better by answering the following questions what does your team consider a completed task veterans are able to review all of their debts and bills in a singular experience who is your product s main user base veterans why does your product require an edge case no does this product currently have a domo dashboard no product resources add links to product outlines feature information or any other resources you think would help us better understand your product and okrs below feel free to also type background information into this section directly the more context you re able to provide the fewer questions we ll need to ask you before getting started we are establishing an overview experience where veterans can review all of their debts and bills in one place here veterans can review both benefit debts as well as medical copays additional resources for context we are hoping to be able to track the following kpis for combined debt portal include all pageviews to manage debt and bills all pageviews to manage debt and bills summary ctr from manage debt and bills summary to manage debt and bills summary copay balances ctr from manage debt and bills summary to manage debt and bills summary debt balances total bounces on manage debt and bills summary navigational clicks on the following four pages there are links to fsr pay va gov and pay gov we would like to better access which part of the experience veteran s tend to access these experiences pages copay bill balances copay bill details benefit debt balances debt details experiences clicks to fsr financial status report form clicks to pay va gov clicks to pay gov additional info please use the for more information on the metrics used in the standard kpi dashboards for additional info read through the if you do not have domo access please ,1 31815041011.0,2023-09-13 19:46:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,user research usability study fsr enhancements issue description tracking the user research tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22101152652.0,2022-06-01 13:50:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,write cypress test for direct schedule flow using vaos service endpoints we have cypress tests written for the request and community care flow that run with the vaos service and feature toggles turned on we should do the same with the direct schedule flow request flow test community care flow test it should work to start from a copy of the request flow test and set up the mocks to put the user in the direct schedule flow and mock the new calls made due to that path mainly clinics and slots ,1 24051735690.0,2022-09-16 13:23:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update telephone component add tty prop to the telephone component the design system team just made an update to the telephone web component which adds a new tty prop for indicating if the number is a tty number or not if the component is used like this the following markup will be rendered inside of the component tty here is the review instance ,1 25566828261.0,2022-11-30 14:51:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, veteran contact information discovery issue description creating a discovery ticket to track investigatory work done for implementing contact information ticket tasks investigate veteran contact information implementation on other forms to allow for profile info editing acceptance criteria have a clear plan for implementing updating veteran contact information in form and profile how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22630433692.0,2022-06-30 14:15:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, spouse income what happened stakeholder reporting that a veteran has reached out saying their fsr populated spouse income however the veteran does not have a spouse and reports he did not enter anything when completing the fsr form online specs device e g iphone macbook browser e g firefox ie test user if applicable steps to reproduce url test user if applicable desired behavior describe in detail what was supposed to happen reference existing github issue that contains a solution if possible acceptance criteria describe the desired working behavior how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 17515667108.0,2021-08-11 06:10:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, swap out lgbt with lgbtq in both system detail pages and playbooks that need to be dispersed user story as a vha digital media web manager the lgbt pages need to be updated to lgbtq so national pages match required changes submitted and approved by va goal remove tech debt for all upcoming dual state systems resources tools documentation see public websites content review tasks find and replace all lgbt with lgbtq for systems not yet in dual state update all playbooks that have not been released to paos with updated system and facility health service language acceptance criteria lgbtq has been updated on systems ready or in queue for dual state lgbtq has been updated in all upcoming playbooks ,1 21336316599.0,2022-04-18 14:58:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add analytics insights team labels to platform orientation templates user story as an analytics insights team member who is assisting with platform orientation i want to make sure the tickets show up my teams backlog so that i can address them as they come up intended audience analytics insights team desired outcome analytics insights label added to both platform orientation template and new vfs teams template due date asap description analytics insights team is helping manage the vfs team roster they need to be informed of new vfs teams and new vfs team members so their label needs to be added to both the platform orientation template and new vfs teams template artifacts needing updates shira already added label update links to templates acceptance criteria platform orientation github template has been updated new vfs teams github template has been updated guidance for new teams and team members on platform website has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 12056469288.0,2020-04-15 14:30:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor appointment type logic on appointment list page we have a lot of conditionals around how to present data on the appointment list page these are mostly located in a utils file and not in components this is not really the typical react pattern which would put that conditional logic in components and switch between different sub components there are a few steps we can take to make this easier to understand move conditional checks to redux store we can put flags on the appointment objects to denote if they re cc video va requests etc we can do this in one place and have more concise logic because we know more about what object is what in the reducer update components to use specific components for different types of appointments instead of burying that logic in a utils file we ll have to balance creating too many components but i think preferring the component based approach will get us more understandable code ,1 15769896781.0,2021-03-31 18:50:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, placeholder wizard content changes this ticket is a placeholder and will be edited once the finalized wizard content is available issue description the vsp content team provided that need to be incorporated into the fsr this ticket encompasses the content changes that need to be made to the form s wizard tasks incorporate the content changes in the provided document into the fsr s staging environment reach out to the design team with any questions acceptance criteria the form s wizard changes have been incorporated into the fsr s staging environment work has been checked off in the ,1 19531472126.0,2021-12-30 17:41:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace manifest json imports with getappurl background our application on vfs has very long build times with lots of flakey unit tests that fail in builds often this is mostly due to the fact that when a build is run all of the apps have to built at the same time to combat this the vsp team has undertaken an initiative to break the apps up and isolate them so that each app can be built independently to do our part we need to get our apps ready for this new build process to do this we need to utilize the getappurl registry helper to remove any import to manifest json in our apps considerations note imported from refers to other applications importing this apps files imported to refers to applications that are importing files from other applications apps we own src applications disability benefits src applications disability benefits view payments src applications lgy coe src applications personalization rated disabilites src applications personalization view dependents src applications personalization view representative src applications static pages dependency verification src applications vre src applications vre tasks search for all manifest json imports from other apps in our apps and replace them using getappurl acceptance criteria all imports of other applications manifest json file should be replaced with getappurl a pr is in place for review,1 31818336042.0,2023-09-13 22:43:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update intro page issue description the intro page needs to be updated to the more detailed version in sketch tasks updated intro page copy based on approved sw copy acceptance criteria intro page copy has been updated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27616921520.0,2023-03-09 20:09:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, fsr link should be an action link issue description add to request help with va form continuation of tasks contact content team to update styling of the fsr link acceptance criteria direct link to fsr on wizard will be updated to utilize the action link style ,1 27094283598.0,2023-02-15 00:36:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove conditional use of the old iscerner method description we need to remove the vaonlineschedulingusedsot feature flag as the selectpatientfacilities selector will no longer be in use acceptance criteria we no longer use the vaonlineschedulingusedsot toggle definition of done all acceptance criteria are met documentation is updated ,1 11873578435.0,2020-03-26 17:31:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace deprecated iconv library task replace deprecated iconv with activesupport inflector transliterate background as part of the circleci migration an issue came up with the iconv library and the default service lang environment variable while its straightforward enough to solve ensure lang en us utf is set on the server it demonstrates clearly that there s some non application configuration and cross platform issues that can be surprising cf the iconv library is only used in app workers education form forms base rb and the failing specs were spec jobs education form forms spec rb and spec jobs education form forms spec rb a quick attempt to use the activesupport transliterate found that the defaults in activesupport do not completely cover the use cases in our test suite these tests are old the authors have moved to other projects so there s not a ton of history but it looks like a large portion of the specs look for handling microsoft quote apostrophe character conversions properly which should be able to be handled in the transliteration configuration per the makandracard article de transliterate rule ä ae ö oe the iconv library was removed in ruby so between that deprecated dependency and the locale env specific variation in underlying iconv implementations moving to a more portable and rails y solution makes sense ,1 22761104154.0,2022-07-07 21:14:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,staging review quality assurance feedback review benefits combined debt portal vfs acceptance criteria let platform know when the must feedback has been incorporated leave any comments for feedback you decide not to take vfs team closes the ticket thoughts questions great use case documentation thanks for that the report looks great and provides assurance that use cases are documented and covered by your test plan feedback must the feedback must be applied should the feedback is best practice consider suggestions enhancements must where the individual debts don t add up should be resolved before proceeding to production should none consider is the ordering of the debt card and the copay card significant i noticed that the mockup displays the debt card above the copay card and the test case lists them in that order ,1 27011924904.0,2023-02-10 16:02:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,mcp tech debt issue description tech debt for medical copays acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24557771689.0,2022-10-12 17:20:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr streamlined waiver wizard design discovery issue description design discovery to learn more about wizard experience currently in the fsr and the changes needed recommended going forward tasks wizard learn more about what the fsr wizard is what is is intended to do how it is used etc identify what improvements changes are needed going forward is the primary change moving to the one question per page format or is it more extensive sync with contact on the design system form system team to determine how they can help with design work or define who owns wizard experience streamlined explore opportunities for wizard to be combined with streamlined waiver review vha decision tree and income calculator spreadsheet prepare questions for vha sme discussion acceptance criteria understanding of next steps and establish github issues for work that is required how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13399037567.0,2020-09-03 13:58:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create betamocks for dmc debt letters apis create betamocks for debt letters debt summary and debt details apis so testing can take place in local environment before merging to staging ,1 19278086485.0,2021-12-10 14:13:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, validate the naming conventions for all visns systems for all of the health services story as a veteran web site visitor the url that i use to access my vamc is accurate and meets standards so i can reliably save and return to the vamc web pages in the future tasks review and validate all urls are correct report any anomalies to determine if a redirect is needed once redirect is in place update correct the url or have cms correct url acceptance criteria a report of anomalies is created as an artifact for this story and can be provided to po,1 18270997169.0,2021-10-04 13:49:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add sentry to improve error reporting issue description we are currently not throwing errors and only capturing exceptions using google analytics which makes it difficult to troubleshoot any issues in the event of a failed api call so there is a need to add sentry to debt letters improve error reporting example implementation import sentry from sentry browser sentry withscope scope sentry capturemessage validation issue not displayed scope setextra prefix trackingprefix scope setextra inprogressformid inprogressformid scope setextra errors errors tasks failed api calls should throw error payload with details acceptance criteria failed api calls should throw error payload with details how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30217675393.0,2023-07-05 16:45:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove combined fsr feature flag issue description combined financial status report has been true for long enough we can remove references to it and clean out deprecated files functionality flipper features combined financial status report some pages that will be deprecated by the removal not a complete list debt selection resolution options recreational vehicles also double check transform functionality for removing feature flag tasks identify and remove all references to combined financial status report feature flag on the frontend identify and remove deprecated files functionality from removing the feature flag update remove unit and tests affected by the removal of feature flag remove feature flag from acceptance criteria combined financial status report references have been removed all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27527127158.0,2023-03-06 18:57:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,verify debts controller endpoints in eks issue description as part of our migration to eks we need to the endpoints owned by our team work as intended with the new infrastructure some instructions can be found tasks create endpoint collection add requests to collection use variables for secretes run tests acceptance criteria we ve validated the tests against our endpoints in eks communicate results with platform devops team associated ticket please communicate updates to lainey how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25859777537.0,2022-12-13 16:08:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add navigation testing to efsr tests what happened need to add back forth and confirmation data retains to further shore up tests desired behavior navigational testing added acceptance criteria navigational testing added how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 21660242951.0,2022-05-06 18:19:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,connecting va gov staging dmc preprod high level user story ies we would like to connect to dmc s preprod environment so we are able to do end to end testing for debt letters and fsr hypothesis or bet if we successfully connect to dmc s preprod environment then we expect to do all the necessary testing in the preprod environment and only deploy confirmed working solution to production definition of done confirm what we can use dmc s preprod environment for using our test users in dmc s preprod environment take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 16194913487.0,2021-05-04 13:31:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, marital status ui and content improvements issue description we received feedback during the fsr s usability study that participants didn t know why their marital status spouse information was necessary additionally there was concern about needing to specify their marital status as divorced separated etc this specification was added in an attempt to provide more context about the veteran s financial situation but the original form only asks if they re married or not married we ve evaluated the content and need to incorporate the ui and content changes tasks uxpin prototype for reference update the question asking about the veteran s marital status to are you married with yes and no radio buttons yes will proceed to gather spousal information whereas no will proceed to the dependent page add an additional info component with the outlined content acceptance criteria the ui has been updated to reflect the provided uxpin prototype the content changes have been incorporated the changes have been reviewed by a designer on the team ,1 23115505001.0,2022-07-27 16:18:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create must should consider guidance for collaboration cycle user story as a vfs team i want to know how to interpret the feedback received at design intent and midpoint review so that i know how to prioritize appropriately intended audience vfs teams desired outcome new guidance drafted on must should consider due date description vfs teams may not have a clear understanding of the differences between must should and consider in the feedback tickets for design intent and midpoint review the must should consider model is built off of the shiragoodman has previously explained must should consider as must likely to result in a documented issue ticket referencing the va gov experience standards should promotes best practices in the industry by may or may not result in an issue ticket consider while the feature of the product isn t incorrect or wrong there may be a better way of handling it artifacts needing updates n a tasks create documentation draft detailing the definitions for must should and consider draft should also include why we use must should and consider at design intent and midpoint review but not staging review share with governance team for internal peer review make changes as appropriate share on platform collaboration cycle channel for approval from octo practice area leads acceptance criteria octo practice area leads have approved of the proposed definitions governance team is in alignment on the proposed definitions related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 13390274717.0,2020-09-02 20:16:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move new appointment flow components to new appointment folder move the components for the new appointment flow into the new appointment feature folder also update the tests folder to reflect this ,1 15597242898.0,2021-03-18 16:42:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,clean up unit test output we have a lot of debug output coming from the vaos tests it would be nice if we could reduce the output without losing important error information ,1 17515678803.0,2021-08-11 06:11:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, find and list all lbgt references so they can be provided to pao for correction story as a public affairs officer i need to know all the location the lgbt reference is made so i can update them in my own web system pages goal provide technical debt created by the lgbtq change to the pao and make it easy for them to find the areas to update task list the page name and area within the page the lgbt term used so we can provide the map to the paos for easy correct acceptance criteria a word document with the page and location of each lgbt reference ,1 25595876768.0,2022-12-01 16:09:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, use redux store for all errors before routing to error page description store all errors as strings in redux state ie dispatch the seterror action when an error occurs usually in a side effect like an api call dispatch seterror bad token create a higher order component to wrap the application and handle errors by routing the application to the error page later this could include more robust error reporting using ga sentry or datadog this also give us the flexibility to create other side effects like add more information to the state object for more complicated error messaging useeffect if error gotoerrorpage error the router utility gotoerrorpage will use the error string to add a query string to the url for ga tracking this gives us more flexibility to get creative with the url parameters replace utility functions like appointmentwascanceled in the error page for pre check in with a check against the error string in the redux store if error appointment cancelled tasks on error dispatch seterror action create hoc for routing and other side effects modify gotoerrorpage to use error type instead of full url parameter replace redundant use of utility functions with error type from state create or update unit tests create or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 20735985585.0,2022-03-14 13:47:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update collaboration cycle operational guidance per vsa contract ending issue description the vsa contract is ending april currently we invite specific members to our review meeting if the product is vsa we need to review our documentation and update it tasks update the document update the document update the document acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22773975080.0,2022-07-08 12:49:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, staging combined debt portal current copay balances how to dispute section links go to prod what happened on staging combined debt portal current copay balances page in how to dispute section links navigated to prod instead of staging mdash returning to staging page killed user session specs device browser all except win firefox mac safari test user if applicable vets gov user gmail com travis steps to reproduce go to and sign in via id me as vets gov user gmail com travis go to page in debt and bill overview section in copay bill summary card click check your balance link on current copay balances page scroll down to how to dispute section click find your nearest link and observe that find va locations page is in prod va gov click browser back button and observe that staging unauthenticated homepage loads instead of current copay balances repeat procedure to check same section s learn more link and observe same behavior video staging find your nearest link goes from to prod desired behavior find your nearest link should go to staging find va locations page not prod clicking browser back button should return to staging current copay balances page learn more link should go to staging dispute your va copay charges page not prod clicking browser back button should return to staging current copay balances page acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 30320181715.0,2023-07-10 18:36:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display housing expenses issue description add housing expenses householdexpensesinputlist as view only on the final review page can likely leverage a custompagereview similar to how utilitybillsummaryreview is implemented only show the values that have been populated see for copy tasks implement read only display on final review page acceptance criteria housing expenses are displayed on the final review page if there is data all tests passing unit how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11199889604.0,2020-01-03 20:03:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update react formation version this is related to ticket changes were required on react formation ,1 27088465388.0,2023-02-14 18:53:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,tech discovery are react based radio buttons being used by forms issue description the design system team has been deprecating older react based versions of our components in favor of web components which have react bindings the scope of this ticket is limited to planned deprecation of the use of react based radio buttons by end of feb tasks technical research to see if react based radio buttons are being used in forms need to know here is a page specifically for developers with relevant information components that have been deprecated in storybook slack thread acceptance criteria discover if forms use react based radio buttons open a ticket to update the forms to replace react based radio buttons with web components the new ticket has a list of all occurrences of react based radio buttons in the application how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12531886671.0,2020-06-04 15:09:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor and add test coverage for presubmit checkboxes technical debt ticket user story as i developer i would like to keep up with technical debt and general house cleaning of my teams application i needed to get my last pr merged do to its ever growing size acceptance criteria refactor presubmit signatureboxes to use usecallback so we can remove eslint ignore line add unit test coverage for presubmit signatureboxes,1 13764893103.0,2020-10-07 12:43:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr employment section as a veteran filling out fsr i want the employment section to guide me in correctly filling out the section i would like to know what to put down for seasonal jobs work like uber or instacart and if i have multiple employers ,1 13236240146.0,2020-08-18 19:27:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,enable uat testing visibility only for manage debt page issue description we have a request from the debt management team to make it so that we can publish the manage your debt landing page so it s only visible to uat testing users link to slack discussion i m opening this and assigning everyone from the slack thread as a placeholder to begin tracking this work please feel free to edit issue as needed leahkeeler can you confirm timing need for this thank you tasks tbd acceptance criteria page is published and visible only for uat testing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 15498259767.0,2021-03-11 06:10:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review clean up of va portsmouth va clinic hampton va user story or problem statement as a veteran web user i must have full accessibility a compliance to my web applications and tools so i can use the vamc system pages in any gui ue including mobile and reader environments goal perform initial page testing and review objectives or key results this is meant to further increase overall quality experience for veteran s accessibility assist and reduce time for complete accessibility and compliance checks resources tools documentation tasks complete content review of system pages from a reader s point of view and make corrections in production prod cms va gov use analytics review document to see changes already implemented va portsmouth clinic prepare for your visit acceptance criteria all url and node pages must have been documented in spreadsheet broken links issues in page duplicates or anomalies must be documented issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 24449925941.0,2022-10-06 21:39:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update medical copay wizard path issue description update medical copay path in the wizard in discussion with sitewide content we will update wizard to open path for medical copays tasks update intro description at the top of the wizard update the path for the medical copays section of the wizard acceptance criteria updates have been made an in staging for content team to review how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23088580819.0,2022-07-26 13:31:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, url doesn t provide clear and specific context in a few words as possible general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers jim ryan jimuhh ia for more information on how to interpret this ticket please refer to the guidance on platform website platform issue url doesn t provide clear and specific context in a few words as possible issue details url title is summary which doesn t match breadcrumb or provide needed context parent page to summary is a link screenshot or steps to recreate va gov experience standard other references platform recommendation vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 14442996159.0,2020-12-07 18:58:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr ch household expenses as a veteran i want the ability to add household expenses to the fsr form to give the dmc an accurate snapshop of my financial status i want the ability to both utilize the categories provided and add additional expenses if my expenses are not listed on the online form ,1 30570678351.0,2023-07-20 21:52:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review display cleanup titles and spacing issue description spacing and title sizes need to be cleaned up and made consistent tasks fix display issues added form system classes to each component acceptance criteria all titles and review page components are consistent how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21956677697.0,2022-05-24 12:43:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the additional information component s chevron color to blue issue description as part of the combined debt portal s midpoint review we received feedback that we re not using the correct hex color code for the additional information component s chevron the correct hex code is tasks update the prototype additional information components to the correct chevron color acceptance criteria the uxpin has been updated and linked in this ticket,1 15770038995.0,2021-03-31 19:00:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr usability readout issue description once synthesis is complete we will need to create a readout document or deck to share with stakeholders and the contract tasks use synthesis deliverable to create a readout document create deck from readout document if needed acceptance criteria readout document uploaded to gh and linked in this ticket deck created if needed add finding suggestions to backlog if needed ,1 24192270813.0,2022-09-23 18:54:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint september oct sprint goals • add copay path on fsr wizard • review and integrate content changes on fsr • update review page on fsr • finalize research plan • mock up “other” living expenses options • continue design wireframes • design intent for fsr enhancement release • monitor phased release of fsr vha • checkbox to input boxes • integrate continuous add feature • lighthouse api to cdw investigation sprint deliverables list of deliverables completed during sprint fsr enhancement collaboration cycle kickoff streamlined waiver collaboration cycle kickoff planned issues combined fsr checkbox to input boxes enhancements pts upload pdf versions of fsr vha requests to pts return pdf details upon fsr submission pts design for fsr review page pts define copay path pts uxpin text updates investigate removing cross app references from fsr pt move fsr api submission logic to background job pts break up funding for va notify requests pts fsr enhancements enhancement continuous add credit card bills pts enhancement continuous add employment history pts research plan review for enhanced fsr pts content changes pts streamlined waiver user scenarios flow for streamlined waiver discovery pts mcp notification authenticate vbs on new statement route pts view payment history work with lighthouse team to determine real time data next steps pts unplanned additions tbd capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline coming soon use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff n a tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 19581102709.0,2022-01-04 21:27:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,deprecate previous versions of vets api how to configure this issue attached to an epic what body of work is this a part of correctly labeled fill in user stories fill in documentation fill in tasks fill in acceptance criteria user story these should be why the veteran cares and the veteran gets out of it fill in fill in related documentation these should be links to feature docs fill in description this should be an understandable description of the ticket this description should have enough context meaning that non technical team members should get the idea tasks this is a list of technical tasks that need for this ticket write rspec tests update relevant documentations readme use cases acceptance criteria when is the ticket done deployed to staging fe engineering team has signed off on the feature ,1 22338813176.0,2022-06-14 21:28:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, deprecate check in experience refresh pre checkin feature flag description check in experience refresh pre checkin feature flag has been turned on in production the task is to remove check in experience refresh pre checkin feature flag and its code reference related documentation acceptance criteria remove feature flag and corresponding code reference modify rspec tasks deploy and test on staging ,1 18292954539.0,2021-10-05 17:12:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add vbms debts to vets api mockdata issue description configure mock debts for vbms debt letters in sample response documentid doctype typedescription dmc second demand letter receivedat documentid doctype typedescription dmc first demand letter receivedat documentid doctype typedescription dmc first demand letter receivedat documentid doctype typedescription dmc second demand letter receivedat tasks configure mock debts for the debt letters endpoint in acceptance criteria api calls to debt letters when mock true should return a response from verify correct payload is being returned how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18727157641.0,2021-11-03 17:25:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,get cidr ip addresses to liberty team technical task get cidr ip addresses from vsp so we can give them to vbs liberty team so they can get staging environments set up with api key and ip restrictions expected behavior cidr ip address range is delivered to vsp liberty team acceptance criteria liberty team has cidr ip range ,1 25100936699.0,2022-11-08 13:35:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, local application reloading redirects to verify page description when running locally the app will redirect back to the verify page on reload in production or on stage this results in routing to an error page figure out if this is intentional on local and if we should make the local app better reflect the live site tasks redirect to error page locally on reload research if we need a ticket to handle reloading of check in pages better in general mark s pr covering full auth could be a possible fix for solving this issue create a new ticket after discussing with lori for the fix ,1 13401603095.0,2020-09-03 17:35:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add get debt letters from vbms method to debt letters service user story or problem statement a method needs to be added the debt letters service that allows a veteran to download a particular debt letter goal method has been added to the service that allows a veteran to download a particular debt letter objectives or key results this is meant to further allows veterans to download debt letters tasks add service method to download debt letters update service related tests acceptance criteria a method will be added to the debt letters dmc service that will allow veterans to download debt letters ,1 19350678861.0,2021-12-15 15:21:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, long or complex sections of content aren t broken up into content chunks or bulleted lists general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers jim ryan jimuhh ia platform issue long or complex sections of content aren t broken up into content chunks or bulleted lists issue details on copay balances page copay name facility name and location are all on the same wrapping line not chunked as per card design pattern best practices link screenshot or steps to recreate va gov experience standard other references wcag sc platform recommendation if possible consider turning those three chunks of info into semantically distinct headings also if possible consider adding date of service to copay summary vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 24680634893.0,2022-10-18 20:58:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design for fsr summary page issue description create design for summary pages on fsr tasks create mockup for summary pages acceptance criteria link summary page ,1 24277614250.0,2022-09-28 14:53:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,certificate of eligibility update to web components value statement as a front end developer we want to make sure that all the coe components are updated to the latest recommendations so that we can ensure we re releasing a quality product background context the coe form contains a few react components that need to be updated to use web components including but not limited to omb → va omb info telephone → add tty prop download link → va link textinput → va text input tasks update components as needed update unit tests definition of done all tasks complete all tests passing ,1 22758127113.0,2022-07-07 18:26:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, your page doesn t follow heading hierarchy headings aren t properly nested and headings and or labels aren t relevant to the page general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue your page doesn t follow heading hierarchy headings aren t properly nested and headings and or labels aren t relevant to the page issue details when viewing details on a debt summary debt balances details and there is an alert at the top of the page the headings skip from to with no between them many screen reader users navigate by heading using the heading levels to explore the structure of the page it s easy to be disoriented or confused when heading levels are skipped or improperly nested link screenshot or steps to recreate when logged in as test user navigate to inspect the code to see that we re offsetting your benefit payments each month until your debt is paid is an va gov experience standard other references wcag sc a wcag sc aa platform recommendation the heading on the alert should be an not an vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 22275096358.0,2022-06-10 15:50:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove step from platform orientation template user story as a new vfs team member i want to not encounter any unobtainable steps in platform orientation so that i can easily complete the steps in the platform orientation process intended audience vfs teams desired outcome platform orientation gh template updated due date tbd description in ticket governance team added the process of getting added to vets gov write gh team to the platform orientation process as opposed to a step that occurs before opening this ticket there are certain steps that cannot be completed now that vets gov write access is now part of this process including adding gh labels to the ticket as such the step add your teams github label under labels needs to be removed from the ticket artifacts needing updates tasks remove how to fill out this ticket add your teams github label under labels review other steps to determine if any other steps need removed acceptance criteria github template platform orientation has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 27145060364.0,2023-02-16 19:16:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,va team onboarding amir nashat welcome to va gov application teams welcome this issue will be used to track your onboarding to your team before you start your program manager will meet with your practice lead and product manager for your team if applicable to review onboarding responsibilities pre onboarding program manager tasks send notifications with new hire details name position start date to bah onboarding point of contact va product owner practice lead add as an assignee to this ticket product manager add as an assignee to this ticket access requests request access to request access to request new hire to complete va onboarding paperwork after new hire is set up with the va organization in github comfirm that the new hire has created a platform orientation ticket onboarding new hire tasks day attend program check in meeting share github handle begin va contractor onboarding paperwork sent by prime contractor onboarding contact review tasks in your personalized or day onboarding plan this will be provided by your practice manager or onboarding buddy week self assign for getting onboarded with va gov platform month request socks access after sac adjudication practice lead tasks a practice lead is responsible for meeting with the new hire and providing orientation structure around their practice area of engineering research design or product some tasks may be delegated as needed to an onboarding buddy or practice manager who will be working more closely with the new team member day reach out to new hire over slack to say hello week conduct practice specific onboarding meeting with new hire add new hire to practice specific meetings month schedule accessibility orientation meeting with new hire and vsa accessibility specialists product manager tasks a product manager will generally be working with the new hire on their second week after they ve spent the first week completing paperwork and getting onboarded with their practice week reach out to new hire over slack to say hello add new hire to the team’s dsva slack channels conduct intro meeting with new hire add new hire to product team meetings create any supporting tickets to onboard new hire to the team you can check this box if your team s onboarding does not require additional documented steps ,1 16525273114.0,2021-05-26 19:13:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,set correct duration for addtocalendar on covid confirmation page we re defaulting the duration to minutes we should be able to get the actual value from clinic data or from calculating the duration from the slot start and end dates should check both versions of the confirmation page ,1 23517600998.0,2022-08-18 23:51:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,generate tech debt opportunities background given we have an opportunity to pay down tech debt i want to generate problem statements opportunities before digging into solutions so we have a better sense of what success looks like after we ve resolved some of that debt tasks generate tech debt problem statements opportunity areas for public websites document those here or in the appropriate repo folder we can chat about where makes sense acceptance criteria the pw team has a better sense of tech debt that can be paid down ,1 19350680767.0,2021-12-15 15:21:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, your page doesn t follow heading hierarchy headings aren t properly nested and headings and or labels aren t relevant to the page general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers noah gelman noahgelman accessibility platform issue your page doesn t follow heading hierarchy headings aren t properly nested and headings and or labels aren t relevant to the page issue details heading elements are not in a sequentially descending order ‘what can you do ” should be an sarah koomson link screenshot or steps to recreate va gov experience standard other references wcag sc a wcag sc aa platform recommendation for introductory purposes your current copay balances should serve as we cant access your current copay balances right now and what you can do should serve as s vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 26513889537.0,2023-01-18 19:13:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, cards mini summary add midpoint review updates issue description midpoint review feedback from design ia and content tasks design update how card is styled to back button chevrons should be primary blue we have recently updated the multiple responses guidelines use the actionlink for adding another item instead of a question put the list of values in the same order as previous list and add “value” to all items content step of household assets your other assets select any other item of value called assets you own not including heirlooms clarify to the user what constitutes an heirloom i recommend clarifying to the user what constitutes and heirloom or simply don t use the word heirloom and instead use the definition of heirloom the same verbiage should apply to the entire list the items in the list are all somewhat subjective i recommend using a threshold for instance you could say anything valued at over or something similar step of household assets you have added these assets precious metals and coins value is the first entry for added items the next added item simply says antiques this is incongruent formatting i recommend using the same formatting and verbiage for each asset entry i recommend removing value from precious metals and coins value and changing the verbiage from how much is each of your assets worth to what is the value of each of your assets acceptance criteria what will be created or happen as a result of this story ,1 14960393665.0,2021-01-27 05:40:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research and upload all staff profiles for visn leadership health services program etc story as a vamc team member i need to have all staff profiles ready and loaded in drupal so i can quickly complete creation and data load in one visit goal assure one and done data load to visn pages upon creation resources tools documentation tasks staff profiles for the the following health service programs leadership page caregiver support homeless veteran care lgbt veteran care mental health care minority veteran care patient advocates returning service member care suicide prevention women veteran care include photos if available for individual caregivers attention there may be duplicates caregivers will support more than one health service program note where duplicated acceptance criteria all staff profiles have been documented for analytics for creation of health service pages ,1 22591798402.0,2022-06-28 20:42:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update documentation within product intro doc issue description ensure our development documentation is cleaned up accurate and in github i’d like to see all product documentation linked on this so we can use this as a way to find architectural diagrams implementation notes decisions etc tasks update documentation in linked product intro acceptance criteria we have a source of truth for our product documentation and architecture how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16482989079.0,2021-05-24 14:12:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos new appointment components vafacilitypage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 23114642895.0,2022-07-27 15:36:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,authenticate and test integration with vha sharepoint issue description brian and the vha sharepoint team will be adding our app to be an authenticated service to post pdfs to their folder repository once we have these credentials in hand we need to test this connection is working as intended tasks receive authentication credentials from vha test connection to sharepoint with credentials acceptance criteria we can verify a secure connection with vha sharepoint via api how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25568883617.0,2022-11-30 16:10:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined fsr product outline high level user story ies as a veteran who has parallel debt from both vba and vha i would like to submit all my debt in the same fsr so i can send one fsr to request help for all my debt hypothesis or bet if we allow veterans to send one fsr for both vba and vha debt then we expect veterans to take actions to request help for more debt and faster debt resolution time due to less submissions needed to resolve these debt okr veterans can submit one fsr for both vba and vha debt faster debt resolution times due to less submissions needed to resolve these debt definition of done what must be true in order for you to consider this epic complete take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations console services tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 26942533287.0,2023-02-08 04:17:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, notice of rights and responsibilities content assistance from the debt resolution team what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with during a round of design feedback with our sme s we received feedback to provide a way for veterans to access their notice of rights and responsibilities within the tool i ve since incorporated that content into a modal that opens up if the veteran clicks on the link notice of rights and responsibilities on the balance s details page uxpin attached below however i noticed that most of the content can be found elsewhere in our tool i m looking for help on how the notice of rights and responsibilities transition from paper format to the site has been handled in the past it seems like we could display a condensed version containing the content not found elsewhere in our tool but i don t know how this topic has been approached with stakeholders for other projects supporting artifacts please provide supporting artifacts as available link to product outline link to or attach user flows link to prototype or mockups link to any epics issues that may be helpful will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date end of september estimated staging review date tbd content and ia work needed by do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name octo de product owner product manager designer fe engineer product team slack channel next steps once you’ve submitted this ticket please post a link to this issue in the  slack channel and tag rlhecht if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 24985047901.0,2022-11-02 14:31:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design discovery changing contact info on veteran s profile issue description allowing veterans to update their contact information as part of their va profile instead of just for the fsr submission that does not persist background as part of the design team questioned why the experience does not transfer to the veteran s profile currently on fsr any reason not to change personal information section to something like this tasks investigate feasibility of implementing the ability for the veteran to change their contact info on the portal acceptance criteria identify and document a path forward for implementation first step connect with supplemental claims team how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23392943394.0,2022-08-11 19:45:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add react testing library tests for servicetypeahead add tests using to cover the following scenarios showerror false no error message displayed showerror true error message displayed inputvalue renders search for an available service message div inputvalue and no matching services renders we couldn t find that please try another service message div inputvalue and matching services no prompt rendered only matching services select service confirm specialty name is shown,1 14960072943.0,2021-01-27 04:52:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add new design and suicide prevention alert to existing visn pages issue description the display of information on the is duplicative poorly formatted and inconsistent with the design system the crisis hotline number is displayed three separate ways erie has added an image for the crisis line we need to standardize this national content for ease and risk mitigation page screenshot most content is nationalized with the exception of some facilities which add local content for behavioral health or community care under ongoing support example from erie tasks delete content and replace with react widget for how do i talk to someone right now va cheyenne health care va eastern colorado health care va western colorado health care va montana health care va eastern oklahoma health care va oklahoma city health care va salt lake city health care va sheridan health care acceptance criteria add alert for how do i speak to someone now pittsburgh visn pages will be cloned and will have source content added ,1 28351807240.0,2023-04-12 03:22:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint march apr sprint goals finalize fsr enhancement front end development team qa for enhancement release progress medical copay notification backend requirements based on discovery add research plan and conversation guide for usability study to research repo define initial wireframes for streamlined waiver planned issues fsr enhancements styling and text updates for fsr design expanding group deprecation fe research approval process from platform pts research updates to resolution options to repeat amount of debt pts design remove combined fsr enhancements feature flag fe design ux qa for staging design research qa uxpin prototype design research employment history summary card update pts fe employment history navigation fixes fe installment contract enhancements fe add signature date to fsr pdf fe other living expenses enhancement fe mcp notification send one fsr submission email per unique request pts be test mpi request payloads in staging pts be streamlined waiver wireframe user flows for streamlined waiver design blocked issues none go team unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 13764849598.0,2020-10-07 12:39:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr personal data section as a veteran filling out the fsr form i want my personal data prefilled as an authenticated user if the data is incorrect i would like the ability to change my contact data i also want guidance around when if i should include spouse and children in the event i am separated am co habituating and have step children ,1 13493540288.0,2020-09-11 19:50:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, mvi errors logged to pii friendly table issue description we need more info on why mvi add person is occasionally failing it may be part of the orchestrated lookup deeper search beyond the local mpi database since we cannot log the body of the response contains pii we need to use something other than sentry to log the pii table in our postgres database acceptance criteria production level logging to the pii friendly table so we can see the mpi error response body how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23214525090.0,2022-08-02 13:06:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, trailers campers and boats page redesign issue description to simplify the form a little and only capture necessary data we need to remove existing list loop for adding trailers campers and boats and replace with single radio button and total estimated value of all trailers campers and boats updated total value page tasks remove unnecessary list loop add new radio button and numeric input pages to replace update cypress tests as necessary acceptance criteria household assets trailers campers and boats page matches design and is functional how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23597440075.0,2022-08-23 20:44:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,form system file upload issues description when uploading a password protected pdf file the form system filefield is used to display the password input and add password button if an incorrect password is entered an upload a new file and cancel button are added below the add password button the screenshots are from the notice of disagreement form but it may apply to all uploads the following issues need to be fixed all elements should be replaced by the the add password button is a styled green button but the green button was recently deprecated so we ll need to img width alt notice of disagreement card showing a pdf that requires a password a password input is shown with a green add password button below and a delete file secondary button below that button src when an incorrect password is provided and the add password button is used the delete file button is replaced by an upload a new file primary button and a cancel secondary button the cancel button should have a white background possibly fixed by switching to va button img width alt notice of disagreement upload card showing an error due to an incorrect password for a locked pdf being entered there is a green add password button below and now a upload a new file primary button next to a cancel secondary button in a row below the add password button src the required label needs to be fixed remove the extra wrapping parentheses and extra asterisk tasks use everywhere change add password to a secondary style fix cancel button style fix required label add tests as needed definition of done all tasks complete all tests passing,1 28040101785.0,2023-03-28 17:49:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,co design feedback sessions synthesis and concise report issue description the co design feedback sessions on the fsr form prototype will be completed as a follow up step we have been and will continue to review and synthesize the feedback noting which areas were unclear for veterans and which ones were delightful combined with the heuristic evaluation feedback we will create a concise report to share what area s of the fsr prototype need further clarity tasks what work is necessary for this story to be completed the review and synthesis process creation of a concise report to share elicit discussion and decision making acceptance criteria what will be created or happen as a result of this story the review and synthesis process ,1 29579541549.0,2023-06-07 03:53:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint may june sprint goals complete any remaining high priority fsr enhancement front end development team qa for enhancement release complete usability research study with veterans complete majority of medical copay notification development goal of launching on streamlined waiver fe discovery planned issues fsr enhancements design ux qa for staging design research use cases for testing needs estimate resolution option content update fe mini summary update page content pt fe review and submit page audit fe remove combined fsr enhancements feature flag aka updating alert cards fe platform content feedback updates for fsr pts design fe usability study sessions pts design research update installment contract page order fe refactor the fsr endpoints and logic to be moved into the debts api module be testing automated testing with axe by deque fe testing wave spot checks code quality review pts fe investigate and clean up sentry errors pt fe add item summary page navigation bug pt fe mcp notifications build request body for mpi find profile by vista be generate service method find profile by vista pts be build mpi response from profile fetch with vista pt be add class function to vaprofile contactinformation service pts be create sidekiq jobs to send va notify emails pts be parse new statement file to get email addresses for existing veteran profiles be authenticate vbs api using apikey header pts be add new statement notification template to va notify pts be update va notify api keys be generate and issue api key to vbs be streamlined waiver streamlined waiver discovery research framing design product outline for streamlined waiver pt design streamlined waiver discovery fe transparency discovery mockups for streamlined waiver design ongoing maintenance bug fixes debt resolution team onboarding thomas davis medallia satisfaction survey data review pts reasearch on hold this sprint due to user research blocked issues conditionally disable month year in employment history pts fe unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint employment date component pts design subtitle update for fsr form design form restart flag bug pt fe points planned points accomplished tbd points over issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 27013105844.0,2023-02-10 16:55:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move marital status and dependent children questions issue description during the design intent for adding copays to the fsr it was brought up that certain questions should be moved in the order of the fsr form this is something that we will revisit as we dig into the streamlined waiver work i am creating this ticket as a reminder to address this as we embark on the streamlined waiver work original ticket tasks consider order of fsr form questions in design move marital status and dependent children questions to the first step in the fsr of veteran information acceptance criteria questions have been ordered appropriately to optimize user clarity across the experience how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25567818004.0,2022-11-30 15:28:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint november sprint goals • align with design intent team on the direction for card design on mini summary and va benefit pages • midpoint review for fsr enhancement release • merge streamlined waiver personas with scenario paths • define wireframe for one streamlined waiver path • submit platform request to configure redirects for legacy mcp and debt letter pages • finalize fe dev for employment history • text placement and screen adjustments in fsr • enhancements for veteran contact information • address compromise amounts not seen on dmc endpoint • resolution option explainer enhancement sprint deliverables list of deliverables completed during sprint user flow for streamlined waiver experience draft of initial wireframes streamlined waiver midpoint review planned issues combined fsr refactor the fsr endpoints and logic to be moved into the debts api module be pts fsr enhancements content changes part fe pts list loop improvement for summary and va benefits design pts fsr review page updates design pts update template names for dmc notifications be pt veteran information required text placement screen adjustments fe pt enhancement continuous add employment history fe pts card discussion with design system team design pt veteran contact information enhancement fe pts resolution option explainer enhancement fe pts streamlined waiver wireframes for user path persona design pts create personas for user flow paths design pts unplanned additions will be added throughout the sprint as identified capacity planning pto holiday s denise scott brandyn andrew megan brie nov thanksgiving day points planned points accomplished points over issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 19908137960.0,2022-01-25 14:45:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, html statement on this page component issue description add on this page component to the html statement page refer to the for details tasks add component to the html statement page acceptance criteria the component should render on the html statement page how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 30217468190.0,2023-07-05 16:36:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,efsr sentry error bugfix this ticket addresses a the undefined reading includes bug that is preventing submissions when expense name is undefined which is blocking form submission for some users this is the error message uncaught typeerror cannot read properties of undefined reading includes at request debt help form entry js at array find at object transform request debt help form entry js at object submitform request debt help form entry js at request debt help form entry js at request debt help form entry js at boundactioncreators request debt help form entry js at request debt help form entry js at htmlunknownelement callcallback request debt help form entry js at object invokeguardedcallbackdev request debt help form entry js the error is on line in the transform js ,1 23877151689.0,2022-09-07 20:15:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, evaluate analytics events for va additional info description the va additional info web components were recently added to replace the react component the web component has analytics built in but form included many unique events so the vaadditionalinfo react binding was used to continue using the possibly unique events now we need to evaluate if these analytic events are indeed unique if no additional event data is missing compared to the built in analytics then the react binding can be removed and the va additional info web component may be used instead tasks evaluate all vaadditionalinfo react bindings in form and switch to va additional info web component if the analytics are the same manually check window datalayer for changes definition of done all tasks complete all tests passing,1 15024037893.0,2021-02-01 19:03:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove featureflip from technical task since we are now finished staggering the release of the with great success we should remove the unneeded feature flip to increase ease of workflow and decrease code complexity expected behavior when starting the application for the first time you should no longer have to toggle the before accessing it acceptance criteria feature flip used to turn form on off is removed ,1 23894564507.0,2022-09-08 13:56:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,streamlined waiver sme questions issue description compile list of questions for smes tasks draft send meeting invite or email to smes acceptance criteria questions emailed or meeting scheduled,1 22105396822.0,2022-06-01 16:36:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,incorrect apo attribution from va gov current behavior currently the pittsburgh regional office is currently receiving claims as part of our foreign workload for veterans claimants that reside within the united states but have a n apo dpo or fpo erroneously listed as their city veterans claimants residing outside of the united states seeking veterans affairs va benefits are considered “foreign” claims some veterans claimants list a n air army post office apo fleet post office fpo or diplomatic post office dpo as their address apo dpo and fpo addresses are considered foreign claims it appears that veterans claimants that reside within the united states are having a n apo dpo or fpo erroneously listed as their city ,0 24415051808.0,2022-10-05 15:13:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update medical copay wizard path issue description update medical copay path in the wizard in discussion with sitewide content we will update wizard to open path for medical copays tasks update intro description at the top of the wizard update the path for the medical copays section of the wizard acceptance criteria updates have been made an in staging for content team to review how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23114229511.0,2022-07-27 15:18:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,generate and submit mock fsr requests to vbs staging issue description as part of end to end testing with the huron servers we need to submit a handful of various fsr requests to post to the vbs staging endpoint tasks create reusable method to generate fsr request submit fsr payloads to vbs staging acceptance criteria vbs has received multiple fsr payloads how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11727610636.0,2020-03-10 16:12:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,project kickoff debt letters mvp steps to complete project kickoff product manager create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in vfs platform support in slack tag megan kelley andreahewitt andrea and megan will schedule meeting with vsp reviewers and requesting team attendees as listed below vsp requesting team kickoff meeting completed all requesting team attendees complete brief survey artifacts please bring the following to the kickoff meeting link to rough draft of product outline you do not need to prepare a presentation meeting attendees from requesting team product manager required leah keeler depo product lead required matt self entire vfs team recommended amen ra mahariel rosario riley orr becca walsh cameron testerman scheduling preferred dates or times week of ,1 27391461930.0,2023-02-28 16:31:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dependents page enhancements issue description remove existing dependents list loop and implement new input number of functionality tasks update dependents page with fsr enhancements acceptance criteria new dependents page s are functioning as anticipate and match mockup how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14530735807.0,2020-12-14 19:42:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr list loop type options issue description we ve compiled a list of options that will filter as veterans type to make adding multiple assets and financial information quicker we need these lists added to their corresponding list loop input fields outlined here tbd of what this will look like in the form tasks incorporate the outlined list loop options to their corresponding input fields ensure the options filter as users type allow users to still add custom string inputs acceptance criteria the list loop options have been incorporated into the fsr s ui the list loops have been tested to make sure filtering works and users can still add custom inputs ,1 14982889602.0,2021-01-28 16:31:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the status and next steps in the debt cards issue description use the content from debt portal to update the statuses being displayed in the debt cards on fsr before after tasks update cards confirm with designers by sending a screenshot acceptance criteria cards updated designers approved ,1 25412536628.0,2022-11-22 20:21:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add specs for statsd config description so far we haven t added rspecs for statsd configuration usage we should add those to prevent issues like related documentation tasks add rspecs for statsd acceptance criteria validated reviewed and merged to master ,1 14381312217.0,2020-12-02 05:05:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review of the policies page for visn user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation tasks complete review of policies top tasks call to action across all visn systems listed below and document and report any issues that may need to be fixed use the following guidance does this content field data in this page make sense does the content field data in this page relate to this system level or specific to a facility is it in the right place based on system facility pages for the veteran to find how does this help with the focus of the page confirm the altoona va butler va coatesville va erie va lebanon va philadelphia va wilkes barre va wilmington va acceptance criteria all top task node pages have been reviewed in spreadsheet and issues found have been been documented issues have been documented and escalated for resolution using vamc support channel and spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 14010957765.0,2020-10-29 06:23:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review at all wilkes barre va system pages to validate mvp and consistency user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation prod cms va gov tasks complete review of system and facility pages for the following content and flow asking these questions does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page confirm all of the facilities are reviewed wilkes barre va medical center allentown va clinic columbia county va clinic northampton county va clinic sayre va clinic tobyhanna va clinic wayne county va clinic williamsport va clinic document all errors items that need update and testing on each page using spreadsheet listed above acceptance criteria all node pages have been reviewed in spreadsheet and issues found have been been documented issues have been escalated for resolution using spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 15084707659.0,2021-02-05 17:33:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, chapter remove feature toggle code description now that view payments has been in production for a while it makes sense to remove the feature toggle code we have in place we do this because the feature toggle has served its purpose and the code is no longer needed in the code base considerations the chapter feature toggle renders code on va gov careers employment education and career counseling screenshot of rendered widget chapter feature toggle renders code on screenshot of rendered widget on dependents benefits page tasks remove all feature toggle checks from the remove entry from remove feature toggle check from run through app and unit tests to make sure nothing relies on feature toggles definition of done feature toggle removed in vets api feature toggle removed in vets website prs submitted ,1 18107030337.0,2021-09-22 20:20:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,vet center css clean up rationale keeps code clean easier to find vet center specific style info tasks separate vet center and vamc specific styles into different files same folder remove warning from css linter ,1 24987419699.0,2022-11-02 16:01:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review page design issue description review page research tasks review past research on review pages acceptance criteria what will be created or happen as a result of this story ,1 30797117163.0,2023-07-31 20:50:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, pilot session issue description complete pilot session tasks schedule pilot session run pilot study take notes debrief make any updated to conversation guide note taking docs if needed acceptance criteria pilot session scheduled pilot session completed with notes conversation guide notetaking docs updated if needed ,1 17147783161.0,2021-07-13 16:25:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content review request for debt alert issue description veterans are mistakenly receiving notifications about owing debts represented as chapter tuition fees yellow ribbon – school liable in the dmc s deduction code spreadsheet while the dmc troubleshoots why veterans are receiving these notifications our stakeholders requested we put up an alert in the debt portal with the following content if you are a student who received a letter regarding a tuition debt please note that a deduction code identifies a debt assigned to your educational institution please communicate with your educational institution prior to making payment on their behalf in order to avoid potential duplicate billing prior to putting this content on the site we wanted to get it reviewed to ensure we re following plain language guidelines the alert s design our proposal is to use the experimental design system s minimalist alert due to the existing coronavirus alert and that this is a use case that doesn t impact all users tasks vsa content writer has provided feedback on the alert s content if there are changes the updated content is sent to dmc stakeholders for approval uxpin is updated with the finalized content acceptance criteria the uxpin is updated with the finalized content is updated with the uxpin and finalized content ,1 25568429359.0,2022-11-30 15:52:15,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,front end documentation pop wrap up issue description ptems pop is ending on december final documentation and wrap up tasks backend documentation acceptance criteria add documentation comments and information to this link tbd how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 18246532669.0,2021-10-01 19:13:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,review debt resolution team tools for instances of sighted language issue description the sitewide content team is moving away from using sighted language such as the word view on va gov tasks review the following products staging environments for sighted language medical device re ordering tool debt management portal financial status report medical copay tool document changes for each tool acceptance criteria areas including sighted language in each tool have been documented and attached to this ticket tickets are created for frontend changes as needed tickets are created for the sitewide content team as needed ,1 26757558294.0,2023-01-31 02:21:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, spouse information sections desired behavior implement new design list loop removed acceptance criteria list loop removed and new designs implemented how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 19532748621.0,2021-12-30 20:32:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace external imports in our applications background our application on vfs has very long build times with lots of flakey unit tests that fail in builds often this is mostly due to the fact that when a build is run all of the apps have to built at the same time to combat this the vsp team has undertaken an initiative to break the apps up and isolate them so that each app can be built independently to do our part we need to get our apps ready for this new build process to do this we need to ensure that our apps aren t importing files from other applications considerations note imported from refers to other applications importing this apps files imported to refers to applications that are importing files from other applications apps we own src applications personalization rated disabilites imported from src applications personalization view dependents importing to dependency verification src applications static pages dependency verification imported from view dependents src applications vre importing to src applications vre importing to tasks ensure that all external imports are addressed acceptance criteria all external imports from our applications are addressed a pr is in place for review,1 15303958380.0,2021-02-24 16:22:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,put all server errors into vaos server error not authorized bucket we have errors mixed into our different error buckets which makes it harder to understand the actual errors happening we should be able to do this in the captureerror helper but if not then we d need to search for uses of captureerror that use a custom error message and check for a request status code before making that call for example there are errors in this group but they should actually all be in ,1 14531275395.0,2020-12-14 20:31:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor feature toggle selectors our feature toggle selector names are not particularly understandable we should come up with a pattern of naming those selectors and what we name the variables that use them that s easier for everyone to understand narin brought this up in a pr we may want to split this into updating selectors easier and then updating uses of those selectors harder ,1 26634331044.0,2023-01-24 20:30:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, midpoint review frontend updates issue description midpoint review recommended several updates to the efsr cards mini summary add item action link tasks design update how card is styled to card styles explorations we have recently updated the multiple responses guidelines use the actionlink for adding another item instead of a question content step of household assets your other assets select any other item of value called assets you own not including heirlooms clarify to the user what constitutes an heirloom i recommend clarifying to the user what constitutes and heirloom or simply don t use the word heirloom and instead use the definition of heirloom the same verbiage should apply to the entire list the items in the list are all somewhat subjective i recommend using a threshold for instance you could say anything valued at over or something similar updated to select any other items of value called assets you own not including items passed down in your family for generations i recommend using the same formatting and verbiage for each asset entry i recommend removing value from precious metals and coins value and changing the verbiage from how much is each of your assets worth to what is the value of each of your assets acceptance criteria frontend updates made ,1 24051918760.0,2022-09-16 13:32:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, create tests for copay resolution options desired behavior tests for copay resolution options should be created and passing for maximal and minimal acceptance criteria tests passing for maximal and minimal how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 15614881515.0,2021-03-19 18:24:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor fl actions index js issue description the facility locator code src applications facility locator is in need of some refactoring this issue focuses on actions index js tasks break up actions index js into functional groups such as searchactions mapactions geolocationactions acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21641238825.0,2022-05-05 19:01:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, pages require sensory characteristics to be understood or operable general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers josh kim joshkimux accessibility platform issue pages require sensory characteristics to be understood or operable issue details no alternative is provided to screen reader users to inform them that content is important which is demonstrated to sighted users through the icon link screenshot or steps to recreate va gov experience standard other references wcag sc a platform recommendation following va design system guidance we recommend including a sr only span to provide an alternative to this icon font for example alert for more details check out this ticket that resolved a similar issue on alt icon text vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 24255222052.0,2022-09-27 17:10:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove research support in vfs facing di and mpr guidance user story as a vfs team member i want to know what practice area feedback i ll receive at design intent and midpoint review so that i am able to better prepare for those touchpoints and manage my teams expectations assignee peer reviewer briandeconinck description due to clayton zook s departure on wednesday governance team is no longer able to provide research focused feedback at the design intent or the midpoint review because of this we need to update our vfs facing guidance on platform website so that vfs teams are not expecting to receive feedback in addition because clayton is no longer involved in the research review octo de is once again the owner of the research review touchpoint this ticket will also ensure that vfs facing guidance is updated to show that governance team is not involved in the research review touchpoint impacted artifacts touchpoints page image from tasks review platform website collaboration cycle and identify all the areas where we specify that research feedback is provided at di and mpr note research review is still part of the collab cycle so references to research support are ok it just needs to be removed at specific touchpoints link all impacted pages above in the impacted artifacts section ensure all references to research support are removed from design intent guidance ensure all references to research support are removed from midpoint review guidance note if changes are made to either the di or mpr script the script needs to be modified on platform website and in the moderator responsibilities docs peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs teams do not expect to receive research feedback at design intent and or midpoint review vfs teams understand that octo de not governance team is the owner of the research review touchpoint how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 24285131489.0,2022-09-28 21:14:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor cypress test to remove deprecated cy setup and cy route commands description refactor cypress test to remove deprecated cy setup and cy route commands these commands have been deprecated since in a future release support for cy server and cy route will be removed acceptance criteria all stubbed endpoints should use cy intercept design assets n a definition of done all acceptance criteria are met documentation is updated how to configure this issue attached to an epic what body of work is this a part of labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14966647251.0,2021-01-27 14:49:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update installment contracts and other debts section to use inputs instead of radio selections issue description dmc has asked that we reintroduce text inputs for the date of debt and amount overdue questions on the installment contracts and other debts section of the form tasks incorporate new inputs into the fe according to confirm with screenshot to designers acceptance criteria ui updated confirmed with screenshot to designers,1 23854422890.0,2022-09-06 21:21:06,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, itemize other living expenses provided by veterans what happened other living expenses are currently lumped together with a singular total the cowc staff who process the forms need to review those expenses individually and determine if the expense amount is reasonable if they are all clumped together as one total they are unable to determine if the veteran s submission is reasonable stakeholder is requesting that the expenses be separated so that each expense has an associated amount desired behavior use fsr field to capture one living expense with one associated amount all other amounts need to be moved to the additional information section at the end of the form acceptance criteria describe the desired working behavior how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 13893857262.0,2020-10-19 14:01:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert calendar class components to function components we have a lot of class components mostly page components that could be converted to function components and use hooks for whatever stateful behavior is needed datetimerequestpage calendarrow calendarwidget datetimeselectpage,1 30694515762.0,2023-07-26 17:30:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design intent ia feedback debt resolution streamlined waiver ia feedback from design intent session held on friday april for streamlined waiver thoughts questions very impressive user flows i cannot understate how helpful it is to see the branching logic described with user scenarios tasks and request content help specifically i would encourage you to ask for focused help on these branch pages clarity there will be key to ensuring successful outcomes acceptance criteria comment on this ticket if the platform reviewer has any thoughts questions that require responses not applicable based on feedback when must feedback has been incorporated as appropriate link to any other github issues or prs related to this feedback not applicable based on feedback when should consider feedback has been incorporated or if any feedback will not be addressed as appropriate link to any other github issues or prs related to this feedback close the ticket when all feedback has been addressed feedback practice areas will document their feedback on the vfs provided artifacts following the must should and consider framework platform reviewers may also provide additional notes that don’t comment on the artifacts themselves but are important for implementation eg engineering coding notes should i really commend your huge effort here this is a complex form and you are introducing a lot of very technically difficult branching logic knowing that all of these new branch paths are deviations from the current state i think you should submit a ticket to work with sitewide caia and request content help specifically i would encourage you to ask for focused help on these branch pages clarity there will be key to ensuring successful outcomes if you do any user testing down the road i would encourage you to include tasks that specifically measure look at whether there is any hesitation or confusion on those branching pages one last thing a plug to connect with the forms digitization team po is humancompanion usds they have introduced a lot of really nice personalized language in step chapter headings example your information instead of veteran information are working on some updated error messaging with help from sitewide caia and have improved plain language in alert messaging those things are not necessarily living in the forms library yet but would be good to have on your radar ,1 24583370439.0,2022-10-13 17:26:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,updating urls that link to vha fsr issue description there combined debt portal is complex and has many different routes to the electronic fsr experience we have discovered pathways that aren t routing to the onlinefsr waiver submission process tasks validate that following pathways to the electronic fsr from copay cards and detailed pages img width alt image src acceptance criteria update link from the copay details card to the online fsr experience how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14002142980.0,2020-10-28 14:27:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, figure out how to get va benefits pre deduction amount issue description va benefits such as compensation and pension amounts can be discovered using the paymenthistory endpoint however the amounts reflected in payment history are the amounts that are actually deposited in a veteran s bank account and do not reflect the amounts the veteran is actually entitled to before deductions are removed tasks discover the endpoint s libraries etc that will enable a developer to pull in the pre deduction va benefits amount acceptance criteria endpoint is known that exposes the pre deduction va benefits amount ,1 15833564331.0,2021-04-06 15:46:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ga implementation for form submission issue description since form submission data was recently implemented we need to add ga tags to submission events changes outlined tasks there s a typo within the datalayer for reason for alert with an extra e in related add the following submission events to fsr submission successful submission failed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12440654759.0,2020-05-26 12:23:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,guard is not running due to threadsafety rubocop running make guard results in this error when a file is changed error unrecognized cop threadsafety classandmoduleattributes found in rubocop todo yml unrecognized cop threadsafety instancevariableinclassmethod found in rubocop todo yml unrecognized cop threadsafety newthread found in rubocop todo yml error the following exception occurred while running guard rubocop usr local bundle gems json lib json common rb in parse unexpected token at json parsererror we should restore guard to a working state,1 31162864817.0,2023-08-16 17:18:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add dollar sign to spouse benefits on review page issue description are missing symbol in review mode from removing recreational vehicles from this ticket since it is addressed add sign to recreational vehicles and real estate as well since they still need it tasks add dollar sign to spouse benefits review page portion add dollar sign to recreational vehicles review page portion add dollar sign to real estate review page portion acceptance criteria spouse benefits dollar amount correctly displayed with dollar sign recreational vehicles dollar amount correctly displayed with dollar sign real estate dollar amount correctly displayed with dollar sign how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11780802376.0,2020-03-16 20:53:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create schemas for direct schedule appointments and appointment requests the front end needs a schema for the data to be sent to the backend when creating an appointment request and when booking an appointment directly there are examples of payload in the team repo these examples contain duplicate info and data that looks unnecessary so a lot of the work here is going to be finding what data is actually used ,1 21335047528.0,2022-04-18 13:38:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content spot check for redesigned status cards issue description we consolidated designs for the status cards in debt portal to mimic the cards created for mcp we also incorporated payment plan information into these new cards the cards have been reviewed by the dmc team for accuracy we d like a content spot check to ensure that the content meets plain language standards please reach out to riley if reviewing in a spreadsheet format would ease the review process tasks review the status cards in the provided uxpin prototype for plain language compliance comment on any status cards that need adjusted content acceptance criteria the status cards have been reviewed tag riley on this ticket as a comment if any adjustments need to be made ,1 20158656800.0,2022-02-09 18:59:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analytics kpi dashboard request for debt resolution fsr form request a kpi dashboard what this form is for use this template to request a kpi dashboard on domo for your product instructions for the vfs team for additional info read through the your kpis are clearly linked back to veteran outcomes link your kpis below kpis should be in your product outline add your team label to follow progress is this a new kpi dashboard request or is this an iteration please check the corrrect response new dashboard iteration of current dashboard i would like the dashboards for debt portal and fsr combined into a single view vfs information kpis i would like the data laid out in the following format in domo broken out by devices of veterans landing page logged in page of veterans completing abandoning fsr online form where the veteran abandoned time to complete fsr form time veterans spend on each page how many veterans land on debt portal that click through to fsr referring page ie google etc a separate card if referral is email as part of vanofity email send they can append url please leave the following blank vsp analytics insights acceptance criteria groom analytics groom analytics for technical feasibility document data sources for each metric document unavailable vs available metrics if any add implementation issue for additional necessary implementation draft pst dashboard draft dashboard on domo structure data for etl pipe available metrics to domo add appropriate team members to dashboard please see definition of done kpis have been groomed and connected to domo dashboard has been shared back with the vfs team kpi dashboard full qa checklist completed ,1 21525248185.0,2022-04-28 17:44:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ia support from claims appeals what does your team need support for check all that apply launching one or more new unauthenticated static va gov pages making revisions to one or more existing unauthenticated static va gov page launching a new online form app or tool on va gov making revisions to an existing online form app or tool on va gov something else please add details in the next question what do you need help with content support ia support when viewing the an additional services block includes a link to we need to remove the e benefits link and replace it with a new link or links img width alt claim status tool additional info block with link to e benefits src the sentence to update your personal information get help filing claims or appeals or view your uploaded documents go to ebenefits will send the veteran to three different pages on va gov please confirm the destinations update your profile profile personal information get help filing claims or appeals disability get help filing claim view your uploaded documents in the claim status tool you can only see uploaded documents for a specific claim in the status tab as an event or in the supporting artifacts please provide supporting artifacts as available link to product outline link to or attach user flows link to prototype or mockups link to any epics issues that may be helpful will this work be going through the collaboration cycle yes no when does this work need to be done estimated launch date estimated staging review date content and ia work needed by no set date do you plan to bring this to an upcoming content office hours session yes benefit content office hours thursdays p m to p m et yes health content office hours thursdays a m to a m et yes unauth office hours mondays a m to a m et no but i d like to schedule time to talk about this request no let s work asynchronously and meet if needed note if we think this work would benefit from a collaborative session with you we may ask you to bring it to office hours or set up a separate time to meet about your team team name claims appeals octo de product owner matt self product manager tbd in transition designer tbd in transition fe engineer mottie product team slack channel vsa claims appeals next steps once you’ve submitted this ticket please post a link to this issue in the  slack channel and tag beth potts if you also need engineering support from the public websites team fill out their if you need a page url redirected a url changed or a vanity url set up please submit a ,1 22154921277.0,2022-06-03 21:15:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,coe update introduction page updates value statement as a frontend engineer i want to use the most up to date components so that i can ensure consistency in quality and design of component across the app background context the logged in is not using the also additional margins should be added below the first request a certificate of eligibility action link extra margins below the process list should be removed so that the bottom action link doesn t have so much space above it tasks switch to use va process list adjust margins above and below the va process list as appropriate compare changes with design if it can be found definition of done all tasks complete all tests passing,1 23987032989.0,2022-09-13 20:04:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor cypress test to remove deprecated cy setup and cy route commands description refactor cypress test to remove deprecated cy setup and cy route commands these commands have been deprecated since in a future release support for cy server and cy route will be removed acceptance criteria background the toggle toggle is on all stubbed endpoints should use cy intercept design assets n a definition of done all acceptance criteria are met documentation is updated how to configure this issue attached to an epic what body of work is this a part of labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14175647499.0,2020-11-12 21:58:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add mocks for metadata in carma models submission spec description mock calls to metadata in spec lib carma models submission spec rb to avoid double testing metadata and causing unit tests for submission to execute metadata source code ,1 24553144929.0,2022-10-12 14:01:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,other income populating for veteran spouse issue description we ve noticed instances of the income populating for both a veteran and a spouse when it should just be for the veteran this seems to only happen with manually inputted data and has happened when the veteran doesn t have a spouse tasks determine cause for duplication only show income for veteran acceptance criteria we have removed duplicate value from spouse column how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23392819737.0,2022-08-11 19:38:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove the addpager call in health care region js for full builds description in full builds the pageditems object used for pagination is computed in the addpager function in the logic for generating pagination has been moved into a liquid filter liquid filters paginatepages it is being used by the events listing drupal liquid template if all templates that need pageditems followed this pattern we could delete the addpager code and its dependencies e g paginatepages this would accomplish the following pave the way for supporting pagination in preview mode help support accellerated small batch publishing eliminate a large chunk of technical debt ,1 13303617026.0,2020-08-25 15:45:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, bdd can we prefill separation date from military history information issue description since we can pull military service history we could potentially pre fill the separation date acceptance criteria figure out whether this is possible and create dev ticket s how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 26568786895.0,2023-01-20 23:43:36,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, refactor and reduce hoc useage description we have hocs in the containers directory i think one isn t in use we should evaluate if all are needed and if we can consolidate the usage a bit the data persistence work also adds a component based wrapper where some of this functionality could reside tasks evaluate hocs refactor hocs create or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 14238552660.0,2020-11-18 18:48:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,error messaging for validated fields mapping map validated fields in fsr with error states acceptance agree on validated fields w design work with fe for error states 
 
,1 32010351813.0,2023-09-21 17:32:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,zero dollar monthly expenses issue description veteran services is noticing that there appear to be more automatically approved instances coming through where a veteran lists no monthly expense veteran services is concerned that there might be a glitch causing data to show as zero when veterans are submitting the requests tasks review the examples provided by veterans services transaction id s listed below and verify that veterans are indeed submitting the request with zero dollar expenses provide an answer to veteran services question do expenses play a role in the calculation on whether the veteran is pre approved or not example transaction ids acceptance criteria examples have been explored and feedback shared with denisecoveyduc to relay to veteran services how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22608269783.0,2022-06-29 14:56:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update existing debt letters widget for cdp and investigate staging only page issue description once static pages are complete we ll need widgets to navigate to the new combined debt portal manage debt and bills summary page tasks add widgets for cdp investigate loading drupal page only in staging acceptance criteria new widget has been added that directs to cdp summary page currently manage debt and bills summary how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12826221102.0,2020-07-06 16:11:13,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,write appointment cancellation integration tests write integration tests for requests on appointment list these tests should use rtl and following the existing integration test patterns ,1 29813767856.0,2023-06-16 17:13:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,user research usability study streamlined waiver issue description epic for streamlined waiver usability study,1 12216351670.0,2020-05-01 14:58:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,usability testing prep debt letters steps to complete usability testing prep product manager create this issue and fill in feature name in the title and other bolded information appropriately link to this issue once created in vfs platform support in slack tag megan kelley andreahewitt andrea and megan to schedule meeting with vsp reviewers and requesting team attendees as listed below at least days before scheduled meeting you must complete list of artifacts below vsp requesting team review meeting completed practice area reviewers create sub issues attached to this one with feedback for your team on feature name requesting team completes attached feedback tickets based on definition of done included in each practice area feedback ticket may differ for each practice area please refer to attached tickets for further instruction all requesting team attendees complete brief survey artifacts please provide the following artifacts at least days before scheduled meeting link to product outline link to or attach prototype or mockups link to or attach artifact with copy if separate from prototypes mockups link to research plan and script link to regression test plan if there isn t already a regression test plan for this feature in testrail for qa practice area review link to test cases test plan in testrail even if just a draft for qa practice area review meeting attendees from requesting team product manager required name depo product lead required name anyone else from your team who significantly contributed to the artifacts provided required names scheduling preferred dates or times additional notes during this collaboration point you will receive feedback from the following practice areas design accessibility content qa and optional information architecture ia product ,1 24121707678.0,2022-09-20 19:20:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design for other living expenses issue description itemized design for other living expenses see current state in the current fsr submission experience a veteran is able to select other and add a dollar amount without including an indication of what that amount is related to our stakeholders would like the veteran to include a description of the other expense that they are including on their fsr tasks discuss accessibility concerns with angela create preliminary designs acceptance criteria designs created ,1 22475531177.0,2022-06-22 11:58:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update debt letters cypress tests under cdp issue description cypress tests will need to be updated for the merged debt letters application to reference the new urls and page flow since it s being moved under the combined debt portal tasks update debt letters cypress tests under the combined debt portal acceptance criteria debt letters cypress tests under combined debt portal will be running and passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13257160708.0,2020-08-20 13:43:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters mvp pay gov link goes to what happened on staging your va debt page in how do i pay my va debt online section pay gov link went to note while the link worked fine this defect calls out the need to fix either the link text or link destination it d be prudent to verify through independent documentation whether the link should really navigate to or because financial transactions are involved veteran users should not have to just assume we sent them to the correct place to pay specs device browser test user if applicable vets gov user gmail com greg steps to reproduce go to sign in as vets gov user gmail com greg in how do i pay my va debt online section click pay gov link observe that the destination hostname is desired behavior see note in what happend section above either the link text or link destination should be fixed acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 18092375630.0,2021-09-22 04:12:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, user story as a vha digital media web manager the mobile clc and dom systems need to be archived removed from operation status and remove from menu locations so a new experience can be created for these products goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks remove all operating status listings of mobile clc doms archive moble clc dom facility pages disable menu selections for these facility types acceptance criteria all mobile clc dom facility types are archived and not visible these types are not deleted so they can be pulled back into new product type when ready ,1 17354481040.0,2021-07-29 12:55:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery on usage of va notify api technical task on the fsr veterans would like a confirmation email to know that their application has been submitted correctly and is being processed research integration vets api lib va notify for fsr expected behavior we know how to implement notifications on fsr using va notifty ,1 16016214514.0,2021-04-20 16:19:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,prepare vso presentation prepare vso presentation minutes in length intro of why we built this how we built this and demo ,1 11942031757.0,2020-04-02 19:31:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create use new bot user for ruby danger the problem ruby danger uses the va vfs bot in order to make comments on vets api pull requests this is a problem because va vfs bot is over privileged for the ruby danger use case more context the ruby danger doc outlines that we should not be using a user in our repo since our repo is an open source project work to be done create a new github user that does not belong to department of veterans affairs create an api key for this bot user to be able to make pr comments store login credentials for this user in credstash replace the usage of va vfs bot with ruby danger with the new bot user,1 13305679123.0,2020-08-25 18:56:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,content review of debt letters mvp empty states issue description i m looking for a content review on some empty states i m working on for the debt letters tool there are potential empty states that can occur the veteran would not have any debts nor any debt letters this is the base empty state for the tool we have a constraint where we will be unable to display resolved debts so we need an empty state for the debt summary section while we still provide access to the veteran s resolved letters dmc put debt collection on hold in march a veteran can still actively receive debt s but they won t receive any letters therefore we want to provide them information about why they have a debt but don t have any letters i m unsure about this content because it seems a little long and i bet there s a more eloquent way to phrase why the veteran isn t receiving debt collection letters i m debating if we want to include the dmc s contact info in this empty state since there s no action on the veteran s part note the designs linked use the right rail component we re going to be releasing a second iteration that replaces the right rail content with the on this page anchor links just wanted to give ya a heads up in case you were wondering while reviewing the content please feel free to edit this ticket to fit whatever format works best for you ,1 26510611901.0,2023-01-18 16:49:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove alert from download debt letter page issue description alert highlighting incorrect repayment plans can now be removed alert can be found on the debt balance letters page tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24561605353.0,2022-10-12 20:50:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unneeded feature flags background we have removed references to different feature flags from vets website request locked pdf password evss upload limit they need to be removed from vets api as well tasks make pr to remove feature flags referenced above acceptance criteria pr has been merged,1 20783033818.0,2022-03-16 16:19:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update the promo banner info web component in the vaos application description platform design system team built a promo banner web component we should replace the existing promo banner react component to the updated promo banner web component there is a migration script so it can be easily migrated from the react to the web component version known differences tasks try out replacing the promo banner react component with promo banner web component and document any differences that appear acceptance criteria replace promo banner react components with promo banner web components ,1 15085741085.0,2021-02-05 19:09:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,make personalization components dir for shared components we use the nametag and identitynotverified component in both profile and dashboard they should live in a folder that resides above those apps the identitynotverified component will have to be made flexible enough for both uses we should also make sure our team owns that dir ,1 20923106564.0,2022-03-24 19:26:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add vba mock debt to mcp user issue description as we implement the combined debt portal we will need to have a test user that has both vha and vba debt tasks create betamock data file with vba debt for a medical copay user acceptance criteria one user can log in and have both vba and vha debt how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24848520058.0,2022-10-26 17:54:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,content of additional information in fsr is getting cut off issue description determine the max character length achievable in this field and specify tasks determine max character length update pdf fill with specification test vbs api submissions with max content acceptance criteria we accept large bodies of content within additional information how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24849020195.0,2022-10-26 18:19:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, checkbox to input boxes enhancements other living expenses issue description add checklist to box functionality in fsr for the following pages example of functionality tasks add checkbox to input functionality for pages listed above acceptance criteria new page formats are functioning as expected and match design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20920903166.0,2022-03-24 17:17:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, combined debt portal background this epic outlines the ui work for the combined debt portal i ve split out each page into the corresponding use cases each use case includes a link to the uxpin prototype or an indication if it s tbd note uxpin prototypes may also contain comments to provide more information about components data additionally labeling may evolve as we receive content feedback use cases your va debts and bills this is the overview page that will will show the combined total of vba debts and vha copay bills we ll make two api calls on this page to get that information from the separate databases veteran has both vba debts and vha copay bills alert tbd veteran has only vba debts no vha copay bills tbd alert tbd veteran has only vha copay bills no vba debts tbd alert tbd empty state tbd veteran has neither vba debts nor vha copay bills tbd current debts vba once the veteran clicks check the status and resolve your debt from the overview page or enters this page from a debt specific entry point they ll see a list of their current vba debts and their statuses we ll also make an api call to see if the veteran has a copay balance as well note the patterns from the existing debt portal have been updated to match the components used in the medical copay tool this will support a cohesive experience for both vba debts and vha copays debt status card improvements gray cards veteran has current vba debt and vha copay bills alert tbd veteran has current vba debt and no vha copay bills alert tbd empty states veteran doesn’t have current vba debt but has vha copay bills tbd veteran doesn’t have current vba debt or vha copays tbd vba debt detail the debt detail page and its use cases already exist as part of the debt portal however the components will need to be updated to align with the medical copay tool debt status card improvements blue cards vba debt detail debt letter download the debt letter download page and its various use cases already exists as part of the debt portal however we will iterate on the ui to provide a more accessible format of downloading the letters switching from table to list redesigned letter download page tbd current copays vha once the veteran clicks check your balance and resolve your bills from the overview page or enters this page from a debt specific entry point they ll see a list of their current vba debts and their statuses we ll also make an api call to see if they have vba debts as well veteran has current vha copay bills in this case facility and vba debt alert tbd veteran has current vha copay bills and no vba debt alert tbd empty states veteran doesn’t have current vha copay bills but has vba debt tbd veteran doesn’t have current vha copay bills or vba debt tbd copay details vha this page already exists as part of the medical copay tool html statements vha the epic for this work could be cross linked to this epic if it s helpful to track for release ,1 20380517276.0,2022-02-21 21:02:55,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add feature request info to platform orientation materials user story as a new vfs team member i want to be made aware of the platform feature request so that i can submit a feature request for improvements ideas for the va gov platform description the service design team launched a new process recently for vfs teams to submit feature requests to platform this means that if a vfs team member has an idea for how platform could improve an existing process reduce time to complete a task or has an idea for a new product altogether they now have the option to let platform know easily the service design team launched the page on platform website and have asked that governance team integrate it into the platform orientation materials artifacts tasks add a checklist item to the platform orientation template under general for the reviewing the submitting a feature request page add a slide to the general orientation slide deck work with shira communicating to vfs teams that they have the opportunity to submit feature requests to platform team acceptance criteria platform orientation gh template has been updated per the criteria specified above general orientation slide deck has been updated to reference the feature request updates have been peer reviewed by governance team member or octo guidance to be created governance team resources how to configure this issue ticket type is labeled tech debt collaboration cycle attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe ,1 27405705983.0,2023-03-01 06:31:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create a basic and updated user flow issue description what details are necessary for understanding the specific work or request tracked by this issue we currently have a user flow diagram on mural specifically representing the we are creating a more comprehensive user flow from veteran s point of entry to fsr all the way to completion of fsr form this new and updated user flow will give us a more comprehensive bird s eye view of the entire process this user flow will serve as a visual to help facilitate conversation during the heuristic evaluation workshop it is a necessary step for workshop planning team members will be able to refer to the user flow now and in the future tasks what work is necessary for this story to be completed create the user flow in sketch app and share with core team acceptance criteria what will be created or happen as a result of this story a user flow diagram how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 11627727886.0,2020-02-27 17:00:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, claim status tool double error messaging on files tab user story in the claim status tool when viewing a single claim appeal on the files tab messages that appear on the screen for the veteran appear in double locations see screenshot below for messages relating to file uploading the messaging should only appear under the additional evidence header for messages relating to everything else the messaging should only appear at the top of the page the messaging at the top of the page is the original messaging before the file upload functionality was added to the page in this ticket screenshot acceptance criteria errors relating to file uploading only appear below additional evidence all other errors only appear at the top of the page,1 24364552065.0,2022-10-03 14:15:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add fsr enhancement feature flag issue description fsr enhancement effort will need to be thoroughly tested before going live so we need to implement a flag to show hide these features separate from the existing combined fsr flag tasks implement new feature flag for fsr enhancements acceptance criteria new feature flag is implemented how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25412749541.0,2022-11-22 20:33:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add work in progress notification to product development checklist user story as a vfs team member i was to know what pages are under construction so that i know the guidance may not be reliable as a governance team member i want to ensure that the product development checklist page is marked as work in progress so that vfs team members know that the guidance is not reliable description the product development checklist is live on platform website however it is not fully in use and or up to date because of this we want to add work in progress note to the top of the page so that vfs teams are aware in addition martha noticed that the “everything is accessible and there are no sev accessibility bugs ” item links to an old branch this should be updated to link to master artifacts needing updates tasks add work in progress to the top of the page reached out on vsp confluence slack channel for guidance on how this should be done update accessible link to master branch acceptance criteria updates have been peer reviewed by governance team member user story need has been fulfilled accessible link is correct vfs teams are able to see that the page is a work in progress governance team resources how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 13767701256.0,2020-10-07 16:04:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,be fsr add prefill form to vets api as a veteran filling out the fsr form online i want my contact record to be prefilled if the information is incorrect i would like the ability to update the records online so the dmc has my correct information the following fields should be pre filled definition of done for a test user the information should be prefilled and the veteran should be able to update the social security number should be hidden per va security standards ,1 17795314461.0,2021-08-31 21:17:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create versioned facility fetch mock helpers following up from the mock testing spike we should start creating more versioned higher level helpers something like this in tests mocks fetch js js export function mockfacilityfetchbyversion id name address phone lat long isparent null version also as part of this ticket we should update some or all of the appointment list tests to use this new helper and create tickets for other areas we could convert ,1 26513472860.0,2023-01-18 18:54:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, research plan review for enhanced fsr issue description research plan review for enhanced fsr tasks team reviews and makes updates to research plan acceptance criteria research plan reviewed by team,1 24849028345.0,2022-10-26 18:20:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, checkbox to input boxes enhancements utility bills issue description add checklist to box functionality in fsr for the following pages example of functionality tasks add checkbox to input functionality for pages listed above acceptance criteria new page formats are functioning as expected and match design how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21190352979.0,2022-04-08 16:40:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add scripts for design intent midpoint review and staging review to their respective platform website pages user story as a vfs team member i want to have a clear understanding of what will happen at a collaboration cycle review so that i can ensure my team is prepared intended audience vfs teams desired outcome script for each meeting is shared on platform website due date description in order to ensure there is no gap of understanding from the operational side guidance documented in confluence for governance team to follow to the vfs facing side platform website we should be as transparent as possible the script that is read before each collaboration cycle governance owned touchpoints design intent midpoint review and staging review should be published to platform website so it is clear what is expected please note that this is a short term fix to address an immediate need platform governance team will be modifying updating our vfs facing guidance and documentation in a larger initiative artifacts needing updates tasks scripts can be found here acceptance criteria platform website design intent on platform website has been updated per guidance platform website midpoint review on platform website has been updated per guidance platform website staging review on platform website has been updated per guidance updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 23371731386.0,2022-08-10 20:32:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt and copay selections update issue description as a part of the combined fsr update the debt selection page is being updated to provide clarity on debts and copays being selected and minimizing extra noise on the page existing solution click to expand updated solution tasks remove card ui component and add checkbox selections with additional subtext information include copays in checkbox list for selection update cypress tests if necessary acceptance criteria new debt selection page matched design and is functioning how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 17400524535.0,2021-08-02 18:58:14,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, claims payee code errors issue description when we submit a form to evss we sometimes get back the error submit establishclaim serviceerror benefit type payee code or ep code is not valid benefit type must be cpd payee code must be or what can we do to better handle this error note this is not something we submit and does not feel like a retryable error so likely need to just tell evss to fix it tasks confirm this is still happening in prod if still happening ask evss what this error means provide them with some ids acceptance criteria if still happening understand why and provide technical solution code up if within estimate of points ,1 15866693762.0,2021-04-08 16:01:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unauth mock data issue description mock data was added to the initial state for unauth users and should be removed more details can be found on this tasks remove mocks from initialdata found in form js acceptance criteria unauth users should not so show any fields pre populated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14983517290.0,2021-01-28 17:18:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, hard code contact information for staging usability issue description we want to prefill a couple of inputs in the unauthenticated experience for usability tasks prefill first email input in contact section with ‘hector smith email com’ prefill phone number with ‘ acceptance criteria inputs show as prefilled in the unauthenticated experience,1 19689324869.0,2022-01-12 03:59:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and standardize all naming conventions for vamc campus map pages story as a veteran i need to have a clear understanding of what and where the vamc campus map is viewings so i can better navigate the buildings and campus in my health care journey resources tasks review all vamc campus map vamc detail pages and assure that the meets the standard naming convention of the main facility campus map if more than one main facility then there should be a campus map for each related medical facility review all vamc detail pages campus map document all that are out of compliance and verify if url alias needs to be fixed as well update so that it meets compliance report urls that need changing so that a redirect can be submitted before changing acceptance criteria all non conforming pages with are updated to correct naming list of pages and url alias that need adjustment is attached to this ticket or listed in vamc share for upcoming stories ,1 23772847833.0,2022-09-01 17:56:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, design for other living expenses issue description itemized design for other living expenses see tasks acceptance criteria ,1 23137758783.0,2022-07-28 15:34:04,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,have va telephone component render numbers with tty supporting text general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue button and link language isn t descriptive and or their purpose isn t clear issue details whenever a number is provided please include tty in both the aria label and the visible link text eg tty this helps users who are deaf or hard of hearing to quickly identify the number and helps indicate to other users that they don t need to call that number particularly screen reader users who may be tabbing from link to link and might not hear the if you have hearing loss context link screenshot or steps to recreate va gov experience standard other references wcag sc a platform recommendation this is a known issue on the va telephone component flagging here for dst visibility vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 23907090167.0,2022-09-09 02:46:47,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,vbms letter debt portal audit issue description on september it was identified when vbms updated the third demand letter form additional veteran data was shared on some letters from to this is one of a few letters veterans can access when they have a vba overpayment in the debt portal a toggle switch has been added to production which enables the team to turn off access to the letters until the issue is resolved to understand the impact this issue has caused an audit needs to be done to provide estimates of the number of veterans who accessed their letters during the time period determine the identities for those veterans that accessed and identify the number of veterans who downloaded the form document tasks provide estimates for the debt portal audit the of veterans that have accessed their letters during the time period estimated completion identities for those veterans that accessed estimated completion identify number of veterans who downloaded the form document estimated completion tbd still under evaluation acceptance criteria summarize and report on findings how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23370131577.0,2022-08-10 19:00:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,list loop discovery issue description design discovery for list loop enhancements tasks watch recording of riley showing ux prototype review ux improves to understand what changes are we making review that describes why these changes are important and why original list loop implementation wasn’t successful acceptance criteria general understanding of the list loop changes planned for the fsr experience how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12893265014.0,2020-07-13 21:15:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, claims look into center regex error user story or problem statement understand evss submission error center name pattern severity error text must match and found at furthermore there are a number of places where we could have other regex issues and when we obtain the schema from evss we can confirm we are never sending invalid data the current solution is to clean up the data we send downstream and evss tentatively agreed to open up their regexs acceptance criteria no regex errors coming back from evss anymore how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16061433261.0,2021-04-23 13:07:01,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,move mock data into individual tests generally we want to use our mock data helpers to create mock data for rtl tests inside individual tests this makes it easier to add new tests later or tweak existing ones if their data requirements change over time files src applications vaos tests appointment list components confirmedappointmentdetailspage index unit spec jsx src applications vaos tests appointment list components requestedappointmentdetailspage unit spec jsx ac files don t have mock data defined globally for the tests aside from initialstate mock data is created in each test using mock data helper functions also be sure to check the parameters you can pass to make generating the data you need more concise ,1 23242057640.0,2022-08-03 16:25:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,link topline summary template on platform user story as a vfs researcher i want all the important guidance i need in one location that i know to be source of truth so i don t have to hunt for it and so that i know that i m getting the latest guidance as platform governance team i want make sure researchers have access to important information on platform since it is source of truth for research guidance intended audience vfs teams desired outcome guidance moved to platform and marked deprecated in gh due date assignee claytonzook peer reviewer seanasewell description there is a we ve moved that that document to but unsure if and where it s linked on platform website new artifacts artifacts potentially confirmed needing updates as updated on the tasks content audit to figure out if the old gh document is linked anywhere on platform if needs new links decide where on platform this should be linked from acceptance criteria platform links to the old doc is replaces with the new doc updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate initiative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 15304086726.0,2021-02-24 16:30:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr integrate va benefits with fe ui as a veteran filling out fsr form i want my va benefits to be prefilled in the income section of the form definition of done for a test user logged into va gov the va benefits amounts must be pre filled ,1 15021409206.0,2021-02-01 15:46:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, error handling bug within fsr s progressive disclosure issue description some progressive disclosures are throwing errors for subsequent questions if the previous question threw an error how to recreate this bug in staging navigate to step your employment history select the continue button to attempt to proceed to the next page you should now see an error for have you been employed within the past two years question select yes for the have you been employed within the past two years question bug you should now see an error message for the are you currently employed question ideal experience errors shouldn t be displayed by default the second error should only be displaying if the user attempts to proceed again without selecting a response note the same bug is happening in multiple areas of the form including the your other income page the bug doesn t seem to happen if the next question in the progressive disclosure is a list loop please refer to this video for a visual of the bug tasks resolve the bug that s automatically throwing errors in the form s progressive disclosure interactions test that none of the progressive disclosures in the form no longer have the identified bug acceptance criteria the error handling within progressive disclosures aligns with the outlined ideal experience the solution has been pushed to staging and reviewed by a designer ,1 30676635838.0,2023-07-26 06:01:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,copy of sprint priorities debt resolution team debt team sprint priorities sprint july needs to be updated sprint goals update review page finish code clean up complete conversation guide complete the streamlined waiver prototypes planned issues fsr enhancements use cases for testing analytics add efsr feature flag to submission event for tracking pt fe downtime dependency update pt fe navigation content update pt fe mcp notifications setup datadog dashboard for copay notifications pts be streamlined waiver streamlined waiver discovery research framing design product outline for streamlined waiver pt transparency discovery mockups for streamlined waiver design ongoing maintenance bug fixes medallia satisfaction survey data review pts reasearch on hold this sprint due to user research blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished xx tbd xx points over xx issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 16455489804.0,2021-05-21 11:59:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,make all checkbox lists use a checkbox group technical task during a it was called out that when you have a list of checkbox its better for accessibility to have them grouped by a fieldset in order to accomplish this in the form system we need to wrap the checkboxes in a checkbox group expected behavior all checkbox lists are wrapped in a fieldset to accommodate accessibility acceptance criteria all checkbox list on the hca are wrapped in a fieldset additional context ,1 25287370600.0,2022-11-16 20:30:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create personas for user flow paths issue description create personas for user flow paths on miro board tasks create personas for each path discuss with smes acceptance criteria personas created meeting created ,1 15820598149.0,2021-04-05 19:13:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update content and style on all viable system pages story as a veteran i need to have all pages read accurately and clean so they are easy to digest and understand in my health care journey goal optimize content to meet latest updates in style and plain language task review and update content pages for latest updates of content style provide pages that have been updated and or sheet to utilize for planning acceptance critieria all pages are updated with new revised content team is prepped in meeting for future cloning and process,1 17607378796.0,2021-08-17 18:58:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add ssn and filenumber to submission payload issue description we are currently not passing ssn and filenumber in the submission payload and should be added personalidentification ssn string filenumber string fsrreason string tasks add ssn and filenumber properties to transform js acceptance criteria ssn and filenumber properties should be added to submission payload how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 28311419748.0,2023-04-10 15:44:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, updates to resolution options to repeat amount of debt issue description update text and design to repeat the amount of debt for the here are the before and after with the after being the proposed solution resolution options waiver monthly payments compromise beneifit before benefit after resolution options waiver compromise copay before copay after tasks update designs in sketch for each resolution option archive old designs in sketch for each resolution option update uxpin prototype for each resolution option acceptance criteria attach updated designs for each resolution option attach links to updated designs in uxpin ,1 16623230848.0,2021-06-03 06:07:21,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, swap out current policies page with new hardened policies page for visn and publish user story as a vha digital media web manager the national policies need to be hardened and available to national administrators only so national content should be changed from one source to all systems goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks archive current policies page replace with cloned page and add to menu for the following systems altoona butler abie abraham va health care center hcc coatesville erie double check as this may be complete lebanon philadelphia wilkes barre wilmington complete the follow these steps for each system open policies page in edit mode a change name to policies old b remove menu by un checking menu box c save as archive open fargo or iowa city system and find policies page a select clone from tabs and select clone b go to edit and remove cloned c change governance to match new owner and related system d select menu enable check box e type in policies in name f select from drop down about va from system you are cloning to g copy visiting hours and or security information from original policies page security information will go into other policies section save new policies page as current status of system i e published or draft acceptance criteria all original policies pages have been archived and removed from menu all new policies pages are published and link is in menu at bottom of menu items ,1 14001470437.0,2020-10-28 13:41:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr resolution options as a veteran filling out the fsr form and after entering my income assets and expenses including the amount of discretionary income calculated i want the ability to chose the resolution option i am requesting from the dmc this si supported by content explaining my options and what they mean ,1 15019818039.0,2021-02-01 14:00:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, the cancel button functionality needs to be updated in the list loop component issue description there are multiple bugs occurring with the cancel buttons in the list loop component how to recreate the bugs in staging navigate to step your employment history select yes for have you been employed within the past two years select yes for are you currently employed select the add payroll deduction button bug selecting the cancel button on the second payroll deduction card doesn t close the card ideal experience selecting the cancel button should remove the card bug selecting the cancel button on the default payroll deduction card breaks the form ideal experience there shouldn t be a cancel button on the default card unless the user has already saved inputted values and is in the edit mode in this case the cancel button s action would cancel the action and close the card with the original inputted values please refer to this video to see a visual of the bugs tasks update the list loops so that selecting the cancel button on subsequently added cards removes the card remove the cancel button on the default card ensure that the cancel button only displays on the default card if the user is editing previously inputted values acceptance criteria updates have been pushed to staging and sent to a designer for review ,1 14703831167.0,2021-01-04 15:36:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for va salt lake city health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field to include is a referral required are walk ins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems va salt lake city health care elko va clinic george e wahlen va medical center idaho falls va clinic ogden va clinic orem va clinic pocatello va clinic price va clinic roosevelt va clinic st george va clinic weber county va clinic western salt lake va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 31166115375.0,2023-08-16 19:51:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, staging review accessibility feedback html markup is not valid during the staging review on this launch blocking feedback was provided platform issue html markup isn t valid issue details in step when indicating whether you have any of each type of assert real estate vehicles trailers campers boats the radio button group is labeled with a label which isn t the appropriate html element for radio buttons the practical impact here is that the label isn t programmatically associated with the radio buttons so it won t be announced by screen readers when the user tabs to the radio buttons a screen reader user will hear the heading that introduces the topic but they re not likely to hear the actual question they re answering eg do you currently own any property link screenshot or steps to recreate va gov experience standard other references wcag sc a platform recommendation recommend using the va radio component which groups the radio buttons in a fieldset and labels them with a legend it looks like that s what was done everywhere else in the product this was just a minor oversight ,1 23726922288.0,2022-08-30 20:33:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,new platform page for research methods user story as a vfs researcher i want guidance on which research methods work well in a given situation this can help prompt me or otherwise guide me to the best research method as platform governance team i want to make sure researchers can find all important guidance on platform assignee peer reviewer description the does have a quick overview however the is something to aspire for vfs facing guidance impacted artifacts new platform page research planning research methods tasks decide what if not everything from applies to vfs teams transfer relevant information to a new platform page including links to relevant and nn g pages peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria placeholder ac how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 16597394368.0,2021-06-01 14:56:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, financial status report content styling anomalies what happened on staging fsr form the following content styling anomalies were found device browser agnostic step of household income your spouse information form page subtitle content didn t match prototype mobile step of household expenses installments after adding an installment debt form page subtitle and body text was missing vertical spacing specs devices browsers test user if applicable vets gov user gmail com colder vets gov user gmail com jerry vets gov user gmail com greg steps to reproduce url test user if applicable sign in as needed advance as needed to each form page listed and observe each anomaly listed screenshots device browser agnostic step of household income your spouse information mobile step of household expenses installments desired content styling device browser agnostic step of household income your spouse information form page subtitle should be your spouse information mobile step of household expenses installments form page subtitle and body text should have vertical spacing acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 15783515456.0,2021-04-01 14:05:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,consider replacing moment with date fns a different date library date fns is being used in some platform code it s unlikely that we could completely exclude moment from our build but we could potentially avoid moment timezone because date fns uses built in browser apis and the design system team polyfilled that for older browsers we should explore how much effort would it take to convert our existing timezone related logic to use date fns what is the bundle size impact of using just date fns i e is date fns moment less than moment moment tz ,1 17193675329.0,2021-07-16 14:25:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore ways to reorganize and rename tests to improve clarity it can be hard to read through test files and understand how they re organized and what they re testing we should attempt to do some reorganization and renaming of tests to make what s being tested clearer this should be timeboxed and follow up tickets created after that ,1 22271795228.0,2022-06-10 13:04:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,setup config for new vbs endpoint issue description a new endpoint is available for the vbs service for fsr submission set up the necesary configuration within settings and library to make this usable tasks update settings config configure new route in library acceptance criteria the new vbs endpoint can be integrated how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 22631350264.0,2022-06-30 14:53:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits sprint priorities sprint june formerly debt resolution team 🎉 welcome megan gayle to the team 🎉 officially on gh now 🎉 sprint goals prepare for cdp usability research with veterans open cdp staging review ticket and schedule develop test plan for lower environment testing for vha fsr integrate with vbs endpoint for json transfer sprint deliverables list of deliverables completed during sprint test plan for combined fsr lower environment testing staging review scheduled pilot session conducted ahead of usability research planned issues combined debt portal bug the existing empty state ui doesn t align with the intended experience cdp sanitize text in statement table cdp staging review content updates bug the existing empty state ui doesn t align with the intended experience cdp missing debt letter history download debt letters sections cdp users not reaching correct state usability prep update existing debt letters widget for cdp and investigate staging only page both zero alert message showing when one endpoint errors and the other has zero balance combined fsr setup config for new vbs endpoint integrate fsr submission with vbs endpoint other update documentation within product intro doc unplanned additions tbd capacity planning pto holiday s denise scott brandyn andrew riley june last day with the team megan june juneteenth code freeze points planned points accomplished tbd points over tbd issues tbd points over tbd issues 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr streamlined waiver github epic product outline use cases flow release plan architectural diagram use cases usability testing n a dates product guide mcp product guide kickoff design intent midpoint review content ia request analytics request required contact center review research plan review required staging review staging url staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes ,1 30691389292.0,2023-07-26 15:23:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, sw implement income limit back end issue description implement income limit threshold back end to fetch limit based on number of dependents and zip code store gmt in redux and calculate and of gmt to be used for routing tasks implement income limits api calls to fetch gmt based on dependents and zip code store gmt in redux with percentage calculations for routing acceptance criteria income limits fetching is implemented and values are stored in redux how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 20823594798.0,2022-03-18 17:57:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update the current debts once letters after are available for download issue description since letters sent after december are unavailable for download we removed the cta to download letters in the debt portal current debt overview s this ticket captures that the sentence should be added back once the issue is resolved and veterans are able to download all their letters tasks the alert s been updated with the appropriate content notifying veterans that they may still be able to download letters related to their debt acceptance criteria the alert has been updated and the uxpin has been linked in this ticket a frontend ticket has been created and linked in this ticket ,1 31273908632.0,2023-08-22 03:56:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, midpoint review accessibility headings updates post launch during the midpoint review there updates that needs to be made noted here should i really appreciate the unique headings describing each page within the multipart steps if you re not already planning to do this those headings should receive keyboard focus when landing on each page of the workflow that will ensure they re the first thing a screen reader user hears meaning they ll know they ve advanced to the next step and have some context for where they are instead of hearing step of multiple times as they move through the workflow ,1 26811944507.0,2023-02-01 23:19:19,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,socks access for aaron ponce your name aaron ponce your email aaron ponce com your role and team front end engineer vsa debt product manager pm name and email denise coveyduc gcio com product owner po name and email emily theis emily theis va gov access type requesting developers public ssh key ssh rsa ro nb fl kyue aaron ponce lan user must exist in a roster before socks access can be granted search for user on the vfs team roster or search for user on the platform team roster if user is on a vfs team but not in the vfs team roster add the not yet label and instruct them to start the platform orientation process if a user is on a platform team but not on the platform team roster in confluence add the not yet label and instruct them to reach out to their product manager to be added comment in this issue saying which roster the user is listed in ,1 13925970515.0,2020-10-21 17:36:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,rewrite calendar page tests using react testing library we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos ,1 23846878413.0,2022-09-06 14:38:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,upload pdf copy of form to vha sharepoint issue description we have functionality for creating pdf and code from testing sharepoint integration but need to link them together tasks create class to upload pdf get authentication key create pdf upload pdf get sharepoint listitem update listitem fields acceptance criteria forms that apply to vha debt get uploaded to sharepoint as pdfs how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12498454730.0,2020-06-01 18:19:03,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, establish connectivity with dmc test environment user story or problem statement as a backend engineer i need to establish connectivity with the dmc so that vets api and the dmc s apis can communicate with one another goal that communication is established and viable between the dmc and vets api tasks work with dmc team and vfs devops to establish connectivity between dmc and vets api setup fwdproxy to dmc api acceptance criteria connectivity is established between dmc and vets api ,1 15025225122.0,2021-02-01 20:46:22,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,do not try getting full name personal info or military info for users background if a user is we should not even try to get their name personal info or military info for the profile we should also make sure we don t show the generic profile error if that data is not available tasks stopping making those api calls from the profile if the user is adjust the logic for determining if all profile data has loaded confirm that shownotalldataavailableerror does not flip to true for users potentially update the cypress tests to confirm endpoints aren t hit ,1 20681651209.0,2022-03-10 14:26:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, submit transformer unit test issue description once payload submissions have been verified by the dmc we need to create a unit test for the submission payload transformer to ensure the correct data is passed tasks create test for payload transformer acceptance criteria transformer test should be passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14010862047.0,2020-10-29 06:10:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, vamc team to take second look at all previous system pages to validate mvp and consistency user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation prod cms va gov tasks complete review of system and facility pages for the following content and flow asking these questions does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page confirm all of the facilities are reviewed erie vamc ashtabula county va clinic crawford county va clinic mckean county va clinic venango county va clinic warren county va clinic document all errors items that need update and testing on each page using spreadsheet listed above acceptance criteria all node pages have been reviewed in spreadsheet and issues found have been been documented issues have been escalated for resolution using spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 23320823931.0,2022-08-08 16:12:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add new va gov experience standard re new component user research user story as an octo team member supporting the va gov platform i want to ensure that any new components being used are researched tested with veterans and or va gov users before launch so that we can document and address any usability issues that may come up especially ones related to accessibility intended audience octo vfs and governance team desired outcome new standard is created and added to the va gov experience standards lists due date tbd assignee briandeconinck peer reviewer jimuhh description vfs teams may need to create new components to solve their products problems because the va gov design system doesn t currently have a component that meets the products needs this is expected and has occurred with vfs teams previously however if the vfs team does create a new component then they are required to test that component with veterans and or va gov users during their research sessions in order to document issues concerns etc the purpose of this ticket is to document this expected behavior in the form of a va gov experience standard within this ticket we will document the following category category number standard the expected behavior issue the problematic behavior issue number wcag reference if applicable impacted practice areas accessibility content design and or ia severity launch blocking depends or non launch blocking artifacts needing updates va gov experience standards see wrt how to update the actual standards tasks create a draft page for the proposed new standard define the following category category number standard the expected behavior issue the problematic behavior issue number wcag reference if applicable impacted practice areas accessibility content design and or ia severity launch blocking depends or non launch blocking share on platform governance team channel for peer review from governance team make modifications edits if necessary share on platform collaboration cycle channel and ask for octo practice area lead review only the octo practice area leads for the impacted practice areas will need to sign off however all should see and validate that their practice area is or is not impacted by this new standard once approved make the changes to the va gov experience standards per the va gov experience standards guidance on confluence validate that the changes have been published to platform website validate that the changes have been published to the draftingtemplate confirm with shiragoodman if needed acceptance criteria a new va gov experience standard has been added to the va gov experience standards list octo practice area leads have signed off on the new va gov experience standard vfs teams have been notified of the new standard per vfs all teams and the collaboration cycle change history log how to configure this issue ensure that story is attached to appropriate initiative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 28366263752.0,2023-04-12 14:04:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,streamlined waiver user flow planning issue description what details are necessary for understanding the specific work or request tracked by this issue tasks meeting with smes on acceptance criteria make updates based on conversations with smes,1 12238621254.0,2020-05-04 20:08:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor appointment list instructions there s a lot of parsing and formatting of instructions that happens in utils appointment js which should really be handled by a react component steps here would be map the instructions fields for requests cc appointments and va appointments to the instructions property on the appt object collect the booking notes and instructions fields for video appointments into an object and set instructions to that see example data in create a component for va appointment instructions that does the checks for patient entered instructions and display them when found same logic as we have currently don t display video appointment instructions at all pending work in effectively this is no change from what happens currently display request and cc instructions as they are now may want to create a component for cc instructions to make code a little cleaner ,1 22758129943.0,2022-07-07 18:26:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, no va gov experience standard for the issue found general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue no va gov experience standard for the issue found issue details there are a number of places i ve noticed where an aria attribute is used but not in a way that benefits screen reader users an example links with an aria label that s identical to the visible link text even though there s no barrier introduced to assistive technology users this introduces the potential for future issues eg a future iteration updates the visible text but forgets to update the aria label and now there s a mismatch between what sighted users and screen reader users experience it makes the product a little more fragile from an accessibility perspective link screenshot or steps to recreate two examples i ve noticed when conducting my review on summary the check your balance and check the status links each have an aria label that are identical to the visible text you can just remove the aria label entirely in that situation on summary copay balances the dollar amount headings for each copay card have an aria describedby that references the text immediately following the heading that s not consistent with the other card headings and doesn t provide much value va gov experience standard other references platform recommendation this isn t urgent or even required but i would encourage a review of aria attributes that might be duplicates or unnecessary as a general rule aria should be used only when out of the box html doesn t provide enough coverage for screen reader users is a great discussion on this and i m happy to have a follow up conversation too vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 13908948558.0,2020-10-20 14:22:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr submission endpoint issue description create endpoint and associated business logic to handle fsr submissions tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23117066617.0,2022-07-27 17:43:28,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, the content isn t written in plain language and contains excess words and modifiers general information vfs team name debt resolution vfs product name combined va debt portal vfs feature name point of contact reviewers cheryl evans cherylevans content for more information on how to interpret this ticket please refer to the guidance on platform website platform issue the content isn t written in plain language and contains excess words and modifiers issue details although the verbiage mostly falls in line with plain language tenants the sentence because the letters sent after this date are unavailable for download right now we need to refer you to the letters you receive by mail could be confusing to the veteran we need to refer you to the letters you receive by mail is ambiguous and could be somewhat misleading does it indicate that the veteran has already received a letter via mail or does it indicate that the veteran will receive a letter via mail at a future date link screenshot or steps to recreate test user download debt letters yellow warning box va gov experience standard other references platform recommendation recommend a simple rewrite for user comprehesibility consider the questions posed in issue details when reworking the verbiage recommend a more direct and plain way to say we need to refer you to the letters you receive by mail vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 12975847409.0,2020-07-21 17:42:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters mvp ui debt letters table issue description in order to quickly provide functionality allowing veterans to access and download their va debt letters the mvp has pivoted to display a list of these letters as a table and provide content for resolving va debts tasks update the frontend with share the updated ui with the design team for feedback approval integrate with debt letters route of vets api acceptance criteria debt letters mvp frontend matches the uxpin s design ui has been approved by design team ,1 14906764089.0,2021-01-22 01:24:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt portal iteration view payment history high level user story ies as a veteran who is logged into the debt portal i would like the ability to view my payment history with amounts and dates including any adjustments definition of done identify if the data is available on dmc backend business rules and exceptions for displaying data add data to api create design take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content ,1 23114665266.0,2022-07-27 15:37:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, usability study synthesis research findings issue description veterans expect to find all money they owe to va in one location on the site additionally congress has mandated that we provide a way for veterans to access all their debts in one spot we need to validate the combined vba vha debt portal design with veterans to ensure it meets our users needs tasks synthesize usability findings and create research findings ppt and readout meeting created acceptance criteria research findings document created readout meeting created ,1 16527300765.0,2021-05-26 22:06:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove unpublished vet center check issue description during vet center pilot phase we added logic to check to see if a vet center location added as a nearby location is published to determine data source cms or lighthouse this logic was necessary so that unpublished content within cms would not be displayed on the front end once vet center pages are rolled out nationally all locations will be published and this duplicate code will not longer be needed tasks prune out published check for nearby vet centers acceptance criteria cleaner code base no unnecessary logic ,1 23853614270.0,2022-09-06 20:29:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update the cypress viewport updater issue description cypress changed the cypress config file from json to js causing the cypress viewport updater to break may s values were copied over to the js file but it hasn t been updated since tasks update the sidekiq job that updates the json config to update the js config so viewports are kept up to date acceptance criteria the updated sidekiq job will successfully update the cypress js config with last month s viewport data ,1 25548577860.0,2022-11-29 21:11:02,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, download va benefit letters issue description stakeholder have decided to remove the use of vbms for letter downloads their raised this and suggested that we may want to explore this functionality and meet with the team responsible this could be a good solution to provide letters for veterans in the future tasks discovery work to validate team working on this functionality current understanding it is the benefits team acceptance criteria what will be created or happen as a result of this story how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21485468068.0,2022-04-26 22:39:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add platform guidance on screening for specific assistive technology users user story as a vfs researcher i want to ensure that i get desired participant mix especially when planning for assistive tech participants intended audience vfs desired outcome understand how to better find assistive tech participants for research due date tbd description the perigean screener is managed by pra paperwork reduction act and therefore takes a large effort to change the current screener perigean uses asks do you use any assistive devices such as screen readers or braille display to access the internet if no leave blank researchers looking for a specific assistive tech participants should include an additional screener in their research plan like do you regularly use a screen reader while on your computer since this is not well known or documented adding this guidance to platform could reduce frustration associated with not having the desired participants new artifacts artifacts needing updates relevant platform page s about research recruiting tasks figure out which platform page s this information should live on update platform page s accordingly acceptance criteria platform website page name has been updated updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 14501738131.0,2020-12-11 19:57:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,convert textareawidget and needhelp tests to rtl tests textareawidget needhelp we want to rewrite our enzyme based tests with tests in rtl that do not test implementation details general guidelines don t test component implementation details class names dom structure etc favor checking for something a user would look for there are some exceptions to this like if we want to verify that the correct icon is used which can only be checked by class try to mock as little redux state as possible in favor of call helpers that set data using the actual page components prefer longer tests to doing a single test per assertion that model doesn t work very well with rtl or ui code it s fine for plain js tests check code coverage to make sure major functionality is covered yarn test unit coverage app folder vaos make sure to use the default exported component in the tests and you should remove the old export of the unconnected component,1 25412685239.0,2022-11-22 20:29:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, url shortener api error alerting description based on a discussion around the url shortener work it was determined additional alerting would be needed this ticket is to add alerting around api errors for the url shortener tasks create alerting for the following api errors acceptance criteria alerting structure has been implemented and api errors successfully populate,1 27422990378.0,2023-03-01 18:02:10,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add mock mvi responses for debt users issue description mockdata identity changes were not updated for all users to allow for successful sign in and loa we need to add the mvi profile mock responses for our team s users and any data needed for them tasks add mock response for user add mock response for user add edipi identifier to responses acceptance criteria we have a way to successfully login with our users locally how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23321656654.0,2022-08-08 16:57:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, determine best authentication approach for mcp notifications endpoint issue description we need a way to authenticate the vbs external service to connect to the new statements endpoint possible options include validating via api key or using a jwt approach tasks connect with platform and other engineers to evaluate possible authentication methods acceptance criteria we know how to implement authentication with vbs for the new statements endpoint how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 25333038986.0,2022-11-18 14:42:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,intermittent with staging copays users issue description we are intermittently running into issues with copay errors due to staging users missing edipi among other values this at first glance appears to be an identity data or mpi issue tasks start conversation with identity team to discuss missing data depending on conversation take steps to fill in data possibly create lett ticket to add values to mpi acceptance criteria intermittent errors are resolved how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27745379692.0,2023-03-15 16:41:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add additional interactions to uxpin prototype issue description what details are necessary for understanding the specific work or request tracked by this issue tasks what work is necessary for this story to be completed acceptance criteria what will be created or happen as a result of this story ,1 24848903684.0,2022-10-26 18:14:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, discovery estimation of timeline and work effort issue description read through vafs design system current fsr code and requested updates to come up with rough idea of timeline and estimation of work effort acceptance criteria rough timeline established to completion of combined fsr how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24176670974.0,2022-09-23 03:06:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities benefits team benefits team sprint priorities sprint september sprint goals review streamlined waiver user flow and discovery questions with vha smes draft design wireframes and user for streamlined waiver and wizard initiate phased roll out of combined fsr for vha monitor combined fsr roll out review application page text changes with smes move fsr api submission logic to background job return pdf details upon fsr submission create tests for copay resolution options upload pdf versions of fsr vha requests to create design for other living expenses implement checkbox to input boxes on fsr integrate continuous add credit card bills resolve sentry error for numeric input define three user scenarios for wizard and streamlined waiver generate staging api key for vbs authenticate vbs on new statement route sprint deliverables list of deliverables completed during sprint streamlined waiver user scenarios design wireframes for streamlined waiver fsr enhancement collaboration cycle kickoff streamlined waiver collaboration cycle kickoff planned issues combined fsr review application page text changes with smes pt move fsr api submission logic to background job pts carry over to return pdf details upon fsr submission carry over to upload pdf versions of fsr vha requests to pts carry over to create tests for copay resolution options create tests for debt resolution options content updates with addition of copays pts fsr enhancements design for other living expenses pts investigate removing cross app references from fsr pt carry over to checkbox to input boxes enhancements pts carry over to enhancement continuous add credit card bills pts streamlined waiver wireframes user scenarios for wizard and streamlined waiver draft pts define three user scenarios for wizard and streamlined waiver pts mcp notification generate staging api key for vbs pt authenticate vbs on new statement route pt unplanned additions sentry error for numeric input fix pt vbms letter debt portal audit pts capacity planning pto holiday s denise scott brandyn andrew megan brie points planned points accomplished points over issues tbd points over tbd issues sprint work was impacted by vbms pii incident causing reporting and portal audit as well as sentry issues identified during user testing sessions 🛠️ reference section 🛠️ artifacts artifact medical co pays combined debt portal combined fsr fsr enhancements streamlined waiver github epic product outline coming soon use cases flow and release plan architectural diagram use cases usability testing n a dates n a product guide mcp product guide kickoff n a tbd coming soon design intent midpoint review content ia request analytics request required contact center review research plan review complete staging review staging url changed to staging users copay debt only debt only copay neither privacy security review qa artifacts qa defects helpful links incl code freezes analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 17150088218.0,2021-07-13 19:19:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,pre need switch pure html alerts to use va alert description switch the pure html alert to use the va alert web component in the pre need form tasks replace html alert usa alert with va alert update unit tests update tests if applicable definition of done tasks completed all tests passing,1 18110599824.0,2021-09-23 03:01:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review contact us pages and remove all referenences to pittsburgh story each system should have unique data and information so that the editor can make the pages their own as they review and validate goal remove all referenced and data from the original pittsburgh template task remove references to vhapth vhap or similar emails update contact us section report an issue give us website feedback from vhapthwebteam va gov to correct webmaster or pao e mail for that section you may have to contact the main visn webmaster pao or contact to determine the best email to use if no contact delete section acceptance criteria there are no remaining references to pittsburgh e mails or pittsburgh abbreviations on any visn contact pages ,1 23597255099.0,2022-08-23 20:33:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,pdf password component fixes description when a password protected pdf is uploaded the showpdfpassword component is rendering a required label with extra parentheses and an asterisk img width alt required input label with the required text wrapped in extra parentheses and an asterisk src updating the component to use component library web components will fix this issue it will also change the green deprecated button into a blue add password button tasks update react components in showpdfpassword to use web components update tests acceptance criteria all tasks complete all tests passing,1 14004354828.0,2020-10-28 16:59:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debtres fsr debt resolution options as a veteran who has filled out my financial information and see a calculated field for disposable income i want the ability to chose the resolution path for dmc to consider ,1 20768000219.0,2022-03-15 23:16:20,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update the modal web component in the vaos application description platform design system team built a modal and promo banner web component we should replace the existing modal and promo banner react component to the updated modal and promo banner web component there are migration scripts for both components so it can be easily migrated from the react to the web component version default promobanner default known differences tasks try out replacing the modal react component with modal web component and document any differences that appear try out replacing the promo banner react component with promo banner web component and document any differences that appear acceptance criteria replace modal react components with modal web components ,1 30676504449.0,2023-07-26 05:53:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,sprint priorities debt resolution team debt team sprint priorities sprint july august needs to be updated sprint goals identify all sw mvp work and create tickets for all mvp development complete desktop mobile prototypes complete research plan guide for sw secure approval for sw content complete all be work for sw update review page for sw planned issues fsr enhancements downtime dependency update pt fe navigation content update pt fe streamlined waiver product outline for streamlined waiver pt mobile prototype uxpin design sw implement income limit back end fe streamlined waiver prep fe organization of folders fe front end discovery form navigation back to review page pts fe review display employment questions pts fe review display installment contracts fe look into possible approaches for adding an indicator for sw forms be observer notes documents design sw add new chapter level depends and structures fe sw update transform and helpers fe add streamlined waiver notification to va notify portal pt be send streamlined waiver notification for eligible requests be add an indicator for sw forms be sw release plan finalize transparency content design sw create example submission objects for be pts fe finalize conversation plan on github research finalize research plan on github research pilot session design ongoing maintenance bug fixes blocked issues unplanned additions tbd added as sprint progresses when if additional tickets are added to the sprint points planned points accomplished xx tbd xx points over xx issues x points over x issues 🛠️ reference section 🛠️ please click to open artifact lists for fsr enhancements fsr enhancement artifacts artifact link s github epic product outline user journey flows and release plan architectural diagram use cases usability research product guide kickoff design intent midpoint review details on kickoff feedback tickets design ia and content accessibility content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects streamlined waiver streamlined waiver artifacts github epic product outline user journey flows and release plan architectural diagram use cases feedback research usability testing product guide kickoff design intent midpoint review content ia request analytics request contact center review research plan review staging review staging url staging users privacy security review qa artifacts qa defects archive to older artifacts tbd link coming soon prototypes helpful links incl code freezes debt team heuristic workshop march analytics reference information link to link to it contains like to access request for ga and other resources and faqs for ga on the website that would be helpful too ,1 26965301602.0,2023-02-08 21:46:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, replace soon to be deprecated radio button components issue description is being deprecated and needs to be replaced in the fsr va radio appears to be the most up to date and note the import of react bindings that can help with react events potentially creating a reusable component like they did could be cool too tasks replace the react component in the following locations src applications financial status report components resolutiondebtcards jsx src applications financial status report wizard pages decision jsx src applications financial status report wizard pages recipients jsx src applications financial status report wizard pages reconsider jsx src applications financial status report wizard pages repayment jsx src applications financial status report wizard pages request jsx src applications financial status report wizard pages start jsx confirm these changes do not affect unit tests acceptance criteria all radiobuttons instances have been replaced all tests continue passing how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21100735854.0,2022-04-04 14:18:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, set up the transition between design development issue description as development for the combined debt portal ramps up design needs to set up documentation for the transition from design to development tasks set up an epic containing the available tickets and outstanding use cases to be covered by design add comments link interactions to uxpin screens as needed acceptance criteria the epic has been linked to this ticket,1 11136542702.0,2019-12-20 16:50:52,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, explore using dependabot for automated dependency pr s dependabot automatically creates pull requests to keep our dependencies secure and up to date and we should consider using it in at least vets api vets website as a way to keep our dependencies secure and up to date this is a free tool that would automate the process of updating our dependencies rails testing framework job processing all of the open source libraries and provides a better description of what it is pr suggestions would be presented to us and we would be able to decide if we wanted to merge that or not acceptance criteria decide and document if we want to do this at all if so proceed to next step if not document reason not to in this issue sign off on the documentation from other tech leads implement the change,1 26564067536.0,2023-01-20 18:23:00,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,services all use the same base error middleware user story or problem statement currently our services implement error handling with disparate approaches this can cause confusion and introduces increased complexity to our codebase goal external client classes that implement error handling do so using a consistent middleware for common error cases any developer can easily understand the logic for handling errors from a given service acceptance criteria latest faraday changes to response middleware are identified and leveraged if appropriate all external service client classes use the same base middleware how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 27527124967.0,2023-03-06 18:57:08,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,find cause of not found veteran identifiers in iam issue description there were user cspids that were not found by the iam team when pulling the records for the vbms audit we need to find the provider these cspids were pulled from and determine a reason why they were not found or if they are still valid tasks create script to find user account and identity provider connect with identity team to discuss theories acceptance criteria we are able to report the results to iam how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 16194914099.0,2021-05-04 13:31:18,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, include contractor as an employment type add contractor as an option in the employment type dropdown on both the veteran employment sections and the spouse employment sections ,1 22593127382.0,2022-06-28 22:04:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, deprecate check in experience update information page enabled feature flag tasks remove the feature flag remove all orphaned code remove unit tests update end to end tests ,1 13305761322.0,2020-08-25 19:04:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, debt letters update content in the coronavirus empty state issue description peggy provided updated content for the coronavirus empty state in the debt letters tool tasks update the coronavirus empty state with the new content review updated alert with designer acceptance criteria the content on the frontend matches the content in the uxpin prototype the updated ui has been approved by a designer ,1 13925972570.0,2020-10-21 17:36:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,map atlas data into fhir format we re pulling the tasinfo data on the appointment list page directly from the legacy api data object rather than mapping it into the fhir appointment resource ac atlas location should be mapped to a location resource in the contained array atlas confirmation code should be added to healthcareservice resource created for video appointments maybe as a characteristic or identifier ,1 16088926004.0,2021-04-26 14:31:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, financial status report submission allowed without checking required self certify checkbox what happened on staging fsr form review page submission was allowed even though by checking this checkbox i certify checkbox was not checked specs device browser test user if applicable vets gov user gmail com colder vets gov user gmail com jerry vets gov user gmail com greg video capture steps to reproduce url test user if applicable advance to review page completing req d fields and clicking continue button on the way there without checking by checking this checkbox i certify checkbox click submit button observe that browser advances to we ve received your request confirmation page desired behavior form submission should not be allowed without checking self certification checkbox should not advance to confirmation page acceptance criteria how to configure this issue attached to a milestone when will this be completed attached to epic what body of work is this a part of possibly ongoing maintenance labeled with team product support analytics insights operations triage tools improvements labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with bug ,1 20115309473.0,2022-02-07 18:52:23,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, bug the existing empty state ui doesn t align with the intended experience issue description bug explanation the vba debt portal s empty state doesn t match the intended ui when signed into test user there s a card at the top of the screen stating the veteran doesn t have any current debts however lower on the page there s an error about being unable to access current debt information i ve attached a screenshot below intended experience the empty state card shouldn t be above the on this page component it should display under the current debts header tasks update the ui to align with the provided uxpin prototype acceptance criteria the ui has been updated please tag rileyorr in this ticket to review the updates ,1 20114819138.0,2022-02-07 18:21:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,analytics implementation and qa support for edu how to apply wizards google analytics implementation or qa request what this form is for more information use this template to request google tag manager and google analytics implementation or qa for your product please fill out all brackets please see the following information for implementation timeline new teams implementation will usually be completed in sprints sprint discovery orientation sprint fe implementation sprint tagging implementation sprint qa all other teams implementation will usually be completed in sprints sprint discovery and fe implementation sprint tagging implementation and qa for more information please check out the an example of a completed request template can be found a fully completed issue can help speed up the implementation process description is this request for google analytics implementation or qa potentially both the how to apply for educational benefits wizard is being migrated from drupal to react all the current tags have been copied over to teh new pages but i think it needs a fresh review who is this request for leah k leahkeeler john h johnhashva provide any relevant contact information and link this issue to the insights team on the dsva slack channel vfs platform support what team project is this work for this adds context for the data is working with public webites in collaboration provide the domain where google analytics needs to be implemented and identify if pii is passed in url or title tag no please provide any upcoming deadlines or important milestones ex launch typical website interactions to track conversions understanding the user flow provide urls that are part of the application from introduction page to successful form completion conditional pages that are visible depending on an applicant s answer should be marker accordingly other user interactions provide details on other interactions and metrics like click to help text links that are helpful in understanding user behavior sample users when authentication is required do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository test users to replicate the event do not put staging credentials in your va gov team ticket store or reference them in a md file in the va gov team sensitive repository this is unauthenticated and a client side cookie will keep information for partial searches certain conditions responses that need to be reviewed additional comments please note that the tagging currently in place was migrated over from the drupal implementation and needs validation please leave the following blank acceptance criteria qa has been completed vfs team completes brief survey definition of done all appropriate issue tagging is completed all ac completed ,1 26712314399.0,2023-01-28 03:09:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,debt letter revamp high level user story ies debt resolution team to update the debt letter portion of the combined portal problem statement veterans are able to see their debt letters on the va debt portal previously they were able to download a copy of any debt letters that were mailed to them however due to a privacy incident our stakeholders have decided to stop using vbms to provide those letters to the portal as a result the debt team would like to revisit and overhaul how we present the debt letter information that we have available to veterans at the same time the debt resolution team will examine the debt letter history table and explore any enhancements that may be needed hypothesis or bet how will this pathway impact the quality of vfs or vsp teams’ work in how will this pathway be easy for vfs or vsp teams or how will it be easier than what they did before okr which objective key result does this epic push forward success metrics how will you track this pathway’s impact on performance of the platform’s systems and services how will you track adoption of this pathway how will you track the vfs or vsp experience using this pathway we will know we re done when what requirements does this project need to meet for you to close this super epic additional details notes optional any other relevent information about this project not already listed above artifacts link to product outline communication team that owns this super epic e g product support teams contributing to this super epic e g fe tools be tools ops ,1 26807854026.0,2023-02-01 19:43:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, veteran entered compromise amount not seen on dmc endpoint issue description dmc has reported that they are not receiving the dollar amount that veteran s request when they submit a compromise tasks troubleshoot error and determine what is needed acceptance criteria either fix or solution has been identified how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24823815811.0,2022-10-25 18:45:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, resolution option explainer enhancement issue description add resolution option explainer to fsr that matches tasks add resolution option explainer page behind feature flag acceptance criteria resolution option explainer page added behind enhancement feature flag how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23192695927.0,2022-08-01 13:55:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,revise navigation for research and design based on results of tree test user story as a researcher designer or team stakeholder on the va platform i want to easily find resources that may affect my team s research and design practices on va platform assignee peer reviewer description ticket was to perform quick research asking questions regarding findability on platform website for research and design this ticket is to implement the findings impacted artifacts tasks reorganize research and design pages to align to results of findability study create tech debt tickets for potential improvements that fall outside the scope of reorganization peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs team members are able to find important information quicky platform team members are able to navigate platform website and provide links to resources how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 19689452965.0,2022-01-12 04:14:09,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add configuration for fsr email notification issue description add the necessary configuration to be able to setup notification trigger and be able to turn feature on off tasks add va notify template reference to settings add feature flipper for sending fsr notifications acceptance criteria configuration for fsr notifications is in place how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14235873824.0,2020-11-18 15:20:12,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr create usability conversation guide issue description to kick off usability testing for fsr we need to write a research plan using tasks write a conversation guide for the fsr usability test study send the completed conversation guide to shawna for feedback after the conversation guide is approved by shawna send the document to lauren to kick off the recruiting process acceptance criteria shawna has approved the conversation guide the conversation guide is uploaded to github and linked to this ticket the conversation guide is sent to lauren ,1 23100799877.0,2022-07-27 02:23:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,list loop discovery issue description design discovery for list loop enhancements tasks watch recording of riley showing ux prototype review ux improves to understand what changes are we making review research that describes why these changes are important and why original list loop implementation wasn’t successful acceptance criteria general understanding of the list loop changes planned for the fsr experience how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 21936765085.0,2022-05-23 14:23:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,bdd switch to use va date web component description in the all claims wizard benefits delivery at discharge bdd path there is a react date component being used we need to switch it to use the new va date web component tasks replace react date widget with va date update tests as need definition of done all tasks complete all tests passing,1 15837236702.0,2021-04-06 20:29:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, redesign resolution selection screens issue description in usability we found that veterans struggled with the resolution selection page looping through each of their debts do some design rework for this section keeping in mind potential expansion of the feature to allow for secondary choices tasks create a new design for the resolution selection screen s update uxpin create fe ticket to implement acceptance criteria new design in uxpin and linked to this ticket fe ticket created and linked to this ticket,1 19680255078.0,2022-01-11 16:07:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, change learn how to pay your copay bill to pay your copay bill per staging review feedback issue description we received feedback during staging review that the learn how to pay your copay bill button and link language isn t descriptive and or their purpose isn t clear users may think they re being redirected to a tutorial to make the action more direct we have been advised to update it to pay your copay bill view the updated uxpin here tasks update the content on the facility s detail page from learn how to pay your copay bill to pay your copay bill acceptance criteria the detail page s ui has been updated with the new content ,1 17150784476.0,2021-07-13 20:17:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,create migration plan for dmc credential changes description on dmc will expire our current credentials the new credentials have been provided and will go into effect at about pm ct on the dmc is expected to be down for service on from pm – pm ct during this time vsa debt team should implement a downtime banner on va gov and apply the credential changes to the production configuration servers a c create the plan of action for conducting the production credential migration with limited website downtime and monitoring create the tickets needed to do the migration ,1 31815219200.0,2023-09-13 19:54:43,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,design debt issue description capturing future design iterations or ideas that will be progressed and prioritized as time allows tasks design team to capture information on required enhancements or changes that need designated design time to implement clean up header and footer symbols on efsr sketch file update fields to use symbols from ds on efsr sketch file acceptance criteria issue is a collection of ideas and can remain as long as it is helpful for the team all symbols are from the ds on efsr sketch file how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 23443219861.0,2022-08-15 16:53:33,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, combined debt portal from epic based on our meeting with jill from a couple weeks ago our team is moving towards combining the vba debt portal and medical copay tool into one va debt portal we ve previously discussed ia constraints that prevented us from releasing a combined portal as part of the mvp so i d like to brainstorm how we can combine these tools supporting artifacts link to product outline link to or attach user flows link to prototype or mockups when does this work need to be done research starting estimated launch about your team team name the debt resolution team octo de product owner product manager denisecoveyduc designer rileyorr and kevinstachura fe engineer dr pongo and optionselect product team slack channel vsa debt ,1 25838878735.0,2022-12-12 22:05:38,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,decision reviews fix verify modal design value statement as a benefits team member i want to design of the verify your identity modal to match the new design so that we have consistent messages across all decision review forms acceptance criteria user sees verify your identity alert only preventing them from starting higher level review form user sees verify your identity alert only preventing them from starting notice of disagreement form user sees verify your identity alert only preventing them from starting supplemental claim form update unit tests update tests accessibility testing complete reviewed and approved by product and or design designs and build notes img width alt you’ll need to verify your identity to access more va gov tools and features with green alert and lock icon we need to make sure you’re you — and not someone pretending to be you — before we can give you access to your personal and health related information this helps to keep your information safe and to prevent fraud and identity theft this one time process takes about minutes action link to verify your identity at the bottom src current verify alert img width alt warning alert at the top of the page verify your identity to start your request before we give you access to your personal information we need to make sure that you re you and not someone pretending to be you this helps us keep your information safe verify your identity to start your request non action link at the bottom src definition of ready clear value description testable acceptance criteria accessibility added to acceptance criteria approved designs attached sample data provided where appropriate estimated to fit within the sprint dependencies and blockers linked definition of done meets acceptance criteria passed testing coverage passed unit testing coverage passed integration testing if applicable code reviewed internal submitted to staging reviewed and approved by product and or design ,1 14889790034.0,2021-01-20 21:58:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,fsr list loop type options issue description we ve compiled a list of options that will filter as veterans type to make adding multiple assets and financial information quicker we need these lists added to their corresponding list loop input fields outlined the word document also contains links to the corresponding uxpin pages under each category of what this will look like in the form tasks incorporate the outlined list loop options to their corresponding input fields ensure the options filter as users type allow users to still add custom string inputs acceptance criteria the list loop options have been incorporated into the fsr s ui the list loops have been tested to make sure filtering works and users can still add custom inputs ,1 19350677956.0,2021-12-15 15:21:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, content organization and or categorization isn t clear or actionable general information vfs team name debt resolution vfs product name medical copays mcp point of contact reviewers jim ryan jimuhh ia platform issue content organization and or categorization isn t clear or actionable issue details on copay details page details on charges aren t available except as inconspicuous downloadable pdf details label implies that this info will be available on linked page link screenshot or steps to recreate blob va gov experience standard other references platform recommendation if it s not possible to provide more detail at page level make pdf link more prominent vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 23097186145.0,2022-07-26 20:50:29,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,combined fsr cfsr design discovery issue description design team familiarity and discovery related to the online financial status report experience tasks demo overview meeting with pm – q a review the to understand what the paper form looks like and what it contains review the and resources available about the fsr learn how to auto populate fsr experience explore fsr experience on staging using staging users understand different staging users and how to log in for each acceptance criteria above tasks are complete and designers have a fundamental understanding of what the online fsr experience is and what purpose it serves for veterans how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 12236445756.0,2020-05-04 16:21:45,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,other aws accounts need love to user story or problem statement as admins of all the various va aws accounts we use within our workflows we need to be more conscious of compliance security etc with the less used ones also goal ideally all the accounts would be managed in code via terraform for all resources pieces like iam users vpc s etc this may be a bit of an undertaking though so i would say the most immediate current concerns would be auditing those accounts and making sure offboarded users do not still have accounts objectives or key results this is meant to further ato compliance security better off boarding process es tasks decide as a team if we want to go ahead and try to get these accounts managed more in code or push forward for now manually remove off boarded users unused resources outdated objects etc acceptance criteria cleaner aws account management ideally in code but if nothing else the removal of old accounts resources etc should be completed within the near future how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 27405539451.0,2023-03-01 06:20:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,part heuristic evaluation workshop issue description what details are necessary for understanding the specific work or request tracked by this issue the heuristic evaluation workshop is an opportunity for the debt resolution team to collaborate creatively as a team learn about or refresh knowledge of usability heuristics and practice design thinking become familiar with the fsr form and or enhance present understanding think about possible usability improvements within current constraints tasks planning for part presentation part takes place acceptance criteria part of the the heuristic evaluation workshop has taken place ,1 15836083375.0,2021-04-06 18:50:25,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review alerts in debt letters design issue description with debt letters approaching release the design team needs to review the second iteration to determine where how alerts will display now that the pages are being broken out tasks review the debt letters ui to determine where the alerts should display create a ticket for frontend implementation including documentation for the alerts acceptance criteria designs have been updated for the alerts as needed a ticket for frontend implementation has been created and linked to this ticket ,1 25597306902.0,2022-12-01 17:07:59,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,cst use startapp in favor of startreactapp background all new apps use the startapp method to start their applications cst is doing much of the work that startapp is doing already so it makes sense to migrate to using the platform supported method this will ensure that our app continues to start up properly as we move forward considerations currently we are adding a listener to the react router history object to fire a redux action creator every time the page changes the action creator keeps track of the last page visited as well as a running log of all routes visited within the cst application it isn t clear what purpose this is done for but until we can evaluate it at some point in the future it s better to keep the functionality working we will need to get a copy of the router in the component and attach a listener to it from there the router can be injected as a prop into the component by using the withrouter hoc provided by the react router package make sure to use react router and not react router dom tasks move routes into the existing routes jsx so that all routes are in one place replace the code in claims status entry jsx with a call to startapp attach a listener to the router object in the component acceptance criteria cst is calling startapp instead of custom startup code set last page redux action is still being fired,1 20117951311.0,2022-02-07 21:43:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, the content has spelling punctuation or typo errors general information vfs team name debt resolution vfs product name medical copays point of contact reviewers practice area randi hecht content platform issue the content has spelling punctuation or typo errors issue details there is an extra space between the phone number and the comma in the pay your balance blue box there is an extra space between the phone number and a period under option pay online there is a comma missing after the date in the alert about paying your full balance link screenshot or steps to recreate img width alt screen shot at am src img width alt screen shot at am src img width alt screen shot at am src va gov experience standard other references platform recommendation delete extra space for first screen shots above add a comma after the year our style is to always have a comma following a full date in running text july vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket platform directions update issue title link to collab cycle touchpoint meeting epic add to the feedback pipeline on the platform product support board add your feedback add assignees vfs pm add labels vfs team label va gov experience standard issue number ccissuexx yy where xx is the category number and yy is the issue number per the va gov experience standards practice area labels accessibility ia content design per the va gov experience standards defect label if applicable defect defect defect defect defect launch blocking label if applicable ,1 26334762291.0,2023-01-10 13:34:16,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,refactor addtocalendar component to use new va link component once it s merged we should use the new accessible download link being added in formation pr ,1 14010905611.0,2020-10-29 06:16:48,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, take second pass review at all butler va system pages to validate mvp and consistency user story or problem statement as a veteran mc website user i must have a consistent theme across all of the pages that makes sense relate to the system and provide direction for my journey so i can quickly find the solutions and tools to support my health care journey goal does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page objectives or key results this is meant to further resources tools documentation prod cms va gov tasks complete review of system and facility pages for the following content and flow asking these questions does this content field data in this page make sense does the content field data in this page relate to this facility or system is it in the right place based on facility system how does this help with the focus of the page confirm all of the facilities are reviewed coatesville va medical center delaware county va clinic spring city va clinic document all errors items that need update and testing on each page using spreadsheet listed above acceptance criteria all node pages have been reviewed in spreadsheet and issues found have been been documented issues have been escalated for resolution using spreadsheet if issue was easily fixed issues should list fixed if they were updated in product or high lighted in red if still an outstanding issue ,1 18763891293.0,2021-11-05 20:09:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, tech debt clinic name changes in indiana west lafayette va clinic now lafayette indianapolis west va clinic bloomburg how to kb article process to change name of facility location mission and vision about us facility page itself ,1 19704239509.0,2022-01-12 19:58:41,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update status cards to align with mcp s status cards issue description during mcp s staging review we received feedback to change learn how to pay your copay bill to pay your copay bill we need to update the debt portal s status cards to follow the same content guidelines tasks update the debt portal s status cards to align with the updated mcp status cards acceptance criteria the status cards have been updated and linked in this ticket ,1 20617281410.0,2022-03-07 14:23:05,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, refactor unit test for removing a provider in a cc request when the residential address is missing tasks understand state of the data determine if the appropriate mechanisms are in place update unit tests,1 16092509495.0,2021-04-26 18:33:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in newappointmentsection we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos new appointment index jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 11387765704.0,2020-01-29 15:33:44,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, remove lodash fp from front end application code user story as a i need so that i can tasks acceptance criteria bundle size has shrunk regression testing completed site still works as before configuration attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team e g vsa authenticated exp vsa caregiver labeled with practice area backend frontend devops design research product ia qa analytics call center research accessibility content labeled with type bug request discovery documentation etc ,1 24706367113.0,2022-10-19 19:26:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,ia content edits to other expenses issue description joni s suggestions for other expenses tasks make updates to acceptance criteria uxpin link or screenshot sent to jill ,1 13389168021.0,2020-09-02 18:26:51,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,content review of debt letters mvp covid alert issue description i m looking for a content review on an alert informing veterans that va debt collection has been put on hold for the rest of the year due to covid that is doing to be displayed in the debt letters tool i ve attached a screenshot of the alert but you can also reference to see how it looks within the tool s ui note the designs linked use the right rail component we re going to be releasing a second iteration that replaces the right rail content with the on this page anchor links just wanted to give ya a heads up in case you were wondering while reviewing the content please feel free to edit this ticket to fit whatever format works best for you ,1 15817977807.0,2021-04-05 15:22:07,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update cypress tests to use best practices axe check we added a helper for the vaccine flow cypress tests called axecheckbestpractices we should use this across all of our cypress tests ac all vaos cypress tests use axecheckbestpractices instead of axecheck any revealed accessibility errors are resolved or spun into separate tickets ,1 19100061270.0,2021-11-29 21:18:53,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,redirect request for vamc lgbt web pages to new vamc lgbtq web pages story as a veteran i need to be redirected from old lgbt web page to new lgbtq web page so i assure i have the latest information and health services type of request we are retiring or taking down a page and need to redirect the url complete redirect section we are changing the url of an existing page complete redirect section we need a custom vanity url complete vanity url section implementation date immediately these pages were found to have incorrect urls on the updated webpages the new web pages will take affect asap to mitigate any broken links for veterans please process redirects as soon as possible thank you redirects current url redirect destination or new url vanity urls n a link to campaign landing page request issue process roles and responsibilities requesting team above information is provided requesting team all appropriate va stakeholders are notified as appropriate ia request is vetted and documented and implementation plan is clear ia request is assigned to appropriate team for implementation implementation team work is complete implementation team validated in production requesting team validates everything is correct in production and closes ticket ,1 23642164760.0,2022-08-25 18:09:17,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, refactor skipped test to work more consistently background we received a pr review request to skip one of our tests that often fails ci we have asked in the pr as part of our review for more information to help troubleshoot we should refactor the test in question based on this feedback so that it passes consistently pr tasks fix test update relevant documentations readme and use cases acceptance criteria test passes ci consistently code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 28069340390.0,2023-03-29 17:50:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update style of fsr link issue description add to request help with va form continuation of tasks validate and work with content team to update styling of the fsr link acceptance criteria direct link to fsr on wizard will be updated to utilize the action link style ,1 24123060865.0,2022-09-20 20:37:24,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,define three user scenarios for wizard and streamlined waiver issue description wireframes user flow for wizard and streamlined waiver with user scenarios similar to for reference three user scenarios trevor found he was charged twice for the same office visit he selects “i disagree – report an error” trevor only uses vha wizard yolanda is going to school full time received overpayment from gi bill yolanda is a full time student and does not have an income she is approved for debt forgiveness after filling out the streamlined waiver rodney makes over the threshold amount but can’t afford to pay he is not approved for streamlined waiver must fill out the full fsr for additional resolution options tasks define user scenarios acceptance criteria user scenarios created and commented in ticket,1 16596772310.0,2021-06-01 14:19:42,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in clinicchoicepage we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos project cheetah components clinicchoicepage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 19340149687.0,2021-12-15 02:51:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update correct govdelivery on vamc system pages to add the usvha story gov delivery numbers need to be correct s all subscription updates and mail will go out correctly tasks utilize cms listing of systems that do not have full usvha to numbers on the system pages for gov delivery using report update system page with correct and full gov delivery numbers acceptance criteria system pages are updated with the correct gov delivery numbers update is provided to cms so they can test report ,1 17604407873.0,2021-08-17 15:20:31,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, verify expense calculations issue description verify all expenses are being calculated correctly and passed in the fsr submission payload it was also noticed during prod uat that some values are captured as floating point values and should be restricted to decimal values tasks verify all expenses are calculated correctly format results to a fixed number of acceptance criteria expenses are calculated correctly and passed to submission payload values transmitted should be a fixed number of decimal values how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design tools be tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 24329645515.0,2022-09-30 18:06:11,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,updating urls that link to vha fsr issue description there combined debt portal is complex and has many different routes to the electronic fsr experience we have discovered pathways that aren t routing to the onlinefsr waiver submission process tasks validate that following pathways to the electronic fsr from copay cards and detailed pages acceptance criteria all links have been updated to provide veterans with a seamless experience how to configure this issue attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14240323508.0,2020-11-18 21:31:26,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update mvi statsd keys issue description following some mvi to mpi rename changes in the lib directory we will need to update any rules or grafana boards that reference the old mvi keys directly example mvi service statsd key prefix find profile total is now mpi service statsd key prefix find profile total an effort towards these changes was started here by duplicating the existing mvi board tasks update grafana promql referencing mvi keys to mpi ,1 21654327799.0,2022-05-06 12:43:49,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add footer to platform pages where it s missing user story as a persona i want to so that intended audience desired outcome due date description the is missing the footer a brief look through some other pages shows that others in the and and sections are also missing see more in the new artifacts artifacts needing updates several pages across platform that governance team manages tasks content audit each page the governance team manages to find which ones need the footer added on pages as necessary acceptance criteria confluence page name has been updated confluence page name has been created github template page name has been created github template page name has been updated platform website page name has been updated platform website page name has been created updates have been peer reviewed by governance team member user story need has been fulfilled related governance team resources for additional information and guidance to complete tasks please see links below how to configure this issue ensure that story is attached to appropriate iniative if not tech debt what body of work is this a part of ensure that any additional labels are added tech debt collaboration cycle ensure that story is in the correct pipeline backlog planned in progress review qa closed ensure that assignees are correct so you receive all updates comments on the ticket ,1 26955527594.0,2023-02-08 14:40:27,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,focus is not set to the and the change isn t clearly announced general information vfs team name authenticated experience vfs product name my va vfs feature name on site notifications point of contact reviewers brian deconinck briandeconinck accessibility for more information on how to interpret this ticket please refer to the guidance on platform website platform issue no va gov experience standard for the issue found issue details when following the manage your va debt link in the notification and going to the current va debt page manage va debt your debt focus is not set to the and the change isn t clearly announced by a screen reader screen reader users may not be certain what change has happened link screenshot or steps to recreate steps to reproduce visit staging va gov and authenticate as test user activate a screen reader recommend testing with nvda on windows or voiceover on mac press until keyboard focus is set to the manage your va debt link press to follow the link note that after the page is loaded and after the intermediate announcements while the page is loading no announcement is made for the heading press note that the first tab stop is the skip to content link va gov experience standard other references platform recommendation the behavior typically exhibited across va gov would be for focus to be set to the current va debt on page load and the next tab stop to be the first link that follows that heading since that s the main interaction pattern following the link in the notification should match that pattern the actual impact on users is relatively minor the first tab stop is a skip link that takes them to the place they d expect to go but it s a deviation from the expected behavior that might trip up some users not sure if this is actually in scope for onsite notifications or if it s an issue with the current va debt page but flagging anyway so it can be assigned to the appropriate team as needed vfs team tasks to complete comment on the ticket if there are questions or concerns close the ticket when the issue has been resolved or validated by your product owner if a team has additional questions or needs platform help validating the issue please comment in the ticket ,1 18948789923.0,2021-11-18 13:10:35,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, add content to fsr s confirmation page indicating that veterans will receive an email confirmation issue description we re adding an email notification via vanotify that confirms that an fsr has been submitted we should update the confirmation page to notify veterans that they will receive a confirmation email so they know to expect it tasks update the fsr s confirmation page to indicate that the veteran will receive an email confirmation acceptance criteria updated design has been linked in this ticket a ticket for frontend implementation is linked in this ticket ,1 24644696863.0,2022-10-17 14:06:39,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, utilize the term overpayment issue description consider using the term overpayment when referring to debt caused by an overpayment several participants mentioned overpayment when defining debt one participant stated he liked when it was mentioned so it doesn t make you feel fraudulent and makes the dispute process easier tasks discuss where utilizing the term overpayment makes sense acceptance criteria issue discussed with stakeholders and content team to determine next steps,1 22150363600.0,2022-06-03 16:06:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,collaboration cycle kickoff the debt resolution team combined va debt portal steps to complete the collaboration cycle kickoff vfs product manager create this issue and notify the collaboration cycle team of this ticket in the in vfs platform support answer the questions below and attach any artifacts you have available close this ticket when kickoff is complete and platform has provided the recommended touchpoints platform review the responses and comment in ticket with recommended touchpoints and practice area involvement platform add project to the artifacts if available provide links or documents for the following questions please refer to the guidance in for detailed information and examples for the below questions will your work result in visible changes to the user experience yes no examples of visible changes include any changes that the user will see adding a new form tool or page modifying buttons design elements interactions or page layouts reordering content adding new calls to action alert boxes expandable sections or error messages examples of no visible changes include changes to code that the user won’t see changes to accessible labels these might include aria label aria labelledby aria describedby is your work a new product or an iteration to an existing product new iteration examples of a new product or feature include migrating over a paper form that has new design components creating a new design component to a page layout adding new functionality to an existing tool that is completely new to va gov examples of an iteration to an existing product include modifying or adding functionality an interaction or content to an existing page adding additional form fields or interactions to an existing online form re organizing content adding headings subheadings new paragraph order if this is an iteration please tell us what product or feature you re iterating product or feature we are combining and into the combined va debt portal are you making changes to the visual design yes no examples of changes to the visual design include any changes to design components buttons layout or patterns any changes to colors icons or typography examples of no changes to the visual design include code only changes are you doing research with va gov users yes no examples of research with va gov users include usability testing user surveys card sorting will your work involve changes to select all that apply tools and applications static pages both for tools and applications take into account if any static page entry points will need updates will your work include new content changes to existing content are you making a change to the user flow yes no examples of changes to the user flow include adding a new section to a form moving from a wizard to one thing per page form model are you making a change to urls navigation or entry points yes no examples of changes to url navigation or entry points include moving an online tool or content page within the site or retiring or redirecting a page modifying options within core navigation elements for example top nav left nav home page does your product or feature have google analytics tracking and a kpi dashboard in domo yes no the vba debt portal and medical copay tool have ga tracking and a kpi dashboard in domo i imagine we ll iterate on these as we move towards the combined experience if yes do you need to capture any other analytics or metrics in addition to what you re currently tracking yes no is there a github label in the va gov team repo for this product no yes please specify combinedvadebt who is the va business owner for this body of work vha veterans health administration vba veterans benefits administration nca national cemetery administration vaco veterans affairs central office other please specify additional information please refer to the guidance on platform website for more information about the collaboration cycle fyi shiragoodman chaseakirby ,1 18734123463.0,2021-11-04 03:42:58,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, update current policies page with new hardened policies page for all remaining systems and publish user story as a vha digital media web manager nationalized content should be isolated so i can focus on local and regional policies and issues goal remove tech debt for all new hardened policies pages resources tools documentation tbd tasks update all remaining systems that still have old policies page with new hardened content page copy old data from policy page delete any instance of a policies url create new content page content add content vamc policies page save new hardened page with content copied from old and it should replace old in list confirm policies replaced is either draft or archive status acceptance criteria all policies pages have been updated to hardened page and published old pages now state policies replaced,1 19562919431.0,2022-01-03 18:53:37,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace manifest json imports with getappurl background our application on vfs has very long build times with lots of flakey unit tests that fail in builds often this is mostly due to the fact that when a build is run all of the apps have to built at the same time to combat this the vsp team has undertaken an initiative to break the apps up and isolate them so that each app can be built independently to do our part we need to get our apps ready for this new build process to do this we need to utilize the getappurl registry helper to remove any import to manifest json in our apps considerations note imported from refers to other applications importing this apps files imported to refers to applications that are importing files from other applications apps we own src applications disability benefits src applications disability benefits view payments src applications lgy coe src applications personalization rated disabilites imported from src applications personalization view dependents importing to dependency verification src applications personalization view representative src applications static pages dependency verification imported from view dependents src applications vre importing to src applications vre importing to tasks search for all manifest json imports from other apps in our apps and replace them using getappurl acceptance criteria all imports of other applications manifest json file should be replaced with getappurl a pr is in place for review,1 16048428762.0,2021-04-22 16:05:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,replace connect with hooks in requestedappointmentslist we want to update the way we use react redux to the current recommended approach which is to use the useselector and usedispatch hooks path src applications vaos appointment list components requestedappointmentdetailspage jsx docs note it s worth paying attention to the section if a selector is returning an object that object is changing each time the selector is run and we re just using individual properties within that object consider using shallowequal ac connect is no longer used on page all actions that were in mapdispatchtoprops are now wrapped in dispatch when called all data in mapstatetoprops is pulled in through useselector hooks,1 29495281542.0,2023-06-02 16:24:40,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, investigate and clean up sentry errors issue description seeing some new issues crop up in mostly failed to fetch errors coming from what looks like save in progress put but they are showing as new investigate and clean up sentry logs to reduce noise as we prep to move into staging review errors seem infrequent enough to not cause concern but warrant further investigation i normally use the following filter for fsr is unresolved location generated request debt help form entry js note things like t props onextendsession is not a function can be marked as resolved in sentry ui since it has been tasks investigate sentry error logs clean up resolved issues generate any new tickets as necessary for errors that need further investigation handling acceptance criteria sentry logs are cleaned up so we can better track any new issues that may appear from staging review go live how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 13306238407.0,2020-08-25 19:53:57,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dl usability topline summary issue description create a topline summary based on the debrief session discussions tasks conduct debrief sessions consolidate debrief impressions into a topline summary upload topline summary into gh optional if applicable create a short deck for demoing topline summary acceptance criteria upload topline summary into gh ,1 14960073198.0,2021-01-27 04:52:32,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, manually migrate facility health services from blobby plain text to detail field front end for va montana health care system facilities story as a veteran i need to see all of the facility health services in a detail manner so i can best verify my required contact information by health service in each facility resources tasks move all data in the current blobby text field down into detail fields if information is same as default information then confirm that the use default information is checked and move to next field to include is a referral required are walkins accepted is online scheduling available phone number for appointments service location address if different than default hours if different than default contact info if provided in detail complete the above for the following systems va montana health care anaconda va clinic benjamin charles steele va clinic bozeman va clinic cut bank va clinic david j thatcher va clinic fort harrison va medical center glasgow va clinic glendive va clinic great falls va clinic hamilton va clinic kalispell va clinic lewistown va clinic merril lundman va outpatient clinic miles city va medical center plentywood va clinic acceptance criteria all facility health services are updated contact pm on how to best confirm data is accurate ,1 26002856745.0,2022-12-20 16:38:54,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, use redux store for all errors before routing to error page description issue created from this store all errors as strings in redux state ie dispatch the seterror action when an error occurs usually in a side effect like an api call dispatch seterror bad token create a higher order component to wrap the application and handle errors by routing the application to the error page later this could include more robust error reporting using ga sentry or datadog this also give us the flexibility to create other side effects like add more information to the state object for more complicated error messaging useeffect if error gotoerrorpage error the router utility gotoerrorpage will use the error string to add a query string to the url for ga tracking this gives us more flexibility to get creative with the url parameters replace utility functions like appointmentwascanceled in the error page for pre check in with a check against the error string in the redux store if error appointment cancelled tasks on error dispatch seterror action create hoc for routing and other side effects modify gotoerrorpage to use error type instead of full url parameter replace redundant use of utility functions with error type from state create or update unit tests create or update tests update relevant documentations readme and use cases acceptance criteria passes accessibility checks using axe deployed to staging tested on staging designer has signed off on the feature product team has signed off on the feature prod validation not necessary scheduled code review steps read ticket details and verify that acs are met review code in pr run branch locally check that new and updated translations use new keys check for hardcoded strings ,1 19897729264.0,2022-01-25 02:18:50,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, review and validate vamc system pages have operating status link is in place story as a veteran i need to have a link to the operating status on the system page so i can quickly find facility operational status resources tasks review the vamc system pages and confirm that operating status link is correct and updated acceptance criteria validation of all vamc systems have operating status complete ,1 16771194584.0,2021-06-14 14:58:30,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,explore ways to improve verification of ics files our test code to verify that ics files for calendar appointments are correct is very verbose it doesn t necessarily validate that the file is a valid ics file either we should look into some ways of making it easier to verify the content of these files tony wrote some code to break the file into tokens ac tests checking ics file data are more readable and less verbose stretch goal ics files are verified to be valid against the ics file spec,1 19683585378.0,2022-01-11 19:21:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,update wizard content and links technical task assuming that wizard content and links and been solidified we need to update them according to content and design recommendations expected behavior update scaffold to contain finalized content and links acceptance criteria add updates when finalized here ,1 23988571164.0,2022-09-13 21:37:34,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,add product directory update action to staging review and kickoff user story as a vfs pm i want clear guidance for how to update the product directory so that i am able to provide updates and verify information as a qa standards team member i want vfs pms to update the product directory so that our process can run and load data mapped to their manifest file assignee cherylevans peer reviewer briandeconinck description qa standards is ready to roll out the product directory they would like to leverage the collaboration cycle to request that teams verify their information in the directory for existing products vfs teams can verify their product information at any time however for new products this needs to be late enough in the process that code has been written so that the manifest file is generated after walking through the collaboration cycle process as is and slack discussions we determined that it would make the most sense to include two actions for vfs teams to verify their entry in the product directory at collaboration cycle kickoff and at staging review this will allow the qa standards teams process to run and process data that will run test cases chase met with curt and peter on to discuss and determine best location for this checkbox impacted artifacts tasks add if your product is already on va gov please verify your product information in the product directory checkbox to vfs product information section of yaml template pr add guidance to platform website collaboration cycle kickoff for new checkbox link to qa standards teams documentation for how to verify their entry staging review add please verify your product information in the product directory checkbox to the vfs actions section of the staging review code block link to qa standards teams documentation for how to verify their entry add please verify your product information in the product directory checkbox to the vfs actions section of the deprecated staging review template pr link to qa standards teams documentation for how to verify their entry add guidance for platform website staging review for new checkbox link to qa standards teams documentation for how to verify their entry update open collaboration cycle request tickets with checkbox announce change to staging review update gov team decided it is not necessary to post updates to slack as qast had already announced that vfs teams would begin to see the product directory integrated into their collab cycle touchpoints need to determine appliable channels peer review ticket reassigned to peer reviewer when ready for peer review peer reviewer completes review and validates user story acceptance criteria are met acceptance criteria vfs teams are asked to verify product information in the product directory within the collaboration cycle process qa standards team has a defined touchpoint that they can expect teams will verify their information in the product directory how to prepare this issue attach story to appropriate initiative or quarterly tech debt epic add user story description tasks and acceptance criteria add any once all above items are checked add the ready label ticket has been discussed as a team at planning ticket has been sized as a team ticket has been assigned to a sprint once assigned to the upcoming or current sprint move to the planned pipeline once assigned to the upcoming or current sprint add assignee and specify peer reviewer ,1 27266214383.0,2023-02-22 18:14:56,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team, dependent page enhancements review page issue description remove existing dependents list loop and implement new input number of functionality tasks update dependents page with fsr enhancements to support a review section acceptance criteria new dependents page s are functioning as anticipate and match mockup and edit on review section how to configure this issue attached to a milestone when will this be completed attached to an epic what body of work is this a part of labeled with team product support analytics insights operations service design console services tools fe labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content labeled with type bug request discovery documentation etc ,1 14491381461.0,2020-12-11 04:31:46,department-of-veterans-affairs/va.gov-team,https://api.github.com/repos/department-of-veterans-affairs/va.gov-team,remove to pdf stubs in integration test for deliverpdftocarmajob spec description the deliverpdftocarmajob has an integration test to ensure that all the pieces work together to deliver the attachment to carma in this spec we stub to pdf because the cassette has a file contents of the string encoded this is a problem since we do not get a full test of adding the job to the queue generating the pdf delivering it and deleting the related resources risk if changes were made to the pdf generation process or how it s attached to the request to carma we could potentially not have a failing test signifying that the bug was introduced accept criteria remove the to pdf stub in order to have a full top to bottom integration test ,1