Skip to content

[Merge] Category field and Reimbursable toggle are missing on confirm page when bulk merging expenses #78190

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.2.85-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #73248
Email or phone of affected tester (no customers): sdoisjnoisjoisdjoijdsio@gmail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Mac 26.1 / Chrome
App Component: Search

Action Performed:

Precondition:

  • Account has self DM and workspace chat.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create an expense of amount 10.00
  4. Go to self DM.
  5. Create an expense of amount 1.00 (lower than workspace expense).
  6. Go to Reports > Expenses.
  7. Click Amount title so that the expense is sorted from low to high amount (workspace expense must be below self DM expense).
  8. Select both expenses via checkbox.
  9. Click dropdown button > Merge.
  10. Select all the details from workspace expense in Step 3.
  11. Click Next.

Expected Result:

On confirm page, Category field and Reimbursable toggle will be shown.

Actual Result:

On confirm page, Category field and Reimbursable toggle are missing.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7034098_1766208759542.111.mp4

View all open jobs on GitHub

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.EngineeringReviewingHas a PR in reviewWeeklyKSv2

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions