Skip to content
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

create standard court orders on a per organization basis #5781

Open
2 of 3 tasks
Tracked by #5782
elasticspoon opened this issue May 28, 2024 · 5 comments · May be fixed by #5910
Open
2 of 3 tasks
Tracked by #5782

create standard court orders on a per organization basis #5781

elasticspoon opened this issue May 28, 2024 · 5 comments · May be fixed by #5910
Labels
Difficulty: Intermediate Spans multiple domains or requires more advanced coding knowledge

Comments

@elasticspoon
Copy link
Collaborator

elasticspoon commented May 28, 2024

What type(s) of User Does This Feature Affect?

  • supervisors
  • admins
  • volunteers

Description

We would like to make it a bit easier for volunteers to set up court orders. Typically an organization has a set of "standard" court orders that cases will be subject to. Lets make it a bit easier for them to set that up on a per case basis.

This can be modeled off of Court Report Topics in terms of how to display them:

Image

Completion Criteria

  • make the tables and models needed for organizations to create these standard court orders
  • create the views needed to display these on the /casa_org/:id/edit page
  • ensure that the dropdown on the case show page (/casa_case/:id) for the standard court orders uses these values

How to Access the QA Site

Login Details:
Link to QA site

Login Emails:

password for all users: 12345678

Questions? Join Slack!

We highly recommend that you join us in slack #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.

@elasticspoon elasticspoon added Ruby for Good 2024 DC Difficulty: Intermediate Spans multiple domains or requires more advanced coding knowledge labels May 28, 2024
@dalmaboros dalmaboros self-assigned this Jun 19, 2024
Copy link

This issue has been inactive for 262 hours (10.92 days) and will be unassigned after 98 more hours (4.08 days). If you have questions, please

If you are still working on this, comment here to tell the bot to give you more time

@dalmaboros
Copy link
Collaborator

I'm still working on it, bot!

Copy link

This issue has been inactive for 246 hours (10.25 days) and will be unassigned after 114 more hours (4.75 days). If you have questions, please

If you are still working on this, comment here to tell the bot to give you more time

@dalmaboros dalmaboros linked a pull request Jul 15, 2024 that will close this issue
@dalmaboros dalmaboros linked a pull request Jul 15, 2024 that will close this issue
Copy link

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

Copy link

github-actions bot commented Aug 4, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Difficulty: Intermediate Spans multiple domains or requires more advanced coding knowledge
Projects
Status: In progress
Development

Successfully merging a pull request may close this issue.

2 participants