-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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-12-16] [$250] Web - IOU - Error message paying elsewhere partially a report with two held expenses and a tracked #53425
Comments
Triggered auto assignment to @VictoriaExpensify ( |
Triggered auto assignment to @techievivek ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
Production behavior Screen.Recording.2024-12-03.at.8.19.04.AM.mov |
@bernhardoj Do you mind taking a look at this ticket and see if it's related to your changes above? |
Job added to Upwork: https://www.upwork.com/jobs/~021864070097967682615 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @sobitneupane ( |
Demoting as discussed in thread: https://expensify.slack.com/archives/C01GTK53T8Q/p1733206499066379 |
I wanna test this on prod, but the PR is deployed to prod already. I think this issue exists on prod too. The prod video here doesn't show the pay behavior. The issue here is that, when we pay money request with held expenses partially, we use the amount of Lines 6642 to 6645 in 1462048
However, The solution to this is to subtract |
@bernhardoj This seems like something we missed? The plan already covered that.
|
@bernhardoj Please raise a PR since this is a regression (or at least it's something that was supposed to be done in the PR) |
That plan only handles the amount to be shown, not the API params. |
I'll handle this tomorrow. |
PR is ready |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.72-1 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-12-16. 🎊 For reference, here are some details about the assignees on this issue:
|
@sobitneupane @VictoriaExpensify @sobitneupane 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] |
This issue was a regression from #49971 PR and is handled by the author of the PR, payment and checklist will be handled in the original issue. |
Let's close this one. No payment is due here (regression) |
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: 9.0.70-0
Reproducible in staging?: Y
Reproducible in production?: N
Issue was found when executing this PR: #49971
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
The partial amount is paid
Actual Result:
"The requested amount has changed" error message is shown
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6682495_1733185782355.Recording__1103.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @VictoriaExpensifyThe text was updated successfully, but these errors were encountered: