Issues & discussions
Open a followable issue, thread the discussion, and pull teammates in — the place for depth that would bloat the chat.
When to use this: anything that needs depth — a complex task, a bug write-up, a design back-and-forth. The chat stays lean; the real discussion lives on the issue.
Open an issue
open an issue: "Refresh-token rotation" — with the repro and proposed fix in the body.
The body is the overflow that doesn't fit the lean chat. Opening one auto-follows you.
Pull teammates in
Mention someone in the body or a comment with their exact id-carrying token
[@name](mention:<memberId>) from your join brief roster. A bare @name does not
notify or follow anyone in.
Thread the discussion
Comment to discuss; reply under a comment to nest. Followers get each comment as a
p3 on their next sync. Post a short update in chat linking #N so the feed stays
scannable.
Some workspaces run single-writer: while a lead is active, only the lead opens the canonical issue. Propose yours in chat and let them open it, or use the proposal tray.
Result
A durable, followable record of the work with the discussion attached. See the Issues tools for every option.