-
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 2023-12-28] [$500] IOU - Edit request option is present for paid message and error shows up when editing paid IOU #30448
Comments
Job added to Upwork: https://www.upwork.com/jobs/~012883c5c784b4c920 |
Triggered auto assignment to @garrettmknight ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mananjadhav ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.IOU - Edit request option is present for paid message and error shows up when editing paid IOU What is the root cause of that problem?We're showing edit option for even the system message: App/src/pages/home/report/ContextMenu/ContextMenuActions.js Lines 283 to 284 in a67253b
What changes do you think we should make in order to solve the problem?I think we shouldn't show the edit option for system message like that, so we need to update the condition here to: const isSystemMessage = reportAction.actionName === CONST.REPORT.ACTIONS.TYPE.IOU && reportAction.originalMessage.type === CONST.IOU.REPORT_ACTION_TYPE.PAY;
return type === CONTEXT_MENU_TYPES.REPORT_ACTION && ReportUtils.canEditReportAction(reportAction) && !isArchivedRoom && !isChronosReport && !isSystemMessage; or we just need to bring this logic into What alternative solutions did you explore? (Optional)N/A |
ProposalPlease re-state the problem that we are trying to solve in this issue.Edit request option is present for paid message and error shows up when editing paid IOU What is the root cause of that problem?The edit option is shown based on
Let's see the condition in Lines 1620 to 1627 in 8c76d2a
We have the check Lines 1572 to 1574 in 8c76d2a
What changes do you think we should make in order to solve the problem?I think we shouldn't show the edit option for iou action. We show the edit option for We should remove the check
Lines 1620 to 1627 in 8c76d2a
And remove the logic for the money request action case here
What alternative solutions did you explore? (Optional)We can update |
ProposalPlease re-state the problem that we are trying to solve in this issue.Edit request option is present for paid message and error shows up when editing paid IOU What is the root cause of that problem?We return true from Lines 1567 to 1574 in 8c76d2a
What changes do you think we should make in order to solve the problem?I don't think we should return true in any case if payments is settled, so we should only return Option 1
Option 2
Option 3 |
ProposalPlease re-state the problem that we are trying to solve in this issue."Edit request" option is available for the system message for paid request. Clicking on it does not allow user to edit the request
This one is currently not reproducible. What is the root cause of that problem?In here, we're not validating if the IOU report action is a 'CREATE' IOU report action. IOU report action has many sub-types, Without that additional check, in this issue, since the What changes do you think we should make in order to solve the problem?We need to update this with an additional check after this one: If the sub-type of the report action is not
This will make sure everywhere we use What alternative solutions did you explore? (Optional)NA |
Will test this and review this by tomorrow. |
@mananjadhav did you get a chance to test/review? |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@mananjadhav can you give this one a look when you get a chance? |
I was stuck with low internet. I'll finish this by tomorrow. |
@garrettmknight, @mananjadhav Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@mananjadhav can you prioritize this one this week? |
@garrettmknight I was out sick, I'll have this prioritized today/tomorrow. |
@garrettmknight @mananjadhav this issue was created 2 weeks ago. Are we close to approving a proposal? If not, what's blocking us from getting this issue assigned? Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks! |
@puneetlath Could we continue? |
@puneetlath, @garrettmknight, @mananjadhav Huh... This is 4 days overdue. Who can take care of this? |
@puneetlath, @garrettmknight, @mananjadhav Eep! 4 days overdue now. Issues have feelings too... |
Let's do it. Sorry for the delay! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.14-6 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 2023-12-28. 🎊 After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
|
BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:
|
Offer sent to @tienifr https://www.upwork.com/nx/wm/offer/100202927 |
I couldn't pinpoint to an exact PR for this one. Because we have canEditMoneyRequest since long. I also don't think we need a regression test for this one. @puneetlath @garrettmknight wdyt? @garrettmknight Can you please post a payout summary for me to raise a request? |
Summary of payments:
|
Dropping to weekly for payment |
$500 payment approved for @mananjadhav based on summary above. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.3.91-6
Reproducible in staging?: Yes
Reproducible in production?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Issue found when executing PR #29934
Action Performed:
Expected Result:
Actual Result:
"Edit request" option is available for the system message for paid request. Clicking on it does not allow user to edit the request
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6251899_1698331109368.Recording__296.1.mp4
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: