Skip to content

[Due for payment 2026-01-23] “Nothing to show” message appears after adding columns in Reports #79535

Closed

Description

@mitarachim

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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:

  1. Open the Reports → Expenses page.
  2. Click Columns.
  3. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

Bug7048765_1768379716744.2026-01-14_09-33-32.mp4
Bug7048765_1768378533768.2026-01-14_09-05-27.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @kadiealexander

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jan 14, 2026
  2. melvin-bot commented on Jan 14, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78864

  3. melvin-bot commented on Jan 14, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. melvin-bot commented on Jan 14, 2026

    @melvin-bot

    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.

  5. github-actions commented on Jan 14, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. OSBotify commented on Jan 14, 2026

    @OSBotify
    Contributor

    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:

    • Issue is reproducible on staging but NOT on production
    • PR Fix custom columns search syntax #78864 is in staging deploy checklist v9.3.1-0
    • Bug occurs after adding columns via Columns button
    • Frontend code is correct - no filtering logic removes results based on columns
    • Backend returns hasResults:true with empty data array

    This is a backend bug where the Search API doesnt properly handle the columns parameter.

  7. JS00001 commented on Jan 14, 2026

    @JS00001
    Contributor

    Going to revert this one

  8. removed
    DeployBlockerIndicates it should block deploying the API
    on Jan 14, 2026
  9. JS00001 commented on Jan 15, 2026

    @JS00001
    Contributor

    This is fixed

  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 16, 2026
  11. 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
  12. melvin-bot commented on Jan 16, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  13. melvin-bot commented on Jan 16, 2026

    @melvin-bot

    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. 🎊

  14. melvin-bot commented on Jan 16, 2026

    @melvin-bot

    @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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions