[Due for payment 2025-05-22] [Due for payment 2025-05-20] Expense-The Change workspace option is available to the employee and the approver

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: 9.1.42-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: #60872
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Windows 11/ Chrome, Samsung S23FE/ Android 14
App Component: Money Requests

Action Performed:

Pre-conditions:

• An employee account
• An approver account
• An admin account
• Workspace with all members above
• Workflow is configured to Add approvals and approver set to approver account
• Only use Expensifail accounts
• Employee and approver are members of at least 2 workspaces [Just create a workspace for every user, (the employee and the approver)]

1. Go to staging.new.expensify.com
2. Log in with the employee account
3. Submit an expense to the workspace
4. [Approver] Approve the report
5. [Employee] Verify that you don't see the Change workspace option
6. [Approver] Verify that you don't see the Change workspace option

Expected Result:

The Change workspace option is not displayed to the employee and the approver after approving an expense report.

Actual Result:

The Change workspace option is available to the employee and the approver after approving an expense 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

Bug6825073_1746677299420.Change_workspace_option_displayed_2.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @alexpensify

[melvin-bot]

Triggered auto assignment to @alexpensify (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]

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

[melvin-bot]

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

[github-actions]

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

[MariaHCD]

Related to #60872

cc: @luacmartins @rayane-d

[luacmartins]

PR in review

[melvin-bot]

Reviewing label has been removed, please complete the "BugZero Checklist".

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.44-8 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix workspace change logic #61667

If no regressions arise, payment will be issued on 2025-05-20. 🎊

[melvin-bot]

@MariaHCD / @luacmartins @alexpensify @MariaHCD / @luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

[melvin-bot]

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.45-21 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• [CP Staging] Fix workspace change logic #61667

If no regressions arise, payment will be issued on 2025-05-22. 🎊

[melvin-bot]

@MariaHCD / @luacmartins @alexpensify @MariaHCD / @luacmartins The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]