Skip to content

[$250] Expense - Different destination opens when bulk merging vs merging individually #83257

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.3.25-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #79766
Email or phone of affected tester (no customers): jsodjsodnjoisjdosij@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com

  2. Create an expense in self DM.

  3. Create an expense in workspace chat.

  4. Go to Reports > Expenses.

  5. Open the workspace expense.

  6. Click More > Merge.

  7. Select self DM expense > Continue.

  8. Select second option in each section > Next > Merge expenses.
    → Transaction thread opens.

  9. Create an expense in self DM.

  10. Create an expense in workspace chat.

  11. Go to Reports > Expenses.

  12. Select workspace expense via checkbox.

  13. Click dropdown button > Merge.

  14. Select self DM expense > Continue.

  15. Select second option in each section > Next > Merge expenses.

Expected Result:

Transaction thread will open after merging expenses via bulk option (similar to Step 8).

Actual Result:

Self DM opens after merging expenses via bulk option.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7086423_1771884485618.5.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @rojiphil
Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~022026066651163126006
  • Upwork Job ID: 2026066651163126006
  • Last Price Increase: 2026-02-23

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributorOverdue

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
No status

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions