You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Duplicate workspace plan changes to Control type after duplicating Collect workspace #69833
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:
Navigate to staging.new.expensify.com
Create 2 workspaces - one Collect WS & the other Control WS (upgrade plan in Overview tab)
Go to Workspaces list
Tap 3 dots for Collect workspace
Select Duplicate workspace
Tap Next >> Continue
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
👋 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:
Identify the pull request that introduced this issue and revert it.
Activity
melvin-bot commentedon Sep 4, 2025
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 commentedon Sep 4, 2025
Triggered auto assignment to @mollfpr (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 4, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 4, 2025
👋 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:
narefyev91 commentedon Sep 4, 2025
Feature is under the beta - @mountiny looks like BE issue
mollfpr commentedon Sep 4, 2025
Yup, this is a BE issue.
mollfpr commentedon Sep 4, 2025
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
joekaufmanexpensify commentedon Sep 4, 2025
Nice, going to close then as this seems to be expected