Skip to content

Duplicate workspace - Reports field shows 1 report field when workspace has no report field #69710

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.2.1-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 TestRail: #69146
Email or phone of affected tester (no customers): applausetester+2608203kh@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

Precondition:

  • Log in with Expensifail account.
  1. Go to staging.expensify.com
  2. Create a workspace
  3. Go back to workspace list
  4. Click 3-dot menu on the workspace
  5. Click Duplicate Workspace
  6. Click Next

Expected Result:

Reports field will not appear in the list because the new workspace does not have any report field.

Actual Result:

Reports field appears in the list when the new workspace does not have any report field.

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

Bug6933803_1756856237090.Screen_Recording_2025-09-03_at_07.33.49.mp4

View all open jobs on GitHub

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 Sep 3, 2025
  2. melvin-bot commented on Sep 3, 2025

    @melvin-bot

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

  3. melvin-bot commented on Sep 3, 2025

    @melvin-bot

    Triggered auto assignment to @alexpensify (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 Sep 3, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 3, 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. lakchote commented on Sep 3, 2025

    @lakchote
    Contributor
  7. narefyev91 commented on Sep 3, 2025

    @narefyev91
    Contributor

    I think it's expected - I added comment in this one #69054
    OldDot working in the same manner cc @mountiny
    Anyway feature is under the beta - and could checked off @alexpensify @lakchote

  8. lakchote commented on Sep 3, 2025

    @lakchote
    Contributor

    Checking it off, and removing the blocker labels since it's behind beta.

    @mountiny can you confirm it's expected please?

  9. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    DeployBlockerIndicates it should block deploying the API
    on Sep 3, 2025
  10. mountiny commented on Sep 3, 2025

    @mountiny
    Contributor

    Sorry yeah I think this is expected cc @MitchExpensify if you agree, can you please close the issue?

  11. MitchExpensify commented on Sep 3, 2025

    @MitchExpensify
    Contributor

    Correct, expected

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

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions