-
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-10-04][$250] Update UpdatePolicyConnectionConfiguration to be 1:1:1 - Part 4 #47522
Comments
Triggered auto assignment to @zanyrenney ( |
Sorry @zanyrenney forgot to remove |
Sounds good, thanks for the update @dangrous |
@shubham1206agra @rushatgabhane can you comment here so I can assign you? Thanks! |
@dangrous fyi, we don't need to comment for getting assigned as we're on exfy org in GitHub |
Here |
oh whoops! sorry about that. |
Job added to Upwork: https://www.upwork.com/jobs/~01eef0bc66034bca70 |
Current assignee @rushatgabhane is eligible for the External assigner, not assigning anyone new. |
📣 @shubham1206agra 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
any update here please @shubham1206agra |
I am done with the code. I just figuring out a way to test this flow. |
cool! |
fyi backend pr is deployed now so should be able to test the new commands! |
@dangrous, I am getting 404 here. Can you please check this? |
back end PR is up on staging! |
@dangrous, @rushatgabhane, @zanyrenney, @shubham1206agra Whoops! This issue is 2 days overdue. Let's get this updated quick! |
The PR has pending review from @rushatgabhane |
This issue has not been updated in over 15 days. @dangrous, @rushatgabhane, @zanyrenney, @shubham1206agra eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
Shush Melvin this was just merged! |
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. |
Why no automationnnnnnn - went to prod 3 days ago according to the comment on the PR |
Triggered auto assignment to @RachCHopkins ( |
Hi! I will be OOO until 7th october, please can you handle the final stage here of the payment @RachCHopkins thanks! |
Payment Summary:
Upwork job here @rushatgabhane I'm late to the party here - can you confirm that's correct please? |
Ok, I see that @dangrous updated the GH title last week, so I assume if the pricetag was wrong, it would have been corrected. Going to go ahead and pay this as it's due. |
@shubham1206agra the original offer had expired, so I have sent you a new manual offer. |
@RachCHopkins Offer accepted |
Payment Summary: Contributor: @shubham1206agra paid $250 via Upwork - completed. Thanks for the new manual offer sent @RachCHopkins I have paid it out. |
$250 approved for @rushatgabhane |
Problem
Our UpdatePolicyConnectionConfiguration API command is not 1:1:1 - it is the same API call for all related user actions, when it should be split up for each connection (QBO, Xero, etc.) and configuration setting (
autoSyncVendor
,enableNewCategories
, etc.). At the end of this we should not call that function anywhere.This is polish for the Collect QBO project.
Solution
When we created the NetSuite commands, we followed the correct pattern, and so need to do so here too.
This requires backend and frontend work in tandem (to create the commands and then to use them), so we're looking for a contributor(s) to handle the frontend. You can see an example PR here - there is some extra prep work there that you can ignore, but adjusting all calls like this is what we're going for:
Here is a list of the commands handled in this issue:
If there are others that follow the same pattern as
UpdateQuickbooksOnlineExport
(same object, different keys) we will need to split those as well.Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @Issue Owner
Current Issue Owner: @zanyrenneyThe text was updated successfully, but these errors were encountered: