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

✨ Allow users to opt back into talent searches after they are hired #12212

Closed
6 tasks
gobyrne opened this issue Dec 5, 2024 · 1 comment · Fixed by #12330
Closed
6 tasks

✨ Allow users to opt back into talent searches after they are hired #12212

gobyrne opened this issue Dec 5, 2024 · 1 comment · Fixed by #12330
Assignees
Labels
deployment Requires a change during deployment feature New feature or request.

Comments

@gobyrne
Copy link
Member

gobyrne commented Dec 5, 2024

✨ User story

As an employee that was hired through the platform, I want to start showing up in talent searches again, so I can move to a new job if the one I'm in isn't ideal.

🕵️ Details

In the new applicant dashboard dialogues #12214, we present UI for hired candidates to opt back in for being referred. This doesn't work yet though! So... we should probably fix that.

Right now only candidates with Qualified-Available and Placed-Casual (and Placed-Tentatative) statuses will show up in searches. We want to allow for more flexibility when candidates are "placed".

In this new model, we will "suspend" candidates when they get placed (unless it's placed-casual), but we continue to allow "Placed" candidates to show up in searches.

Update the search

Currently Qualified available, Placed Tentative and Placed Casual show up in searches. To this we need to add:

  • Placed term
  • Placed indeterminate

Of course, anyone with a "suspendedAt" date, will not show up in talent searches.

Suspend candidates when placed

Add new functionality:
When an admin sets Placed term or Placed indeterminate for a candidate - set the "suspendedAt" date (as well as the placedAt date). Updating to ANY OTHER status sets suspendedAt date to null.

Migration to make this work for all current users

To make this work for existing applications, we need to "suspend" all candidates that are currently Placed term, or Placed indeterminate

  • Write a artisan command to set "suspendedAt"="placedAt" for all Placed term and Placed indeterminate candidates. Write this as a SQL command or Eloquent update command, not a loop of code, for efficiency. Ensure its wrapped in a transaction. Run this at deployment.
  • Create a ticket to delete your artisan command

🙋‍♀️ Proposed Implementation

Update PoolCandidate.scopeAvailable

Currently Qualified available, Placed Tentative and Placed Casual show up in searches. To this we need to add:

  • Placed term
  • Placed indeterminate

(Probably update the qualifiedEquivalentGroup?)

And filter out anyone with "suspendedAt" date.

✅ Acceptance Criteria

  • Search updated to show all "Placed" candidates (unless they are suspended)
  • New functionality to suspend candidates when an admin sets them to Placed-term or Placed-indeterminate
  • Artisan command to suspend currently Placed-term and Placed-indeterminate candidates
    • create ticket to delete command in the future
  • phpunit feature tests that updating a user sets suspendedAt correctly.
  • add/update phpunit tests to ensure Placed-term and Placed-intedeterminate candidates show up in search correctly (including not showing up when suspended)

🛑 Blockers

Blocked By

Preview Give feedback
No tasks being tracked yet.
@gobyrne gobyrne added the feature New feature or request. label Dec 5, 2024
@gobyrne gobyrne added this to the New Applicant Dashboard milestone Dec 5, 2024
@gobyrne gobyrne added the review in refinement Ready to be looked at and pulled into "ready to dev" label Dec 5, 2024
@tristan-orourke tristan-orourke removed the review in refinement Ready to be looked at and pulled into "ready to dev" label Dec 9, 2024
@tristan-orourke tristan-orourke moved this to 🏭 Ready for Estimate in GC Digital Talent Dec 9, 2024
Copy link

Status: Blocked ❌

Issues blocking this PR:


This comment was automatically written by the Blocking Issues bot, and this PR will be monitored for further progress.

@github-actions github-actions bot added the blocked: dependencies Blocked by other issues. label Dec 16, 2024
@tristan-orourke tristan-orourke added the deployment Requires a change during deployment label Dec 16, 2024
@tristan-orourke tristan-orourke moved this from 🏭 Ready for Estimate to 📋 Ready for Dev in GC Digital Talent Dec 16, 2024
@tristan-orourke tristan-orourke moved this from 📋 Ready for Dev to 🏃 Prioritized for Dev in GC Digital Talent Dec 16, 2024
@vd1992 vd1992 self-assigned this Dec 16, 2024
@vd1992 vd1992 moved this from 🏃 Prioritized for Dev to 🏗 In progress in GC Digital Talent Dec 16, 2024
@tristan-orourke tristan-orourke removed the blocked: dependencies Blocked by other issues. label Dec 17, 2024
@vd1992 vd1992 moved this from 🏗 In progress to 👀 In review in GC Digital Talent Dec 17, 2024
@github-project-automation github-project-automation bot moved this from 👀 In review to ✅ Done in GC Digital Talent Dec 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployment Requires a change during deployment feature New feature or request.
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants