Skip to content

[Due for payment 2026-07-07] [Due for payment 2026-07-06] Workspace - admins room become pinned only after entering room #94781

Closed

Description

@applause-bot

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: v9.4.21-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/folder/13177080/test-cases/41237924
Email or phone of affected tester (no customers): -
Issue reported by: Applause Internal Team
Bug source: Regression TC Execution
Device used: Windows 11 / Chrome
App Component: Left Hand Navigation (LHN)

Action Performed:

  1. Go to Workspaces tab
  2. Add new workspace
  3. Go to Inbox tab
  4. Click on #admins room

Expected Result:

#admins room pinned after creating workspace (step 3). No need to enter room

Actual Result:

#admins room become pinned (icon appears) and rises on top of the chat list.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7192949_1782574685008.bandicam_2026-06-27_18-31-06-994.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7192949

Activity

  1. applause-bot commented on Jun 28, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/af9d2e0ab36df74a3c52ac0429a040e242ebc77d5af1b1fd0a33222df77c3012

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 28, 2026
  3. melvin-bot commented on Jun 28, 2026

    @melvin-bot

    Triggered auto assignment to @Julesssss (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Jun 28, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. melvin-bot commented on Jun 28, 2026

    @melvin-bot

    📣 @basukusuvo! 📣
    Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
    Please follow these steps:

    1. Make sure you've read and understood the contributing guidelines.
    2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
    3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
    4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
      Screen Shot 2022-11-16 at 4 42 54 PM
      Format:
    Contributor details
    Your Expensify account email: <REPLACE EMAIL HERE>
    Upwork Profile Link: <REPLACE LINK HERE>
    
  6. github-actions commented on Jun 28, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  7. mountiny commented on Jun 29, 2026

    @mountiny
    Contributor

    @emkhalid @linhvovan29546 @lakchote fo visibility, I will revert the offending pr

  8. izarutskaya commented on Jun 29, 2026

    @izarutskaya

    Chrome / v9.4.21-7
    admins room not displayed in LHN after we creation but room appears and pinned when user try to search it

    REC-20260629124156.mp4
    Recording.3827.mp4
  9. added and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jun 29, 2026
  10. changed the title [-]Workspace - admins room become pinned only after entering room[/-] [+][Due for payment 2026-07-06] Workspace - admins room become pinned only after entering room[/+] on Jun 29, 2026
  11. melvin-bot commented on Jun 29, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  12. melvin-bot commented on Jun 29, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.21-9 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 2026-07-06. 🎊

  13. melvin-bot commented on Jun 29, 2026

    @melvin-bot

    @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]. If no checklist is needed for this issue, you can click: [no checklist button]

  14. changed the title [-][Due for payment 2026-07-06] Workspace - admins room become pinned only after entering room[/-] [+][Due for payment 2026-07-07] [Due for payment 2026-07-06] Workspace - admins room become pinned only after entering room[/+] on Jun 30, 2026
  15. melvin-bot commented on Jun 30, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.24-0 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 2026-07-07. 🎊

  16. melvin-bot commented on Jun 30, 2026

    @melvin-bot

    @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]. If no checklist is needed for this issue, you can click: [no checklist button]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions