[Due for payment 2025-09-04] Workspace - Rules are enabled on Collect workspace 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: 9.1.98-0
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: https://app.slack.com/client/E8J4YNJHH/D05090F14AG#:~:text=the%20workspace%20address.-,https%3A//github.com/Expensify/App/pull/67412,-(edited)%C2%A0
Email or phone of affected tester (no customers): sdhshssdjiosdndjs@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Workspace Settings

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new Collect workspace.
3. Go back to workspace list.
4. Click 3-dot menu on the workspace.
5. Click Duplicate Workspace.
6. Click Next > Continue.
7. Open the duplicated workspace.
8. Go to Rules.

Expected Result:

Rules will not be enabled because the original workspace is on Collect plan and does not have Rules enabled.

Actual Result:

Rules are enabled when the original workspace is on Collect plan and does not have Rules enabled.
Receipt required amount, Max expense amount and Max expense age field values are all 0.

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

Issue Owner

Current Issue Owner: @Christinadobrzyn

[melvin-bot]

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

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

[melvin-bot]

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

[melvin-bot]

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

[marcaaron]

If this was caught during regression testing, add the test name, ID and link from TestRail: https://app.slack.com/client/E8J4YNJHH/D05090F14AG#:~:text=the%20workspace%20address.-,https%3A//github.com/Expensify/App/pull/67412,-(edited)%C2%A0

broken link