-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] iOS/Android WS features -Feature is not enabled after enabling it and upgrading workspace to Control #53360
Comments
Triggered auto assignment to @muttmuure ( |
👋 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:
|
Triggered auto assignment to @carlosmiceli ( |
💬 A slack conversation has been started in #expensify-open-source |
Job added to Upwork: https://www.upwork.com/jobs/~021863284829899625527 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Ollyws ( |
Demoting as it does not block the user from moving ahead |
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: 9.0.69-1
Reproducible in staging?: Y
Reproducible in production?: N
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: Y
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Action Performed:
Expected Result:
Rules feature will be enabled after enabling it and upgrading workspace to Control plan (production behavior).
Actual Result:
Rules feature is not enabled after enabling it and upgrading workspace to Control plan. User has to enable it again.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6681091_1733044347819.ScreenRecording_12-01-2024_17-08-41_1.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @OllywsThe text was updated successfully, but these errors were encountered: