Skip to content

[Due for payment 2025-02-28] Web - Reports - Expense reports are not sorted correctly #57156

Closed

Description

@IuliiaHerets

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.1.2-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 TestRail: Exp
Email or phone of affected tester (no customers): applausetester+190201kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Search

Action Performed:

Precondition:

  • Account has a few grouped expenses (a few expenses in each report) and also single expenses (one expense in each report).
  1. Go to staging.new.expensify.com
  2. Go to Reports.
  3. Go to Expense Reports > All status.
  4. Click on the sorting (Date, Merchant, Total).

Expected Result:

The expense reports will be sorted accordingly.

Actual Result:

The expense reports are not sorted correctly. Sometimes the reports (in different accounts) are not sorted at all.

Workaround:

Unknown

Platforms:

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

https://github.com/user-attachments/assets/b874062a-f1a6-46b6-be5e-10123c659ebe
https://github.com/user-attachments/assets/4a0bd40c-e15a-480a-b312-675de4e72064

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @abekkala

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerCashThis issue or pull request should block deployment
    on Feb 20, 2025
  2. melvin-bot commented on Feb 20, 2025

    @melvin-bot

    Triggered auto assignment to @abekkala (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 Feb 20, 2025

    @melvin-bot

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

  4. melvin-bot commented on Feb 20, 2025

    @melvin-bot

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

  5. github-actions commented on Feb 20, 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. MariaHCD commented on Feb 20, 2025

    @MariaHCD
    Contributor

    Looks like the new Expense Reports option in the LHN was added here: #56850

    @ishpaul777 @ZhenjaHorbach mind taking a look here? Do the filters currently only work for expenses and not for expense reports?

    cc: @puneetlath

  7. MariaHCD commented on Feb 20, 2025

    @MariaHCD
    Contributor

    Related Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1740032671476689

    For now, we've gone ahead with a temporary solution of disabling the sorting options for expense reports: #57175

    We can discuss whether we want to have these sorting options for expense reports and if so, a new PR can be raised for that as part of #56785

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Feb 21, 2025
  9. changed the title [-]Web - Reports - Expense reports are not sorted correctly[/-] [+][Due for payment 2025-02-28] Web - Reports - Expense reports are not sorted correctly[/+] on Feb 21, 2025
  10. melvin-bot commented on Feb 21, 2025

    @melvin-bot

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

  11. melvin-bot commented on Feb 21, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.3-4 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-02-28. 🎊

  12. melvin-bot commented on Feb 21, 2025

    @melvin-bot

    @MariaHCD @abekkala @MariaHCD 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.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions