Skip to content

Reports - "Pay via workspace" option is missing in the Pay menu after app reset #65164

Closed

Description

@mitarachim

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: 9.1.72-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 TestRail: #56838
Email or phone of affected tester (no customers): noidsjoijnoisjsoid2e@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Search

Action Performed:

Precondition:

  • The default currency for User A is USD.
  • User B has at least one workspace.
  1. Go to staging.new.expensify.com
  2. [User A] Open 1:1 DM with User B and submit an expense to User B.
  3. [User B] Go to Reports.
  4. [User B] Click Pay button on the expense.
  5. [User B] "Pay via workspace" option is present in the Pay menu.
  6. [User B] Go to Account > Troubleshoot > Clear cache and restart > Reset and refresh.
  7. [User B] Go to Reports.
  8. [User B] Click Pay button on the expense.

Expected Result:

"Pay via workspace" option will be present in the Pay menu after app reset.

Actual Result:

"Pay via workspace" option is missing in the Pay menu after app reset.
The option only appears after opening the IOU report.

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

Bug6873523_1751266319952.20250630_144644.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.
    DeployBlockerIndicates it should block deploying the API
    on Jun 30, 2025
  2. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    Triggered auto assignment to @isabelastisser (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 Jun 30, 2025

    @melvin-bot

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

  4. melvin-bot commented on Jun 30, 2025

    @melvin-bot

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

  5. github-actions commented on Jun 30, 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. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  7. melvin-bot commented on Jun 30, 2025

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  8. IuliiaHerets commented on Jun 30, 2025

    @IuliiaHerets

    Issue not Repro 🕸️ Windows 11 / Chrome, v9.1.72-7

    video_38-1.mp4
  9. puneetlath commented on Jun 30, 2025

    @puneetlath
    Contributor

    Great, closing!

  10. added and removed
    DeployBlockerIndicates it should block deploying the API
    on Jun 30, 2025
  11. added a commit that references this issue on Jul 2, 2025
    4ba0311
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.DailyKSv2EngineeringReviewingHas a PR in review

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions