## What is the current behavior?
The "What issue are you having?" dropdown in the contact support form
has a fixed set of categories. There's no catch-all option, so users
with an issue that doesn't cleanly match any category are forced to pick
an inaccurate one.
Fixes
[FE-4145](https://linear.app/supabase/issue/FE-4145/add-other-to-what-issue-are-you-having-in-contact-support-form)
— reported case: a user had to select "Database Unresponsive" for an
issue that only affected one user's connection, not the database itself.
## What is the new behavior?
Added an "Other" option to the category dropdown.
## Additional context
- Category value must stay `Others` (plural) rather than `Other` —
Front's `Type` custom field is a fixed, case-sensitive enum that only
contains`others`; sending `Other` would silently fail to set the field
in Front (ticket still submits, but shows as `unknown` category).
- Traced end-to-end (frontend zod → network call → backend DTO →
controller → Front custom field mapping) to confirm no fixed enum or
switch statement elsewhere breaks on an unrecognized category value.
- Open item, not blocking this PR: following up with Front admin access
to confirm no routing rule explicitly lists `Type` values in a way that
would leave `others` unmatched (worst case is a missed auto-route, not a
lost ticket).
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Clarified the handling of the “Other” support category for improved
internal reference.
* Documented that the category’s value is normalized consistently during
processing.
* No changes were made to the category’s behavior or the end-user
support experience.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Adds "Multigres" to the "Which services are affected?" multi-select on
the Contact Support form, so Alpha customers can tag tickets for the
Multigres Front inbox. Placed alphabetically between Edge Functions and
Realtime; the later option ids are renumbered, which is safe — they're
only used as React list keys, and the submit payload sends the lowercase
value tokens (`affectedServices: "multigres;..."`, verified with a live
submission).
Addresses
[FE-4273](https://linear.app/supabase/issue/FE-4273/add-multigres-to-support-form-services).
Front-inbox routing itself is Platform-side (SUPPORT-421) and should
match on the token `multigres`.
## To test
- Open /support/new → "Which services are affected?" → Multigres appears
between Edge Functions and Realtime, selectable alongside other
services, and the combobox search finds it
- Submit a ticket with it selected → the POST to
`/platform/feedback/send` carries `affectedServices` containing
`multigres`
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Added Multigres as a selectable service option in the support
interface.
* Updated service ordering to accommodate the new option.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: Alaister Young <10985857+alaister@users.noreply.github.com>
Bug fix
## What is the current behavior?
The client library selector validation was failing when the simplified
support form was used, because the field was required but hidden.
## What is the new behavior?
The client library selector is only required when: client library JSON
flag is on + not using simplified support form + client libraries is
chosen as the problem category.
## Summary by CodeRabbit
* **Bug Fixes**
* Improved support form validation logic and category eligibility for
support access requests.
* Refined conditional rendering of support access toggle based on
selected category.
* **New Features**
* Added feature-flag-based library selection capability for support
submissions.
* **Refactor**
* Streamlined support category options and removed obsolete entries.
* Simplified form schema initialization and made library field optional
where applicable.
…all support categories (#42254)"
This reverts commit a87387b56e.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Bug Fixes**
* Fixed support access eligibility logic to correctly reflect which
support categories qualify for access.
* **Refactor**
* Restructured support form to improve category filtering and visibility
handling for better organization.
* Updated category option structure to properly support hidden category
states and filtering.
* Streamlined support access determination based on selected category,
improving form logic clarity.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Previously, the “Allow support access to your project” toggle was only
shown for specific issue categories in our support form. This change
makes the toggle available for all categories.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Bug Fixes**
* Support access toggle and submission now suppress support access for
Account Deletion, Sales Enquiry, and Refund categories.
* **Refactor**
* Reworked category gating so UI visibility and submitted payload
consistently respect the disabled-category list.
* **UI**
* Category list updated—"Others" removed and category options adjusted
so all available options are shown.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
---------
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
* refactor: refactor support form
Refactor support form to make it easier to maintain:
- Split up large components into smaller components and hooks
- Lift state up so we don't have to do complex child/parent
state-syncing via useEffect
- Use nuqs parsing for consistent serialization/deserialization of
support form prefilled fields
* test: support form
Add comprehensive tests for support form
* fix(support form): project and org empty state
* Nit clean up
* More clean up
* cleannnn
* fix(support form): allow case-insensitive category in url
* clean(support form tests): remove unused param
* fix(support form): incorrect logic for sending affected services in payload
* clean(support form): use NO_ORG_MARKER and NO_PROJECT_MARKER instead of strings
* fix(support form): don't show upgrade cta if already on enterprise
---------
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
* Add UpgradePlanButton which handles redirecting either to subscription page or support page
* Update upgrade CTAs to go to support if billing:all flag is disabled
* Nit
* Nit
* Smol fix
* Temp show plan upgrade support category
* revert as instructed
* asChild
---------
Co-authored-by: Alaister Young <a@alaisteryoung.com>
* Dont hide org field when project is selected
* Refactor SupportForm to use new form components and fix UX oddities identified
* Add scroll area to docs search results
* Address feedback
* Small padding nudge
* Add check
---------
Co-authored-by: Terry Sutton <saltcod@gmail.com>
* Move all studio files from /studio to /apps/studio.
* Move studio specific prettier ignores.
* Fix the ui references from studio.
* Fix the css imports.
* Fix all package.json issues.
* Fix the prettier setup for the studio app.
* Add .turbo folder to prettierignore.
* Fix the github workflows.
Monica Khoury