Start adding polymorphic reads to replace old followups via case_contact

[acasarsa]

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

• volunteers?
• supervisors?
• admins?

Description

Part 2 of epic to create followups for emancipation checklist

This PR will deal with updating the reads across the app for followup. It will also reorg the dir structure to remove it from under case contacts.

May want to spread this out over a few PRs due to the structural changes and the sheer amount of files that need changing.

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

password for all users: 12345678

reminders of files that need to change:

• followup_notifier still relies on case_contact
• followup_service and the send_notification method
• make sure case_contact followup still works without the belongs_to on followup
• FollowupResolvedNotifier also needs to be updated to not use case_contact
• make sure that resolve works for all login account types
• look into possibility that you can't resolve reminders while impersonating a volunteer.
• update def self.in_organization(casa_org) Followup.joins(case_contact: :casa_case).where(casa_cases: {casa_org_id: casa_org.id}) end

[github-actions[bot]]

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[bot]]

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

[acasarsa]

still working on this will be at office hours next week

[github-actions[bot]]

This issue has been inactive for 245 hours (10.21 days) and will be unassigned after 115 more hours (4.79 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[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 open without changes for a long time! What's up?

[github-actions[bot]]

This issue has been inactive for 367 hours (15.29 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 open without changes for a long time! What's up?