Reports -"Change Workspace" available on expense report on chat but not on "Reports" section

[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.25-0
Reproducible in staging?: Yes
Reproducible in production?: Unable to check in Prod, new feature
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Yes, reproducible on both
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Money Requests

Action Performed:

Prerequisite: Use a Gmail account with SelfDM and have at least one workspace available.

1. Open the staging.new.expensify.com website.
2. Tap on FAB and select "Create Expense"
3. Complete the creation flow and submit it to Self DM.
4. On system message on chat, select "Share with my accountant"
5. Add a merchant and submit the expense to any workspace.
6. Open the expense report.
7. Tap on "More" and note that "Change Workspace" option is present.
8. Navigate to "Reports"
9. Open the same expense report.
10. Tap on "More" and note that "Change Workspace" option is not present.

Expected Result:

"Change Workspace" option should be available for a track expense when opening report on chat and also on "Reports" section.

Actual Result:

"Change Workspace" option is not available on expense on "Reports" section, but is present when opening the report on chat.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @maddylewis

[melvin-bot]

Triggered auto assignment to @maddylewis (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 @Valforte (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.

[jnowakow]

I'm not able to reproduce it:

[Valforte]

Reproduced on staging

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

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

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

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

[luacmartins]

FYI we reverted the original offending PR

[jasperhuangg]

I think we can close it out, confirmed fixed

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

• [CP Staging] Revert "Simplified actions on report header" #59931

If no regressions arise, payment will be issued on 2025-04-18. 🎊

[melvin-bot]

@Valforte @maddylewis @Valforte 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]

[jnowakow]

@luacmartins the root cause of this bug is that on reports screen we display transaction in RHP not report:

So technically it's not bug because those are two different views. In RHP on search page we display transaction screen instead of report screen. That's why there are different options

[luacmartins]

hmm we can show the report in the RHP. If you go to Reports > Expense reports and click on one, you'll see that the report is opened in the RHP. That being said, I agree that the video in the OP is opening a transaction and not an expense report. We're also changing this in the other report projects (where the report will show in the main screen). So maybe we don't need to worry about this one now.

Screen.Recording.2025-04-11.at.9.23.30.AM.mov

[luacmartins]

Reopening since this one doesn't seem to be fixed

[luacmartins]

The bug is coming from the BE. When we convert the tracked expense to a request, we're keeping the type: 'track' instead of updating it to type: 'create', which in turn makes isFromOneTransactionReport return false and we display the MoneyRequestHeader component instead of MoneyReportHeader which have different available actions. I have a PR in review to fix that.