Skip to content

[Due for payment 2025-12-16] Expense - Create report button is shown in confirm page in non-default workspace chat #76734

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.2.72-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: #76023
Email or phone of affected tester (no customers): siodjosidjosjosjisjd@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 26.1 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Create two workspaces - A and B. A is the default workspace.
  3. Go to workspace chat B.
  4. Create two reports.
  5. Click + > Create expense > Manual.
  6. Enter amount > Next.
  7. On confirm page, click Report field.
  8. Click Create report.
  9. Enter merchant.
  10. Click Create expense.

Expected Result:

In Step 8, Create report button should appear for workspace B, since the create flow was triggered from the B's workspace chat.

Actual Result:

In Step 8, Create report button is shown when the expense is created in workspace chat B.
The new report is created in workspace chat A, and the expense is created in workspace chat B, so the button serves no purpose in this case.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

1.mp4

View all open jobs on GitHub

Issue OwnerCurrent Issue Owner: @bfitzexpensify

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 @bfitzexpensify (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 @inimaga (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

    Rather than not showing the button, I think we should just update it to create a report in workspace B, updating the expected behavior

  7. jasperhuangg commented on Dec 4, 2025

    @jasperhuangg
    Contributor

    #76023 seems suspicious

  8. jasperhuangg commented on Dec 4, 2025

    @jasperhuangg
  9. 18 remaining items

  10. inimaga commented on Dec 4, 2025

    @inimaga
    Contributor

    @jasperhuangg Step 5 wasn't actually triggered from the FAB. But seems like the deployblocker got resolved as the likely culprit is now reverted. Have asked for a re-test.

  11. m-natarajan commented on Dec 4, 2025

    @m-natarajan

    There is no Create report option(Step 8), MacOS Monterey / Chrome, Web v9.2.72-2

    Screen.Recording.2025-12-05.at.01.42.26.mp4
  12. 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.

  13. inimaga commented on Dec 5, 2025

    @inimaga
    Contributor

    Closing as no longer an issue atm.

  14. added
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Dec 9, 2025
  15. changed the title [-]Expense - Create report button is shown in confirm page in non-default workspace chat[/-] [+][Due for payment 2025-12-16] Expense - Create report button is shown in confirm page in non-default workspace chat[/+] on Dec 9, 2025
  16. melvin-bot commented on Dec 9, 2025

    @melvin-bot

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

  17. 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. 🎊

  18. melvin-bot commented on Dec 9, 2025

    @melvin-bot

    @inimaga @bfitzexpensify 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