A report has two places to talk: the Internal discussion card, which is about the report as a
whole, and a thread on each individual pin, which is about one spot on the screenshot. Both are
internal to your account.
On the report page, every numbered pin on the screenshot carries its own
thread. Open a pin, read its note, and reply underneath it, with @ mentions exactly as in the main
thread. You can edit and delete your own replies, and mark the pin done when that specific point
is settled.
This is the difference between “the page is broken” and “these four things are wrong, and two of them
are now fixed”. The main thread stays for the decision about the report; the pin threads hold the
argument about each spot.
Posting a comment notifies two groups, and never the same person twice:
The people you mentioned get a mention notification.
Everyone who can reach the report’s project gets a comment notification — the whole project
team, plus the report’s assignee and anyone who has commented before even if they are not on the
project. Anyone you just mentioned is excluded from this second wave, so a mention never arrives
twice.
That width is deliberate: a comment on an unassigned report nobody has touched yet has to reach the
team rather than nobody. But it does mean a plain comment is a wide notification, not a quiet
one. “The project team” is every account admin, everyone whose role carries “open every project in
this space”, and everyone attached to this project — however far the
thread is from their own work. Each person controls their own share of it: the Comment row in
notification preferences turns the type off for email, for the
bell, or for both, and the Muted projects section on the same page silences one project for you
alone without touching how anyone else is notified.
Both notifications land in-app, in the bell, and that is never plan-gated: you must always be able
to see what happened to your own reports. Email follows each member’s own
notification preferences and needs a plan that includes email
notifications — Starter and up. On Free none of these is ever emailed; the bell is the only
delivery.
A team channel is a mention-only road. mentioned is one of the events a
channel can subscribe to; comment is not on that list at all, so a
plain comment can never reach Slack, Telegram, Microsoft Teams or a webhook, however the project is
routed. Which channel kinds you can connect is its own plan question: Free has webhook only, Slack
and Telegram start at Starter, and Microsoft Teams at Professional.
The thread’s job is to record the mention reliably so that nothing is dropped or duplicated.
Edit: change the body; the comment is marked edited. If your edit adds new mentions, only the
newly added people are notified; anyone already mentioned is never re-notified, and removing a
mention notifies nobody.
Delete: a soft delete. The comment collapses to one faint Comment removed line with its
author and time, so the shape of the conversation survives without exposing what was said.
Only mention someone when you need their eyes or their hands: of the two, only a mention
can reach a team channel. Do not reach for a plain comment as the quiet alternative — it
stays in email and the bell, but it goes to the whole project team rather than to one
person.
Put the argument on the pin
If it is about one spot on the page, reply on that pin and resolve it there. The report thread
stays readable, and “what is left” becomes countable.
Write for the next triager
Record what you found and what you decided. Whoever opens this report next should inherit your
context instead of re-deriving it.
Edit to correct, delete to retract
Fix a typo with an edit; pull a comment you should not have posted with delete. The thread
stays honest either way: edits are marked and deletions leave a tombstone.