-
-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chore: Reorder support form fields for better user flow and clarity #26473
Merged
+194
−159
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
No changes detected in Branching Preview Branches by Supabase. |
monicakh
force-pushed
the
monicakh/fix-support-form-project
branch
from
May 21, 2024 20:36
218dce3
to
db9383f
Compare
monicakh
force-pushed
the
monicakh/fix-support-form-project
branch
from
May 22, 2024 11:14
1dba882
to
db9383f
Compare
saltcod
approved these changes
May 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
UI improvements to the support form.
What is the new behavior?
Repositioning Form Fields:
"Which organization is affected?" has been moved to the top of the form to prioritize organization selection.
The positions of "Which project is affected?" and "What area are you having problems with?" have been swapped for a more logical flow.
Information Box Updates:
Updated the information box displayed when no specific project is selected to include a more prominent notice: "Please note that no project has been selected."
Post-Submission Message Update:
Enhanced the confirmation message displayed after ticket submission to include both the project name and reference ID: "Your ticket has been logged for the project {projectName}, reference ID: {projectRef}."
How to test?
Before Changes
Click to view images
Organization and Project Selection:
Confirmation Message on Ticket Submission:
After Changes
Click to view images
No Project Selected
When Project is Selected
Confirmation Message on Ticket Submission