-
-
Notifications
You must be signed in to change notification settings - Fork 476
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
Case Contact Details UX Improvements #5896
Comments
Hello, can I take this on? |
@MclPio sorry this issue isn't reserved per se but @josephmsmith has a bit more context (we talkeda bout this issue a few hours ago) so I'll leave it up for him to decide if he wants to take the issue first. Feel free to comment on something else or wait a bit for this one |
Hi - I will take this on since I have a bit more context. I will ping you if anything changes @MclPio ! |
This issue has been inactive for 244 hours (10.17 days) and will be unassigned after 116 more hours (4.83 days). If you have questions, please If you are still working on this, comment here to tell the bot to give you more time |
This issue has been inactive for 363 hours (15.13 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project. |
This issue has been inactive for 360 hours (15.00 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.You’ve just been unassigned from this ticket due to inactivity – but feel free to pick it back up (or a new one!) in the future! Thank you again for your contribution to this project. |
Addressed in #6048 , but client side validation may still be desired. |
What type(s) of user does this feature affect?
Description
The Case Contact form (
case_contacts/:id/form/details
) is the primary form with which volunteers interact with the application. We want this experience to be as smooth as possible.Currently there are a few UX issues around recording contact details. Feel free to split this up into more PRs if needed.
Contact Details:
This section could use some UX improvements:
Contact Type Selection:
How to access the QA site
Login Details:
Link to QA site
Login Emails:
/all_casa_admins/sign_in
password for all users: 12345678
Questions? Join Slack!
We highly recommend that you join us in slack #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.
The text was updated successfully, but these errors were encountered: