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 Remediation - Sev -3 - SM - Triage Team Error Remediation #7037

Open
bischoffa opened this issue Oct 18, 2023 · 8 comments
Open

Bug Remediation - Sev -3 - SM - Triage Team Error Remediation #7037

bischoffa opened this issue Oct 18, 2023 · 8 comments
Assignees
Labels
blocked-UX Issues blocked by UX/ design dependencies bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work Health Tickets are tied to the Health Product Team Pms help-wanted mobile-feature-support 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

@bischoffa
Copy link
Contributor

bischoffa commented Oct 18, 2023

Overview:
As a Veteran in the SM (Secure Messaging) of VAHB (VA Health & Benefits) App, I do not want the ability to reply to a message if they are no longer associated with the triage team so that I do not waste time replying only to be told the message won't go through.

Info:

  • Current situation:
    • Veteran in SM can click reply to a message to a triage team when we know the message will not be sent
  • Related to ticket 6822
  • In the past 30 days 3.3k different users has been impacted - 9.2k errors

Items needed

  • Content for the message - if we want one
  • BE work

Acceptance Criteria:

GIVEN Veteran in VAHB App's SM has a triage team message
WHEN that Veteran is no longer associated with that triage team
THEN do not show reply button
AND provide message to the Veteran on what is going on

@bischoffa bischoffa added bug Used to identify a bug ticket that will be worked through the bug process 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 labels Oct 18, 2023
@bischoffa bischoffa changed the title Bug Remediation - SM - Triage Team Error Remediation Bug Remediation - Sev -3 - SM - Triage Team Error Remediation Oct 18, 2023
@bischoffa bischoffa added scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness and removed scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness labels Oct 23, 2023
@dumathane dumathane added front-end Ticket requires front-end work and removed scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness labels Oct 26, 2023
@liztownd liztownd self-assigned this Dec 6, 2023
@dumathane
Copy link
Contributor

@bischoffa Did we ever decide or document anywhere what the UI is supposed to include for user notification regarding this Adam? Is that documented somewhere I'm not seeing or?

@bischoffa bischoffa added the Health Tickets are tied to the Health Product Team Pms label Dec 6, 2023
@bischoffa
Copy link
Contributor Author

bischoffa commented Dec 6, 2023

@dumathane  I do not recall that there was a decision made. I think this ticket may have been picked up prematurely as it doesn't include BE's work on this to. Other ticket looked to size both FE/ BE and looks like FE only did this one.

I don't feel this one can be picked up yet until:

  • BE work
  • Determine message if we want one
  • FE work

I would recommend putting this down and picking something else up

@liztownd liztownd removed their assignment Dec 6, 2023
@bischoffa bischoffa added scrubbed Added to newly-written bug tickets after QA has reviewed them for clarity and completeness blocked-UX Issues blocked by UX/ design dependencies blocked-BE Issues blocked by backend dependencies labels Dec 6, 2023
@Sparowhawk Sparowhawk removed the blocked-BE Issues blocked by backend dependencies label Mar 28, 2024
@Sparowhawk
Copy link
Contributor

@wavelaurenrussell can you let me know what the ux should be for this. @mistymg for copy that likely will be needed

@DJUltraTom DJUltraTom assigned rbontrager and unassigned DJUltraTom May 24, 2024
@rbontrager rbontrager removed their assignment Aug 15, 2024
@ala-yna
Copy link
Contributor

ala-yna commented Oct 1, 2024

Looks like this can be moved to Pending Handoff - something for UX/Content to dig into when there's time.

@wavelaurenrussell
Copy link
Contributor

Unassigning myself for now; appears to be a content ticket.

@jennb33
Copy link

jennb33 commented Jan 7, 2025

1/7/2025 update: @nhuckleberry6 will review this ticket to determine what from UX is blocking the ticket. Is it just pending content? More to come.
Because the impact, as noted in October 2023, was that over 30 days 3.3k different users has been impacted - 9.2k errors, we need to determine if this is still an issue, and what that impact is.

@kimmccaskill-oddball
Copy link
Contributor

Clicking the sentry issue in the investigation ticket takes me to a The issue you were looking for was not found. page.

@jennb33
Copy link

jennb33 commented Jan 29, 2025

1/29/2025 - Per Ryan's comments in OCTO Slack, this ticket will be worked on by the new Core Mobile team. Removing the ticket from our board, @nhuckleberry6 and @kimmccaskill-oddball

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocked-UX Issues blocked by UX/ design dependencies bug Used to identify a bug ticket that will be worked through the bug process front-end Ticket requires front-end work Health Tickets are tied to the Health Product Team Pms help-wanted mobile-feature-support 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