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
[Due for payment 2025-07-25] Expense - Unable to add unreported expense to expense report #66107
Version Number: 9.1.81-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory Email or phone of affected tester (no customers):sdiodsjnosnodsi@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Chat Report View
Action Performed:
Precondition:
Account has self DM.
Go to staging.expensify.com
Go to self DM.
Submit a track expense.
Go to workspace chat.
Create a new report.
Click Add expense > Add unreported expense.
Select the track expense.
Click Add to report.
Expected Result:
User will be able to add unreported expense to expense report.
Actual Result:
User is unable to add unreported expense to expense 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.
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
None
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
changed the title [-]Expense - Unable to add unreported expense to expense report[/-][+][Due for payment 2025-07-25] Expense - Unable to add unreported expense to expense report[/+]on Jul 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.82-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@MariaHCD@stephanieelliott@rayane-d 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]
Activity
melvin-bot commentedon Jul 15, 2025
Triggered auto assignment to @stephanieelliott (
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.github-actions commentedon Jul 15, 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:
melvin-bot commentedon Jul 15, 2025
Triggered auto assignment to @mjasikowski (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jul 15, 2025
💬 A slack conversation has been started in #expensify-open-source
daledah commentedon Jul 15, 2025
Proposal
Please re-state the problem that we are trying to solve in this issue.
User is unable to add unreported expense to expense report.
What is the root cause of that problem?
This comes from #65802
We check for
isMoneyRequestReporthereApp/src/pages/AddUnreportedExpense.tsx
Line 187 in 7323ec5
This condition also returns
trueif report is WS Chat. And in WS chat, there's no recipient, so we return early here and do nothingApp/src/libs/actions/IOU.ts
Lines 5098 to 5101 in 8c0d91a
What changes do you think we should make in order to solve the problem?
We should only check for IOU report here
App/src/pages/AddUnreportedExpense.tsx
Line 187 in 7323ec5
What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?
None
What alternative solutions did you explore? (Optional)
Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.
6 remaining items
rayane-d commentedon Jul 15, 2025
PR is up #66130
luacmartins commentedon Jul 16, 2025
This is fixed in staging. Regression from #65802, no payments needed. CLosing.
Screen.Recording.2025-07-16.at.11.30.50.AM.mov
[-]Expense - Unable to add unreported expense to expense report[/-][+][Due for payment 2025-07-25] Expense - Unable to add unreported expense to expense report[/+]melvin-bot commentedon Jul 18, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jul 18, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.82-7 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-07-25. 🎊
For reference, here are some details about the assignees on this issue:
melvin-bot commentedon Jul 18, 2025
@MariaHCD @stephanieelliott @rayane-d 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]