[HOLD for payment 2024-12-09] [HOLD for payment 2024-12-07] Workspace - The button to save the type of plan doesn't work

[IuliiaHerets]

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.0.68-0
Reproducible in staging?: Y
Reproducible in production?: N/A - new feature, doesn't exist in prod
Issue reported by: Applause Internal Team

Action Performed:

1. Go to https://staging.new.expensify.com/
2. Login with the new Gmail account in incognito mode.
3. Complete the incorporation process using the option “Something Else”
4. Enter a first name and click on the Continue button.
5. Click on the "FAB" button and click on "New Workspace".
6. Click on the "Plan type" section and select "Control" and click on "Save".
7. Click on the "Upgrade button" and click on the "Got it, Thanks" button.
8. Change the Subscription details to Pay-per-use.
9. Try changing the Plan type from the workspace section to "Collect".

Expected Result:

The save button should work correctly.

Actual Result:

The button to save the plan type chosen for the workspace does not work after changing the subscription type.

Workaround:

Unknown

Platforms:

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Bug6679177_1732806110532.2024-11-28_10-52-41.mp4

View all open jobs on GitHub

Issue Owner

Current Issue Owner: @garrettmknight

[melvin-bot]

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

[melvin-bot]

Triggered auto assignment to @RachCHopkins (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]

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

[mountiny]

@trjExpensify i thought its not possible to downgrade in app now?