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 2026-03-31] [$250] Expense - Change workspace option is shown in paid expense in 1:1 chat for employee #83091
Version Number: 9.3.24-1 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/folder/13176725/test-cases/41237073 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: MacBook air 15.7.3 Chrome App Component: Money Requests
Action Performed:
Preconditions: User A is a member of User C's workspace. User A is not an admin of any workspace
Sign in to ND as User A and User B
As User A, send an expense in 1:1 chat with User B
As User B, mark the expense as paid
As User A, open expense details, click More - Change workspace
Expected Result:
"Change workspace" option is not presented in paid expense for User B, because when clicking on it, it does not show any workspaces
Actual Result:
"Change workspace" option is shown in paid expense in 1:1 chat for employee, when clicking on it, blank RHP is opened
Please re-state the problem that we are trying to solve in this issue.
"Change workspace" option is shown in paid expense in 1:1 chat for employee, when clicking on it, blank RHP is opened
What is the root cause of that problem?
There is a inconsistency between how we filter the valid policy to change to in here and here.
What changes do you think we should make in order to solve the problem?
We should sync the logic between them. In here, we should check whether the report is settled and whether the current user is not an admin of the policy. If both conditions are true, we should skip that policy.
What alternative solutions did you explore? (Optional)
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
User A is a member of User C's workspace. User A is not an admin of any workspace
Test:
Sign in to ND as User A and User B
As User A, send an expense in 1:1 chat with User B
Activity
truph01 commentedon Feb 23, 2026
Proposal
Please re-state the problem that we are trying to solve in this issue.
What is the root cause of that problem?
What changes do you think we should make in order to solve the problem?
What alternative solutions did you explore? (Optional)
marcaaron commentedon Feb 28, 2026
Seems like pretty low hanging fruit. Let's implement this?
melvin-bot commentedon Feb 28, 2026
Triggered auto assignment to @stephanieelliott (
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.42 remaining items
mallenexpensify commentedon Apr 1, 2026
Payment Summary
Contributor: @truph01 due $250 via NewDot
Contributor+: @FitseTLT paid $250 via Upwork
@FitseTLT plz complete the BZ checklist and tag me in a post once you have. Thx
FitseTLT commentedon Apr 2, 2026
BugZero Checklist:
[Contributor] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.
Link to comment: https://github.com/Expensify/App/pull/60872/changes#r3028269841
[Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.
Link to discussion:
[Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.
[BugZero Assignee] Create a GH issue for creating/updating the regression test once above steps have been agreed upon.
Link to issue:
Regression Test Proposal
Precondition:
Test:
Do we agree 👍 or 👎
Zapier Logs
Run ID: 00040eee-cedb-ae3c-3df4-f5f4c566cdb4FitseTLT commentedon Apr 2, 2026
@mallenexpensify
mallenexpensify commentedon Apr 6, 2026
^ Test case created
Thx
garrettmknight commentedon May 10, 2026
$250 approved for @truph01