Add "4. Court report topics (optional)" card/section to case contact form

[bcastillo32]

What type(s) of user does this feature affect?

• volunteers
• supervisors
• admins

Description

This is part of The Case Contact Form Improvement Epic. If you have any questions, please reach out to me, @bcastillo32, and/or @MalloryPriceDesign. The Case Contact form is one of the most important and heavily used features and your contribution will have a huge impact on CASA volunteers! :)

Reference Materials

Figma File/Prototype

Steps to view a Figma prototype:

1. Access the provided link in your web browser.
2. Press the play button located at the top right of the browser window.
3. (Optional) Create a free account and log in. This grants access to view comments left on the file.
4. (Optional) If the prototype extends beyond your screen width, click the "options" dropdown at the top right of the screen and select "fit width."
5. Explore the prototype by clicking different areas to discover interactive elements.

Styling Chart

Accessing the Case Contact Form

• Login as a Volunteer
• Click on a case
• Click "+ New Case Contact" button

Acceptance Criteria

1. The card header should read "4. Court report topics (optional)" - see reference materials above
2. Card components should match that of the figma file and styling chart - see reference materials
3. Card text should match figma file and use correct styling - see reference materials above

How to access the QA site

Login Details:
Link to QA site

Login Emails:

• [email protected] view site as a volunteer
• [email protected] view site as a supervisor
• [email protected] view site as an admin
• [email protected] view site as an all casa admin
  • go to /all_casa_admins/sign_in

password for all users: 12345678

Questions? Join Slack!

We highly recommend that you join us in slack https://rubyforgood.herokuapp.com/ #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.

[JoshuaMaurer]

Hey Brandon! Is it ok if I pick this one up? Cheers!

[bcastillo32]

hi @JoshuaMaurer how are you coming along? Any blockers? :)

[github-actions]

This issue has been inactive for 241 hours (10.04 days) and will be unassigned after 119 more hours (4.96 days). If you have questions, please

If you are still working on this, comment here to tell the bot to give you more time

[github-actions]

This issue has been inactive for 361 hours (15.04 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.

[elasticspoon]

Hey. I'm interested in taking this but I am new to this code base and I had some questions about this issue. @bcastillo32

1. Is PR meant to both create the HTML form and modify the controller?
2. The court report topics themselves, are they hard coded or are they stored on a model somewhere?
3. When you specify the style ex: Content 1, is that a CSS class somewhere that I can apply or does it have some other meaning?

Thanks

[bcastillo32]

Hey. I'm interested in taking this but I am new to this code base and I had some questions about this issue. @bcastillo32

1. Is PR meant to both create the HTML form and modify the controller?
2. The court report topics themselves, are they hard coded or are they stored on a model somewhere?
3. When you specify the style ex: Content 1, is that a CSS class somewhere that I can apply or does it have some other meaning?

Thanks

Hi @elasticspoon The card will need to be created. I'm not 100% clear on my understanding of controllers but perhaps I can provide a bit more context on what the end design will look like. For now the topics can be hardcoded but soon after this form revamp is done, we will want those topics to be customizable for admins. So one day an admin of an ord might decide to use different topics. Does this help answer your question?

As for the "Content 1" that is to be used for text in the card that say "optional" like the picture below

[elasticspoon]

Well, I've got the basic look of it sketched out

However, I am not totally sure how best to hook this up, as in make this portion of the form actually do something. Like if admins of orgs might want to change this the information should probably live with the org rather than with the case contact.

Who would be best to consult for something like that? As in who would know more about the back end?

[bcastillo32]

Well, I've got the basic look of it sketched out

However, I am not totally sure how best to hook this up, as in make this portion of the form actually do something. Like if admins of orgs might want to change this the information should probably live with the org rather than with the case contact.

Who would be best to consult for something like that? As in who would know more about the back end?

Hi there. if you could please join our slack channel and message me (Brandon) in the #proj-case-contact-refactor channel we can help connect with a backend dev who is a maintainer.

[bcastillo32]

@elasticspoon and apologies - I could have been more clear but the topics will be set at the org level by admins and will be applied to every case contact. Let me know is this helps. Please do connect on slack as well :)

[github-actions]

This issue has been inactive for 263 hours (10.96 days) and will be unassigned after 97 more hours (4.04 days). If you have questions, please

If you are still working on this, comment here to tell the bot to give you more time

[elasticspoon]

still working

[github-actions]

This issue has been inactive for 262 hours (10.92 days) and will be unassigned after 98 more hours (4.08 days). If you have questions, please

If you are still working on this, comment here to tell the bot to give you more time

[elasticspoon]

@bcastillo32 Hey. So a couple of questions came up:

For clarity I will call this the questions page

And this the answers page:

1. On the questions page the user does not select anything, on the answers page the user expands every question. They go back to the questions page. Should the questions be selected now?

2. Who has permissions to add contact topics for an organization?

[bcastillo32]

@bcastillo32 Hey. So a couple of questions came up:

For clarity I will call this the questions page And this the answers page:

1. On the questions page the user does not select anything, on the answers page the user expands every question. They go back to the questions page. Should the questions be selected now?
2. Who has permissions to add contact topics for an organization?

Hi @elasticspoon - I am going to answer these questions in our slack channel and will tag you. question one is more of a design choice and needs to be answered by Mallory. Thank you for calling this out. This is a great edge case we did not think about.

[MalloryPriceDesign]

@bcastillo32 Hey. So a couple of questions came up:
For clarity I will call this the questions page And this the answers page:

1. On the questions page the user does not select anything, on the answers page the user expands every question. They go back to the questions page. Should the questions be selected now?
2. Who has permissions to add contact topics for an organization?

Hi @elasticspoon - I am going to answer these questions in our slack channel and will tag you. question one is more of a design choice and needs to be answered by Mallory. Thank you for calling this out. This is a great edge case we did not think about.

Hi @elasticspoon! Great questions, here are some of my thoughts. Let me know if you have any other questions

1. I do not think we need to update the selections on the questions page if the user has expanded the topics on the answers page. Are you storing these selections in the backend? If we are, then we might want to update the selections, but I'm not sure we need to store this information at all, since we should store the users' text responses in the answers page.
2. Brandon is correct, only admins of that organization have permission to edit topics. Let me know if you have questions about the UX for that page. You can see the admin view in that same Figma file.

[github-actions]

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

[github-actions]

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.

[github-actions]

This issue has been inactive for 435 hours (18.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.

[github-actions]

This issue has been inactive for 459 hours (19.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.