[CST] [ENG] Claim updates on the status page

uxgary commented 6 months ago

Value Statement

As a Veteran who prefers to see claim details at a glance, I want to be see a snapshot of my claim details on the status page So that I can see pertinent information like current step and brief description without seeing the full claim details

Background Context

As part of improving the claim phase experience, we aim to increase transparency on the background process of claims. To start, we are expanding the claims steps from 5 to 8 steps and providing a brief description about each step. Additionally, we are providing claims updates so Veterans can have a better sense of where they are in the claims process.

For additional information see resources listed below:

Collaboration Cycle for Benefits team 1, Claim status tool , Claim Phase Experience

Status page	Overview page (title reference)

Related Issue(s)

department-of-veterans-affairs/va.gov-team/issues/82376

New Feature

Why are we doing this work?
Epic Link, Expand Claim Phases

Design

Ensure revised mocks are ready for engineers
Figma file for visual reference
Figma design for Overview accordion header
Content file containing the body copy for the status page

Enablement team (if needed)

@member of team

Engineering

We want the date displayed in the description the phasechangedate
Will use the field claim.attributes.claimPhaseDates.latestPhaseType for the status for the 8 steps

Out of scope

Add here

Open questions

What does the "Learn more about this step" link go to?

Tasks

[x] use the content doc for the description blurb for each phase on the claim card
[x] Header title should match the accordion headers on the overview page (ie. Step 2 of 8: Initial review, Step 3 of 8: Evidence gathering)
[ ] Add new field with text 'Moved to this step on '
[x] "Learn more about this step" link navigates to the overview page

Definition of Done

[ ] Meets acceptance criteria
[ ] Passed E2E testing (90% coverage)
[ ] Passed unit testing (90% coverage)
[ ] Passed integration testing (if applicable)
[ ] Code reviewed (internal)
[ ] Submitted to staging
[ ] Team approved production verification process
[ ] Design performs design QA and verifies the implementation matches the design spec
[ ] Accessibility specialist performs accessibility review (in code or design)
[ ] Engineering identifies staging users required to test and shares account and credentials with design and product
[ ] Product performs functional QA and verifies acceptance criteria was met

Acceptance Criteria

[x] There is header text for claim phases 1-7 in the "What We're Doing" component and the number and step description matches exactly what is used as headers on the Overview page.
[x] The part of the header that mentions the claim "step" matches exactly the name of the step on the Overview page for the new timeline; When a user is on step 1 of 8 the header shows and the description shows
[x] The description for each phase matches the "What We're Doing" text from this doc consistent with the phase steps.
[x] There is a link to the overview section of CST that says "Learn more about this step"
[x] There is "moved to" text that clearly calls out the date the claim moved to this step.
[x] Behind cst_claim_phases feature flag

uxgary commented 6 months ago

I've created a google doc with the content we can use for the status page content.

pmclaren19 commented 6 months ago

@uxgary we took a look at this during Eng Refinement.

This ticket/mocks are lacking information that engineering will need to work and point this. We need answers to the following things before we can do that...

This is tickets supposed to be a design and eng ticket or just eng? Noticed you added design tasks for information that is crucial for eng
If this ticket relies on the google doc that you commented about I think that should be called out in the actual ticket description. Also your google doc is noting what you want in the overview tab not the status tab so confused on the desired changes.
There should also be tasks to note what you expect to be changed EX: When a user is on step 1 of 8 the header shows <this> and the description shows <this>. Is there anything else other than the header and text that is changing?
Should this be behind a feature flag?

Let me know if you have any questions about this.

pmclaren19 commented 6 months ago

Noticed that the google doc and the design doc had different text for the Step 8 Heading - discussed with @uxgary and he updated the design docs to reflect this update. Slack convo here https://dsva.slack.com/archives/C056854SVT8/p1717016613526739

Updating pr to reflect this change!

pmclaren19 commented 6 months ago

When a claim is closed we do not show the what we're doing section. Talked to @uxgary and this functionality will remain. I will update the AC from

There is header text for each claim phase in the "What We're Doing" component and the number and step description matches exactly what is used as headers on the Overview page.

to

There is header text for claim phases 1-7 in the "What We're Doing" component and the number and step description matches exactly what is used as headers on the Overview page. FYI @jacobworrell

pmclaren19 commented 6 months ago

@uxgary please review for qa design.

uxgary commented 6 months ago

Reviewed, this passes.

department-of-veterans-affairs / va.gov-team