Skip to content

[Due for payment 2025-06-27] [Hold #63621] [$250] Carousel arrows are present in expense RHP when report has only 1 expense after moving expense #63620

@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.60-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): jsoidnjsodijdso@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Submit two expenses to the workspace chat.
  4. Create an empty report via + > Create report.
  5. Go to the report with two expenses.
  6. Click on any expense and send a reply in the transaction thread.
  7. Close the RHP.
  8. Select the other expense that does not have comment via checkbox.
  9. Click on the dropdown button > Move expense.
  10. Select the empty report from Step 4.
  11. Go to Reports > Chats.
  12. Click on the message sent from Step 6.
  13. Click on the carousel "next" arrow.

Expected Result:

There should be no carousel arrows because now the expense report only has one expense after moving the other expense to another report (production behavior).

Actual Result:

The carousel arrows are still present in the transaction thread RHP when the expense report only has one expense. The "next" arrow button opens the expense that is moved to the other report.

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

Bug6852030_1749173139157.20250606_091706.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021931092675154252601
  • Upwork Job ID: 1931092675154252601
  • Last Price Increase: 2025-06-06
Issue OwnerCurrent Issue Owner: @lydiabarclay

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
No fields configured for issues without a type.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions