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-03-27] [HIGH] The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action #56859
The deliverable is to provide reliable reproduction steps for the bug. - Follow the Propose a solution for a job process to submit the steps for review”. Inc. preconditions and additional details if they’re helpful. (ie. require x beta to be enabled, must be on a Collect plan)
Version Number: Reproducible in staging?: Needs reproduction Reproducible in production?: Needs 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:@danielrvidal Slack conversation (hyperlinked to channel name): quality
Action Performed:
User A submits an expense to approver in a report with multiple card expenses
Approver sees a GBR in the LHN
Expected Result:
Expense to be approved appears as the last message in the expense report
Actual Result:
Expense to be approved appears somewhere on the top and user has to scroll up to find the report
It should be ordered by the date on the reportAction.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
changed the title [-]The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/-][+][CRITICAL] The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/+]on Feb 16, 2025
changed the title [-][HIGH] The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/-][+][Due for payment 2025-03-27] [HIGH] The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/+]on Mar 20, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.15-9 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@abdulrahuman5196@VictoriaExpensify@abdulrahuman5196 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: Not a regression. We fixed a possible edge case.
[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: N/A
[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. - N/A Existing normal test should be fine for this case.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Feb 13, 2025
Triggered auto assignment to @VictoriaExpensify (
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 13, 2025
Triggered auto assignment to @puneetlath (
AutoAssignerNewDotQuality)MelvinBot commentedon Feb 13, 2025
This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989
[-]The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/-][+][CRITICAL] The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/+]39 remaining items
[-][HIGH] The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/-][+][Due for payment 2025-03-27] [HIGH] The expense to be approved is not appearing at the bottom of the expense report ordered by date on report action[/+]melvin-bot commentedon Mar 20, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Mar 20, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.15-9 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-03-27. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Mar 20, 2025
@abdulrahuman5196 @VictoriaExpensify @abdulrahuman5196 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]
melvin-bot commentedon Mar 27, 2025
Payment Summary
Upwork Job
BugZero Checklist (@VictoriaExpensify)
VictoriaExpensify commentedon Mar 28, 2025
Payment summary:
Contributor: @sosek108 is from an agency-contributor and not due payment
C+: @abdulrahuman5196 owed $250 via NewDot
abdulrahuman5196 commentedon Apr 10, 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: Not a regression. We fixed a possible edge case.
[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: N/A
[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. - N/A Existing normal test should be fine for this case.
Regression Test Proposal Template
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
JmillsExpensify commentedon Apr 14, 2025
$250 approved for @abdulrahuman5196