(PW) Sprint 7 Priorities & Candidates

[FranECross]

Sprint Priorities

🥅 Goals 🥅

Preview Give feedback

1. 📣Drupal: [Aging Content] Implement text for Developer Configuration Drupal fields #18019
2. 📣FE: [Link Behavior] Correct external link behavior based on updates to design standards #18287
3. 📣UX: #TBD

Candidates for Sprint 7 (June 26, 2024 to July 09, 2024)

Drupal

🥅 [Aging Content] Implement text for Developer Configuration Drupal fields

• Value Prop: Ensure the configuration fields, for configuring Aging Content Notifications are, are easily understood by implementing verbiage provided by UX.
  • Note: This is from Sprint 6 and is blocked on 18005, and since 18005 is also updating Expirable Content, we'll need to wait for that to merge before we can proceed with this work.
  • [Aging Content] Implement text for Developer Configuration Drupal fields #18019

👉🏼 [Aging Content MVP] Notification emails need to be able to limit sending to specific users/email addresses

• Value Prop: Ensure the notification emails are sent to appropriate people, and not only the last published (since that could be a system publish event).
  • [Aging Content MVP] Notification emails need to be able to limit sending to specific users/email addresses #18311

Front-end

🥅 [Injected (TeamSites) Header/Footer] Complete implementation of authentication code #17291

• Value Prop: As a Veteran, I want to see a fully functional, not regressed, copy of the VA.gov header and footer on TeamSites pages so that I have a consistent visual and functional experience on all VA websites. To achieve this, we are separating the injected header/footer code from the global, new header/footer code so that unintended regressions don't continue to occur, and also so that the DST can componentize the global header/footer when they are ready to do so.
  • Note: This is carrying over from Sprint 6 due to the complexity of code and testing effort.
  • [Injected (TeamSites) Header/Footer] Complete implementation of authentication code #17291

👉🏼 [Link Behavior] Correct external link behavior based on updates to design standards (2pts)

• Value Prop: Ensure PW products & features are following the new design standards set forth by CAIA so that Veterans, their family members, caregivers and survivors have a consistent experience across VA.gov.
  • [Link Behavior] Correct external link behavior based on updates to design standards #18287

👉🏼 [V3 Components] Update va-button, va-link, and va-action link web components now that the DST has released their fixes/components

• Value Prop: Ensure Veterans, their family members, caregivers and survivors don't experience visual anomalies due to missing components. Note: There were 2-3 tickets the DST hadn't released yet, that were released in the past few days, so the tickets below may now be worked on.
  • [Web Component] Use the <va-button>web component for the homepage email signup form #17790
  • [Analytics] [Find a Form] Custom GA events removal & adoption of "action link" va-link component w/analytics #18346
  • [Analytics] [Campaign Landing Pages] Custom GA events removal & adoption of "action link" va-link component w/analytics #18345
  • [Analytics] [Header] Custom GA events removal & adoption of va-link component w/analytics #18347
  • [V1 & 3 Components] Implement the V3 Action Link component in the PACT Act Wizard #17404
  • [EPIC] [V3 Components] Update Action Links to the new V3 component #17557
  • [V1 & 3 Components] Implement available components for Income Limits #17276
  • [Analytics] [Events] Custom GA events removal & va-link component w/analytics adoption #18200

Stretch Goal 👇🏽

👉🏼 [Discharge Upgrade Wizard] Continue to modernize & convert to Subtask pattern > (#8) FE: Start Results Page

• Value Prop: As a Veteran, or caregiver of a Veteran, I need the Discharge Upgrade Wizard to be easily understood a navigable SO I can complete it accurately and improve my chances of my discharge upgrade request being approved.
  • [Discharge Upgrade Wizard] (#8) FE: Start Results Page #16917

UX / Research

🥅 TBD

• Value Prop:

  • #

[jilladams]

From planning we discussed:

• Analytics / component work remaining has no hard deadlines
• Analytics team is behind on processing our spreadsheet. We may need to revisit tickets we do now, after they do their work.
• We will be migrating to AP. We could wrap remaining component / analytics work into AP migrations.

Since we're megateam now and have an opportunity to have FE folks do big rock work across initiatives, we're going to hold off on Analytics/components tickets for now.