rubyforgood / casa

Volunteer management system for nonprofit CASA, which serves foster youth in counties across America.
https://casavolunteertracking.org/
MIT License
314 stars 478 forks source link

add training topics section to learning hours #5108

Closed compwron closed 1 year ago

compwron commented 1 year ago

What type(s) of user does this feature affect?

Description

Add functionality for Org Admins to enable and use "Learning Topic" dropdown in Learning Hours. Admins would be able to edit what volunteers are able to pick from the"Learning Topic" dropdown in the same way they are able to edit "Types of Learning". Currently a volunteer is only able to add a title and choose a "Type of Learning" from a Dropdown. See pic below

image

Acceptance Criteria

In Edit Organization in the "Manage Learning Hours" section add a "Learning Topic" section that functions and uses the same type of components as "Type of Learning". If in use, it would also be a mandatory field similar to the other field in the "Record Learning Hours" Form

image image

Please reach out to @bcastillo32 (Brandon on CASA slack) if you have any questions

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 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.

ycorredius commented 1 year ago

Would be happy to tackle this.

bcastillo32 commented 1 year ago

Would be happy to tackle this.

Thank you!

bcastillo32 commented 1 year ago

@ycorredius removed the criteria about adding topic a column in the tables FYI

github-actions[bot] commented 1 year ago

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

ycorredius commented 1 year ago

Still working. Almost done!

github-actions[bot] commented 1 year ago

This issue has been inactive for 254 hours (10.58 days) and will be unassigned after 106 more hours (4.42 days). If you have questions, please

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

github-actions[bot] commented 1 year ago

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