Skip to content

Story 027: Email and Notification System #27

Description

@iagocavalcante

Summary

As an organizer, I want the system to send transactional and bulk emails, so that attendees stay informed

Blocked By

  • story-005-event-creation-and-management
  • story-010-ticket-purchase-and-cart

Acceptance Criteria

1. Transactional Emails

  1. Event-Triggered: System automatically sends emails for: order confirmation, payment reminder, ticket download, event reminder, and waiting list offers.
  2. Customizable Templates: Organizers can customize email templates per event and preview them before activating.

2. Bulk Messaging

  1. Bulk Send: Organizers can send bulk emails to all attendees or filtered groups.

3. Delivery Management

  1. Mail Queue: Emails are sent asynchronously with retry logic for failed deliveries and exponential backoff.
  2. SMTP Required: Email sending requires a configured SMTP provider.

Tier 2 Edge Cases

  • Email with invalid attendee address
  • Bulk send to empty list
  • Template preview with placeholder data
  • SMTP provider unavailable
  • Duplicate email prevention on retry

Full spec: spec/elixir-phoenix-migration/10-product/stories/story-027-email-and-notification-system.md

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    agentic-workflowStory generated via agentic workflow

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions