-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Features behind a paywall are accessible after downgrading #54506
Comments
Triggered auto assignment to @techievivek ( |
Triggered auto assignment to @sonialiap ( |
💬 A slack conversation has been started in #expensify-open-source |
👋 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:
|
It similars to this issue. We need to update from BE side |
Looking into this and similar issues now. |
The issue for this lies in the back-end, not the front-end, applying the relevant labels |
PR for this has been merged. |
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.78-1
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: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Windows 11 pro/chrome
App Component: Workspace Settings
Action Performed:
Expected Result:
Company cards gets inaccessible
Actual Result:
Company cards page is accessible after downgrading
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6701575_1735004097691.bandicam_2024-12-24_04-28-28-017.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: