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 - The notification onboarding screen does not appear in the onboarding flow after hitting reset first time login in the dev menu #10134

Open
5 tasks
rbontrager opened this issue Nov 7, 2024 · 6 comments
Assignees
Labels
bug Used to identify a bug ticket that will be worked through the bug process global Issues for the global team QA Tickets require QA work / review scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this

Comments

@rbontrager
Copy link
Contributor

What happened?

The push notification onboarding screen does not appear in the onboarding flow after hitting reset first time login in the dev menu.

Specs:

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

Steps to Reproduce

  1. Navigate to the dev menu and tap 'reset first time login'
  2. Navigate through the onboarding flow and notice that the notification screen is not displayed.

Desired behavior

Acceptance Criteria

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking 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)
@rbontrager rbontrager added bug Used to identify a bug ticket that will be worked through the bug process QA Tickets require QA work / review sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this labels Nov 7, 2024
@TKDickson TKDickson added the global Issues for the global team label Nov 8, 2024
@rbontrager rbontrager added the scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness label Nov 13, 2024
@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)

@jennb33
Copy link

jennb33 commented Dec 20, 2024

12/16/2024 - PR to @donmccaughey for review and approval

@jennb33
Copy link

jennb33 commented Jan 2, 2025

1/2/2025 - rolled ticket to Sprint 8 due to the holiday.

@jennb33
Copy link

jennb33 commented Jan 2, 2025

1/2/2025 - PR to Don for review and approval

@jennb33
Copy link

jennb33 commented Jan 3, 2025

1/3/2025 - @donmccaughey has approved this ticket and it is ready for the next release deploy (1/22/2025)

@jennb33
Copy link

jennb33 commented Jan 10, 2025

1/10/2025 - Rolling to Sprint 9 for next release (goes out 1/22/2025; is live in stores on 1/28/2025)

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 global Issues for the global team QA Tickets require QA work / review scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness 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