-
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-01-26] [HOLD for payment 2024-01-25] [$500] Create new command for Payment cancelling in "Paid Elsewhere" reports #32426
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01c0fd3da0a160792d |
Triggered auto assignment to @michaelhaxhiu ( |
Triggered auto assignment to Contributor Plus for review of internal employee PR - @narefyev91 ( |
Seems @Gonals made a PR on HOLD to fix this GH here - #32674 (comment) I'm guessing we want to proceed with internal handling and just wait a little on the fix. |
Yep, this requires development from Auth to App 😁 |
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. |
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 PR has caused numerous deploy blockers in App:
Some might be considered as not a blockers but I think given the number of these and that the author is ooo I will revert the PR and we can just fix this in the second attempt |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.26-2 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-01-25. 🎊 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:
|
Man, this is being more of a pain than expected. Bringing some discussions to Slack |
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.27-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-01-26. 🎊 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:
|
@michaelhaxhiu please handle the payment when you get a chance! |
There is no payment here! And no need for regression steps IMO (it's not a regression from a bug, it's a new feature). |
@michaelhaxhiu I did review #33836, so payment is due there but there were regressions so the 50% penalty applies. Thanks! |
Friendly bump on the above @michaelhaxhiu |
Just been looking through some old notes and realized this one still hasn't been paid. @mallenexpensify Any chance you could help with this? Thanks! |
@Ollyws sorry about that, glad you caught it! |
@mallenexpensify I'll request via ND if that's alright, thanks! |
@Ollyws you were asked to review in January so we need to pay via Upwork Please rescind your NewDot request. It's best practice to wait for the BZ payment summary before requesting funds via NewDot. Thx |
@mallenexpensify Ahh no problem I didn't make a ND request yet. Accepted, thanks! |
Problem
Currently, we have no way to revert an existing payment in NewDot. This is part of our core functionality and something we should be able to do.
Solution
Let's add that functionality as discussed here. We'll start by adding it for "Paid Elsewhere" reports, as it is simpler and will give us the core structure of the command and the UI, and move to "Paid in Expensify" reports in a follow-up issue.
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @mallenexpensifyThe text was updated successfully, but these errors were encountered: