Change Architecture to Make Supervisors Connected with Cases Rather than Volunteers

[CovenantHuman]

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

• supervisors
• admins

Description

Currently our architecture has supervisors having volunteers which then have cases. We would like to change things so that a supervisor has_many cases and volunteers are then discoverable through cases. This will allow us to do things like assign a single volunteer to multiple supervisors through different cases, as is currently an issue for one of our CASAs. For example, for one of our CASAs, the cases belong to the supervisors, so if a volunteer has two different cases, they may belong to two different supervisors:

Sup1        Sup2
  \         /
Case1    Case2
   \      /
  Volunteer

QA 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

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 hear about office hours (currently Tuesday 6-8pm Pacific), stakeholder news, and upcoming new issues.

[github-actions[bot]]

This issue has been inactive for 263 hours (10.96 days) and will be automatically unassigned after 97 more hours (4.04 days).

[github-actions[bot]]

This issue has been inactive for 383 hours (15.96 days) and is past the limit of 360 hours (15.00 days) so is being unassigned.

[littleforest]

Initial plan:

• [ ] Add supervisor_id reference to casa_cases table. Not a required field.
• [ ] Write after party task that fills in the correct supervisor by using the case_assignments table and assigning the volunteer's supervisor.
• [ ] Need to think about what needs to change for going from one supervisor to several supervisors

[github-actions[bot]]

This issue has been inactive for 240 hours (10.00 days) and will be automatically unassigned after 120 more hours (5.00 days).

[github-actions[bot]]

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.

[github-actions[bot]]

This issue has been inactive for 383 hours (15.96 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[bot]]

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.

[github-actions[bot]]

This issue has been inactive for 365 hours (15.21 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[bot]]

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

[mussajoop]

Hello, I would like to work on that issue :)

[mussajoop]

is it ok to start working on it ?

[littleforest]

Hi @mussajoop this is actually a quite complicated ticket because it involves a major redesign of some of our database tables and models. If you would like to work on it, it might be a good idea to find some time to pair together.

[mussajoop]

hello @littleforest, a pair prog sounds good to me. I would enjoy it. Maybe we can get in touch on Slack to discuss when we'll be both available to do so?

[littleforest]

Yes, that would be great. We can coordinate on CASA slack. This will probably be a several PR ticket!

[mussajoop]

great!

[crespire]

Has there been any movement on this at all? I'd love to help on this architectural change.

[littleforest]

@crespire I think the core team needs to treat this as an epic and make some smaller tickets from it. I'm going to move this to not-ready-to-build for now, and try to get some more manageable tickets made. Thanks for reaching out, we will keep you posted.