feat: upgrade Contact Support form with file attachments and Plain integration by beran-t · Pull Request #240 · e2b-dev/dashboard

beran-t · 2026-02-14T01:35:02Z

Summary

Popover → Dialog: Converted the issue report UI from a narrow Popover to a full Dialog with React Hook Form + zod resolver
Rebranded: Renamed from "Report Issue" to "Contact Support" with updated copy, icons (LifeBuoy), and PostHog events
File attachments: Added drag-and-drop file upload (images, PDFs, text; max 5 files, 10MB each) using Plain API native attachments via createAttachmentUploadUrl — no Supabase Storage bucket needed
Enriched Plain thread: Thread body includes a metadata header with Customer email, Account Owner email, Tier (mapped: base_v1→Hobby, pro_v1→Pro), TeamID, and Orbit link
Server-side validation: Uses withTeamIdResolution middleware to verify team membership; fetches team name, email, and tier from the database server-side instead of trusting client-supplied values
Error handling: Uses ActionError for user-facing error messages instead of generic "Unexpected Error"
Button placement: Contact Support button in sidebar footer (50/50 split with Feedback button)
added routing for ?support=true to automatically open the form. In src/app/dashboard/
route.ts

Test plan

Open the Contact Support dialog from the sidebar footer
Submit a message with description only — verify Plain thread contains metadata header and customer message
Submit a message with file attachments — verify attachments appear in Plain thread
Test drag-and-drop and click-to-upload for the file drop zone
Attempt to upload files over 10MB — verify toast error and file rejected
Attempt to add more than 5 files — verify the drop zone disables
Verify sidebar buttons show 50/50 split (Feedback | Contact Support)

…tadata Convert the issue report from a Popover to a Dialog with React Hook Form, add drag-and-drop file attachment support via Supabase Storage, and enrich the Plain thread payload with teamId, teamName, customerEmail, customerTier, and attachment links.

vercel · 2026-02-14T01:35:08Z

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

Project	Deployment	Actions	Updated (UTC)
web	Ready	Preview, Comment	Mar 3, 2026 5:36pm
web-juliett	Ready	Preview, Comment	Mar 3, 2026 5:36pm

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c5a5492ff5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector · 2026-02-14T01:38:53Z

src/features/dashboard/navbar/report-issue-dialog.tsx

+          setAttachments((prev) => [
+            ...prev,
+            {
+              url: data.url,
+              fileName: data.fileName,


Ignore late upload callbacks after dialog reset

Closing the dialog while files are still uploading resets local state, but in-flight upload callbacks still append attachments unconditionally; this repopulates a canceled form with stale files and can also drive uploadingCount below zero when callbacks decrement after reset. Users can then reopen the modal and accidentally submit attachments from a previous canceled attempt, so upload results need to be ignored/canceled once the form session is reset.

Useful? React with 👍 / 👎.

This issue doesn’t actually apply here. The files aren’t uploaded asynchronously in the background — they’re just added to local state as File[] objects (line 141). The actual upload to Plain happens inside the server action when the user clicks “Send” (line 152-156), as a single synchronous submission.

chatgpt-codex-connector · 2026-02-14T01:38:54Z

src/server/support/support-actions.ts

+    const detectedMime = fileType?.mime ?? file.type
+
+    if (!ALLOWED_MIME_TYPES.includes(detectedMime)) {


Reject unknown file signatures in attachment validation

The MIME check falls back to the client-provided file.type whenever fileTypeFromBuffer cannot identify magic bytes, which lets a crafted upload bypass server-side type enforcement by labeling unsupported binary content as text/plain. This defeats the stated magic-byte validation and allows disallowed file formats into storage unless unknown signatures are rejected (or text files are validated independently).

Useful? React with 👍 / 👎.

sent to plain directly, not stored anywhere, do not think we need to adress this

…eader

…x counter, match height

Update icon (Bug → LifeBuoy), dialog copy, form labels, toast messages, and PostHog event names to reflect general support rather than bug reporting.

Replace the two-step Supabase upload with Plain's native attachment system. Files are held in browser state and uploaded to Plain on submit via a single contactSupportAction server action. Remove the tRPC support router, revert storage parameterization, and drop the issue-attachments bucket dependency.

Move the customer metadata header (email, tier, team ID, Orbit link) from the thread body to an internal Plain note so it doesn't get quoted in email replies. Map tier slugs to readable names (base_v1 → Hobby, pro_v1 → Pro).

…eThread fields Switch from deprecated createThread components/attachmentIds to the recommended flow: createThread (bare) → sendCustomerChat (message + attachments). Use AttachmentType.Chat instead of CustomTimelineEntry.

…or handling - Use description field on createThread instead of deprecated components - Switch from Error to ActionError so error messages surface to the user instead of the generic "Unexpected Error" message

sendCustomerChat requires the thread to use the CHAT channel. Also include Plain error message in ActionError for easier debugging.

The API key lacks chat:create permission needed for sendCustomerChat. Revert to using createThread with components and attachmentIds which works with existing thread:create permission.

… logging - Put the ######## header block back into the thread body text - Add detailed logging for each stage of attachment upload (start, URL creation, upload, success/failure with response body) - Remove separate internal note in favor of inline header

beran-t

Code review completed. 1 issue found.

src/server/support/support-actions.ts

The action previously trusted client-supplied teamId, teamName, customerEmail, accountOwnerEmail, and customerTier without verification. An authenticated user could spoof these to impersonate another team. Now uses withTeamIdResolution middleware to verify team membership (matching every other team-scoped action) and fetches team name, email, and tier from the database server-side. Only description, teamIdOrSlug, and files are accepted from the client.

beran-t

Review Summary

Overall this is a well-structured PR. Authentication, authorization (via authActionClient + withTeamIdResolution), and error handling are solid. Team metadata is correctly fetched server-side to prevent spoofing. One issue found below.

src/features/dashboard/navbar/file-drop-zone.tsx

- Set server MAX_FILE_SIZE to 10MB to match the UI's "max 10MB each" - Add client-side file size validation with toast error for oversized files - Move Contact Support button from header back to sidebar footer, next to the Feedback button

beran-t

Review by automated code review agent.

src/features/dashboard/navbar/report-issue-dialog.tsx

- Pass plain object to submitSupport() so withTeamIdResolution middleware can find teamIdOrSlug via the `in` operator (FormData stores entries internally, not as object properties) - Swap sidebar button order: Feedback left, Contact Support right - Add basis-1/2 for even 50/50 split

Allows linking directly to the support dialog by appending ?support=true to any dashboard URL. The param is cleaned from the URL after the dialog opens.

Add 'support' entry to TAB_URL_MAP so /dashboard?tab=support redirects to the user's default team sandboxes page with ?support=true, which auto-opens the Contact Support dialog.

Instead of a TAB_URL_MAP entry that hardcodes ?support=true (which breaks when the redirect URL already has query params), forward the support param via URL.searchParams.set() after building the redirect URL. Link is now /dashboard?support=true.

# Conflicts: # src/features/dashboard/navbar/report-issue-popover.tsx # src/features/dashboard/sidebar/footer.tsx # src/server/api/routers/support.ts

Apply biome import ordering, line wrapping, and replace div[role=button] with semantic <button> element.

beran-t requested a review from ben-fornefeld as a code owner February 14, 2026 01:35

vercel bot deployed to Preview – web February 14, 2026 01:35 View deployment

chatgpt-codex-connector bot reviewed Feb 14, 2026

View reviewed changes

refactor: move Report Issue button from sidebar footer to top-right h…

e88e099

…eader

vercel bot deployed to Preview – web February 14, 2026 01:43 View deployment

refactor: rename button to Contact Support, swap position with sandbo…

0f2a657

…x counter, match height

vercel bot deployed to Preview – web February 14, 2026 01:59 View deployment

refactor: rebrand from Report Issue to Contact Support

7204c81

Update icon (Bug → LifeBuoy), dialog copy, form labels, toast messages, and PostHog event names to reflect general support rather than bug reporting.

vercel bot deployed to Preview – web February 14, 2026 02:19 View deployment

refactor: remove sandbox ID field and widen support dialog

a2d3147

vercel bot deployed to Preview – web February 15, 2026 03:53 View deployment

vercel bot deployed to Preview – web February 25, 2026 00:38 View deployment

feat: format Plain thread body with header block and account owner email

8e848e1

vercel bot deployed to Preview – web February 25, 2026 00:52 View deployment

feat: add Orbit link to support thread header

12c8846

vercel bot deployed to Preview – web February 25, 2026 00:54 View deployment

vercel bot deployed to Preview – web February 25, 2026 01:19 View deployment

vercel bot deployed to Preview – web February 25, 2026 01:21 View deployment

fix: use description field for thread preview and ActionError for err…

90ea7cb

…or handling - Use description field on createThread instead of deprecated components - Switch from Error to ActionError so error messages surface to the user instead of the generic "Unexpected Error" message

vercel bot deployed to Preview – web February 25, 2026 01:28 View deployment

fix: set thread channel to CHAT for sendCustomerChat compatibility

3b785e1

sendCustomerChat requires the thread to use the CHAT channel. Also include Plain error message in ActionError for easier debugging.

vercel bot deployed to Preview – web February 25, 2026 01:31 View deployment

fix: revert to createThread with components for attachment support

2be336d

The API key lacks chat:create permission needed for sendCustomerChat. Revert to using createThread with components and attachmentIds which works with existing thread:create permission.

vercel bot deployed to Preview – web February 25, 2026 01:38 View deployment

vercel bot deployed to Preview – web February 25, 2026 01:49 View deployment

beran-t commented Feb 25, 2026

View reviewed changes

src/server/support/support-actions.ts Show resolved Hide resolved

vercel bot deployed to Preview – web February 25, 2026 12:35 View deployment

beran-t commented Feb 25, 2026

View reviewed changes

src/features/dashboard/navbar/file-drop-zone.tsx Outdated Show resolved Hide resolved

vercel bot deployed to Preview – web February 25, 2026 13:20 View deployment

style: remove border radius from file drop zone

35e035a

vercel bot deployed to Preview – web February 25, 2026 13:21 View deployment

beran-t commented Feb 25, 2026

View reviewed changes

src/features/dashboard/navbar/report-issue-dialog.tsx Outdated Show resolved Hide resolved

vercel bot deployed to Preview – web February 25, 2026 16:02 View deployment

beran-t changed the title ~~feat: upgrade issue report form with file attachments and metadata~~ feat: upgrade Contact Support form with file attachments and Plain integration Feb 26, 2026

feat: auto-open Contact Support dialog via ?support=true URL param

5d3049b

Allows linking directly to the support dialog by appending ?support=true to any dashboard URL. The param is cleaned from the URL after the dialog opens.

vercel bot deployed to Preview – web February 26, 2026 17:35 View deployment

feat: add support tab to dashboard route for universal support link

849ed76

Add 'support' entry to TAB_URL_MAP so /dashboard?tab=support redirects to the user's default team sandboxes page with ?support=true, which auto-opens the Contact Support dialog.

vercel bot deployed to Preview – web February 26, 2026 17:49 View deployment

beran-t added 2 commits February 26, 2026 19:03

chore: trigger rebuild for support param forwarding

30020c0

vercel bot deployed to Preview – web February 26, 2026 18:30 View deployment

Merge remote-tracking branch 'origin/main' into upgrade-issue-form

72a5921

# Conflicts: # src/features/dashboard/navbar/report-issue-popover.tsx # src/features/dashboard/sidebar/footer.tsx # src/server/api/routers/support.ts

vercel bot deployed to Preview – web March 3, 2026 16:40 View deployment

style: fix biome formatting and lint errors

ff8f17d

Apply biome import ordering, line wrapping, and replace div[role=button] with semantic <button> element.

vercel bot deployed to Preview – web March 3, 2026 17:35 View deployment

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: upgrade Contact Support form with file attachments and Plain integration#240

feat: upgrade Contact Support form with file attachments and Plain integration#240
beran-t wants to merge 24 commits intomainfrom
upgrade-issue-form

beran-t commented Feb 14, 2026 •

edited

Loading

Uh oh!

vercel bot commented Feb 14, 2026 •

edited

Loading

Uh oh!

chatgpt-codex-connector bot left a comment

Uh oh!

chatgpt-codex-connector bot Feb 14, 2026

Uh oh!

beran-t Mar 3, 2026

Uh oh!

chatgpt-codex-connector bot Feb 14, 2026

Uh oh!

beran-t Mar 3, 2026

Uh oh!

beran-t left a comment

Uh oh!

Uh oh!

beran-t left a comment

Uh oh!

Uh oh!

beran-t left a comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

		const detectedMime = fileType?.mime ?? file.type

		if (!ALLOWED_MIME_TYPES.includes(detectedMime)) {

Conversation

beran-t commented Feb 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Test plan

Uh oh!

vercel bot commented Feb 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

chatgpt-codex-connector bot Feb 14, 2026

Choose a reason for hiding this comment

Uh oh!

beran-t Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

chatgpt-codex-connector bot Feb 14, 2026

Choose a reason for hiding this comment

Uh oh!

beran-t Mar 3, 2026

Choose a reason for hiding this comment

Uh oh!

beran-t left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

beran-t left a comment

Choose a reason for hiding this comment

Review Summary

Uh oh!

Uh oh!

beran-t left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

beran-t commented Feb 14, 2026 •

edited

Loading

vercel bot commented Feb 14, 2026 •

edited

Loading