-
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-08-14] [$250] [CVP] [Critical] Not redirecting to workspace chat and not converting the IOU to an expense report when Pay with business account selected #46339
Comments
Triggered auto assignment to @lschurr ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.In bottom-up flow, after paying with Expensify using Business bank account, a new workspace created but:
What is the root cause of that problem?For 2, I could not reproduce it, the IOU is indeed converted to a new expense report inside the newly created workspace. We can easily see that in QA's second video at
For 1, we does not navigate to the workspace chat after creation, just navigate to the add bank account page: App/src/components/KYCWall/BaseKYCWall.tsx Lines 128 to 138 in 4ffbd42
What changes do you think we should make in order to solve the problem?
App/src/libs/actions/Policy/Policy.ts Line 2067 in e0581a8
App/src/libs/actions/Policy/Policy.ts Lines 2401 to 2402 in e0581a8
So when const {policyID, workspaceChatReportID, reportPreviewReportActionID} = Policy.createWorkspaceFromIOUPayment(iouReport) ?? {};
if (workspaceChatReportID) {
Navigation.navigate(ROUTES.REPORT_WITH_ID.getRoute(workspaceChatReportID, reportPreviewReportActionID));
} Screenshotsnavigate-to-workspace.movRHP opens on top of Workspace chatThe workspace chat is GBR'ed right away |
Proposal Updated
|
Confirming a couple of things in thread. In the meantime, @gijoe0295 can you include a video of your proposal above to check the expected results? Thanks! |
Okay, so sounds like the two items to look at here are:
|
Job added to Upwork: https://www.upwork.com/jobs/~01f077fda3c01ec8f0 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
@mananjadhav can you jump on that proposal review, please? We'd love to get this one turned around ASAP. Thanks! |
@trjExpensify @mananjadhav Added screenshots to my proposal. My initial proposal addresses all the latest expectations #46339 (comment). |
Note that we have a regression from #46323 where App/src/components/AddPaymentMethodMenu.tsx Lines 75 to 82 in 25646b9
The condition should be |
^^ @marcaaron given the context on that PR that deployed a few hours ago, checking you're okay with that change. For the bottom-up flow, both of these options should be retained: |
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. |
@gijoe0295 's proposal looks good to me. 🎀 👀 🎀 C+ reviewed. |
Triggered auto assignment to @danieldoglas, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
PR ready in 3 hours. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.17-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-08-14. 🎊 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:
|
@trjExpensify Before summarizing payment I wonder if I'm eligible for payments for #46490 since I posted a working solution being used in the PR. |
Yeah, we ended up doing two PRs in the end to clear that blocker? |
@trjExpensify That's correct. And the blocker's PR was implemented by @mananjadhav. |
@trjExpensify We implemented two PRs - one for this blocker which I wrote and the second one for another issue that this PR @gijoe0295 wrote. But yeah I agree they posted the solution before I implemented in the comments. I implemented it unblock the release. |
Cool, so I'll do the following:
How does that sound? |
A little confused here. Are we talking about any other issue? I don’t think the blocker PR implemented was reviewed by C+. I am not in front of the system. I can check later. |
@trjExpensify I don't think I reviewed any PR regarding this issue 😅 |
Ah, @mollfpr is right. You were assigned, but didn't review. Cool, so two issues, two PRs:
Issue: Expense - "Business bank account" option appears briefly when paying with Expensify
So amending the payment summary as follows:
Sound right? |
That’s right. |
Okay great, go ahead and request Manan. @gijoe0295 I've settled up. |
$500 approved for @mananjadhav |
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.13-3
Reproducible in staging?: Y
Reproducible in production?: Y
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: @quinthar
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1722037742346479
Action Performed:
Expected Result:
A new workspace created and moved the IOU to "expense report" for the payer and user redirected to workspace chat
Actual Result:
Workspace created , Not redirected to workspace chat and not converting the IOU to an expense report
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Screen.Recording.2024-07-26.at.4.52.15.PM.mov
Recording.389.mp4
Logs.txt
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @trjExpensifyThe text was updated successfully, but these errors were encountered: