Open JoshBeveridge opened 6 months ago
Notes from Lauren: Hybrid - Just ask "you are willing to work 2 or more days in the office..." and remove the question asking how many days. 1 day is not an option in any department, so let's not create an expectations gap.
@gobyrne
1 day might not be an option in departments, but it is an option for a fully remote employee to request. In my opinion, it's helpful for a manager to know that their fully remote employee is open to hybrid days in the office, even if it's only once a week.
We have DISCUSSED
People might already be living in a location, like the NCR, in which case they would not relocate to NCR as they already live there This would need to be kept in mind for matching by location.
Need to figure out matching and search page design
Replace the slashes (City or town)(Province, territory or region)
Do we run a migration to "translate" Province or territory to Province, territory or region?
Do we run a migration if only "telework" -> Remote Work, else if NOT "telework" -> On-site, else Hybrid
?
Just for simplicity, lets revert the "Relocation details" back to "location exemptions" for the time being. Josh's proposal here is better, but it's not better enough to throw out the old data or run a migration for it imo. Not when we want to do better again the future (#10274)
Need to update the design on the Talent search page for managers too: I think we can ask about Hybrid and Remote work separately. Then we still kinda need to provide the list of regions again to allow for satellite office locations. Or new UI.
Then describe search logic for the devs
Assuming managers are asked:
City and the exemptions are not validated, so we can only match on Province/territory/region location field
Matching logic sudocode:
@Jerryescandon let's discuss
@Jerryescandon to look into exclusion region data and leaving it as exclusion vs migrating it to "relocation details". @NienkeBr to update for 3 days hybrid
@GCTC-NTGC/designers Re the location preference screenshots currently in the GitHub tickets, I'd rather have the copy say:
✨ Summary
Visit the Figma file • Contact @substrae with design questions
This ticket aims to provide both clarity and flexibility to the way applicants communicate their location and work location preferences. It includes moving a few fields around, adding a field or two, and updating copy.
✅ Requirements
Current city
andProvince or territory
to theWork preferences
formRelocation
radio groupRelocation provinces / territories / regions
multiselect field that only shows if the user choosesYes
to relocationRelocation details
field that also only appears if the user choosesYes
to relocation🔍 Details
📸 Relocation logic
![image](https://github.com/user-attachments/assets/f21e7c0f-4d4a-4310-b075-6c7f04ab74ec)📸 Full form (light and dark modes)
![image](https://github.com/user-attachments/assets/313d528e-5790-42dc-a5c0-83a345514925)🔍 Talent Search page
📸 Work location section (new)
![image](https://github.com/user-attachments/assets/8f913989-8d3f-4cc2-88f1-355eec6a5388)
📸 Work location section (dark mode)
![image](https://github.com/user-attachments/assets/f8b3d127-43c7-4a06-a269-4c1d0775d79d)
🔍 Admin pages
We encounter the location as a read view on User profile and the User application snapshot. We also encounter the location as a filter on several places "Candidates", "Candidate results" when inside a specific request and "Candidates table" in the talent placement tab of a process.
📸 New location filter
![image](https://github.com/user-attachments/assets/b38a7b79-cc3e-4197-80a9-f9481b7ffddb)