-
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-08-02] [$250] Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant #45865
Comments
Triggered auto assignment to @twisterdotcom ( |
Triggered auto assignment to @francoisl ( |
👋 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 2 |
ProposalPlease re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
|
ProposalPlease re-state the problem that we are trying to solve in this issue.Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant What is the root cause of that problem?We are using
What changes do you think we should make in order to solve the problem?Use We should also check for similar issue in other fields as well. What alternative solutions did you explore? (Optional) |
Dupe Detection is still under Beta, so I don't think this needs to be |
Job added to Upwork: https://www.upwork.com/jobs/~01a0550d2189cf44a1 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ishpaul777 ( |
And since its in beta we can also remove the blocker labels |
We did fix this issue on the PR. May be there are more cases to be handled. @kubabutkiewicz please add this as well. |
@francoisl I am reassigning the issue to myself so I can review and track the fixes since this is for the duplicate detection project that I am handling. |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.12-0 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-08-02. 🎊 |
@mountiny or @pecanoro who is due payment here? Just @parasharrajat for reviewing #45890? |
Payment Summary:
|
Payment requested as per #45865 (comment) |
$250 approved for @parasharrajat |
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: 9.0.10-2
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Issue reported by: Applause - Internal Team
Action Performed:
Expected Result:
All the fields will reflect the correct information on the confirmation page
Actual Result:
Merchant field is empty on the confirmation page when there is info on merchant field.
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
Bug6548605_1721561004558.bandicam_2024-07-21_19-11-39-312.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @twisterdotcomThe text was updated successfully, but these errors were encountered: