-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[HOLD for payment 2024-01-25] [HOLD for payment 2024-01-03] Expense - Expense preview with a manual and ongoing scan does not show "x request, y scanning" #33512
Comments
👋 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:
|
Triggered auto assignment to @rlinoz ( |
This is a regression from #32469 |
Opened a PR to fix it |
PR is up and merged, but I dont think this needs to be CPed its a minor change so demoting this to not a blocker |
Per this comment #33576 (comment) this is still failing on some platforms cc @kbecciv do you have more details? |
It failed on mWeb, Desktop and IOS app RPReplay_Final1703593634.mp4 |
So the numbers are not correct but the text pattern is fine I think. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.17-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 2024-01-03. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
|
@vitHoracek you mean it should be 2 requests, 1 scanning? |
Working on a PR, should be up tomorrow. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.26-2 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 2024-01-25. 🎊 |
Triggered auto assignment to @twisterdotcom ( |
@allroundexperts is due payment for reviewing the PR |
This would be on Jan 25 right? The automation should send offers to you both. But I will handle it then if not. |
Moving to weekly since it is on hold for payment. |
Okay, so I think the payment summary is just:
|
$500 payment approved for @allroundexperts based on comment above. |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.4.16-3
Reproducible in staging?: Y
Reproducible in production?: N
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: Applause - Internal Team
Slack conversation:
Action Performed:
Expected Result:
The expense preview in the workspace chat will show "x request, y scanning
Actual Result:
The expense preview in the workspace chat just shows "Receipt", as if the receipt in the Scan request is part of the manual expense
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6324154_1703264366246.bandicam_2023-12-22_21-52-25-983__2_.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: