Skip to content
This repository has been archived by the owner on Feb 7, 2025. It is now read-only.

Send email with result count to CDC #1682

Open
31 tasks
brick-green opened this issue Jan 6, 2025 · 0 comments
Open
31 tasks

Send email with result count to CDC #1682

brick-green opened this issue Jan 6, 2025 · 0 comments

Comments

@brick-green
Copy link

brick-green commented Jan 6, 2025

As the CDC, in order to understand how much the ETOR service is being used, I need to receive an email with the total number of ETOR results received.

Pre-conditions

  • No automation needed at this time

Assumptions

  • This story will focus only on results that TI is aware of.

Acceptance Criteria

  • We've documented the process for determining the number of ETOR results received.
  • An email has been sent to a CDC email including the result counts

Research

  • Determine email accounts to send to
    • Who to send prod info?
    • Who to send staging info (most likely just us)?
  • Determine the email type and structure (body versus attachment)
  • Does the CDC need a special subject line?
  • Determine frequency
  • Should the CDC ask or do we just send unsolicited?

Engineering

  • Engineering work needed to complete the story
  • Foundational: Technical runway work to support this and future efforts

Definition of Done

  • Documentation tasks completed
    • Documentation and diagrams created or updated
      • ADRs (/adr folder)
      • Main README.md
      • Other READMEs in the repo
      • If applicable, update the ReportStream Setup section in README.md
    • Threat model updated
    • API documentation updated
  • Code quality tasks completed
    • Code refactored for clarity and no design/technical debt
    • Adhere to separation of concerns; code is not tightly coupled, especially to 3rd party dependencies
  • Testing tasks completed
    • Load tests passed
    • Additional e2e tests created
    • Additional RS e2e assertions created in the rs-e2e project for any new transformations. Includes improvements to the assertion code required to make the new assertions
  • Build & Deploy tasks completed
    • Build process updated
    • API(s) are versioned
    • Feature toggles created and/or deleted. Document the feature toggle
    • Source code is merged to the main branch

Note: Please remove any DoD items that are not applicable

Research Questions

  • Optional: Any initial questions for research

Decisions

  • Optional: Any decisions we've made while working on this story

Notes

  • Optional: Any reference material or thoughts we may need for later reference
@brick-green brick-green added this to the Test Milestone milestone Jan 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants