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

Update check_and_queue_va_profile_email_status_callback method to include service name in the data block #2063

Open
3 tasks
kbelikova-oddball opened this issue Oct 18, 2024 · 1 comment

Comments

@kbelikova-oddball
Copy link

kbelikova-oddball commented Oct 18, 2024

User Story - Business Need

Our partners at VA Profile would like to know which services/business lines have undelivered emails so they could investigate what went wrong and reach out to service directly with suggestions. Our current callback provides only services ID which are not helpful for VA Profile's investigation. They requested including service name in the callback, so they’d know which service originated an email.

  • Ticket is understood, and QA has been contacted (if the ticket has a QA label).

User Story(ies)

As a VA Profile
I want to be able to see which service(s) have undelivered emails
So that we can help services identify data error and suggest fixing them to minimize undelivered emails rate.

As a VA Notify
I want to include service name in check_and_queue_va_profile_email_status_callback's data block
So that our partners receive service name as a part of our callback

Additional Info and Resources

Acceptance Criteria

GIVEN check_and_queue_va_profile_email_status_callback method is updated

WHEN an email notification is attempted 

THEN include service name in notification_data block

  • This work is added to the sprint review slide deck (key win bullet point and demo slide)

QA Considerations

  • verify AC in perf

Potential Dependencies

Potential Dependencies

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants