Skip to content

[Epic]: V1→V2 parity — Email Pipeline #673

Open
8 of 22 issues completed
Open

Description

@nielsdrost7

Domain epic under the V1→V2 feature-parity umbrella (#136). Full audit: 06-email.md (2026-07-18 parity audit, v1 prep/v180 vs v2 develop).

Summary: The most mature domain audited — 9 features fully working (compose modal, editable body, queued dispatch, templates CRUD, merge-tag engine). The gaps are specific and mechanical: PDF/uploads never attached, status transitions never applied on send, CC captured but crashes and is never actually sent, and the EmailTemplateType enum contains custom-field types instead of document types (blocking all typed-template work).

Cross-domain note: #400 (automatic email on recurring-invoice generation) is attached under the Recurring Invoices epic (#644) since it's fundamentally a recurring-invoice trigger; it depends on this domain's #526/#527/#529 plumbing and is cross-referenced here.

Sub-issues

Specific

Reach email-pipeline feature parity with v1: PDF/upload attachment, correct status transitions on send, working per-client CC, a document-typed template system, and the full v1 merge-tag catalogue.

Measurable

All sub-issues closed; sending an invoice or quote email attaches the right files, transitions status correctly, applies all configured CC/BCC, and every v1-style merge tag renders.

Achievable

#667 (enum fix) unblocks the largest cluster (#164, #668, #400, #480); #526/#527/#529 are independent service-layer additions that #400/#164/#671 all reuse.

Relevant

Email is the primary delivery mechanism for invoices and quotes; today customers get body-text-only emails with no attachment, and CC configuration silently does nothing.

Time-Bound

#667 (enum): immediate, small. #526/#527/#529: 1 sprint. Remaining issues: 1-2 sprints after, several blocked on #392 (portal).

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

    epicrefinedRefined with SMART plan / test suggestions

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions