-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[HOLD for payment 2023-12-26] [DISTANCE] LOW: UpdateDistanceRequest 1:1:1 - UpdateMoneyRequestDate - Split out into its own command #29993
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
Job added to Upwork: https://www.upwork.com/jobs/~019eb683577f4e3784 |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @ArekChr ( |
Got started on the auth command today and put up a WIP. I also asked in Slack about how to go about a testing strategy for all these commands. |
I will be able to get started on this again on Monday. |
I am hoping to get started on this today. |
Yesterday I was able to write 90% of the auth PR. The only thing left I need to do is write and return the Onyx updates. I also wrote 95% of the web-e PR and 90% of the app PRs. Today, I am hoping to complete the full flow so that I can begin testing and fine-tuning the solution. |
I'm dropping this back down to weekly while I try to finish up this PR that came off HOLD. |
I got all the changes done in the App PR today. Now I need to revisit both Web-E and Auth and finish up those PRs. They are mainly missing code to return OnyxUpdates to the frontend. Then, testing will commence. |
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.13-8 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 2023-12-26. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
I think this can be closed out since it doesn't look like it requires payment. |
@tgolen I was the C+ reviewer |
Reopening to get the C+ reviewer paid 👍 |
Triggered auto assignment to @JmillsExpensify ( |
This comment was marked as off-topic.
This comment was marked as off-topic.
@JmillsExpensify Can you please pay @cubuspl42 for their C+ review of the PR? |
@JmillsExpensify, @tgolen, @ArekChr Huh... This is 4 days overdue. Who can take care of this? |
Do we need to add any regression tests for this? Assuming no given that it's a backend refactor. |
Payment summary: $500 to @cubuspl42 for PR testing and review. |
Offer sent! |
Accepted |
All paid out. Thank you! |
Uh oh!
There was an error while loading. Please reload this page.
There will be three pieces to this:
This will all be done internally as they are refactored.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @JmillsExpensifyThe text was updated successfully, but these errors were encountered: