Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG - sev-3 - All - Typo in share app message #10275

Open
5 tasks
TKDickson opened this issue Nov 26, 2024 · 11 comments
Open
5 tasks

BUG - sev-3 - All - Typo in share app message #10275

TKDickson opened this issue Nov 26, 2024 · 11 comments
Assignees
Labels
bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work global Issues for the global team sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this

Comments

@TKDickson
Copy link
Contributor

What happened?

There's a typo in the message that's created for veterans when they select "share the app" from the settings screen

It currently reads (feel the missing word 'app' in here):
'Download the VA: Health and Benefits on the App Store or on Google Play'

Image

Specs:

  • Device:
  • OS:
  • User Account:
  • Accessibility State:

Steps to Reproduce

Log in > Profile > Settings > Share the app > pick a venue to share the app (like email)

Desired behavior

Have asked Misty if she wants to add 'app' or remove 'the' (DSVA slack thread)

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

  • Impact: Low
  • Frequency: Low
  • 3 - Low

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 TKDickson added bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work global Issues for the global team sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this labels Nov 26, 2024
@mistymg
Copy link
Contributor

mistymg commented Nov 27, 2024

@TKDickson Thanks for catching! Let's go with "Download VA: Health and Benefits on the App Store or on Google Play"

@jennb33
Copy link

jennb33 commented Dec 11, 2024

12/11/2024 - @kellylein @timwright12 @oddballpete @Eallan919 @ATeal @TKDickson The MFS team will be taking this ticket into Sprint 7, (12/14/2024-12/27/2024)

@kimmccaskill-oddball kimmccaskill-oddball self-assigned this Dec 11, 2024
@kimmccaskill-oddball
Copy link
Contributor

@mistymg Hi Misty! Just to clarify, it should say
"Download VA: Health and Benefits on the App Store: (insert link here) or on Google Play: (insert link here)"
correct? With the colon and the link

@mistymg
Copy link
Contributor

mistymg commented Dec 12, 2024

@kimmccaskill-oddball we can't hyperlink the words "App Store" and "Google Play" can we? That's the most ideal situation. So it'd be like this:

Download VA: Health and Benefits on the [App Store] or on [Google Play]

If we can't do that, let's go with this, so the link for each play store is in a parentheses:

Download VA: Health and Benefits on the App Store ([insert link here]) or on Google Play ([insert link here])

@kimmccaskill-oddball
Copy link
Contributor

kimmccaskill-oddball commented Dec 12, 2024

@mistymg Without opening up too big of a can of worms, here is the CURRENT experience. The full "message" isn't displayed and the user's only option is to copy the text(which they can't see the entirety of what they are copying).
Image

For now and to maintain scope of this ticket, I'll just fix the text as you mentioned in the latter part of your message 😅

@mistymg
Copy link
Contributor

mistymg commented Dec 12, 2024

@kimmccaskill-oddball I think maintaining ticket scope and going with the latter options is fine. Thanks for picking this up!

@jennb33
Copy link

jennb33 commented Dec 13, 2024

@kimmccaskill-oddball - do I need to roll this ticket for future release? Let me know... Thanks!

@kimmccaskill-oddball
Copy link
Contributor

Link to PR

@jennb33
Copy link

jennb33 commented Dec 13, 2024

Bumping this ticket to Sprint 7 to preserve original Core Mobile work and to prep for release in Sprint 8.

Per @kimmccaskill-oddball:
Because all the sprint 7 work is going to be released sprint 8, that makes sense to put it [in Sprint 7] as I don't anticipate it being merged EOD since it is a ticket that also technically needs to go through QA as well.

@kimmccaskill-oddball
Copy link
Contributor

Image

@kimmccaskill-oddball
Copy link
Contributor

Image

@jennb33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work global Issues for the global team sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this
Projects
None yet
Development

No branches or pull requests

4 participants