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 2025-02-28] Web - Reports - Expense reports are not sorted correctly #57156
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).
Go to staging.new.expensify.com
Go to Reports.
Go to Expense Reports > All status.
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.
👋 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 [-]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
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:
@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]
Activity
melvin-bot commentedon Feb 20, 2025
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.melvin-bot commentedon Feb 20, 2025
Triggered auto assignment to @MariaHCD (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Feb 20, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Feb 20, 2025
👋 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:
MariaHCD commentedon Feb 20, 2025
Looks like the new
Expense Reportsoption 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
MariaHCD commentedon Feb 20, 2025
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
[-]Web - Reports - Expense reports are not sorted correctly[/-][+][Due for payment 2025-02-28] Web - Reports - Expense reports are not sorted correctly[/+]melvin-bot commentedon Feb 21, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Feb 21, 2025
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. 🎊
melvin-bot commentedon Feb 21, 2025
@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]