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
Version Number: Reproducible in staging?: need reproduction Reproducible in production?: need reproduction If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: If this was caught during regression testing, add the test name, ID and link from TestRail: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@joekaufmanexpensify Slack conversation (hyperlinked to channel name): expensify - convert
Action Performed:
Login to an account with a lot of report history.
Go to Reports > Expense reports.
Expected Result:
Expense reports are sorted by date in descending order, by default. Meaning you see most recent reports first. Actual query is "inputQuery":"type:expense status:all sortBy:date sortOrder:desc groupBy:reports"
Actual Result:
Expense reports are not shown in this order in the frontend. The list seems to skip around years a bit.
Workaround:
unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Android: Standalone
Android: HybridApp
Android: mWeb Chrome
iOS: Standalone
iOS: HybridApp
iOS: mWeb Safari
Windows: Chrome
MacOS: Chrome / Safari
MacOS: Desktop
Platforms Tested:
On which of our officially supported platforms was this issue tested:
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@brunovjk@sakluger@brunovjk 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]
1a. Result of the original design (eg. a case wasn't considered)
1b. Mistake during implementation
1c. Backend bug
1z. Other:
Where bug was reported:
2a. Reported on production (eg. bug slipped through the normal regression and PR testing process on staging)
2b. Reported on staging (eg. found during regression or PR testing)
2d. Reported on a PR
2z. Other:
Who reported the bug:
3a. Expensify user
3b. Expensify employee
3c. Contributor
3d. QA
3z. Other:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: No PR directly introduced the bug, the part that was changed in the file remained with the same logic since its creation.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Test:
Login to an account with a lot of report history.
Go to Reports > Expense reports.
Check if expense reports are shown in correct order.
i. sorted by date with descending order (newest are first)
Activity
melvin-bot commentedon Apr 17, 2025
Triggered auto assignment to @sakluger (
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.MelvinBot commentedon Apr 17, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
sakluger commentedon Apr 17, 2025
I asked a clarifying question in the original thread.
sakluger commentedon Apr 17, 2025
I was able to reproduce. The trick is to scroll down quickly. I see old reports from 2022, then a half second later, 2023 reports load.
[-]Showing incorrect expense reports search query[/-][+][$250] Showing incorrect expense reports search query[/+]melvin-bot commentedon Apr 17, 2025
Job added to Upwork: https://www.upwork.com/jobs/~021912986422304272884
78 remaining items
melvin-bot commentedon May 22, 2025
📣 @brunovjk 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!
Offer link
Upwork job
[-][$250] Showing incorrect expense reports search query[/-][+][Due for payment 2025-06-02] [$250] Showing incorrect expense reports search query[/+]melvin-bot commentedon May 26, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon May 26, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.51-6 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-06-02. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon May 26, 2025
@brunovjk @sakluger @brunovjk 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]
brunovjk commentedon Jun 2, 2025
BugZero Checklist:
Bug classification
Source of bug:
Where bug was reported:
Who reported the bug:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: No PR directly introduced the bug, the part that was changed in the file remained with the same logic since its creation.
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
Regression Test Proposal
Test:
i. sorted by date with descending order (newest are first)
Do we agree 👍 or 👎
sakluger commentedon Jun 2, 2025
Summarizing payment on this issue:
Contributor: @sosek108 - No payment required, contractor
Contributor+: @brunovjk $250, paid via Upwork