-
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-20] [$125] Split bill - Date and merchant are not saved when splitting bill #29458
Comments
Triggered auto assignment to @abekkala ( |
Bug0 Triage Checklist (Main S/O)
|
@lanitochka17 can you please link the slack conversation and the screen recording of this bug? |
@abekkala Hello You can see the video in the Screenshots/Videos tab |
Job added to Upwork: https://www.upwork.com/jobs/~0127c47ff7ea605892 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @robertKozik ( |
Upwork job price has been updated to $125 |
Flat $125, this is a simple fix. When se call the StartSplitbill with the receipt, we do not pass the created or date, we only pass the description. Lets hide those two fields in case of Split with receipt creation |
ProposalPlease re-state the problem that we are trying to solve in this issue.Setting merchant and date when doing scan money requests is being ignored. What is the root cause of that problem?When we do a scan request, we don't pass both merchant and date to the request. App/src/pages/iou/steps/MoneyRequestConfirmPage.js Lines 201 to 208 in 814345a
So, both merchant and date value is not used. What changes do you think we should make in order to solve the problem?Based on the @mountiny comment above, we want to hide both the merchant and date fields for split bills with scan requests.
|
📣 @bernhardoj 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @burczu ( |
@bernhardoj Can you please raise a pr with urgency |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 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-20. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.83-11 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-20. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-23. 🎊 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:
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.84-10 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-23. 🎊 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:
|
@abekkala Just noting that the PR for this issue was initially deployed to production on 2023-10-13 since it was a deploy blocker, so the payment due date should be 2023-10-20. There were some issues with deploys so Melvin's been a bit confused lately. I will complete the BZ checklist on Friday, the 20th. Thanks. |
PAYMENTS TO BE MADE OCT 20
|
Not a regression. Split bills with scan requests are handled differently in the backend, but the logic was not implemented in the app.
Regression test
Do we agree 👍 or 👎? |
I believe the issue is also eligible for the 50% bonus. Thanks. |
@akinwale yes, you are correct! PAYMENTS TO BE MADE OCT 20
|
@akinwale [$125 + $62.50 bonus] payment made and contract ended - Thank you! 🎉 @bernhardoj [$125 + $62.50 bonus] payment made and contract ended - Thank you! 🎉 |
All set! |
If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!
Version Number: 1.3.83-1
Reproducible in staging?: Yes
Reproducible in production?: No
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:
Date and merchant are saved
Actual Result:
Date and merchant are not saved
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari
Bug6234580_1697121676020.20231012_211537.mp4
MacOS: Desktop
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: