Skip to content

[Due for payment 2025-05-22] [$250] Expense - First expense show "card" icon after reviewing duplicates and submit another expense #61646

@mitarachim

Description

@mitarachim

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.42-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #61273
Email or phone of affected tester (no customers): applausetester+300402kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • Log in with Expensifail account.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses with the same amount and merchant.
  4. Click on the expense preview.
  5. Click Review duplicates.
  6. Click Keep this one on any expense preview.
  7. Click Confirm on the confirmation page.
  8. Click + > Create expense > Manual.
  9. Submit another manual expense.

Expected Result:

The first expense will show "cash" icon instead of "card" icon.

Actual Result:

The first expense show "card" icon instead of "cash" icon after reviewing duplicates and submit another expense.
It changes to "cash" icon after opening the transaction thread.
On small screen, it shows "card" text.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug6825170_1746677346126.20250508_120252.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021920535971542882679
  • Upwork Job ID: 1920535971542882679
  • Last Price Increase: 2025-05-08
Issue OwnerCurrent Issue Owner: @NicMendonca

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions