Repository navigation
Approvals are disabled when creating a workspace during Track Flow onboarding #64144
Description
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: v9.1.66-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: #62561
Email or phone of affected tester (no customers): N/A
Issue reported by: Applause Internal Team
Device used: Windows 11 / Chrome, Android 13-Chrome / Xiaomi Poco F5
App Component: Other
Action Performed:
- Create new account
- Skip if asked for work email
- Choose the Track and budget expenses
- Enter the name > Continue
- Choose the Create workspace when asked for creating a workspace
- Click Continue on Confirm workspace
- Click Skip on Invite members
- Go to Workspace > Workflows
Expected Result:
Approvals should be enabled when creating a workspace during Track Flow onboarding
Actual Result:
Approvals are disabled when creating a workspace during Track Flow onboarding
Note:
- The Approvals are enabled if the user skips creating a workspace on the Track flow onboarding, then creating a Workspace on the Workspace page
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome / Safari
- MacOS: Desktop
Activity
melvin-bot commentedon Jun 13, 2025
Triggered auto assignment to @carlosmiceli (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Jun 13, 2025
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.melvin-bot commentedon Jun 13, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Jun 13, 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:
shubham1206agra commentedon Jun 13, 2025
This is the expected behaviour. cc @dylanexpensify
BlameGPT commentedon Jun 13, 2025
Possible culprit PRs for this issue
carlosmiceli commentedon Jun 13, 2025
@shubham1206agra I see you authored this PR, so you confirm this is expected and we can close?
shubham1206agra commentedon Jun 13, 2025
@carlosmiceli Yes
carlosmiceli commentedon Jun 13, 2025
Great, thanks! Closing.
Julesssss commentedon Jun 13, 2025
Hey @carlosmiceli, it's not a problem but next time can you check this off the blocker list once resolved? thanks
carlosmiceli commentedon Jun 13, 2025
@Julesssss damn, sorry about that, I think I've been forgetting to do this the last couple of times, thanks for the call out 🙏
Julesssss commentedon Jun 13, 2025
It's all good. It only took me a second. Triaging the issue is way more important 🙂