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
Email - Missing the Pay button in the report preview in Email #74913
Version Number: v9.2.54-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:https://test-management.browserstack.com/projects/2219752/test-runs/TR-1932/folder/13176725/41237078/1008198940 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Windows 10/Chrome App Component: Money Requests
Action Performed:
Workspace setup: User is an Admin of a Workspace
Add a member you have access to as an employee
Disable Approvals
Delay Submissions is OFF
Enable payments
Steps - Manual Expense
Log in as the employee
Click on the FAB button -> Create Manual expense
Click on the Expense in the SelfDM
Click on the Report section
Click on the Create Report
Click on the link at the top of the expense and submit it
Check the email inbox of the Admin
Expected Result:
Verify the email subject reads: “Please pay my amount expense”
Verify a “Pay” button is displayed in the report preview component
Actual Result:
The email subject reads Submitted my x.xxx expense
The preview doesn't have a Pay button
👋 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.
Hmm based on the recording it actually seems like this happened because the expense wasn't reimbursable after getting added to the expense report. Is it expected that an unreported expense in a selfDM becomes non-reimbursable after it is added to a report on a workspace?
Activity
melvin-bot commentedon Nov 12, 2025
Triggered auto assignment to @JmillsExpensify (
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 Nov 12, 2025
Triggered auto assignment to @jasperhuangg (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 12, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 12, 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:
cristipaval commentedon Nov 12, 2025
I can't reproduce it
IuliiaHerets commentedon Nov 12, 2025
@cristipaval QA team still can reproduce this issue on Web and iOS app, v9.2.54-1. Two different testers have the same result
Video_2025-11-12_205643.mp4
email.submit.MP4
cristipaval commentedon Nov 12, 2025
Demoting this because emails are always built on the backend.
IuliiaHerets commentedon Nov 12, 2025
@cristipaval Repro on staging build with the prod server, Windows 11 / Chrome, v9.2.54-1
email.1.mp4
Repro on Prod with different subject, Windows 11 / Chrome, v9.2.48-1. Other tester has an unexpected error in Prod
email.prod.1.mp4
Video_2025-11-12_214822.mp4
cristipaval commentedon Nov 12, 2025
Ok, so it seems to reproduce with prod build as well as with staging build pointing to prod.
jasperhuangg commentedon Nov 12, 2025
Seems that some type of regression has happened, this behavior used to work
jasperhuangg commentedon Nov 12, 2025
jasperhuangg commentedon Nov 12, 2025
https://expensify.slack.com/archives/C03U7DCU4/p1762978411579149 asking in #product
jasperhuangg commentedon Nov 13, 2025
clarified here that this is expected behavior.
the tester didn't correctly follow the steps in the linked TC.. it never mentions selfDMs.