Skip to content

[Due for payment 2025-12-16] Expense - To field and Report field show different workspace after creating new report #76737

Closed

Description

@lanitochka17

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.2.72-0
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught during regression testing, add the test name, ID and link from TestRail: #76023
Email or phone of affected tester (no customers): siodjosidjosjosjisjd@gmail.com
Issue reported by: Applause - Internal Team

Action Performed:

Precondition:

  • Create two workspace - A and B.
  • Workspace A is default workspace.
  1. Go to staging.new.expensify.com
  2. Go to workspace chat B
  3. Create two reports
  4. Open FAB > Create expense > Manual
  5. Enter amount > Next
  6. On confirm page, click To field and change to workspace chat B
  7. Click Report field
  8. Click Create report
  9. Click Report field
    → Report from workspace chat A is selected
  10. Click RHP back button
    → To field still shows workspace chat B
  11. Enter merchant and click Create expense

Expected Result:

In Step 10, To field should change to workspace chat A because the new report in workspace A is selected

Actual Result:

In Step 10, To field is still workspace B when the new report in workspace A is selected
In Step 11, the expense is created in workspace B. The report selection in Step 9 is ignored

Workaround:

Unknown

Platforms:

Select the officially supported platforms where the issue was reproduced:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop
Platforms Tested: On which of our officially supported platforms was this issue tested:
  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari
  • MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence
Bug7020760_1764865579906.5.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @NicMendonca

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Dec 4, 2025
  2. melvin-bot commented on Dec 4, 2025

    @melvin-bot

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

  3. melvin-bot commented on Dec 4, 2025

    @melvin-bot

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

  4. github-actions commented on Dec 4, 2025

    @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.
  5. melvin-bot commented on Dec 4, 2025

    @melvin-bot

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

  6. jasperhuangg commented on Dec 4, 2025

    @jasperhuangg
    Contributor

    Okay yeah this seems like a pretty bad bug and warrants a revert I think. @Eskalifer1 I see you're around, do you want to see if you can get a fix up for this so we don't need to revert?

  7. m-natarajan commented on Dec 5, 2025

    @m-natarajan

    Mac Chrome build 9.2.72-2 step 8 - Create report option is missing

    Retest.1.mp4
  8. melvin-bot commented on Dec 5, 2025

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

  9. cristipaval commented on Dec 5, 2025

    @cristipaval
    Contributor

    Great, that's what we want

  10. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 9, 2025
  11. changed the title [-]Expense - To field and Report field show different workspace after creating new report[/-] [+][Due for payment 2025-12-16] Expense - To field and Report field show different workspace after creating new report[/+] on Dec 9, 2025
  12. melvin-bot commented on Dec 9, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.73-5 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 2025-12-16. 🎊

  13. melvin-bot commented on Dec 9, 2025

    @melvin-bot

    @cristipaval @NicMendonca 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]

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