Skip to content

Email - Missing the Pay button in the report preview in Email #74913

Closed

Description

@nlemma

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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

  1. Log in as the employee
  2. Click on the FAB button -> Create Manual expense
  3. Click on the Expense in the SelfDM
  4. Click on the Report section
  5. Click on the Create Report
  6. Click on the link at the top of the expense and submit it
  7. 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

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Bug7001332_1762927251564.pay_button.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 12, 2025
  2. melvin-bot commented on Nov 12, 2025

    @melvin-bot

    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.

  3. melvin-bot commented on Nov 12, 2025

    @melvin-bot

    Triggered auto assignment to @jasperhuangg (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Nov 12, 2025

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. github-actions commented on Nov 12, 2025

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. cristipaval commented on Nov 12, 2025

    @cristipaval
    Contributor

    I can't reproduce it

  7. IuliiaHerets commented on Nov 12, 2025

    @IuliiaHerets

    @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
  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Nov 12, 2025
  9. cristipaval commented on Nov 12, 2025

    @cristipaval
    Contributor

    Demoting this because emails are always built on the backend.

  10. IuliiaHerets commented on Nov 12, 2025

    @IuliiaHerets

    @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
  11. cristipaval commented on Nov 12, 2025

    @cristipaval
    Contributor

    Ok, so it seems to reproduce with prod build as well as with staging build pointing to prod.

  12. added
    InternalRequires API changes or must be handled by Expensify staff
    on Nov 12, 2025
  13. jasperhuangg commented on Nov 12, 2025

    @jasperhuangg
    Contributor

    Seems that some type of regression has happened, this behavior used to work

  14. jasperhuangg commented on Nov 12, 2025

    @jasperhuangg
    Contributor
    Image 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?
  15. jasperhuangg commented on Nov 12, 2025

    @jasperhuangg
    Contributor
  16. jasperhuangg commented on Nov 13, 2025

    @jasperhuangg
    Contributor

    clarified here that this is expected behavior.

    the tester didn't correctly follow the steps in the linked TC.. it never mentions selfDMs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringInternalRequires API changes or must be handled by Expensify staff

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions