-
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
[Due for payment 2025-02-18] [Due for payment 2025-02-13] Workspace - Setup specialist appears in member list and throws error when invited #56351
Comments
Triggered auto assignment to @MarioExpensify ( |
Triggered auto assignment to @OfstadC ( |
💬 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:
|
@OfstadC FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors. |
Hey @vincdargento, thanks for opening this issue. I'm gonna investigate if this is BE related or we can get external help and circle back here. @OfstadC if you have any insights please let us know. |
The issue looks to be related with this PR: #55302 This is the commit that first introduced the issue: bb02e14 @ishpaul777 can you help track and fix this? |
oookay! Looking at the deploy checklist looks like we got this fixed. Thank you for your help @ishpaul777. Closing this. |
Whoops, should not have closed this. Waiting for QA retest. But looks good in Staging already! |
We don't see Setup specialist Recording.2840.mp4Recording.2977.mp4 |
Correct. Setup Specialist should not be displayed in invite list (just like in Prod). |
Closing now that QA retested this! |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.94-25 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-02-13. 🎊 |
@MarioExpensify @OfstadC @MarioExpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.0.95-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2025-02-18. 🎊 |
@MarioExpensify @OfstadC @MarioExpensify The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button] |
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.0.94-1
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?: N/A
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): ssdjmosijmosdjos@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.0 / Chrome
App Component: Workspace Settings
Action Performed:
Expected Result:
Actual Result:
Workaround:
Unknown
Platforms:
Screenshots/Videos
bug.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @OfstadCThe text was updated successfully, but these errors were encountered: