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-19] Spend - After unreporting expense, table is shown without expense on group-by:approver view #105558
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):spodsjondoisjjdo@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.
Click Submit and Approve.
Go to Spend > Expenses.
Click Display > Group by > Approver > Apply.
Expand the group.
Open the expense.
Click More > Unapprove.
Click Report > Remove from report.
Collapse and expand the group.
Expected Result:
After removing expense from report, table will disappear as there is no expense with approver.
Actual Result:
After removing expense from report, table remains.
After collapsing and expanding the group, table is shown without the expense.
👋 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 unreporting expense, table is shown without expense on group-by:approver view[/-][+][Due for payment 2026-11-19] Spend - After unreporting expense, table is shown without expense on group-by:approver view[/+]on Nov 12, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.36-0 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-19. 🎊
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]
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: N/A
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
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/01f9a3ecda59dbc873e06e3855cc02d099986fd607be19b895635283b8e2b01c
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 @iwiznia (
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
14 remaining items
nkdengineer commentedon Nov 9, 2026
@daledah The PR is ready.
[-]Spend - After unreporting expense, table is shown without expense on group-by:approver view[/-][+][Due for payment 2026-11-19] Spend - After unreporting expense, table is shown without expense on group-by:approver view[/+]melvin-bot commentedon Nov 12, 2026
@nkdengineer / @daledah
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.36-0 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-19. 🎊
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]
daledah commentedon Nov 12, 2026
Contributor+ Checklist:
[Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to the comment on the PR: N/A
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎