Manual queue of VAMC editor notifications email

[laflannery]

Background

The first time the notifications email will be sent out to VAMC editors, this will be done manually. The targeted date for this manual push is Monday 4/10.

Acceptance Criteria

• Manually send notifications email
• drush php-eval "print_r(\Drupal::service('va_gov_notifications.outdated_content')->checkForOutdatedVamcContent());"

Team

Please check the team(s) that will do this work.

• CMS Team
• Public Websites
• Facilities
• User support

[laflannery]

What are we doing when/if we get kick backs?

• error reporting for queue
  Create separate issue for what we do with all of this
• technical failures
• bounces cause no longer here
  Create response plan for each of these error cases

Post manual run analysis of results - this is the new ticket
AC

• listing of a cases and tickets to create runbooks for these cases

[laflannery]

We need to pivot this:

• Jessica Schaffer (Vet Centers) asked Facilities to provide analytics but this ask was lost in the shuffle a bit so we are blocked on the Vet Center piece of this until those analytics can be provided to her (is there a ticket we can track for this?)

[laflannery]

Separating the product is possible, with the following tentative schedule we can refine later today:

• Request to change our current sprint goal to Discovery of the changes requested
• Sprint 81 work will potentially be (depending on discovery):
  • Separating product (Vet Centers/all but Vet Centers) so manual email can go to VAMC/other at end of Sprint 81
    • Does it actually make more sense to do only VAMCs instead of everything but Vet Centers?
    • Dave - Just VAMCs
    • We will get ready to do just Vet centers (at some point, when we are unblocked) - set up queue (copy code and change what we are testing for)
    • We will have separate queues for each product so they can be adjusted separately
  • Prepare manual email for Vet Centers for a TBD send date
  • Prepare automatic emails for Vet Centers and VAMC/other with understanding of Vet Centers is TBD on timing
• Tentative new manual email push date for all but Vet Centers: end of Sprint 81 (approx April 12)

Do we send them out at the same time? Different times in the future?

• Might depend because Help desk might be overwwhelmed by questions

This would eventually allow for different email designs for each product

Next steps:

• new discovery ticket for this sprint Discovery: Feasibility of sending product specific notifications emails #13046
• two new tickets:
  • doing vamcs Notifications emails for VAMC editors #13047
  • getting ready for vet centers Notifications emails for Vet Center editors #13048
• Change this manual queue email to VAMCs targeted April 10th (Done, see above)
  • Dawn to update VHA at next (3/28) sync of new timeline
• Add new ticket for manual queue ticket for Vet center for whenever Manual queue of Vet Center editor notifications email #13045
• Add new ticket for adding vet centers to automated queue for whenever Add Vet Centers editor emails to existing tasks.yml #13044

[dawnpruitt]

Didn't mean to move this one back to stretch - wrong ticket number

[laflannery]

There was an issue with the relative links that was discovered once the emails went out. This should be resolved when the next email is sent next month. Slack thread here