Files
Monica Khoury 39c39a9e47 feat: add 'Other' option to support form category dropdown (#49846)
## 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 -->
2026-09-01 13:40:59 +00:00

179 lines
4.1 KiB
TypeScript

import { SupportCategories } from '@supabase/shared-types/out/constants'
import { isFeatureEnabled } from 'common'
const billingEnabled = isFeatureEnabled('billing:all')
export type ExtendedSupportCategories = SupportCategories | 'Plan_upgrade' | 'Others'
export const CATEGORY_OPTIONS: {
value: ExtendedSupportCategories
label: string
description: string
query?: string
}[] = [
{
value: SupportCategories.PROBLEM,
label: 'APIs and client libraries',
description: "Issues with your project's API and client libraries",
query: undefined,
},
{
value: SupportCategories.DASHBOARD_BUG,
label: 'Dashboard bug',
description: 'Issues with the Supabase dashboard',
query: undefined,
},
{
value: SupportCategories.DATABASE_UNRESPONSIVE,
label: 'Database unresponsive',
description: 'Issues with connecting to your database',
query: 'Unable to connect',
},
{
value: SupportCategories.PERFORMANCE_ISSUES,
label: 'Performance issues',
description: 'Reporting of performance issues is only available on the Pro Plan',
query: 'Performance',
},
{
value: SupportCategories.ABUSE,
label: 'Abuse report',
description: 'Report abuse of a Supabase project or Supabase brand',
query: undefined,
},
{
value: SupportCategories.LOGIN_ISSUES,
label: 'Issues with logging in',
description: 'Issues with logging in and MFA',
query: undefined,
},
...(billingEnabled
? [
{
value: SupportCategories.SALES_ENQUIRY,
label: 'Sales enquiry',
description: 'Questions about pricing, paid plans and Enterprise plans',
query: undefined,
},
{
value: SupportCategories.BILLING,
label: 'Billing',
description: 'Issues with credit card charges | invoices | overcharging',
query: undefined,
},
{
value: SupportCategories.REFUND,
label: 'Refund enquiry',
description: 'Formal enquiry form for requesting refunds',
query: undefined,
},
]
: [
// [Joshen] Ideally shift this to shared-types, although not critical as API isn't validating the category
{
value: 'Plan_upgrade' as const,
label: 'Plan upgrade',
description: 'Enquire a plan upgrade for your organization',
query: undefined,
},
]),
{
// Must stay 'Others' (plural). The backend lowercases this before writing
// it to Front's `Type` custom field, which is a fixed, case-sensitive
// enum containing 'others' — not 'other'.
value: 'Others' as const,
label: 'Other',
description: "An issue that doesn't fit the categories above",
query: undefined,
},
]
export const SEVERITY_OPTIONS = [
{
value: 'Low',
label: 'Low',
description: 'General guidance',
},
{
value: 'Normal',
label: 'Normal',
description: 'System impaired',
},
{
value: 'High',
label: 'High',
description: 'Production system impaired',
},
{
value: 'Urgent',
label: 'Urgent',
description: 'Production system down',
},
]
export const SERVICE_OPTIONS = [
{
id: 1,
name: 'Authentication',
value: 'Authentication',
disabled: false,
},
{
id: 2,
name: 'Dashboard',
value: 'Dashboard',
disabled: false,
},
{
id: 3,
name: 'Database',
value: 'Database',
disabled: false,
},
{
id: 4,
name: 'Edge Functions',
value: 'Edge Functions',
disabled: false,
},
{
id: 5,
name: 'Multigres',
value: 'Multigres',
disabled: false,
},
{
id: 6,
name: 'Realtime',
value: 'Realtime',
disabled: false,
},
{
id: 7,
name: 'Storage',
value: 'Storage',
disabled: false,
},
{
id: 8,
name: 'Others',
value: 'Others',
disabled: false,
},
]
export const IPV4_MIGRATION_STRINGS = [
'ipv4',
'ipv6',
'supavisor',
'pgbouncer',
'5432',
'ENETUNREACH',
'ECONNREFUSED',
'P1001',
'connect: no route to',
'network is unreac',
'could not translate host name',
'address family not supported by protocol',
]