-
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-02-07] [$500] Reimbursement - Reimbursement message is not copied with "Copy to clipboard" #34045
Comments
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
|
Triggered auto assignment to @tylerkaraszewski ( |
ProposalPlease re-state the problem that we are trying to solve in this issue.Can not copy message reimbursement What is the root cause of that problem?We do not have a logic for copying the type "MARKEDREIMBURSED" of message in here What changes do you think we should make in order to solve the problem?We should add logic like this if (reportAction.actionName === 'MARKEDREIMBURSED') {
const reimbursMementessage = _.reduce(reportAction.message, (acc, curr) => `${acc}${curr.text}`, '');
Clipboard.setString(reimbursMementessage);
} What alternative solutions did you explore? (Optional) |
ProposalPlease re-state the problem that we are trying to solve in this issue.Reimbursement message is not copied with "Copy to clipboard" What is the root cause of that problem?We did not cover the case of What changes do you think we should make in order to solve the problem?We should add the check to cover reimbursement message type: if (reportAction.actionName === CONST.REPORT.ACTIONS.TYPE.MARKEDREIMBURSED) {
const message = ReportActionsUtils.getMarkedReimbursedMessage(reportAction);
Clipboard.setString(message);
} We should cover other cases of reimbursement messages like What alternative solutions did you explore? (Optional)I also notice that the TS definition here is insufficient. We should supplement all types of messages to avoid type errors. |
ProposalPlease re-state the problem that we are trying to solve in this issue.Copying reimbursed system message copies nothing. What is the root cause of that problem?The reimbursed system message object only contains When we press copy to clipboard, we only take the last message App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx Lines 33 to 36 in a8acf44
So, the copy to clipboard fails to copy the message. What changes do you think we should make in order to solve the problem?Previously, we had a similar issue for SUBMITTED action and the solution is to concat all message App/src/pages/home/report/ContextMenu/ContextMenuActions.tsx Lines 324 to 327 in a8acf44
But instead of handling it case by case, we can make it a general case. So, in addition to
|
Job added to Upwork: https://www.upwork.com/jobs/~01143d94d68559e19a |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @0xmiroslav ( |
@tylerkaraszewski, @0xmiroslav Whoops! This issue is 2 days overdue. Let's get this updated quick! |
reviewing proposals |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@bernhardoj ContextMenuActions is now TS. can you please update proposal accordingly? |
Updated |
@0xmiroslav What do you think about my proposal, so that my proposal solves the current issue without causing any further regression? I think in general it is still based on the current solution. |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @fedirjh ( |
@fedirjh, reassigning, please take over as C+. If you don't have bandwidth, unassign yourself. Thanks |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.33-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-02-07. 🎊 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:
|
Issue is ready for payment but no BZ is assigned. @muttmuure you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@muttmuure)
|
@muttmuure C+ payment should be issued to @0xmiroslav as he has fully reviewed the PR. |
Invited @0xmiroslav and @bernhardoj |
@tylerkaraszewski, @fedirjh, @muttmuure, @bernhardoj Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
Offer sent to @bernhardoj |
Waiting for @0xmiroslav to accept |
Going to close for now, @0xmiroslav please reopen when you'd like to be paid |
@muttmuure Hi, I was scanning through my pending payment and saw that I haven't been paid yet on this one. Here is the offer that I was checking, could you kindly check it on your side? |
Contributor: @bernhardoj paid $500 via Upwork |
@mallenexpensify Thanks! |
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.4.22-0
Reproducible in staging?: Y
Reproducible in production?: N
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:
Action Performed:
Expected Result:
The reimbursement message is copied successfully
Actual Result:
The reimbursement message is not copied
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6333354_1704475020941.20240105_085906.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: