Skip to content

[Due for payment 2025-12-03] [$250] Expense - Empty report state displayed in workspace chat when navigating from reports #74804

Closed

Description

@nlemma

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.2.49-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: N/A
Email or phone of affected tester (no customers): htad26+zxzxzgd@gmail.com
Issue reported by: Applause Internal Team
Device used: Windows 10/Chrome, iOS 26.1/iPhone 13
App Component: Chat Report View

Action Performed:

  1. Create a new workspace
  2. Create a new manual expense in the workspace
  3. Navigate to Reports > Expenses
  4. Click on the created expense > Click on the from link
  5. Navigate to inbox
  6. Navigate back to Reports > Expenses
  7. Click again on the created expense > Click on the from link

Expected Result:

The user is redirected to the workspace chat

Actual Result:

Empty report state displayed above the expense 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

Bug7000567_1762868066298.2025-11-11_16_26_46.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021988250885593272625
  • Upwork Job ID: 1988250885593272625
  • Last Price Increase: 2025-11-11
  • Automatic offers:
    • truph01 | Contributor | 109448892
Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @kadiealexander

Activity

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

    @melvin-bot

    Triggered auto assignment to @kadiealexander (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.

  3. melvin-bot commented on Nov 11, 2025

    @melvin-bot

    Triggered auto assignment to @Gonals (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. github-actions commented on Nov 11, 2025

    @github-actions
    Contributor

    👋 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.
  5. melvin-bot commented on Nov 11, 2025

    @melvin-bot

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

  6. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 11, 2025
  7. 23 remaining items

  8. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Nov 20, 2025
  9. changed the title [-][$250] Expense - Empty report state displayed in workspace chat when navigating from reports[/-] [+][Due for payment 2025-12-03] [$250] Expense - Empty report state displayed in workspace chat when navigating from reports[/+] on Nov 26, 2025
  10. melvin-bot commented on Nov 26, 2025

    @melvin-bot

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

  11. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.63-8 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 2025-12-03. 🎊

    For reference, here are some details about the assignees on this issue:

  12. melvin-bot commented on Nov 26, 2025

    @melvin-bot

    @ikevin127 / @truph01 @kadiealexander 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]

  13. ikevin127 commented on Dec 3, 2025

    @ikevin127
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to comment: N/A - Result of the original design

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    • [BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.

      Link to issue: https://github.com/Expensify/Expensify/issues/574514

    Regression Test Proposal

    1. Create a new workspace.
    2. Create a new manual expense in the workspace.
    3. Navigate to Reports > Expenses.
    4. Click on the created expense > Click on the from link.
    5. Navigate to Inbox.
    6. Navigate back to Reports > Expenses.
    7. Click again on the created expense > Click on the from link.
    8. Verify that the user is redirected to the workspace chat.

    Do we agree 👍 or 👎.

  14. kadiealexander commented on Dec 4, 2025

    @kadiealexander
    Contributor

    Payment Summary

  15. JmillsExpensify commented on Dec 8, 2025

    @JmillsExpensify
    Contributor

    $250 approved for @ikevin127

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.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions