Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork11k
feat(studio): incident notice on support ticket creation#41379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
base:master
Are you sure you want to change the base?
Conversation
vercelbot commentedDec 16, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
The latest updates on your projects. Learn more aboutVercel for GitHub.
6 Skipped Deployments
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
This pull request has been ignored for the connected project Preview Branches by Supabase. |
coveralls commentedDec 16, 2025
github-actionsbot commentedDec 16, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
🎭 Playwright Test ResultsDetails
Flaky testsFeatures › database.spec.ts › Database › Tables columns › can view, create, update, delete, and filter table columns Skipped testsFeatures › sql-editor.spec.ts › SQL Editor › snippet favourite works as expected |
Uh oh!
There was an error while loading.Please reload this page.
What kind of change does this PR introduce?
What is the current behavior?
During active incidents, users continue to file support tickets that are actually incident-related, creating significant work for the support team to tag, respond, update, resolve these tickets. The current incident banner in the dashboard does not sufficiently deflect these tickets.
What is the new behavior?