Repository navigation
[Due for payment 2025-10-01] [Due for payment 2025-09-04] LHN - #admins and workspace chat still show GBR after workspace is deleted #69052
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: 9.1.98-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: #68038
Email or phone of affected tester (no customers): sdjoinsdjdosjdos@gmail.com
Issue reported by: Applause Internal Team
Device used: Mac 15.5 / Chrome
App Component: Left Hand Navigation (LHN)
Action Performed:
- Go to staging.new.expensify.com
- Log in with a new Gmail acount.
- Create a workspace.
- Go to workspace chat.
- Create an expense in workspace chat.
- Delete the workspace.
- Go back to Inbox.
Expected Result:
#admins and workspace chat will not show GBR after workspace is deleted.
Actual Result:
#admins and workspace chat show GBR after workspace is deleted.
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 Aug 22, 2025
Triggered auto assignment to @adelekennedy (
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.github-actions commentedon Aug 22, 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:
melvin-bot commentedon Aug 22, 2025
Triggered auto assignment to @mountiny (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Aug 22, 2025
💬 A slack conversation has been started in #expensify-open-source
mountiny commentedon Aug 23, 2025
That Pr did not fix the issue
mountiny commentedon Aug 23, 2025
I can repro in staging and not in production ✅
mountiny commentedon Aug 23, 2025
@BlameGPT Any suggestions what PR could be causing this blocker?
18 remaining items
melvin-bot commentedon Sep 4, 2025
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO.
melvin-bot commentedon Sep 23, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Sep 24, 2025
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
[-][Due for payment 2025-09-04] LHN - #admins and workspace chat still show GBR after workspace is deleted[/-][+][Due for payment 2025-10-01] [Due for payment 2025-09-04] LHN - #admins and workspace chat still show GBR after workspace is deleted[/+]melvin-bot commentedon Sep 24, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 24, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.17-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-10-01. 🎊
melvin-bot commentedon Sep 24, 2025
@mountiny 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]