Repository navigation
New chat button is not shown in thread after sending message to Concierge from Help button #105481
Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: 9.5.26-0
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 BrowserStack: #100552
Email or phone of affected tester (no customers): jjsndoijsonjsoidj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Other
Action Performed:
- Go to staging.new.expensify.com
- Go to Concierge.
- Send a message to Concierge.
→ New chat button is shown in thread. - Open Help button on the top right.
- Send a message to Concierge.
Expected Result:
New chat button will be shown in thread after sending message to Concierge from Help button.
Actual Result:
New chat button is not shown in thread after sending message to Concierge from Help button.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7300577_1793362007502.4.mp4
Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7300577
Issue Owner
Current Issue Owner: @rushatgabhaneMetadata
Metadata
Assignees
Type
Projects
- Status
Activity
applause-bot commentedon Oct 30, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/0564450c834d3b04160384e53965b1624976c66e5c54c8d88ec4d649d95d7d23
melvin-bot commentedon Oct 30, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #100552
melvin-bot commentedon Oct 30, 2026
@puneetlath @mkhutornyi you have been assigned to this deploy blocker because you reviewed the offending PR: #100552
github-actions commentedon Oct 30, 2026
👋 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 Oct 30, 2026
@rushatgabhane you have been assigned to this deploy blocker because you authored the offending PR: #100552
melvin-bot commentedon Oct 30, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Oct 30, 2026
Deploy Blocker Analysis
Causing PR: [Payment due @mkhutornyi] Add ask Concierge screen (high confidence). It adds the "New chat" button but hides it in the Help side panel. The same PR also makes Help panel messages open a Concierge thread for all users.
Recommendation: Roll forward with a small fix in
HeaderView.tsx. Revert only if the author can't ship the fix quickly.Suggested fix:
!isInSidePanel &&from HeaderView.tsx:527 and HeaderView.tsx:563.startNewConciergeChatpanel-aware. In the side panel, callopenSidePanel({reportID: conciergeReportID})fromuseSidePanelActions. Elsewhere, keepNavigation.navigate(...). Without this change, the button would change the main screen, not the panel.HeaderViewTestcase for a Concierge thread shown in the side panel.Investigation details
Why Help panel messages now open a thread: The PR removed the
conciergeRespondInThreadbeta. useComposerSubmit.ts:82 is nowreportID === conciergeReportIDwith no beta check. The existing panel branch at lines 103-105 then opens the new thread in the panel. Production still has the beta off for most users, so the issue does not appear there.Why the button is missing: HeaderView.tsx:168 sets
isConciergeThreadto true for the panel thread. Both render conditions (lines 527 and 563) also require!isInSidePanel, so the button never shows in the panel.Review context: A reviewer flagged the side panel during review. The author called it out of scope and said it "works the same as production". Removing the beta changed panel behavior for all users, so that no longer held.
Why not revert: The PR touches about 60 files and depends on a backend change that is already deployed. The fix above changes one file.
Next Steps: Reply with
@MelvinBot implement thisto create a draft PR, or@MelvinBot <your feedback>to refine this analysis.rushatgabhane commentedon Oct 30, 2026
NOT A BUG
puneetlath commentedon Oct 30, 2026
Demoting since we haven't really touched the side panel yet. Though I do think it makes sense to show the new chat button in it.