-
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-11-07] [HOLD for payment 2024-10-30] [GR Phase 1] Create empty components for all 6 steps and put them together creating a ‘frame’ of the whole process #50893
Comments
I am Michał from Callstack - expert contributor group. I’d like to work on this job. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.52-5 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-10-30. 🎊 For reference, here are some details about the assignees on this issue:
|
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. |
Issue is ready for payment but no BZ is assigned. @bfitzexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@bfitzexpensify)
|
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 9.0.55-10 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-11-07. 🎊 For reference, here are some details about the assignees on this issue:
|
@hungvu193 please complete the new feature checklist |
Just remember that I reviewed 2 PRs for this issue #51019 and #51231. |
Yes, total price should be $500 for 2 PRs, but with the regression, the total payout will be $250. |
I think that would be fair if we only apply penalty to the second PR (which one caused the regression). I'm not sure why we didn't create a separate issue for the refactor substeps 😬 |
That's fair - so 1st PR at $250, and second PR at $125 with the regression. @hungvu193 can you propose regression test steps to ensure the new feature will work correctly on production in further releases, and then I'll post the payment summary? |
Sure thing. I'll propose regression test later today 😁 |
Regression Test: Enable payments flow:
Reimbursement account - personal info flow:
Reimbursement account - beneficial owner info flow:
Missing personal info for issuing the card flow:
|
Thank you! Payment summary: @hungvu193 to be paid $375 through NewDot Manual Requests |
$375 approved for @hungvu193 |
Design doc link: https://docs.google.com/document/d/1Y4P7G9h0Easjcea7wyk52gKrNB9o1yTjpmJFYkrHDW4/edit?tab=t.0#bookmark=id.yapqct1l25wj
Issue Owner
Current Issue Owner: @bfitzexpensifyThe text was updated successfully, but these errors were encountered: