Skip to content

[HOLD for payment 2024-08-02] [$250] Dupe detect - Merchant field is empty on the confirmation page when there is info on merchant #45865

Closed

Description

@lanitochka17

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:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat
  3. Submit two expenses with same content for every field (amount, description, merchant and category)
  4. Go to transaction thread of any expense
  5. Click Review duplicates
  6. Select Keep this one (any)
  7. 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?

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

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
  • Upwork Job URL: https://www.upwork.com/jobs/~01a0550d2189cf44a1
  • Upwork Job ID: 1815322514359268142
  • Last Price Increase: 2024-07-22
Issue OwnerCurrent Issue Owner: @twisterdotcom

Activity

  1. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 21, 2024
  2. melvin-bot commented on Jul 21, 2024

    @melvin-bot

    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.

  3. added
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    and removed
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jul 21, 2024
  4. melvin-bot commented on Jul 21, 2024

    @melvin-bot

    Triggered auto assignment to @francoisl (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  5. github-actions commented on Jul 21, 2024

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. lanitochka17 commented on Jul 21, 2024

    @lanitochka17
    Author

    We think that this bug might be related to #wave-collect - Release 2

  7. dominictb commented on Jul 22, 2024

    @dominictb
    Contributor

    Proposal

    Please re-state the problem that we are trying to solve in this issue.

    • Merchant field is empty on the confirmation page when there is info on merchant field.

    What is the root cause of that problem?

    • With merchant field, we always use:
      const allFieldsAreEqual = transactions.every((item) => keys.every((key) => item?.[key] === firstTransaction?.[key]));

      but keys is ["modifiedMerchant", "merchant"].
    • So firstTransaction?["modifiedMerchant"] can be "".

    What changes do you think we should make in order to solve the problem?

                        if (fieldName === 'merchant') {
                            keep[fieldName] = isEmpty(firstTransaction?.[keys[0]]) ? firstTransaction?.[keys[1]] : firstTransaction?.[keys[0]];
                        } else {
                            keep[fieldName] = firstTransaction?.[keys[0]];
                        }
    
  8. 24 remaining items

  9. 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
  10. melvin-bot commented on Jul 26, 2024

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  11. melvin-bot commented on Jul 26, 2024

    @melvin-bot

    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. 🎊

  12. twisterdotcom commented on Aug 2, 2024

    @twisterdotcom
    Contributor

    @mountiny or @pecanoro who is due payment here? Just @parasharrajat for reviewing #45890?

  13. twisterdotcom commented on Aug 2, 2024

    @twisterdotcom
    Contributor

    Payment Summary:

  14. parasharrajat commented on Aug 3, 2024

    @parasharrajat
    Member

    Payment requested as per #45865 (comment)

  15. JmillsExpensify commented on Aug 3, 2024

    @JmillsExpensify
    Contributor

    $250 approved for @parasharrajat

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionDailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions