Court Reports

[Zrrrpy]

As a Supervisor,
I want to add the next court date and court report due date per casa_case AND be able to mark a volunteer's associated court report submission as in review or complete,
so that I can more easily track required volunteer activities leading up to their next court appearance with their casa_case.

As a Volunteer,
I want to see my assigned casa_case's next court date and associated court report due date AND see the status of my court report after submitting it,
so that I know when to prepare and submit my court report AND know what stage in the review process it is in.

I also want to generate a court report auto-filled with select details,
SO that I can download it and fill out remaining details before submitting it to my supervisor for review.

As an Admin,
I want to see a casa_case's next court date and the associated volunteer's court report due date AND whether or not their court report has been submitted,
so that I can track progress and know to assist their supervisor assignment if the volunteer is not on track to meeting associated deadlines.

Acceptance Criteria

• supervisors and admins can add next court date per volunteer #807 supervisor and admin can add next court date per casa_case.
• supervisors and admins can associate judge_name and hearing_type with next court_date #927 supervisor and admin can associate a hearing_type and judge_name with a court_date
• admins can customize hearing_types per casa_org #928 admin can customize hearing_types for their casa_org
• admins can customize judge_names per casa_org #929 admin can customize judge_names for their casa_org
• judge_names only display on case details if admin has added judge_names to casa_org #1153 judge_names only display after admin adds them to a casa_org instance
• supervisors and admins can add court report due date per casa_case #808 supervisor and admin can add court report due date per casa_case.
• past court dates should appear with casa_case details #805 Past court dates appear with casa_case details.
• volunteer/admin/supervisor can adjust court report submission status #619 volunteer can adjust court report submission status from false to true
• court report submission status updates automatically #882 court report submission status updates automatically
• supervisors/admins can edit court report submission status #806 supervisor and admin can edit court report status
• Court Date/Report info "clears" once date has passed #881 Next Court Date clears after court date has passed
• volunteers can generate court report for transition aged youth #922 Volunteers can generate a court report for transition aged youth
• volunteers can generate court reports for non transition aged youth #1064 Volunteers can generate a court report for non-transition aged youth
• Add route to "Generate Court Report" to sidebar #923 Volunteers can navigate to "Generate Court Report"

[littleforest]

@Zrrrpy does this make sense for the database schema:

Table: court_dates
Fields:

Field	Type
casa_case	reference
court_date	date
court_report_submitted_at	date
court_report_status	enum (string)
court_report_due_date	date

[Zrrrpy]

This looks good @littleforest!

[acrosman]

I'm a Guardian ad Litem in another state (more or less interchangeable for Maryland CASAs), but new to this project, I'm looking through issues for places to engage productively so if I'm out of line please feel free to tell me. I think the data structure here is a good start but as a volunteer in similar roles it misses two pieces of information I always want: the type of hearing (it matters for report content) and the expected judge (here this can change last minute, but can be helpful to know when appearing).

I would also expect the court_date field to be a datetime not just a date. It is not as useful as one would generally like -- although has been more useful during the current move to virtual hearings when the court is staying much more on a fixed schedule.

So I suggest the following revision to the above table.

Field	Type
casa_case	reference
court_date	datetime
hearing_type	enum (string)*
judge_name	string
court_report_submitted_at	date
court_report_status	enum (string)
court_report_due_date	date

• Ideally this could be adjusted per-instance as different states likely have different options and names for the hearing types.