Skip to content

[Due for payment 2026-01-16] [Due for payment 2026-01-15] Expense - Report field in IOU expense shows IOU, Report field in self DM is blank #79005

Closed

Description

@jponikarchuk

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.95-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: #78409
Email or phone of affected tester (no customers): sjdinjsdoidjsosjosoi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition: Account has self DM.

  1. Go to staging.new.expensify.com
  2. Open 1:1 DM.
  3. Create an expense.
  4. Open the expense report.
    • BUG 1: Report field shows IOU instead of "User owes x".
  5. Go to self DM.
  6. Create an expense.
  7. Open the expense report.
    • BUG 2: Report field is empty.

Expected Result:

BUG 1: Report field will show "User owes x".
BUG 2: Report field shows User (You).

Actual Result:

BUG 1: Report field shows IOU instead of "User owes x".
BUG 2: Report field is empty.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @johncschuster

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jan 7, 2026
  2. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78409

  3. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. melvin-bot commented on Jan 7, 2026

    @melvin-bot

    Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

  5. github-actions commented on Jan 7, 2026

    @github-actions

    👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. twinkle-react commented on Jan 7, 2026

    @twinkle-react

    Proposal

    Please re-state the problem that we are trying to solve in this issue.
    Expense - Report field in IOU expense shows "IOU" instead of the proper report name, and in self DM the Report field is blank.

    What is the root cause of that problem?
    The parentReportID used to determine which report name to display is incorrectly set to the DM parent report instead of the actual IOU report. Additionally, reportNameToDisplay falls back to an incorrect or empty report name when the parent report is missing, causing blank values in self DMs.

    What changes do you think we should make in order to solve the problem?
    File: src/pages/home/report/ReportActionItemContentCreated.tsx

    • Update import:
    import {getOriginalMessage} from '@libs/ReportActionsUtils';
    • Change line 124:
    parentReportID={getOriginalMessage(reportAction)?.IOUReportID || report?.reportID}
    • Change line 187:
    parentReportID={getOriginalMessage(reportAction)?.IOUReportID || transactionThreadReport?.reportID}

    File: src/components/ReportActionItem/MoneyRequestView.tsx

    • Change line 724:
    // Remove fallback to potentially incorrect parent report name
    reportNameToDisplay = getReportName(parentReport);

    What alternative solutions did you explore? (Optional)
    N/A

  7. mountiny commented on Jan 7, 2026

    @mountiny

    Testing this revert #79015

  8. 6 remaining items

  9. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 8, 2026
  10. changed the title [-]Expense - Report field in IOU expense shows IOU, Report field in self DM is blank[/-] [+][Due for payment 2026-01-15] Expense - Report field in IOU expense shows IOU, Report field in self DM is blank[/+] on Jan 8, 2026
  11. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.95-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-01-15. 🎊

  13. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    @arosiclair / @mountiny @johncschuster The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

  14. changed the title [-][Due for payment 2026-01-15] Expense - Report field in IOU expense shows IOU, Report field in self DM is blank[/-] [+][Due for payment 2026-01-16] [Due for payment 2026-01-15] Expense - Report field in IOU expense shows IOU, Report field in self DM is blank[/+] on Jan 9, 2026
  15. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.96-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-01-16. 🎊

  16. melvin-bot commented on Jan 9, 2026

    @melvin-bot

    @arosiclair / @mountiny @johncschuster The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions