QA: claim and appeal status | issue text of board appeals, supplemental claims, and higher level reviews

[amylai-va]

Objective

Veterans see accurate information about the issues (or conditions) they are claiming for their board appeal, supplemental claim, and higher level review.

Reference Material:

• The Caseflow team made updates to the Caseflow Appeals API, specifically to the issue text description.
• This change impacts board appeals, supplemental claims, and higher level reviews, since information about these 3 decision reviews are retrieved from the Caseflow API
• Previously, the issue text description reflected the description of the diagnostic code that was used to rate the condition, not the thing the Veteran was filing a decision review for -- this was a source of confusion for Veterans. Certain descriptions were also vague and not meaningful to the Veteran (e.g., "compensation issue")
• Now, the issue text description will either reflect the description of the "request issue" or "decision issue" from Caseflow.
  • If a decision has been made, the issue text description will reflect the "decision issue"
  • If a decision has not been made, the issue text description will reflect the "request issue"

Known test data:

• VA.gov staging users and test scenarios: https://dvagov.sharepoint.com/:w:/s/vaabdvro/EZOo7mGngHRIqnxu9Lm2Uc0BSDD64H_6Y4mKIHRPHv-SOg?e=rZmEh1

Epic(s)

Ticket Checklist

• Acceptance criteria defined
• Labels added (front-end, back-end, feature)
• Linked to an Epic

Acceptance Criteria

1. • Create test plan
2. • Link to test case folder in TestRail
3. • List of test data (or other testing needs) for Product
4. • QA peer review of test plan & cases complete (sent out & feedback incorporated)
5. • Decide if a feature signoff is needed. If yes, create the ticket and link to the appropriate epic.
6. • Socialize the testing plan with relevant practices (Eng, UX, Product)

Notes: