You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The content you are editing has changed. Please copy your edits and refresh the page.
✨ 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:
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
🙋♀️ Proposed Implementation
Update PoolCandidate.scopeAvailable
Currently Qualified available, Placed Tentative and Placed Casual show up in searches. To this we need to add:
(Probably update the qualifiedEquivalentGroup?)
And filter out anyone with "suspendedAt" date.
✅ Acceptance Criteria
🛑 Blockers
Blocked By
The text was updated successfully, but these errors were encountered: