Skip to content

[Due for payment 2025-03-27] [$250][HIGH] Expense is created in the task report when the reportID is smaller than the reportID of the policy expense chat #58258

@trjExpensify

Description

@trjExpensify

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: v9.1.11-1
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
If this was caught during regression testing, add the test name, ID and link from TestRail: No
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by:@nkdengineer
Slack conversation (hyperlinked to channel name): Follow up from here.

Action Performed:

Precondition: The default workspace is the group workspace

  1. In the default policy expense chat, assign some tasks until we have a task report with the reportID that is smaller than the reportID of the policy expense chat
  2. Open this task report and add a comment.
  3. Reset cache and restart or sign out and sign in again
  4. Go global FAB > Enter any amount
  5. In the confirmation step, add merchant and create the expense
  6. Notice where the expense is displayed

Expected Result:

The expense is displayed in the policy expense chat.

Actual Result:

The expense is displayed in the task report

Platforms:

Which of our officially supported platforms is this issue occurring on?

  • Android: Standalone
  • Android: HybridApp
  • Android: mWeb Chrome
  • iOS: Standalone
  • iOS: HybridApp
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Screen.Recording.2025-03-11.at.12.06.53.mov

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021899616047068547163
  • Upwork Job ID: 1899616047068547163
  • Last Price Increase: 2025-03-12
Issue OwnerCurrent Issue Owner: @trjExpensify

Metadata

Metadata

Labels

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

Type

No type
No fields configured for issues without a type.

Projects

Status
Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions