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 - sign out button is sometimes not available on the settings screen #9628

Closed
5 of 7 tasks
TKDickson opened this issue Sep 19, 2024 · 1 comment
Closed
5 of 7 tasks
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 mobile-feature-support 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
Milestone

Comments

@TKDickson
Copy link
Contributor

TKDickson commented Sep 19, 2024

What happened?

The sign out button should always, no matter what state the app or any given API is in, be available on the Settings screen of the app.

However, the way the screen is currently structured, it's 1) possible to 'hide' the sign out button and 2) easy to do without realizing it. This PR to fix bug ticket #9189, for instance, will have a full screen error (when the authorized services API isn't working) and the sign out button will not be available/showing on the screen.

Specs:

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

Steps to Reproduce

  1. Use Charles Proxy to block, or modify into an error state, the authorized services return during login
  2. Go to Profile > Settings
  3. Notice that there is no sign out button, just the error state alert component

Desired behavior

Sign out button should always be available

Acceptance Criteria

  • Sign out button always available on Settings screen, no matter the app or API state
  • Settings screen code is updated to either 1) make it more difficult to 'cover' the Sign out button, 2) have documentation/comments to explain that the sign out button should always be available or ideally 3) both.

Bug Severity - BE SURE TO ADD THE SEVERITY LABEL

See Bug Tracking for details on severity levels

  • Impact: Low
  • Frequency: 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 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 QA Tickets require QA work / review sev-3 Lowest bug severity level based on QA bug severity scale - QA to assign this labels Sep 19, 2024
@TKDickson TKDickson added the scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness label Sep 30, 2024
@rbontrager rbontrager self-assigned this Nov 25, 2024
@rbontrager
Copy link
Contributor

Verified using Charles that the sign out button in profile > settings is shown when the authorized services return is blocked or errored. Approved by QA.

@kellylein kellylein added this to the v2.43.0 milestone Dec 9, 2024
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 mobile-feature-support 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