VA Health Chat: Implement static link under More resources & support

wesrowe commented 4 months ago

Description

User story

As a Veteran, I want the link to VA Health Chat to always be visible on the MHV landing page, so that I have a chance to use this new service.

Notes

In discovery ticket #86573 we determined that VA Health Chat will inform users in the case they can't use it, either because 1) it's not open right now or 2) the user is not eligible. Thus the MVP is simply the link as the chat application will do the rest.
Opens in same tab
Proposed link text: "Chat live with a health professional on VA Health Chat"
Link destination (per discovery ticket): https://veteran.apps.va.gov/users/v2/login?redirect_uri=/cirrusmd
PoC: Hugo Padilla – best reached on Teams or via email. Copy Patrick on comms.

Design:

Possible tasks:

Acceptance criteria

(UX) Confirmed link text with UXers
A link exists at the top of the "More resources and support" column to the web-based Health Chat
- Put it behind a FEATURE TOGGLE so that it only appears in Staging
Confirmed in code that we expect a GA event to fire when link is clicked
24 HOURS BEFORE ~HITTING MERGE~ enabling feature toggle, checked in with Hugo (see Notes) via email/MSTeams
Post-merge, ensured link is tracked in GA4
Enabled for Kaitlin in prod so that she can smoke-test the link
QA review
A11y review if needed
Updated ticket for roll-out using feature toggle with correct toggle name

wesrowe commented 3 months ago

Moving this out of sprint 36 due to slack discussion with OCTO folks, which appears to have added an interstitial page as a dependency for adding the actual link (pending outcome of #88881).

wesrowe commented 3 months ago

met with OCTO trio today, we have agreement that the static-link approach is best. Rationale: an interstitial page on VA.gov would not be personalized at all, whereas the VAHC experience is personalized/dynamic – e.g., it shows the user what they can do in their VISN and whether those channels are open right now.

batemapf commented 2 months ago

recommend also making sure VA Health Chat team knows when we're adding the link in production just in case they have have maintenance or something out of the ordinary planned.

fmccaf1 commented 2 months ago

Screenshot to link added to landing page:

Link to figma file

allanto-ah commented 2 months ago

Environment: Staging

Verified that the chat link appears as expected and is directed to the URL listed in the description of this ticket

wesrowe commented 2 months ago

Smoke-test slack thread with Kaitlin: https://dsva.slack.com/archives/C0581MN69TJ/p1723236970402709

EDIT: it turned out the code hadn't made it to prod yet

wesrowe commented 2 months ago

Stephen Barrs is going to smoke test this for us on 8/13. I enabled his user in Prod.

carlosfelix2 commented 2 months ago

Per smoke tests and a meeting held 8/21/24 with Cirrus MD, we found that the chat is not letting users to use SSOe to automatically authenticate into Health Chat. The Cirrus MD team is investigating this issue.

carlosfelix2 commented 2 months ago

This is the URL MHV Classic uses to go directly to the chat: https://eauth.va.gov/MAP/users/v2/landing?redirect_uri=/cirrusmd/

wesrowe commented 2 months ago

I just saw in slack that Stephen was able to coax VAHC into accepting his SSO by opening in a new tab (necessary?) the url [edited] https://eauth.va.gov/MAP/users/v2/landing?redirect_uri=/cirrusmd/.

allanto-ah commented 2 months ago

In latest conversation in Slack. Testing in production was successful for Kaitlin Fink, but sometimes worked for Steven Barrs. Carlos is meeting with the Cirrus MD team to see if the above URL is the correct link or not

wesrowe commented 1 month ago

On hold for now, see comment in epic for details.

wesrowe commented 3 weeks ago

this is in prod, can ticket close?

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