[Due for payment 2025-03-28] [Change Policy] Track expense - Expense is not moved to workspace when navigate to /change-workspace

[jponikarchuk]

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.13-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes
If this was caught during regression testing, add the test name, ID and link from TestRail: #57553
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

Precondition:

• Account has self DM and at least one workspace.

1. Go to staging.new.expensify.com
2. Go to self DM.
3. Track a manual expense.
4. Go to transaction thread.
5. Add /change-workspace to the end of the URL and navigate to it.
6. Select a workspace.

Expected Result:

The transaction will be moved to the selected workspace

Actual Result:

The transaction is not moved to the selected workspace.
The same issue also happens with p2p expense and invoice.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6770276_1741923680214.20250314_113744.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @johncschuster

[melvin-bot]

Triggered auto assignment to @johncschuster (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 @mollfpr (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.

[rayane-d]

This is expected. The "Change workspace" page is related only to the workspace expense reports. cc @luacmartins

[mollfpr]

I think this is still an issue. We shouldn't show the policy list if it's not report type expense.

[rayane-d]

I agree. We can display a 'not found' page in these cases. These scenarios were not addressed in the design doc, but we should definitely address them. I can work on a PR to fix these uncovered cases.

[mollfpr]

I'll assign the issues related to this change workspace feature to you, so it will be easier for you to track them!

[mountiny]

Assigning Carlos as we are managing the project. Adding it to migrate project too

[trjExpensify]

@luacmartins you can move an unreported tracked expense to a workspace in this way, right? So I agree, NotFoundPage for this invalid URL. Maybe can consolidate issues with: #58432 (comment)

[luacmartins]

I think this is invalid. For unreported expense, we'd use the "Report transaction" flow and not the change workspace. You can only change policies on reports, not transactions.

[luacmartins]

I'm gonna close this issue since this action is invalid.

[trjExpensify]

@luacmartins you can move an unreported tracked expense to a workspace in this way, right?

Sorry, I meant can't here!! Yeah, I think this should have a NotFoundPage as an invalid link.

[rayane-d]

Fixed in a10d963 by displaying a 'Not Found' page for cases where reports are not of the type 'Expense'

[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.16-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

• Fixes for change policy feature #58534

If no regressions arise, payment will be issued on 2025-03-28. 🎊

For reference, here are some details about the assignees on this issue:

• @eVoloshchak requires payment through NewDot Manual Requests
• @rayane-d requires payment through NewDot Manual Requests

[melvin-bot]

@eVoloshchak / @rayane-d @johncschuster @eVoloshchak / @rayane-d 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]