Skip to content

[Due for payment 2025-04-28] Expense - Expense is created in report from other workspace when a new workspace is selected #60234

Closed

Description

@jponikarchuk

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.1.28-1
Reproducible in staging?: Yes
Reproducible in production?: Unable to check, new feature
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: No, reproducible on hybrid only
If this was caught during regression testing, add the test name, ID and link from TestRail: Exp
Email or phone of affected tester (no customers): sdjsdmiojoms@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.3 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create two new workspaces.
  3. Click FAB > Create expense > Manual.
  4. Enter amount > Next.
  5. Enter merchant and click Create expense.
  6. Click FAB > Create expense > Manual.
  7. Enter amount > Next.
  8. Click Show more.
  9. Click Report.
  10. Click on the same report.
  11. Click To field.
  12. Select the second workspace.
  13. Note that the Report field shows the new report title and not the one selected in Step 10.
  14. Enter merchant.
  15. Click Create expense.

Expected Result:

The expense should be created in a new report in the second workspace.

Actual Result:

The expense is created in the selected report from the first workspace in Step 10, even though another workspace is selected and Report field shows a new report in Step 13.

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 OwnerCurrent Issue Owner: @CortneyOfstad

Activity

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

    @melvin-bot

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

  3. melvin-bot commented on Apr 15, 2025

    @melvin-bot

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

  4. melvin-bot commented on Apr 15, 2025

    @melvin-bot

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

  5. github-actions commented on Apr 15, 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.
  6. rayane-d commented on Apr 15, 2025

    @rayane-d
    Contributor
  7. luacmartins commented on Apr 15, 2025

    @luacmartins
    Contributor

    We'll put this button behind a beta and tackle the issue as a follow up.

  8. self-assigned this
    on Apr 15, 2025
  9. 1 remaining item

  10. luacmartins commented on Apr 15, 2025

    @luacmartins
    Contributor

    No longer available in staging. Demoting.

  11. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Apr 15, 2025
  12. melvin-bot commented on Apr 21, 2025

    @melvin-bot

    @waterim Eep! 4 days overdue now. Issues have feelings too...

  13. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Apr 21, 2025
  14. changed the title [-]Expense - Expense is created in report from other workspace when a new workspace is selected[/-] [+][Due for payment 2025-04-28] Expense - Expense is created in report from other workspace when a new workspace is selected[/+] on Apr 21, 2025
  15. melvin-bot commented on Apr 21, 2025

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.1.30-4 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-04-28. 🎊

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

    • @waterim does not require payment (Contractor)
  16. melvin-bot commented on Apr 21, 2025

    @melvin-bot

    @luacmartins / @techievivek @CortneyOfstad @waterim 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]

  17. luacmartins commented on Apr 22, 2025

    @luacmartins
    Contributor

    We can close this issue since it's fixed.

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