Skip to content

[Due for payment 2026-02-03] Expense - Create report button shows wrong workspace, expense cannot be moved #80414

Closed

Description

@mitarachim

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


Version Number: 9.3.8-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #76000
Email or phone of affected tester (no customers): sdjoisdnjodinjsodjidsji1@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

Precondition-

  • Admin has two workspaces - A and B.
  • Workspace A is default workspace.
  • Admin invites member to workspace B.
  1. Go to staging.new.expensify.com
  2. [Member] Go to the invited workspace chat.
  3. [Member] Create an expense.
  4. [Admin] Open member's expense report.
  5. [Admin] Click Report > Create report.

Expected Result:

Create report button will show workspace B as the subtitle.

Actual Result:

Create report button shows workspace A as the subtitle. As a result, the expense cannot be moved to a new report.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7056840_1769217104761.8.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @heyjennahay

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jan 24, 2026
  2. melvin-bot commented on Jan 24, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #78634

  3. melvin-bot commented on Jan 24, 2026

    @melvin-bot

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

  4. melvin-bot commented on Jan 24, 2026

    @melvin-bot

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

  5. github-actions commented on Jan 24, 2026

    @github-actions
    Contributor

    👋 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.
  6. situchan commented on Jan 26, 2026

    @situchan
    Contributor

    Seems related to #76000

  7. 9 remaining items

  8. s77rt commented on Jan 26, 2026

    @s77rt
    Member

    Thanks for handling this!

  9. m-natarajan commented on Jan 26, 2026

    @m-natarajan

    Not Repro, Chrome and Honor x6b/ Android 14, v9.3.8-3 (Waiting for validation result in iOS)

    Video.mp4
    Screen.Recording.2026-01-26.at.22.05.57.mp4
  10. chuckdries commented on Jan 26, 2026

    @chuckdries
    Contributor

    Thanks! This logic won't be different across devices, we're good to close

  11. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Jan 27, 2026
  12. changed the title [-]Expense - Create report button shows wrong workspace, expense cannot be moved[/-] [+][Due for payment 2026-02-03] Expense - Create report button shows wrong workspace, expense cannot be moved[/+] on Jan 27, 2026
  13. melvin-bot commented on Jan 27, 2026

    @melvin-bot

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

  14. melvin-bot commented on Jan 27, 2026

    @melvin-bot

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

    If no regressions arise, payment will be issued on 2026-02-03. 🎊

  15. melvin-bot commented on Jan 27, 2026

    @melvin-bot

    @chuckdries @heyjennahay 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]

  16. melvin-bot commented on Apr 9, 2026

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

  17. jayeshmangwani commented on May 28, 2026

    @jayeshmangwani
    Contributor

    Coming from this issue #84618, here we are passing selectedReport?.policyID. However, on the IOURequestEditReport page, where we are using IOURequestEditReportCommon, we are not passing the second param to usePolicyForMovingExpenses. Because of that, it shows the current workspace under "Create report", but the report actually gets created in the default workspace.

    const {policyForMovingExpensesID, shouldSelectPolicy} = usePolicyForMovingExpenses(hasPerDiemTransactions);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.EngineeringWeeklyKSv2

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions