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

[CON/Mentorship Match]: Link the mentoring sessions to a respective mentorship match #949

Closed
3 tasks
katamatata opened this issue Aug 7, 2024 · 0 comments · Fixed by #991
Closed
3 tasks
Assignees
Labels

Comments

@katamatata
Copy link
Contributor

katamatata commented Aug 7, 2024

Why are we doing this?

Currently, there is no relation between mentoring sessions and respective mentorship matches. We want to create this relation in order to implement the reminder emails for mentors who haven’t logged any session for their mentorship match and to be able to send the Mentorship Program Completion Certificates to mentors and mentees. There are also other benefits to this, including accessing reports in Salesforce, and the data model simply making more sense.

What needs to be done?

  • Salesforce: The Mentoring Session object gets a new field - Mentorship Match (already added in partial and prod orgs, needs to be added on contp org).
  • Existing mentoring sessions: We run a one-time script that goes through every mentoring session, finds its related mentorship match, and assigns it to the mentoring session. This is to populate the data to the Mentorship Match field for existing mentoring sessions.
  • CON backend: When the new mentoring session is being logged, our backend links it to the related mentorship match. Make changes in the con-mentorship-matches.resolver.ts file:

In the @ResolveField for mentoringSessions
image
change the filter to look up the Mentorship Match instead of Mentor & Mentee.

Screenshots

The current state of the Mentoring Session object:
image

Ghaid's example of the solution:
image

@katamatata katamatata moved this to Ready for Execution in CON: ReDI Connect Aug 7, 2024
@astkhikatredi astkhikatredi moved this from QA by DevLead, DesignLead & PO to Done & Deployed in CON: ReDI Connect Oct 31, 2024
@katamatata katamatata linked a pull request Nov 6, 2024 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants