Workspace - When creating first workspace, "Workflows" appears and disappears on WS settings

[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.51-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail: N/A
Email or phone of affected tester (no customers): ibellicotest+874@gmail.com
Issue reported by: Applause Internal Team
Device used: Motorola MotoG60 - Android 12 - Chrome / Windows 10 - Chrome
App Component: Workspace Settings

Action Performed:

1. Open the Expensify app.
2. Sign up with a new account.
3. Complete onboarding modal selecting "Track and budget" expenses option.
4. Once on inbox, tap on FAB and select "New Workspace".
5. Tap on "Confirm"
6. When redirected to the new workspace´s settings, note that the "Workflows" feature appears and disappears.

Expected Result:

"Workflows" feature shouldn´t be displayed as enabled when creating the first workspace on an account.

Actual Result:

"Workflows" feature appears and disappears when navigated to workspace´s settings after creating the first workspace on an account.

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 @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]

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.

[twilight2294]

I guess this is BE issue

[RachCHopkins]

@MonilBhavsar can you confirm, is this Internal?