You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-01-26] [HOLD for payment 2024-01-25] [HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports #32427
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. Once we have it for "Paid Elsewhere" we need to expand it for "Paid in Expensify" reports.
changed the title [-][HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/-][+][HOLD for payment 2024-01-25] [HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/+]on Jan 18, 2024
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:
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:
[@Ollyws] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
changed the title [-][HOLD for payment 2024-01-25] [HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/-][+][HOLD for payment 2024-01-26] [HOLD for payment 2024-01-25] [HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/+]on Jan 19, 2024
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:
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:
[@Ollyws] Please propose regression test steps to ensure the new feature will work correctly on production in further releases.
[@puneetlath] Link the GH issue for creating/updating the regression test once above steps have been agreed upon.
Activity
melvin-bot commentedon Dec 4, 2023
Triggered auto assignment to @puneetlath (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.melvin-bot commentedon Dec 4, 2023
Bug0 Triage Checklist (Main S/O)
Platformsin OP are ✅)melvin-bot commentedon Dec 4, 2023
Current assignee @puneetlath is eligible for the NewFeature assigner, not assigning anyone new.
melvin-bot commentedon Dec 4, 2023
Job added to Upwork: https://www.upwork.com/jobs/~01f33337b0d8b040ed
melvin-bot commentedon Dec 4, 2023
Triggered auto assignment to Contributor Plus for review of internal employee PR - @Ollyws (
Internal)32 remaining items
melvin-bot commentedon Jan 17, 2024
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.
[-][HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/-][+][HOLD for payment 2024-01-25] [HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/+]melvin-bot commentedon Jan 18, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jan 18, 2024
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:
melvin-bot commentedon Jan 18, 2024
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:
[-][HOLD for payment 2024-01-25] [HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/-][+][HOLD for payment 2024-01-26] [HOLD for payment 2024-01-25] [HOLD for payment 2024-01-02] Create new command for Payment cancelling in "Paid in Expensify" reports[/+]melvin-bot commentedon Jan 19, 2024
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:
melvin-bot commentedon Jan 19, 2024
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: