Skip to content

[Better Expense Report View] Expense Reports - Merchant is still displayed in the row after merchant is removed #58855

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.1.16-1
Reproducible in staging?: N
Reproducible in production?:
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail: #58360
Email or phone of affected tester (no customers): applausetester+kok1@applause.expensifail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • Log in with Expensifail account
  1. Go to staging.new.expensify.com
  2. Open FAB > Submit expense > Manual
  3. Submit a manual expense with merchant to any user
  4. Go to transaction thread
  5. Click Merchant
  6. Clear the merchant and save it
  7. Go to Reports
  8. Go to Expense Reports
  9. Click on the expense report from Step 3

Expected Result:

Merchant field will no longer show the previous merchant because it is removed

Actual Result:

Merchant field still shows the previous merchant after it is removed
This issue also happens when the merchant is changed from A to B. The expense row will show merchant A instead of merchant B
This issue also happens with Amount field

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug6777287_1742499648586.20250321_033635.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @Kicu

Activity

  1. melvin-bot commented on Mar 20, 2025

    @melvin-bot

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

  2. melvin-bot commented on Mar 20, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  3. github-actions commented on Mar 20, 2025

    @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.
  4. luacmartins commented on Mar 20, 2025

    @luacmartins
    Contributor

    This view is behind a beta. NAB. @Kicu

  5. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Mar 20, 2025
  6. 13 remaining items

  7. trjExpensify commented on Apr 1, 2025

    @trjExpensify
    Contributor

    I think this one can be characterised as pretty much any expense details you update either:

    • Doesn't update at all in the table (e.g merchant and amount)
    • Only updates after a refresh (e.g category)
    2025-04-01_17-28-27.mp4
  8. melvin-bot commented on Apr 4, 2025

    @melvin-bot

    @Kicu Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

  9. Kicu commented on Apr 4, 2025

    @Kicu
    Contributor

    This is expected to be fixed in: #59459 (comment)

  10. melvin-bot commented on Apr 8, 2025

    @melvin-bot

    @Kicu Whoops! This issue is 2 days overdue. Let's get this updated quick!

  11. melvin-bot commented on Apr 10, 2025

    @melvin-bot

    @Kicu Huh... This is 4 days overdue. Who can take care of this?

  12. Kicu commented on Apr 11, 2025

    @Kicu
    Contributor

    verified that merchant will be cleared when removed from transaction

    Screen.Recording.2025-04-11.at.08.17.03.mov
  13. Kicu commented on Apr 11, 2025

    @Kicu
    Contributor

    we can close this

  14. mountiny commented on Apr 11, 2025

    @mountiny
    Contributor

    Perfect thanks!

  15. moved this from Second Cohort - CRITICAL to Done in [#whatsnext] #migrateon Apr 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions