supabase / supabase / 42031284640

87%

push

github

chore(studio): encourage shorter, clearer support requests (#52492)

## What

Updates the Message field on the support form to encourage shorter,
clearer requests.

- Replaces the "Please be as detailed and specific as possible"
placeholder with three plain questions: "What are you trying to do? What
happened instead? What have you tried?"
- Adds one line of guidance under the field, with a link to the KB
article on formatting support requests
- Replaces the static "5000 character limit" label with a live `count /
2,500` counter, and lowers the limit to 2,500

## Why

The old wording encouraged very long requests. Closes FE-4716:

https://linear.app/supabase/issue/FE-4716/review-support-form-wording-to-encourage-shorter-clearer-requests

Copy follows design feedback in the Slack thread. Layout changes to the
wider support form are out of scope and tracked separately.

The 2,500 limit comes from the proposed mockup on the ticket, which was
marked as a proposal rather than an agreed change. Flagging it here so
it gets confirmed in review.

A prepopulated template is not included. A placeholder gives the same
guidance without text users have to delete, and avoids conflicting with
flows that prefill the message.

## How to test

1. Run `pnpm dev:studio` and open the support form
2. Check the placeholder shows the three questions, and disappears when
you type
3. Check the line under the field links to the KB article via "Learn
more"
4. Type in the field and check the counter goes up (`0 / 2,500` to `N /
2,500`)
5. Paste text longer than 2,500 characters and check it is cut off at
the limit
6. Type `ipv4` in the message and check the IPv4 alert appears below the
guidance, then delete it and check the alert disappears

2042 of 2411 branches covered (84.7%)

Branch coverage included in aggregate %.

2838 of 3198 relevant lines covered (88.74%)

201.09 hits per line