-
-
Notifications
You must be signed in to change notification settings - Fork 454
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
Start adding polymorphic reads to replace old followups via case_contact #5630
Comments
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 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. |
still working on this will be at office hours next week |
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 |
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. |
What type(s) of user does this feature affect?
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:
password for all users: 12345678
The text was updated successfully, but these errors were encountered: