Skip to content
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

Closed
madmax330 opened this issue Oct 16, 2024 · 18 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Weekly KSv2

Comments

@madmax330
Copy link
Contributor

madmax330 commented Oct 16, 2024

Design doc link: https://docs.google.com/document/d/1Y4P7G9h0Easjcea7wyk52gKrNB9o1yTjpmJFYkrHDW4/edit?tab=t.0#bookmark=id.yapqct1l25wj

Issue OwnerCurrent Issue Owner: @bfitzexpensify
@MrMuzyk
Copy link
Contributor

MrMuzyk commented Oct 17, 2024

I am Michał from Callstack - expert contributor group. I’d like to work on this job.

@madmax330 madmax330 added the Daily KSv2 label Oct 17, 2024
@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 Awaiting Payment Auto-added when associated PR is deployed to production and removed Daily KSv2 Weekly KSv2 labels Oct 18, 2024
@melvin-bot melvin-bot bot changed the title [GR Phase 1] Create empty components for all 6 steps and put them together creating a ‘frame’ of the whole process [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 Oct 23, 2024
Copy link

melvin-bot bot commented Oct 23, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 23, 2024
Copy link

melvin-bot bot commented Oct 23, 2024

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:

  • @hungvu193 requires payment through NewDot Manual Requests
  • @MrMuzyk does not require payment (Contractor)

@melvin-bot melvin-bot bot added Reviewing Has a PR in review Weekly KSv2 and removed Weekly KSv2 labels Oct 24, 2024
Copy link

melvin-bot bot commented Oct 29, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

@melvin-bot melvin-bot bot added Weekly KSv2 Daily KSv2 and removed Weekly KSv2 labels Oct 29, 2024
Copy link

melvin-bot bot commented Oct 30, 2024

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!

Copy link

melvin-bot bot commented Oct 30, 2024

Payment Summary

Upwork Job

  • Reviewer: @hungvu193 owed $250 via NewDot
  • Contributor: @MrMuzyk is from an agency-contributor and not due payment

BugZero Checklist (@bfitzexpensify)

  • I have verified the correct assignees and roles are listed above and updated the neccesary manual offers
  • I have verified that there are no duplicate or incorrect contracts on Upwork for this job (https://www.upwork.com/ab/applicants//hired)
  • I have paid out the Upwork contracts or cancelled the ones that are incorrect
  • I have verified the payment summary above is correct

Copy link

melvin-bot bot commented Oct 31, 2024

⚠️ Looks like this issue was linked to a Deploy Blocker here

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.

@melvin-bot melvin-bot bot added Weekly KSv2 and removed Daily KSv2 labels Oct 31, 2024
@melvin-bot melvin-bot bot changed the title [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 [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 Oct 31, 2024
@melvin-bot melvin-bot bot removed the Reviewing Has a PR in review label Oct 31, 2024
Copy link

melvin-bot bot commented Oct 31, 2024

Reviewing label has been removed, please complete the "BugZero Checklist".

Copy link

melvin-bot bot commented Oct 31, 2024

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 requires payment through NewDot Manual Requests
  • @MrMuzyk does not require payment (Contractor)

@garrettmknight
Copy link
Contributor

@hungvu193 please complete the new feature checklist

@hungvu193
Copy link
Contributor

Just remember that I reviewed 2 PRs for this issue #51019 and #51231.
Should the price for this issue be 500$? cc @garrettmknight and @madmax330

@bfitzexpensify
Copy link
Contributor

Yes, total price should be $500 for 2 PRs, but with the regression, the total payout will be $250.

@hungvu193
Copy link
Contributor

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 😬

@bfitzexpensify
Copy link
Contributor

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?

@hungvu193
Copy link
Contributor

Sure thing. I'll propose regression test later today 😁

@hungvu193
Copy link
Contributor

Regression Test:

Enable payments flow:

  1. Log in to the App
  2. Go to Settings -> Wallet
  3. Add bank account
  4. Click "Enable wallet"
  5. Test all the "Personal info" steps full name, address, date of birth.

Reimbursement account - personal info flow:

  1. Log in to the App
  2. Create a new workspace
  3. Invite new member to the workspace
  4. Go to More features section and enable the Expensify Card option
  5. Go to Expensify Card section that just appeared
  6. Tap Issue new card
  7. Go through the process of connecting to the bank account.
  8. At some point in the process you'll need to provide requestor information like first and last name, date of birth etc. - test if it works correctly

Reimbursement account - beneficial owner info flow:

  1. Repeat steps 1-7 described above
  2. On the later steps of the process, you'll be asked: "Do you own 25% or more of Alberta Bobbeth Charleson?" - select "No"
  3. On the next step: "Do any individuals own 25% or more of Alberta Bobbeth Charleson?" - select "Yes"
  4. You'll land on the next personal info multiple steps form - test it if it works correctly.

Missing personal info for issuing the card flow:

  1. Log in to the App as User A.
  2. Go to the Workspace that you are admin of.
  3. Invite a completely new user (User B).
  4. Turn on Expensify Card for this workspace if not done yet.
  5. Set it up
  6. Tap "Issue new card" and issue the card for User B.
  7. Log in to the App as User B.
  8. Go to the Workspace chat - you should see the "Add shipping details" button - tap it.
  9. You'll see the multiple-step form asking you to fill in your personal details - test it and make sure it works as expected.

@bfitzexpensify
Copy link
Contributor

Thank you!

Payment summary:

@hungvu193 to be paid $375 through NewDot Manual Requests
@MrMuzyk does not require payment (Contractor)

@github-project-automation github-project-automation bot moved this from External Bugs and Follow Up Issues to Done in [#whatsnext] #expense Nov 7, 2024
@garrettmknight
Copy link
Contributor

$375 approved for @hungvu193

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Weekly KSv2
Projects
Status: Done
Development

No branches or pull requests

5 participants