-
-
Notifications
You must be signed in to change notification settings - Fork 463
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
Admins/Supervisors Learning Hours Tab - Clicking on Volunteer name should route to Volunteer's Learning Hours Page #5474
Comments
Hi @bcastillo32 can you please assign this to me? |
Yes! Thank you for picking this up and please reach out if you have any questions :) |
Okay..Thanks |
This issue has been inactive for 242 hours (10.08 days) and will be unassigned after 118 more hours (4.92 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 362 hours (15.08 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. |
Impacted User Types
Current Behavior
When the Admin or Supervisor clicks on the volunteer's name in the "Learning Hours" page, they are routed to "Editing Volunteer"
How to Replicate
ex:
Expected Behavior
When the Admin or Supervisor clicks on the volunteer's name in "Learning Hours", they should be routed to that Volunteer's Learning Hours page so they see what types of learnings the volunteer has done.
Where to see the expected routing point
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 #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: