Right now we get one status for every email we send (even on successful delivery).
For that mailing list scenario or some of our web app features, since we don’t do anything when we get a callback, we would have been able to disable it. Could even be more than just on/off but like “only let me know if it failed to be sent” or “only let me know if it was successfully sent”.
WHY are we building?
Feature Request
WHAT are we building?
VALUE created by our solution
Description
Right now we get one status for every email we send (even on successful delivery). For that mailing list scenario or some of our web app features, since we don’t do anything when we get a callback, we would have been able to disable it. Could even be more than just on/off but like “only let me know if it failed to be sent” or “only let me know if it was successfully sent”.
WHY are we building? Feature Request WHAT are we building? VALUE created by our solution
Documentation and Artifacts
Good docs, figma mockups, ADRs, screenshots etc. Related incident https://docs.google.com/document/d/1RgCaUH96ABI--9z5igG2y9xKTXL6racZFWYYkT_FGmE/edit?tab=t.0#heading=h.gjdgxs
Acceptance Criteria
Given some context, when (X) action occurs, then (Y) outcome is achieved
[ ] Cypress UI tests if needed.
[ ] Generate appropriate log messages so that executions of this feature can be tracked
[ ] Can misuse of this feature cause harm? If yes, create an alert
[ ] Update the status of related findings, insights, and hypotheses on the Research Airtable
[ ] Once change/fix/feature is implemented, link relevant Airtable records to design artifacts (Figma)
[ ] Does the feature change our Information Architecture? If so, update the Sitemap in En/Fr
A11y
Bilingualism
Privacy considerations
Security controls in place
Measuring success and metrics
Related Research Airtable records
QA Steps