Skip to content

Duplicate workspace plan changes to Control type after duplicating Collect workspace #69833

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: v9.2.1-11
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: Exploratory around #69146
Email or phone of affected tester (no customers): applausetester+ck93251@applause.expensifail.com
Issue reported by: Applause Internal Team
Device used: Windows 11/Chrome, iPhone 16/iOS 18.3.1, Pixel 8a/Android 15
App Component: Workspace Settings

Action Performed:

  1. Navigate to staging.new.expensify.com
  2. Create 2 workspaces - one Collect WS & the other Control WS (upgrade plan in Overview tab)
  3. Go to Workspaces list
  4. Tap 3 dots for Collect workspace
  5. Select Duplicate workspace
  6. Tap Next >> Continue
  7. Observe the plan type changes to Control when duplicating Collect workspace

Expected Result:

Workspace plan should not change to Control type when duplicating Collect workspace. Duplicate workspace should have Collect plan type

Actual Result:

Duplicate workspace plan changes to Control type after duplicating Collect workspace

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

Activity

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

    @melvin-bot

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

    @melvin-bot

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

  4. melvin-bot commented on Sep 4, 2025

    @melvin-bot

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

  5. github-actions commented on Sep 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.
  6. narefyev91 commented on Sep 4, 2025

    @narefyev91
    Contributor

    Feature is under the beta - @mountiny looks like BE issue

  7. mollfpr commented on Sep 4, 2025

    @mollfpr
    Contributor

    Yup, this is a BE issue.

  8. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Sep 4, 2025
  9. mollfpr commented on Sep 4, 2025

    @mollfpr
    Contributor

    https://github.com/Expensify/Web-Expensify/blob/588fccdc951a8d732058b5ffb70c3a907f0c9923/lib/Policy/Copier.php#L66-L71

    Look at the above condition, this case seems expected. We deliberately change the policy type to corporate if the user has corporate policies.

    cc @mountiny

  10. joekaufmanexpensify commented on Sep 4, 2025

    @joekaufmanexpensify
    Contributor

    Nice, going to close then as this seems to be 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