-
-
Notifications
You must be signed in to change notification settings - Fork 485
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
Bug: "Youth's Date in Care" being deleted when new case is created #5291
Comments
I can take a look at this issue. |
After an initial look, it appears that def casa_case_params
params.require(:casa_case).permit(
:case_number,
:birth_month_year_youth,
:court_report_due_date,
:empty_court_date,
casa_case_contact_types_attributes: [:contact_type_id],
court_dates_attributes: [:date]
)
end |
@mattzollinhofer Can you start with an initially failing test and then make the changes to fix it? |
Ha, sorry -- I was just taking notes while I wasn't assigned to the issue. I'll certainly get specs around this and get an PR out. |
The date in care was not a permitted param so it was not being included in the attributes during CasaCase creation. Added it to the list of permitted params. Fixes rubyforgood#5291
The date in care was not a permitted param so it was not being included in the attributes during CasaCase creation. Added it to the list of permitted params. Fixes rubyforgood#5291
Impacted User Types
Environment
desktop
Current Behavior
When a new case is created, "Youth's Date in Care" entered is deleted.
Before Clicking "+Create CASA Case" (submitting form)
After - "Edit Case Details"
Expected Behavior
When a New CASA Case is created, all info submitted is saved
How to Replicate
ex:
How to access the QA site
Login Details:
Link to QA site
Login Emails:
/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 hear about office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.
The text was updated successfully, but these errors were encountered: