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 - Missing "Waiting for you to add expense(s)" message in empty report #66123
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:https://expensify.testrail.io/index.php?/tests/view/6499055 Email or phone of affected tester (no customers):dsjnodjdsoisjdoj@gmail.com Issue reported by: Applause Internal Team Device used: Mac 15.5 / Chrome App Component: Money Requests
Action Performed:
Precondition:
Have at least a workspace.
Go to staging.expensify.com
Click FAB > Create report.
Expected Result:
"Waiting for you to add expense(s)" message is shown in the empty report.
Actual Result:
"Waiting for you to add expense(s)" message is missing in the empty 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.
changed the title [-]Expense - Missing "Waiting for you to add expense(s)" message in empty report[/-][+][Due for payment 2025-07-25] Expense - Missing "Waiting for you to add expense(s)" message in empty 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:
@luacmartins / @srikarparsi@dylanexpensify 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 @dylanexpensify (
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 Jul 15, 2025
Triggered auto assignment to @srikarparsi (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.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
💬 A slack conversation has been started in #expensify-open-source
9 remaining items
srikarparsi commentedon Jul 16, 2025
Waiting on CP to staging
melvin-bot commentedon Jul 16, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
luacmartins commentedon Jul 16, 2025
Fixed in staging
[-]Expense - Missing "Waiting for you to add expense(s)" message in empty report[/-][+][Due for payment 2025-07-25] Expense - Missing "Waiting for you to add expense(s)" message in empty 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. 🎊
melvin-bot commentedon Jul 18, 2025
@luacmartins / @srikarparsi @dylanexpensify 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]