Skip to content
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

Create models and controllers needed for ContactTopic. #5500

Closed
elasticspoon opened this issue Jan 28, 2024 · 2 comments
Closed

Create models and controllers needed for ContactTopic. #5500

elasticspoon opened this issue Jan 28, 2024 · 2 comments
Assignees

Comments

@elasticspoon
Copy link
Collaborator

elasticspoon commented Jan 28, 2024

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

  • volunteers?
  • supervisors?
  • admins?
  • all casa admins?

Description

This issue blocks #5388.

Issue: Create models and controllers needed for ContactTopic.

Behavior is still not fully figured out but the basic principles are such:

  • Organizations create contact topics
    • These topics have a title and details (maybe other stuff in the future)
    • initially organizations will just have several default ones ability to modify them will be added later
  • When creating a CaseContact the user should be presented with all of an organizations contact topics and answer some, none or all of them.
    • Those contact topics will then be associated with a case contact (contact topics can be selected but not answered)

Acceptance Criteria

  • There should be model tests added for the new model and whatever other models are afftects
  • There should be controller / request tests for the forms controller

Some Notes from Slack

The controller in question here is controllers/case_contacts/form_controller.rb. Depending on how you decide the database question (see below) you may or may not need to update it, but you will definitely need to update the CaseContactParamters which are listed in the controller. Here's a diagram of how the controller works.
image

potential idea: Maybe just start with the join table, since that's what this will need by the end. Something like this...
image

my current plan:

The way I was thinking was each court report topic essentially has a title, details, and an answer. I was thinking

  • each organization has many topics without answers
  • When you start creating the case contact, you create copies of those cord topics and assign them to the case contact
  • When you save the case contact they finally get created

contact topic ideas

How to access the QA site

Login Details:
Link to QA site

Login Emails:

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.

@elasticspoon elasticspoon added the Help Wanted This is a special label that enables github to showcase issues that want help label Jan 28, 2024
@elasticspoon
Copy link
Collaborator Author

I can't self assign but I will work on this as part of the related issue.

@github-actions github-actions bot removed the Help Wanted This is a special label that enables github to showcase issues that want help label Mar 2, 2024
@elasticspoon
Copy link
Collaborator Author

This is done in #5517

@elasticspoon elasticspoon closed this as not planned Won't fix, can't repro, duplicate, stale Mar 2, 2024
@github-project-automation github-project-automation bot moved this from Todo to Merged to QA in CASA Volunteer Portal Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant