Skip to content

[Due for payment 2025-12-26] Reports - Unreported expenses are not grouped together when sorted by Status #77843

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: 9.2.79-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: #77673
Email or phone of affected tester (no customers): yonghongkok2+161211@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Account has some unreported expenses and many expenses of different status (draft, outstanding, approved, paid).
  1. Go to staging.new.expensify.com
  2. Go to Reports > Expenses.
  3. Click Columns.
  4. Uncheck To and From.
  5. Check Status.
  6. Click Save.
  7. Click Status title on the table header.

Expected Result:

  • Unreported expenses should have "Unreported" status.
  • Unreported expenses will be grouped together.

Actual Result:

  • Unreported expenses do not have "Unreported" status.
  • Unreported expenses are not grouped together. They are randomly between other reported expenses.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7031701_1765938735002.11.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @jliexpensify

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 Dec 17, 2025
  2. melvin-bot commented on Dec 17, 2025

    @melvin-bot

    Triggered auto assignment to @jliexpensify (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.

  3. melvin-bot commented on Dec 17, 2025

    @melvin-bot

    Triggered auto assignment to @youssef-lr (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Dec 17, 2025

    @melvin-bot

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

  5. github-actions commented on Dec 17, 2025

    @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. jliexpensify commented on Dec 17, 2025

    @jliexpensify
    Contributor

    @youssef-lr not a deploy blocker, right?

  7. 5 remaining items

  8. JS00001 commented on Dec 17, 2025

    @JS00001
    Contributor

    This is expected, there is no unreported status

  9. jliexpensify commented on Dec 17, 2025

    @jliexpensify
    Contributor

    @JS00001 can we close this if it's expected?

  10. IuliiaHerets commented on Dec 18, 2025

    @IuliiaHerets

    Reproducible with v9.2.81-4. but it is expected

    bandicam.2025-12-18.13-56-53-884.mp4
  11. luacmartins commented on Dec 18, 2025

    @luacmartins
    Contributor

    This is fixed (expected)

  12. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 19, 2025
  13. changed the title [-]Reports - Unreported expenses are not grouped together when sorted by Status[/-] [+][Due for payment 2025-12-26] Reports - Unreported expenses are not grouped together when sorted by Status[/+] on Dec 19, 2025
  14. melvin-bot commented on Dec 19, 2025

    @melvin-bot

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

  15. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.84-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 2025-12-26. 🎊

  16. melvin-bot commented on Dec 19, 2025

    @melvin-bot

    @luacmartins / @JS00001 @jliexpensify 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