-
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-06-11] [HOLD for payment 2024-05-20] [Wave Collect] [Xero] [Import Flow] Create the Tracking Categories Page #39732
Comments
Triggered auto assignment to @jliexpensify ( |
Hi @lakchote - would this need to go to |
Hi Jason! I've updated detail in the issue's body. Thanks! |
Awesome, thanks Lucien - have left a message for SWM. |
Hi! I am Filip from SWM and I'd like to work on this issue! |
Not overdue! Any updates @filip-solecki? |
I will be working on this today or tomorrow as I had to jump to new Onboarding flow |
Looks like the PR deployed to staging 9 hours ago. There shouldn't be a hold in the title of this issue, right? Removing that. |
Yes, you're right. I've explained why this was merged here. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.72-1 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-05-20. 🎊 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:
|
Triggered auto assignment to @cead22, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
@lakchote can I confirm that no payment is needed here?
Is that correct? |
Exactly, no payment needed here for @filip-solecki and @fedirjh. As Filip was OOO, Manan took the lead on it to finish it in time. I'm going to assign @mananjadhav for this issue, to reflect that, thanks! |
Ok great, thanks! In that case - I think @mananjadhav is requesting one payment for the entirety of this project, is that correct? Let me know if you need a Payment Summary - otherwise I'll close this out when I get online tomorrow. |
Payment Summary
BugZero Checklist (@jliexpensify)
|
I believe Manan is including this as part of a larger invoice, so I'm going to close this out. There was no Upworks job. |
|
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.
Issue Owner
Current Issue Owner: @jliexpensifyThe text was updated successfully, but these errors were encountered: