"Prevent members from changing custom report name" not toggled off after downgrade WS

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email [email protected] to request to join our Slack channel!

---

Version Number: v9.1.45-18
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: Exploratory around #59568
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Windows 11/Chrome, iPhone 16/iOS 18.3.1
App Component: Workspace Settings

Action Performed:

1. Navigate to staging.new.expensify.com
2. Create new account
3. Go to Accounts >> Workspaces >> Create new workspace
4. Go to workspace settings >> Reports option
5. Toggle on "Prevent members from changing custom report name"
6. Click Upgrade
7. Click "View your subscription" link
8. Select Explore all plans button
9. Downgrade to Collect WS
10. Go to Workspaces & select the collect WS
11. Click Reports option & observe "Prevent members from changing custom report name" toggle is on

Expected Result:

"Prevent members from changing custom report name" should automatically toggle off after downgrading WS to Collect WS

Actual Result:

"Prevent members from changing custom report name" not automatically toggled off after downgrading WS to collect WS.
Issue does not happen for Report fields option. When workspace is downgraded to WS, report field toggle button is OFF as expected

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

Bug6831686_1747276595437.Recording__160.mp4

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @miljakljajic (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 @MonilBhavsar (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.

[francoisl]

I don't think this is worth being a deploy blocker, we can fix it in a follow-up PR. Also it might require backend changes to disable that feature when you downgrade a policy.

[MonilBhavsar]

Demoting as discussed in https://expensify.slack.com/archives/C01GTK53T8Q/p1747277980550709

[suneox]

It seems to be a backend issue after downgrade to Collect WS does not disable areReportFieldsEnabled

[MonilBhavsar]

Thanks! Discussing in the slack thread about next steps

[FitseTLT]

@MonilBhavsar U can add a note to handle this in #61612 and close this as it should normally handle it.

[melvin-bot]

@miljakljajic, @MonilBhavsar Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

[miljakljajic]

Being handled in #61612

[carlosmiceli]

Reopening because this issue does not follow the same logic as downgrading approval workflow. Will solve in another PR.

[carlosmiceli]

PR is up for review.