Case Contact Details UX Improvements
Opened this issue · 5 comments
What type(s) of user does this feature affect?
- supervisors
- admins
- volunteers
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:
- Mark each individual field as required instead of the whole section
- Add client side validation to the fields. Currently if there is an error it reloads the page and you must scroll all the way down.
Contact Type Selection:
- Sort the options in the dropdown by recency.
How to access the QA site
Login Details:
Link to QA site
Login Emails:
- volunteer1@example.com view site as a volunteer
- supervisor1@example.com view site as a supervisor
- casa_admin1@example.com view site as an admin
- all_casa_admin1@example.com view site as an all casa admin
- go to
/all_casa_admins/sign_in
- go to
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.
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.