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
{{ message }}
Repository navigation
[Due for payment 2026-10-30] R2: Show Ashby-specific Advanced approver fields #103091
Make the Recruiting Advanced-approval field selector show the roles supported by the connected ATS provider. Ashby offers Recruiter, Hiring Manager, and Recruiting Coordinator; Greenhouse continues to offer Recruiter and Recruiting Coordinator.
Implementation notes (from design doc)
Extend src/CONST/index.ts with the Ashby Hiring Manager approver-field value. Use the value accepted by Web's provider-specific validation in #675428.
Update src/pages/workspace/recruiting/approver/MergeATSApproverFieldPage.tsx to derive its options from the connected provider instead of displaying every value in CONST.MERGE.ATS_APPROVER_FIELD.
Update src/pages/workspace/recruiting/utils.ts so the selected Hiring Manager value has a readable label on the approval page and Recruiting card.
Add the English and Spanish translation strings. Keep the existing Greenhouse options and saved values working.
Verify the approval draft and Save flow sends the Ashby selection to the existing UpdateMergeApprovalMode or UpdateMergeATSApproverField command.
Tests
Greenhouse shows only Recruiter and Recruiting Coordinator.
Ashby shows Recruiter, Hiring Manager, and Recruiting Coordinator.
A saved Ashby Hiring Manager selection appears correctly when the admin reopens the page and on the Recruiting card.
changed the title [-]R2: Show Ashby-specific Advanced approver fields[/-][+][Due for payment 2026-10-30] R2: Show Ashby-specific Advanced approver fields[/+]on Oct 23, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.18-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
Activity
melvin-bot commentedon Oct 5, 2026
Triggered auto assignment to Design team member for new feature review - @shawnborton (
NewFeature)shawnborton commentedon Oct 6, 2026
Anything needed from Design here?
bernhardoj commentedon Oct 6, 2026
I think no
trjExpensify commentedon Oct 12, 2026
Same here, going to move this to #convert as discussed.
[-]R2: Show Ashby-specific Advanced approver fields[/-][+][Due for payment 2026-10-30] R2: Show Ashby-specific Advanced approver fields[/+]melvin-bot commentedon Oct 23, 2026
@bernhardoj / @DylanDylann
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.18-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-30. 🎊
Contributor+ Checklist: The following checklist (instructions) needs to be completed before this issue can be closed:
If no checklist is needed for this issue, use the K2 [no checklist button].
melvin-bot commentedon Oct 26, 2026
@bernhardoj Whoops! This issue is 2 days overdue. Let's get this updated quick!
DylanDylann commentedon Oct 28, 2026
Not overdue. And no payment required
melvin-bot commentedon Oct 28, 2026
@bernhardoj Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Oct 29, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 29, 2026
Payment Summary
Resolving PRs:
[Merge ATS] Add Ashby specific approver field #103134
Reviewer: @bernhardoj owed $175 via NewDot
Reviewer: @DylanDylann owed $175 via NewDot
BugZero Checklist (@mallenexpensify)