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

[$250] [HOLD for payment 2024-10-17] [Wave Control] [QBD] Handle the initial connection for QBD #49697

Closed
lakchote opened this issue Sep 25, 2024 · 15 comments
Assignees
Labels
Awaiting Payment Auto-added when associated PR is deployed to production Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor

Comments

@lakchote
Copy link
Contributor

lakchote commented Sep 25, 2024

Will be worked on by an external contributor (see https://expensify.slack.com/archives/C03SLTAEULW/p1726876645021139).

Design doc link: https://docs.google.com/document/d/1LQNlTBlHjFqRdru_4UkqVr0QRseNNDq2IhFFpXcgfwY/edit#bookmark=id.uy1tfxvjfmf3

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021847419775270058956
  • Upwork Job ID: 1847419775270058956
  • Last Price Increase: 2024-10-18
  • Automatic offers:
    • hoangzinh | Reviewer | 104527673
    • ZhenjaHorbach | Contributor | 104527674
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @hoangzinh
@lakchote lakchote self-assigned this Sep 25, 2024
@lakchote lakchote moved this to Release 3: Fall 2024 (Nov) in [#whatsnext] #expense Sep 25, 2024
@lakchote lakchote changed the title [HOLD E#430951] Handle the initial connection for QBD [HOLD E#430951] [Wave Control] [QBD] Handle the initial connection for QBD Sep 25, 2024
@lakchote lakchote changed the title [HOLD E#430951] [Wave Control] [QBD] Handle the initial connection for QBD [Wave Control] [QBD] Handle the initial connection for QBD Oct 2, 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 Weekly KSv2 labels Oct 7, 2024
@melvin-bot melvin-bot bot changed the title [Wave Control] [QBD] Handle the initial connection for QBD [HOLD for payment 2024-10-17] [Wave Control] [QBD] Handle the initial connection for QBD Oct 10, 2024
Copy link

melvin-bot bot commented Oct 10, 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 10, 2024
Copy link

melvin-bot bot commented Oct 10, 2024

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.47-4 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-17. 🎊

For reference, here are some details about the assignees on this issue:

  • @hoangzinh requires payment (Needs manual offer from BZ)

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

melvin-bot bot commented Oct 17, 2024

Issue is ready for payment but no BZ is assigned. @mallenexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks!

Copy link

melvin-bot bot commented Oct 17, 2024

Payment Summary

Upwork Job

  • ROLE: @hoangzinh paid $(AMOUNT) via Upwork (LINK)

BugZero Checklist (@mallenexpensify)

  • 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

@dylanexpensify dylanexpensify moved this from Release 3: Fall 2024 (Nov) to Hold for Payment in [#whatsnext] #expense Oct 18, 2024
@mallenexpensify mallenexpensify added the Bug Something is broken. Auto assigns a BugZero manager. label Oct 18, 2024
Copy link

melvin-bot bot commented Oct 18, 2024

Current assignee @mallenexpensify is eligible for the Bug assigner, not assigning anyone new.

@mallenexpensify mallenexpensify added the External Added to denote the issue can be worked on by a contributor label Oct 18, 2024
@melvin-bot melvin-bot bot changed the title [HOLD for payment 2024-10-17] [Wave Control] [QBD] Handle the initial connection for QBD [$250] [HOLD for payment 2024-10-17] [Wave Control] [QBD] Handle the initial connection for QBD Oct 18, 2024
Copy link

melvin-bot bot commented Oct 18, 2024

Job added to Upwork: https://www.upwork.com/jobs/~021847419775270058956

@melvin-bot melvin-bot bot added the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 18, 2024
Copy link

melvin-bot bot commented Oct 18, 2024

Current assignee @hoangzinh is eligible for the External assigner, not assigning anyone new.

@mallenexpensify
Copy link
Contributor

@hoangzinh can you please accept the job and reply here once you have?
https://www.upwork.com/jobs/~021847419775270058956

You were assigned on the date of your eligibility, since you're not setup on NewDot payments yet and I want to err on the safe side, I want to pay this via Upwork.

@mallenexpensify mallenexpensify removed the Help Wanted Apply this label when an issue is open to proposals by contributors label Oct 18, 2024
@hoangzinh
Copy link
Contributor

Accepted the offer. Btw @mallenexpensify, @ZhenjaHorbach should be assigned to this issue as a C+ too.

Copy link

melvin-bot bot commented Oct 22, 2024

📣 @hoangzinh 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job

Copy link

melvin-bot bot commented Oct 22, 2024

📣 @ZhenjaHorbach 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app!

Offer link
Upwork job
Please accept the offer and leave a comment on the Github issue letting us know when we can expect a PR to be ready for review 🧑‍💻
Keep in mind: Code of Conduct | Contributing 📖

@mallenexpensify
Copy link
Contributor

mallenexpensify commented Oct 22, 2024

Contributor: @hoangzinh paid $250 via Upwork
Contributor+: @ZhenjaHorbach paid $250 via Upwork

@ZhenjaHorbach can you please accept the job and reply here once you have?
https://www.upwork.com/jobs/~021847419775270058956

Also, plz complete the BZ checklist.

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:

  • [@] The PR that introduced the bug has been identified. Link to the PR:
  • [@] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:
  • [@] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:
  • [@] Determine if we should create a regression test for this bug.
  • [@] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • [@bz] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

@ZhenjaHorbach
Copy link
Contributor

ZhenjaHorbach commented Oct 22, 2024

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:

  • [@] The PR that introduced the bug has been identified. Link to the PR:

New feature

  • [@] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment:

New feature

  • [@] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion:

NA

  • [@] Determine if we should create a regression test for this bug.
  • [@] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
  • Sign in on an account that enabled beta quickbooksDesktopOnNewDot
  • Go to any Workspace
  • Enable Accounting if it hasn't enabled
  • Go to Workspace's Accounting
  • Verify that the QuickBooks Desktop connection is available
  • Click on "Connect" button
  • Verify that it shows "QuickBooks Desktop setup" page with the setup link for Web/Desktop
  • Verify that it shows "Can't connect from this device" page for mWeb/Native apps

@ZhenjaHorbach
Copy link
Contributor

@mallenexpensify
I accepted the offer and added BugZero Checklist
Thanks !

@mallenexpensify
Copy link
Contributor

Thanks @ZhenjaHorbach , you've ben paid, payment confirmation updated above

test case created

@github-project-automation github-project-automation bot moved this from Hold for Payment to Done in [#whatsnext] #expense Oct 22, 2024
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 Bug Something is broken. Auto assigns a BugZero manager. Daily KSv2 Engineering External Added to denote the issue can be worked on by a contributor
Projects
Archived in project
Development

No branches or pull requests

4 participants