-
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-06-11] [Wave Collect] [Xero] [Advanced] Create the Purchase Bill Status Selector Page #39748
Comments
Triggered auto assignment to @mallenexpensify ( |
Job added to Upwork: https://www.upwork.com/jobs/~0114d834a9c20463ee |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @jjcoffee ( |
Checking on in #bug-zero https://expensify.slack.com/archives/C01SKUP7QR0/p1712525687667159 @jjcoffee would you be interested in building this? |
@mallenexpensify In principle yes, but I have requested access to the doc so I can see the full scope. Also what sort of deadline would there be for this? |
Yes, agency engineers will work on this. I've put this as a weekly first, since we won't be able to work on this until the Xero authorization flow is done. It entails NewDot, Web-E, and IS changes (see DD details here). Once this whole block is done, we'll be able to make progress here. |
Thanks @lakchote , going to leave 'as is' , just avoid adding |
@mallenexpensify, @jjcoffee Whoops! This issue is 2 days overdue. Let's get this updated quick! |
Unassigning you @jjcoffee as this will be handled by internal or SWM engineers. I might have internal engineers interested in this, I'm double-checking. |
Still holding |
Draft PR is up. |
Triggered auto assignment to @srikarparsi, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
Assigning @mananjadhav as he'll need to be paid for the C+ review of the linked PR once this hits production and the 7 day regression period passes. |
Assigning @pecanoro as she has helped with reviewing the PR and providing translations. |
Xero issues are paid "centrally". We'll get a flat fee after all Xero related issues are closed. |
@rushatgabhane Including the C+? |
@pecanoro yes - @mananjadhav @hungvu193 and me |
Ok, then I think we can close this one, thank you guys! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.78-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-06-11. 🎊 For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR adding this new feature has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
You need to build the page following the steps outlined here.
This will be worked on by SWM engineers, see Slack discussion here.
Until the Xero authorization flow (NewDot issue) is done (which entails NewDot, Web-E and IS changes), we won't be able to work on this yet.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mallenexpensifyThe text was updated successfully, but these errors were encountered: