Skip to content

[Standardize Payment Buttons] Expense - Pay button does not update accordingly after changing workspace #64949

Description

@joekaufmanexpensify

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


Issue reported by: @joekaufmanexpensify
Slack conversation: #convert

Action Performed:

  1. Create two workspaces.
  2. Go to the first workspace chat.
  3. Submit an expense to the workspace chat.
  4. Click Submit, Approve, Pay and Mark as paid.
  5. Submit another expense to the same workspace chat.
  6. Click on the expense preview.
  7. Click Submit and Approve.
  8. Click More > Change workspace.
  9. Select the second workspace.
  10. Refresh the page.

Expected Result:

In Step 9, after changing workspace, Pay button in the expense report will change to "Pay" because there is no prior expense payment in the second workspace.

Actual Result:

In Step 9, after changing workspace, Pay button in the expense report is still "Mark as paid".
In Step 10, after refreshing the page, the Pay button changes to "Pay".

Workaround:

N/A

Platforms:

Select the officially supported platforms where the issue was reproduced:

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

Screenshots/Videos

2025-06-23_14-35-34.1.1.mp4

View all open jobs on GitHub

Upwork Automation - Do Not Edit
  • Upwork Job URL: https://www.upwork.com/jobs/~021937922925998133982
  • Upwork Job ID: 1937922925998133982
  • Last Price Increase: 2025-06-25
Issue OwnerCurrent Issue Owner: @

Activity

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.ExternalAdded to denote the issue can be worked on by a contributorReviewingHas a PR in reviewWeeklyKSv2

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions