BUG - sev-3 - All - No veteran will ever see the "enroll in VA healthcare" banner

TKDickson commented 6 months ago

What happened?

How to determine if someone is enrolled in VA healthcare

A non-veteran (like @dumathane who has a production id.me account) will be authorized for appointments via the return in authorized services. See long DSVA thread for more details.

this is (effectively) the policy for appointments: user.icn.present? && user.loa3?

Which means that the "enroll in VA healthcare" banner that we've added to the health category screen with HSP (which shows if you don't have appointments, Rx, messages or..... I want to say vaccines in your auth services) will never appear.

Specs:

Device:
OS:
User Account:
Accessibility State:

Steps to Reproduce

Desired behavior

We might eventually be able to key off of a new/different API (backend investigation ticket #8589). We are blocked until that ticket is resolved.

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See [Bug Tracking](https://department-of-veterans-affairs.github.io/va-mobile-app/docs/QA#issue-severity) for details on severity levels

Impact: High Low
Frequency: High Low

3 - Low
2 - High
1 - Critical

Linked to Story

Screen shot(s) and additional information

Full JSON response for services related to issue (expand/collapse)

Ticket Checklist

[ ] Steps to reproduce are defined
[ ] Desired behavior is added
[ ] Labels added (front-end, back-end, global, Health, relevant feature, accessibility, etc)
[ ] Estimate of 1 added (for front-end tickets)
[ ] Added either to the relevant feature epic (if found during new feature implementation), or the relevant team's bug epic (Global, Health & Benefits, API, QART)

TKDickson commented 4 months ago

Update, it's possible to use a different endpoint to get this info (!) and the BE team has a ticket in their backlog for it, which they added as a blocker here, #8786.

TKDickson commented 4 months ago

Confirmed with the backend team that the endpoint created in #8786 is ready to be used for this banner. They're still investigating whether it should be used for other authorization policies or not, so --- do not expand beyond healthcare, without talking with BE first. Moving this out of blocked.

dumathane commented 4 months ago

We need to have a PM chase down with the web health folks what logic they are using to display the enroll in healthcare banner in order to continue developing this. This may include the linked api that we can ingest if we are certain, but should we only display the banner if they are not enrolled? Should we continue to check for this status? Alayna you can discuss with me if you're confused.

timwright12 commented 3 months ago

@ala-yna (because there was no ping in the pervious message)

ala-yna commented 2 months ago

Based on the work done in https://github.com/department-of-veterans-affairs/va-mobile-app/issues/8786 it seems like this issue should be workable now - moving to Pending Handoff

department-of-veterans-affairs / va-mobile-app