[Core]: V1 to V2 feature parity checklist #136

Migration to V2 must ensure feature parity with V1 where applicable. Missing features must be identified before release.

Status (updated 2026-07-18)

A full domain-by-domain audit comparing InvoicePlane v1 (prep/v180) against v2 (develop) ran on 2026-07-18, covering 8 domains. Each domain has its own epic below, holding every tracked/improved/newly-filed issue for that area as a native GitHub sub-issue. Full audit reports (classification matrix + drafted issue bodies) live at summary-feature-parity.md in the repo root and the underlying per-domain reports referenced there.

Batch result: 4 issues reopened (verifiably broken despite being closed as done), 34 new issues filed with full SMART/AAA specs, 17 existing issues given improved bodies, 8 domain epics created below.

Domain epics

• [Epic]: V1→V2 parity — Recurring Invoices #644 — Recurring Invoices (critical gap: zero generation-engine/scheduler infrastructure exists)
• [Epic]: V1→V2 parity — Guest/Client Portal #650 — Guest/Client Portal (critical gap: zero portal code exists — all share links are dead)
• [Epic]: V1→V2 parity — Online Payments #654 — Online Payments (critical gap: zero Stripe/PayPal integration exists)
• [Epic]: V1→V2 parity — E-invoicing #666 — E-invoicing (critical gap: zero e-invoicing code exists; [Invoices]: Peppol e-invoicing — pluggable multi-provider architecture #126 is the architectural foundation)
• [Epic]: V1→V2 parity — PDF, Templates, Themes, QR #665 — PDF, Templates, Themes, QR (2 issues reopened — closed as done, still stubs on develop)
• [Epic]: V1→V2 parity — Email Pipeline #673 — Email Pipeline (most mature domain — 9 features working; gaps are attachment/status-transition wiring)
• [Epic]: V1→V2 parity — Custom Fields & Uploads #675 — Custom Fields & Uploads (schema exists, zero UI)
• [Epic]: V1→V2 parity — Import, Export, Reports, Dashboard #682 — Import, Export, Reports, Dashboard (v1→v2 migration path has no issue anywhere until this audit)

Also filed from this audit (not parity, but found during it)

• [Core]: wkhtmltopdf PDF driver fatals — instantiates nonexistent Pdf class #661 — wkhtmltopdf PDF driver bug (instantiates a nonexistent class) — verified with a failing test on branch chore/verify-pdf-list-stub-and-wkhtmltopdf-bug

Original SMART plan (2026-07-16, preserved below)

Specific

As a project reviewer, I want a full comparison of V1 vs V2 features to ensure nothing is missing.

Measurable

A completed checklist of all modules and features with green "done" states.

Achievable

By auditing V1 routes, controllers, and views and mapping them to V2 equivalents.

Relevant

Ensures users transitioning to V2 do not lose functionality.

Time-Bound

Review complete by end of Q2 2025.

Arrange

• V1 and V2 environments are available.
• A comparison matrix exists.

Act

• The reviewer evaluates features module-by-module.
• Differences are recorded.

Assert

• All V1 features are matched, replaced, or deprecated intentionally.
• Missing features are listed clearly.
• The comparison document is approved.