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-11-23] Spend - After approving report, result only shows up after reapplying group-by:approver #105557
Version Number: 9.5.27-0 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:#102635 Email or phone of affected tester (no customers):sondjosdjosio@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Search
Action Performed:
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Go to Spend > Expenses.
Click Display > Group by > Approver > Apply.
Go back to workspace chat.
Click Submit and Approve on the expense.
Go to Spend > Expenses.
→ No result is returned after submitting and approving report when group by is Approver.
Click Display > Group by > Reset.
Click Display > Group by > Approver > Apply.
→ Result only returns after reapplying group-by:approver.
Expected Result:
After approving report, result will auto show up on group-by:approver view.
Actual Result:
After approving report, result only shows up after reapplying group-by:approver.
👋 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.
changed the title [-]Spend - After approving report, result only shows up after reapplying group-by:approver[/-][+][Due for payment 2026-11-23] Spend - After approving report, result only shows up after reapplying group-by:approver[/+]on Nov 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.39-2 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-11-23. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
applause-bot commentedon Oct 31, 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/4c2be7f5c7a71d37e6f6f74bc889d3007db243b715297ccecb788be8dc7f2266
melvin-bot commentedon Oct 31, 2026
@neil-marcellini recently merged #102635, but they are OOO right now, so I'll auto-assign someone else.
melvin-bot commentedon Oct 31, 2026
Triggered auto assignment to @amyevans (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Oct 31, 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 Oct 31, 2026
@neil-marcellini @daledah you have been assigned to this deploy blocker because you reviewed the offending PR: #102635
melvin-bot commentedon Oct 31, 2026
@nkdengineer you have been assigned to this deploy blocker because you authored the offending PR: #102635
9 remaining items
melvin-bot commentedon Nov 5, 2026
@nkdengineer Whoops! This issue is 2 days overdue. Let's get this updated quick!
nkdengineer commentedon Nov 6, 2026
@daledah The PR is ready for review.
[-]Spend - After approving report, result only shows up after reapplying group-by:approver[/-][+][Due for payment 2026-11-23] Spend - After approving report, result only shows up after reapplying group-by:approver[/+]melvin-bot commentedon Nov 16, 2026
@nkdengineer / @daledah
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.39-2 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-11-23. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]