feat(support): Enhance ticket status update with email notifications

[codeunia-dev]

• Add email notification when support ticket status changes
• Retrieve user profile to personalize status update email
• Implement email generation for ticket status transitions
• Add error handling for email sending process
• Improve status update API endpoint with more robust logic
• Ensure email notifications are sent without blocking request processing

Summary by CodeRabbit

• New Features

  • Users now receive automatic email notifications when their support ticket status changes, keeping them informed of all updates.

• Improvements

  • Enhanced error handling ensures ticket status updates complete successfully even when email delivery encounters temporary issues.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
codeunia	Building	Preview	Comment	Nov 8, 2025 3:36am

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The PATCH endpoint for updating support tickets now sends email notifications when ticket status changes. It retrieves the current ticket to compare the old and new status, fetches the user's email and name, generates a status-update email, and sends it. Email failures are logged without blocking the response.

Changes

Cohort / File(s)	Summary
Email notification on ticket status update app/api/admin/support/tickets/[id]/route.ts	Added email notification flow triggered on ticket status change. Fetches current ticket to detect status change, retrieves user email and name, generates and sends status-update email. Email sending failures are caught and logged without failing the overall request. Refactored to use newStatus variable with validation for allowed values.

Sequence Diagram

sequenceDiagram
    participant Client
    participant Handler as PATCH Handler
    participant DB as Database
    participant Mail as Email Service
    
    Client->>Handler: PATCH /tickets/[id]
    Handler->>DB: Fetch current ticket
    DB-->>Handler: Current ticket data
    
    alt Status changed
        Handler->>DB: Update ticket with newStatus
        DB-->>Handler: Updated ticket
        Handler->>DB: Fetch user email & name
        DB-->>Handler: User data
        
        Handler->>Mail: Generate & send email
        
        alt Email success
            Mail-->>Handler: Email sent
        else Email fails
            Handler->>Handler: Log error (non-fatal)
        end
    else Status unchanged
        Handler->>DB: Update ticket
        DB-->>Handler: Updated ticket
    end
    
    Handler-->>Client: 200 OK (updated ticket)

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

• Email generation logic: Verify that email template and content generation are correct
• Error handling paths: Ensure email failures don't cause cascading issues and are properly logged
• Status comparison logic: Confirm that old vs. new status comparison correctly identifies changes
• User data retrieval: Review the query for fetching user email and first name for accuracy

Poem

🐰 A ticket's status shifts with grace,
An email flies through cyberspace,
When updates fail, we log with care,
The user waits—our love's still there! ✉️

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/adminsupport

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b1e31ea and 849e7bc.

📒 Files selected for processing (1)

• app/api/admin/support/tickets/[id]/route.ts (2 hunks)

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}