You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2024-08-02] [$250] Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant #45865
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:
Go to staging.new.expensify.com
Go to workspace chat
Submit two expenses with same content for every field (amount, description, merchant and category)
Go to transaction thread of any expense
Click Review duplicates
Select Keep this one (any)
Proceed to confirmation page
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?
👋 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:
Identify the pull request that introduced this issue and revert it.
changed the title [-][$250] Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant[/-][+][HOLD for payment 2024-08-02] [$250] Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant[/+]on Jul 26, 2024
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:
Activity
melvin-bot commentedon Jul 21, 2024
Triggered auto assignment to @twisterdotcom (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Jul 21, 2024
Triggered auto assignment to @francoisl (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.github-actions commentedon Jul 21, 2024
👋 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:
lanitochka17 commentedon Jul 21, 2024
We think that this bug might be related to #wave-collect - Release 2
dominictb commentedon Jul 22, 2024
Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
merchantfield, we always use:App/src/libs/TransactionUtils.ts
Line 905 in f3a8f73
but
keysis["modifiedMerchant", "merchant"].firstTransaction?["modifiedMerchant"]can be"".What changes do you think we should make in order to solve the problem?
App/src/libs/TransactionUtils.ts
Line 905 in f3a8f73
to:
24 remaining items
[-][$250] Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant[/-][+][HOLD for payment 2024-08-02] [$250] Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant[/+]melvin-bot commentedon Jul 26, 2024
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 26, 2024
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. 🎊
twisterdotcom commentedon Aug 2, 2024
@mountiny or @pecanoro who is due payment here? Just @parasharrajat for reviewing #45890?
twisterdotcom commentedon Aug 2, 2024
Payment Summary:
parasharrajat commentedon Aug 3, 2024
Payment requested as per #45865 (comment)
JmillsExpensify commentedon Aug 3, 2024
$250 approved for @parasharrajat