[Dashboard] Adding telegram field to support ticket creation

[Joe-Thirdweb]

Adding a spot in the support ticket creation for telegram handles. Business team often attempts to associate a TG customer with an active ticket.

Result in Unthread

---

PR-Codex overview

This PR adds a new SupportForm_TelegramInput component to the ticket creation process, allowing users to input their Telegram handle. It updates the ticket creation action to include this new field and modifies the email body to display the Telegram handle.

Detailed summary

• Added SupportForm_TelegramInput component for Telegram handle input.
• Updated CreateTicket component to include SupportForm_TelegramInput.
• Modified createTicketAction to handle telegramHandle.
• Updated email body to include the Telegram handle in the ticket information.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 381ab6d

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs-v2	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 17, 2025 5:55am
login	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 17, 2025 5:55am
thirdweb_playground	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 17, 2025 5:55am
thirdweb-www	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 17, 2025 5:55am
wallet-ui	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 17, 2025 5:55am

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• merge-queue - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 55.10%. Comparing base (9091e81) to head (381ab6d).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #6754   +/-   ##
=======================================
  Coverage   55.10%   55.10%           
=======================================
  Files         896      896           
  Lines       56700    56700           
  Branches     3914     3914           
=======================================
  Hits        31247    31247           
  Misses      25357    25357           
  Partials       96       96           

Flag	Coverage Δ
packages	55.10% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

size-limit report 📦

Path	Size	Loading time (3g)	Running time (snapdragon)	Total time
thirdweb (esm)	50.57 KB (0%)	1.1 s (0%)	113 ms (+247.47% 🔺)	1.2 s
thirdweb (cjs)	138.73 KB (0%)	2.8 s (0%)	166 ms (+108.66% 🔺)	3 s
thirdweb (minimal + tree-shaking)	5.59 KB (0%)	112 ms (0%)	44 ms (+1957.97% 🔺)	156 ms
thirdweb/chains (tree-shaking)	514 B (0%)	11 ms (0%)	34 ms (+4683.89% 🔺)	44 ms
thirdweb/react (minimal + tree-shaking)	19.36 KB (0%)	388 ms (0%)	54 ms (+920.86% 🔺)	442 ms