-
Notifications
You must be signed in to change notification settings - Fork 3.2k
[$250] WS Setting - Troubleshoot panel appears beneath the Edit Photo RHP #61949
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
Comments
Triggered auto assignment to @CortneyOfstad ( |
Triggered auto assignment to @cead22 ( |
💬 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:
|
#58608 MIGHT cause this |
Job added to Upwork: https://www.upwork.com/jobs/~021922401729583332126 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @allroundexperts ( |
After reverting #58608, this is no longer reproducible. We can close this issue. |
Thanks |
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.1.45-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: Exp
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Device used: Web, mweb, android
App Component: Workspace Settings
Action Performed:
Expected Result:
The Troubleshoot panel should appear above the Edit Photo RHP
Actual Result:
Troubleshoot panel appears beneath the Edit Photo RHP.
Workaround:
Unknown
Platforms:
Screenshots/Videos
Bug6830129_1747165108400.bandicam_2025-05-13_22-05-06-481.mp4
View all open jobs on GitHub
Upwork Automation - Do Not Edit
Issue Owner
Current Issue Owner: @allroundexpertsThe text was updated successfully, but these errors were encountered: