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-10-21] Expense - "Select at least one expense" error is not shown when there is no result #72310
Version Number: 9.2.29-0 Reproducible in staging?: Yes Reproducible in production?: N/A - new feature, doesn't exist in prod If this was caught during regression testing, add the test name, ID and link from BrowserStack:#70280 Email or phone of affected tester (no customers):sdionjsdoisjdos@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Have at least 16 unreported expenses in self DM.
Go to staging.new.expensify.com
Go to workspace chat.
Create an empty report in workspace chat.
Click Add expense > Add unreported expense.
Enter anything that will not return any result.
Click Add to report.
Expected Result:
"Select at least one expense" error will be shown when there is no result
Actual Result:
"Select at least one expense" error is not shown when there is no result
👋 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.
changed the title [-]Expense - "Select at least one expense" error is not shown when there is no result[/-][+][Due for payment 2025-10-21] Expense - "Select at least one expense" error is not shown when there is no result[/+]on Oct 14, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.30-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@Valforte@zanyrenney 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]
No payment will be necessary here @zanyrenney, this issue was a regression that has already been fixed. Payment will be processed in the original issue. Thank you.
Activity
melvin-bot commentedon Oct 10, 2025
Triggered auto assignment to @Valforte (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 10, 2025
Triggered auto assignment to @zanyrenney (
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 Oct 10, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 10, 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:
7 remaining items
brunovjk commentedon Oct 13, 2025
Yes, I tested and this issue is fixed here, I'm waiting for the QA team to confirm it too 🤞
[-]Expense - "Select at least one expense" error is not shown when there is no result[/-][+][Due for payment 2025-10-21] Expense - "Select at least one expense" error is not shown when there is no result[/+]melvin-bot commentedon Oct 14, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.30-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 2025-10-21. 🎊
melvin-bot commentedon Oct 14, 2025
@Valforte @zanyrenney 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]
zanyrenney commentedon Oct 22, 2025
hey @Valforte can you confirm the contributors here please?
brunovjk commentedon Oct 22, 2025
No payment will be necessary here @zanyrenney, this issue was a regression that has already been fixed. Payment will be processed in the original issue. Thank you.
zanyrenney commentedon Oct 23, 2025
Thanks @brunovjk !