You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expense - Wide RHP closes after adding unreported expense/moving expense to new report #77595
Version Number: 9.2.78-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:#75886 Email or phone of affected tester (no customers):siodjosdinjosjsoinjso@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Money Requests
Action Performed:
Bug 1:
Precondition:
Create an expense in self DM.
Go to staging.new.expensify.com
Go to workspace chat.
Create an empty report.
Open the empty report.
Click Add expense > Add unreported expense.
Select the expense in self DM > Add unreported expense.
Bug 2:
Go to staging.new.expensify.com
Go to workspace chat.
Create two expenses.
Open the expense report.
Select all expenses.
Click More > Move expenses > Create report.
Expected Result:
Bug 1: Wide RHP will not close after adding unreported expense.
Bug 2: Wide RHP will not close after moving expense to new report.
Actual Result:
Bug 1: Wide RHP closes after adding unreported expense.
Bug 2: Wide RHP closes after moving expense to new report.
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Dec 13, 2025
Triggered auto assignment to @greg-schroeder (
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.melvin-bot commentedon Dec 13, 2025
Triggered auto assignment to @Valforte (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Dec 13, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Dec 13, 2025
👋 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:
m-natarajan commentedon Dec 15, 2025
Issue no longer reproducible. Retested on Windows11/Chrome. Build 9.2.78.1
Wide.Close.mp4