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-05] Domains - Member who requested admin access remains in Requests list after closing account #101042
Version Number: 9.4.77-1 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#100161 Email or phone of affected tester (no customers):applausetester+sdodjsoddddds@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
As Expensifail domain member, go to Workspaces > Domains > applause.expensifail.com > Request admin access.
Log in as Expensifal domain admin and perform the steps below:
Go to staging.new.expensify.com
Go to Workspaces > Domains.
Click applause.expensifail.com
Go to Domains members.
Search for the member who requested admin access.
Click on the member > Close account > Force close account > Close account.
Go to Domain admins.
Expected Result:
The member whose account is closed will no longer appear in Requests list.
Actual Result:
The member whose account is closed still remains in Requests list.
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
Identify the pull request that introduced this issue and revert it.
Activity
applause-bot commentedon Sep 13, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/77c9abfed5ec8e0e6c8b2db6cd11c8d6291987a23a316a79163330063b564432
melvin-bot commentedon Sep 13, 2026
@mountiny recently merged #100161, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Sep 13, 2026
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Sep 13, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Sep 13, 2026
@mountiny @ZhenjaHorbach you have been assigned to this deploy blocker because you reviewed the offending PR: #100161
melvin-bot commentedon Sep 13, 2026
@jakubstec you have been assigned to this deploy blocker because you authored the offending PR: #100161
26 remaining items
melvin-bot commentedon Oct 1, 2026
@ZhenjaHorbach Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
ZhenjaHorbach commentedon Oct 2, 2026
@mountiny
Let's close this!
melvin-bot commentedon Oct 4, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 4, 2026
Payment Summary
Resolving PRs:
fix: drop pending domain adminship request when closing a user account #101353
Contributor: @war-in does not require payment (Contractor)
Contributor: @jakubstec does not require payment (Contractor)
Reviewer: @ZhenjaHorbach owed $175 via NewDot
Contributor: @rayane-d does not require payment (Contractor)
BugZero Checklist (@mallenexpensify)