-
-
Notifications
You must be signed in to change notification settings - Fork 479
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
add the ability for organization to create and edit placement types within their org #5778
Comments
I can take this one. |
@jalletto all you! |
This issue has been inactive for 248 hours (10.33 days) and will be unassigned after 112 more hours (4.67 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 368 hours (15.33 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. |
This issue has been open without changes for a long time! What's up? |
What type(s) of user does this feature affect?
Description
Part of #4695
We currently have a partially implemented Placements feature. Placements are essentially a combination way to track with whom and where a case subject is living and for how long.
Currently there are placement types that got implemented with #4702.
Lets add the ability for organization to create and edit placement types.
Initial Defaults
Lets start with some simple defaults:
Screenshots
It may make sense to model this off of Case Contact Topics (
/casa_org/:id/edit
)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 #casa channel to ask questions quickly. And discord for office hours (currently Tuesday 5-7pm Pacific), stakeholder news, and upcoming new issues.
The text was updated successfully, but these errors were encountered: