Open shiragoodman opened 1 year ago
@shiragoodman it's my understanding that work on legacy secure messaging is not going to be prioritized over work on the new secure messaging tool. We've asked the secure messaging team if we're able to link to the new tool as that would resolve this issue since there are indicators about unread/new messages to align with the dot on My VA, but the agreed plan with MHV stakeholders is to not provide direct access to the tool until phase 2, so I don't see this being resolved any time soon. (More details in this thread)
thanks @ajakabcin. I am going to remove your team label and product label from this ticket.
Question you might know the answer to... why does MyVA even link out to the legacy MHV secure messaging in the first place? Has it always or was this a decision made a while back?
Yup! this has always been the practice on My VA for health care tools/resources. Prior to the migration work, that was the only place to send users to complete health care tasks. Our research/data shows that veterans prefer to have access to all of their benefits (including health) in one place.
General Information
VFS team name
Authenticated Experience
VFS product name
My VA
VFS feature name
Dot indicator
Point of Contact/Reviewers
Erin White - @erinrwhite - IA Brian Smolensky - @BSmolensky - Content
*For more information on how to interpret this ticket, please refer to the Anatomy of a Staging Review issue ticket guidance on Platform Website.
Platform Issue
A user flow doesn't provide content or navigation to help users understand where to go or what to do next.
Issue Details
When a user clicks on the "Go to my inbox" from My VA and is sent to MHV secure messaging, there is little visual information towards the top of the secure messages page that indicates why there was a notification - except the red text that matches the color of the notification dot, urging Veterans to call 911 if experiencing a medical emergency. After scrolling down, new messages are indicated in bold. This is not launch-blocking, and might be beyond this team's purview, but could be confusing for users.
Link, screenshot or steps to recreate
VA.gov Experience Standard
Category Number 03, Issue Number 02
Other References
Platform Recommendation
Possible solutions would involve changes to the MHV secure messaging page. I understand if this is not within the team's span of control or influence.
Please clean up this page.
VFS Guidance