When a Slack-rooted conversation continues in the dashboard, Slack gets no signal until someone posts in the thread again.
Current behavior
Dashboard turns stay conversation-log only (publishExternally: false).
Later Slack turns can use dashboard history as context and link to the full transcript.
There is no proactive Slack notice when dashboard-only activity lands.
Gap
Thread participants who stay in Slack can miss that the conversation moved forward in the UI.
Full message cross-post is intentionally out of scope (see Start and continue conversations in the dashboard #1200 ).
A short notice with a dashboard link would close the gap without impersonating the author or copying message bodies.
Proposal from product discussion
Post a short Slack notice such as “something was said in the web UI — check the full transcript.”
Include a link to the dashboard conversation.
Do not auto-copy dashboard message bodies or impersonate the author.
Related: #1200 (return-to-Slack path only covers the next Slack turn).
Requested by Pierre Massat .
--
View Junior Session [Sentry]
When a Slack-rooted conversation continues in the dashboard, Slack gets no signal until someone posts in the thread again.
Current behavior
publishExternally: false).Gap
Proposal from product discussion
Related: #1200 (return-to-Slack path only covers the next Slack turn).
Requested by Pierre Massat.
--
View Junior Session [Sentry]