Duplicate workspace plan changes to Control type after duplicating Collect workspace

[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

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

[melvin-bot]

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

[melvin-bot]

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

[github-actions]

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

[narefyev91]

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

[mollfpr]

Yup, this is a BE issue.