Skip to content

[Due for Payment 2026-02-12] Reports - Expense that was removed from report, is still displayed on "Top Spenders" section #79158

@lanitochka17

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.2.96-1
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: #78410
Email or phone of affected tester (no customers): ibellicotest+2250@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Motorola MotoG60 / Android 12 (Hybrid app) - Windows 11 / Chrome
App Component: Search

Action Performed:

Prerequisite: Account has at least one workspace.

  1. Open the Expensify app.
  2. Open any workspace chat.
  3. Create two manual expenses with date of last month.
  4. Navigate to "Reports" > "Top Spenders"
  5. Expand the results and note that both expenses are correctly displayed.
  6. Return to chat and open expenses report.
  7. Select one of the expenses.
  8. Tap on dropdown menu and select "Move Expense"
  9. Remove expense from report.
  10. Return to "Reports" > "Top Spenders"
  11. Note that removed expense is still visible on results despite not belonging to a workspace anymore.

Expected Result:

Only expenses from a workspace should be visible on "Top Spenders" section.

Actual Result:

Expense that was removed from report and moved to Self DM, is still visible on "Top Spenders" section.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7043858_1767892591083.Top.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @mananjadhav

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringOverdue

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions