-
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-04-15] [$500] IOU - Replace receipt option is available for requestee in combined IOU report #39436
Comments
Triggered auto assignment to @tylerkaraszewski ( |
👋 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:
|
We think that this bug might be related to #wave-collect - Release 1 |
ProposalPlease re-state the problem that we are trying to solve in this issue.Replace receipt option is available for User B (requestee). What is the root cause of that problem?When we open the receipt in combine report, the reportID in URL is the expense report so App/src/components/ReportActionItem/ReportActionItemImage.tsx Lines 98 to 101 in 879378f
App/src/pages/TransactionReceiptPage.tsx Line 36 in 879378f
What changes do you think we should make in order to solve the problem?We should get the transactionReportID and pass it as App/src/components/ReportActionItem/ReportActionItemImage.tsx Lines 98 to 101 in 879378f
To do that we should store
App/src/components/ReportActionItem/ReportActionItemImage.tsx Lines 98 to 101 in 879378f
What alternative solutions did you explore? (Optional)NA |
This comment was marked as off-topic.
This comment was marked as off-topic.
Job added to Upwork: https://www.upwork.com/jobs/~01e259e1fb396c9678 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @abdulrahuman5196 ( |
Triggered auto assignment to @kadiealexander ( |
📣 @nkdengineer You have been assigned to this job! |
I don't think this is worth blocking deploy on this as we're marking other bugs related to the combined IOU report view as non-blockers. |
@jasperhuangg The PR is here |
@jasperhuangg Wanted to check if C+ is needed here? Seems I was removed and deployment blocker is also removed? |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.60-13 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-04-15. 🎊 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. @alexpensify you are the lucky winner! Please verify the payment summary looks correct and complete the checklist. Thanks! |
Payment Summary
BugZero Checklist (@alexpensify)
|
@nkdengineer - I've sent an offer via Upwork. Please accept and I can complete the payment process. Thanks! |
Closing, I was able to complete the payment to @nkdengineer. @allroundexperts please submit a request in Chat. Thanks! |
$500 approved for @allroundexperts |
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.59-0
Reproducible in staging?: y
Reproducible in production?: n
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
There will be no Replace receipt option for User B (requestee).
Actual Result:
Replace receipt option is available for User B (requestee).
This issue only happens in combined IOU report.
Workaround:
n/a
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6435778_1712075771965.20240403_003243.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: