-
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 2023-10-13] [$500] The subtitle in LHN display wrong message when requesting message by scanning #27697
Comments
Triggered auto assignment to @anmurali ( |
Job added to Upwork: https://www.upwork.com/jobs/~0154605d61aec2e78e |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @sophiepintoraetz ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @cubuspl42 ( |
Proposal by @DylanDylannPlease re-state the problem that we are trying to solve in this issue.The subtitle in LHN display wrong message when requesting message by scanning What is the root cause of that problem?Lines 1440 to 1446 in 60b8dae
Let’s see here, we only check isMoneyRequestAction, not check isReportPreviewAction. Not that, isMoneyRequestAction only be true if this reportAction is in the IOU chat. In case, the report action is in the main chat the type is REPORTPREVIEW What changes do you think we should make in order to solve the problem?In this function Line 1423 in 60b8dae
We should add the condition and return Localize.translateLocal(‘iou.receiptScanning’) for REPORTPREVIEW like we did forisReportPreviewAction
We can create a function to dry code App/src/libs/OptionsListUtils.js Line 400 in 2ea1c71
we need to pass shouldConsiderReceiptBeingScanned is true in the third param Result<img width=“1440” alt=“Screenshot 2023-09-18 at 16 26 33" src=“https://github.com/Expensify/App/assets/141406735/a7d44705-0466-458d-b6d2-d4c83aa81285”> |
Re-post proposal with a bit change ProposalPlease re-state the problem that we are trying to solve in this issue.The subtitle in LHN display wrong message when requesting message by scanning What is the root cause of that problem?Lines 1440 to 1446 in 60b8dae
Let’s see here, we only check isMoneyRequestAction, not check isReportPreviewAction. Note that isMoneyRequestAction only be true if this reportAction is in the IOU chat. In case, the report action is in the main chat the type is REPORTPREVIEW What changes do you think we should make in order to solve the problem?In this function Line 1423 in 60b8dae
We should add the condition and return Localize.translateLocal(‘iou.receiptScanning’) for REPORTPREVIEW like we did forisReportPreviewAction
We can create a function to dry code App/src/libs/OptionsListUtils.js Line 400 in 2ea1c71
we need to pass shouldConsiderReceiptBeingScanned is true in the third param Result |
@cubuspl42, @anmurali, @sophiepintoraetz Whoops! This issue is 2 days overdue. Let's get this updated quick! |
The proposal by @DylanDylann sounds reasonable. I agree that there might be potential for refactoring the shared logic in a helper function, we'll focus on that when working on the PR. C+ reviewed 🎀 👀 🎀 |
Triggered auto assignment to @tylerkaraszewski, see https://stackoverflow.com/c/expensify/questions/7972 for more details. |
📣 @cubuspl42 🎉 An offer has been automatically sent to your Upwork account for the Reviewer role 🎉 Thanks for contributing to the Expensify app! |
📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
📣 @DylanDylann 🎉 An offer has been automatically sent to your Upwork account for the Reporter role 🎉 Thanks for contributing to the Expensify app! |
@cubuspl42 Could you help review this PR? |
Based on my calculations, the pull request did not get merged within 3 working days of assignment. Please, check out my computations here:
On to the next one 🚀 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.78-4 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-10-13. 🎊 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:
As a reminder, here are the bonuses/penalties that should be applied for any External 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:
|
|
@tylerkaraszewski, @cubuspl42, @anmurali, @sophiepintoraetz, @DylanDylann Eep! 4 days overdue now. Issues have feelings too... |
I also think this was eligible for the urgency bonus, given the merging delay was on our end. |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
In chat (main chat) the message is "Receipt scan in progress…"
Actual Result:
In chat (main chat) the message is ".... owes 0"
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: 1.3.71-5
Reproducible in staging?: y
Reproducible in production?: y
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
Notes/Photos/Videos: Any additional supporting documentation
Recording.1592.mp4
Expensify/Expensify Issue URL:
Issue reported by: @DylanDylann
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1694581294081939
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: