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-01-23] “Nothing to show” message appears after adding columns in Reports #79535
Version Number: v9.3.1-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#78864 Email or phone of affected tester (no customers):applausetester+t1sab@applause.expensifail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Web App Component: Other
Action Performed:
Open the Reports → Expenses page.
Click Columns.
Select Tax column and save.
Expected Result:
“Nothing to show” message should not appear.
All expenses are displayed with an additional column for Tax in the table.
Actual Result:
The message “Nothing to show” is displayed after adding columns.
👋 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.
The PR added columns parameter support to the search query, but the backend Search API appears to be returning empty results when the columns parameter is present in the query.
Root Cause
The PR modified buildQueryStringFromFilterFormValues() to include columns in the query. When a user selects custom columns and saves, the query string includes a columns parameter like columns:taxRate. The backend API returns hasResults: true but with an empty data array, causing the frontend to show "Nothing to show".
Evidence:
Issue is reproducible on staging but NOT on production
changed the title [-]“Nothing to show” message appears after adding columns in Reports[/-][+][Due for payment 2026-01-23] “Nothing to show” message appears after adding columns in Reports[/+]on Jan 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.3-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@JS00001@kadiealexander The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
Activity
melvin-bot commentedon Jan 14, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #78864
melvin-bot commentedon Jan 14, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 14, 2026
Triggered auto assignment to @kadiealexander (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.github-actions commentedon Jan 14, 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:
OSBotify commentedon Jan 14, 2026
Investigation Summary
Classification: Backend bug (API issue triggered by frontend changes)
Causing PR: #78864 - "Fix custom columns search syntax" by @JS00001 (High confidence)
Recommendation: REVERT
The PR added columns parameter support to the search query, but the backend Search API appears to be returning empty results when the columns parameter is present in the query.
Root Cause
The PR modified buildQueryStringFromFilterFormValues() to include columns in the query. When a user selects custom columns and saves, the query string includes a columns parameter like columns:taxRate. The backend API returns hasResults: true but with an empty data array, causing the frontend to show "Nothing to show".
Evidence:
This is a backend bug where the Search API doesnt properly handle the columns parameter.
JS00001 commentedon Jan 14, 2026
Going to revert this one
JS00001 commentedon Jan 15, 2026
This is fixed
[-]“Nothing to show” message appears after adding columns in Reports[/-][+][Due for payment 2026-01-23] “Nothing to show” message appears after adding columns in Reports[/+]melvin-bot commentedon Jan 16, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.3-8 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-01-23. 🎊
melvin-bot commentedon Jan 16, 2026
@JS00001 @kadiealexander The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]