You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD] Reports - Messages displayed with "Is:pinned" filter, are still shown after chat is unpinned #71161
Version Number: 9.2.17-2 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:#70702 Email or phone of affected tester (no customers):ibellicotest+1844@gmail.com Issue reported by: Applause Internal Team Device used: Motorola MotoG60 / Android 12 / Chrome ( mWeb / Hybrid app) - Windows 11 / Chrome App Component: Search
Action Performed:
Open the Expensify app.
On "Inbox", long tap on any chat with messages, and select "Pin". (For example: Concierge chat)
Navigate to "Reports" > "Chats"
Tap on the "Is" filter and select "Pinned"
Note that all the messages from the pinned chat, correctly appear.
Tap on the link to chat on the "In" row, from any message.
Tap on chat header and select "Unpin"
Return to "Reports" > "Chats" using the back button on the top left corner.
Note that filter is still applied and all the messages from the unpinned chat are still displayed.
Expected Result:
When a chat is unpinned after applying the "Is:pinned" filter, all the messages from chat, should disappear from results list.
Actual Result:
Messages displayed on results list on "Chats" after applying the "Is:pinned" filter, are still shown when the chat is unpinned.
👋 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:
Identify the pull request that introduced this issue and revert it.
Hmm we have this issue in many places, where an action taken in the RHP doesn't update the underlying search. I think we need to solve this in a holistic way
changed the title [-]Reports - Messages displayed with "Is:pinned" filter, are still shown after chat is unpinned[/-][+][HOLD] Reports - Messages displayed with "Is:pinned" filter, are still shown after chat is unpinned[/+]on Sep 25, 2025
Activity
melvin-bot commentedon Sep 24, 2025
Triggered auto assignment to @zanyrenney (
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.melvin-bot commentedon Sep 24, 2025
Triggered auto assignment to @Beamanator (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Sep 24, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Sep 24, 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:
mitarachim commentedon Sep 24, 2025
QA team found issue reproduce in Prod with below steps :
Screen.Recording.2025-09-24.at.14.02.09.mov
4 remaining items
Beamanator commentedon Sep 24, 2025
Thank you sir! I wish you all the best :D
luacmartins commentedon Sep 25, 2025
Hmm we have this issue in many places, where an action taken in the RHP doesn't update the underlying search. I think we need to solve this in a holistic way
luacmartins commentedon Sep 25, 2025
I'm gonna put a hold on this since we're discussing changes to Search that might solve this problem.
[-]Reports - Messages displayed with "Is:pinned" filter, are still shown after chat is unpinned[/-][+][HOLD] Reports - Messages displayed with "Is:pinned" filter, are still shown after chat is unpinned[/+]zanyrenney commentedon Oct 6, 2025
ON HOLD, not adding to project.
zanyrenney commentedon Oct 29, 2025
Still on HOLD. @luacmartins please feel free to change the labels/ ping me in DM if we need to pick this one back up sooner.
luacmartins commentedon Oct 30, 2025
This is not a priority right now. I think we close this since we're aware of the root cause affecting a few other flows.