-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[HOLD for payment 2024-06-13] [$250] Pay someone - Add receipt placeholder is shown when receipt is not allowed when paying someone #41489
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
Comments
Triggered auto assignment to @trjExpensify ( |
Triggered auto assignment to @MariaHCD ( |
👋 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:
|
@trjExpensify I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
We think this issue might be related to the #collect project. |
Production Recording.2418.mp4 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Add receipt placeholder is shown when receipt is not allowed when paying someone What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?We can get the type from parentReportAction which is pay in this case and use it here
We can also create a utility function for future cases.
We should also add this check here App/src/components/ReportActionItem/MoneyRequestView.tsx Lines 339 to 344 in 20bd114
We can hide the above part (total + separator) to make the view similar to invoices What alternative solutions did you explore? (Optional) |
This is related to the shouldShowEmptyReceiptState logic implemented in #37813 I think it makes sense to not show the receipt empty state if the IOU is already paid. cc: @cead22 @JmillsExpensify for confirmation on what the expected UI/UX should be here. |
I also don't think this should necessarily block the deploy. |
If the receipt can't be added, then I agree we shouldn't show the empty state (cc @Krishna2323 @sobitneupane) |
@cead22, thanks for the confirmation, will handle this one. |
Thanks |
Job added to Upwork: https://www.upwork.com/jobs/~0172e358c2fd0ab1cb |
@MariaHCD @trjExpensify @sobitneupane @Krishna2323 this issue is now 4 weeks old, please consider:
Thanks! |
The PR has been approved and merged |
Chill Melv, awaiting a deploy. |
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results. If a regression has occurred and you are the assigned CM follow the instructions here. If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.79-11 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-06-13. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Payment Summary
BugZero Checklist (@trjExpensify)
|
@trjExpensify, bump for payments. |
@MariaHCD, @trjExpensify, @sobitneupane, @Krishna2323 Huh... This is 4 days overdue. Who can take care of this? |
Apols, I've been OoO. Payment summary as follows:
@sobitneupane go ahead and request, @Krishna2323 I've sent you an offer. |
@trjExpensify accepted, thanks. |
Paid! |
Regression Test Proposal:
Do we agree 👍 or 👎 |
$250 approved for @sobitneupane. Reopeninf for the decision on the regression test. |
Regression test created, closing again. |
Uh oh!
There was an error while loading. Please reload this page.
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: