Comments and Threads
Use Issue comments, replies, reactions, resolved threads, deleted placeholders, and history.
Issue comments are for discussion directly attached to an Issue. They stay with the Issue history and remain separate from external planning comments in Linear or Notion.
Add a comment
Use the composer at the top of Issue Activity. Comments support rich text and mentions of people who can access the Issue, plus readable Issues, Features and Initiatives. A mentioned private item appears as Restricted item to readers without access.
Submitting a comment waits for the server write before the composer clears. If the write fails, Integrity keeps the draft in place and shows an error toast.
File attachments are not active for Issue comments in this release.
Who can comment
Public Teams default to Anyone with Issue access. The alternative is Team members and the original reporter, which is the default for private Teams. Authorized Team settings managers can change this in Access and permissions. All commenters need current Issue access and an active Issue. The original reporter can continue after triage while they retain access.
Reporter access
When an outside reporter cannot read a private Issue, authorized share managers see Share with reporter beneath the header. This shares only that Issue; it does not reveal the private Team or its other Issues. Dismiss for everyone hides the notice for the current reporter and Team context without changing access. Revoking a reporter's share removes their access and does not immediately bring the notice back. Reporting or mentioning an Issue never shares it automatically.
Reply to a thread
Reply below a top-level comment to keep discussion grouped. Thread replies can mention users, participate in thread notification rules, and remain visible when the parent comment is deleted.
Thread subscriptions are separate from Issue subscriptions. Following a thread does not automatically follow every Issue update.
Resolve and reopen
Use resolve when a thread no longer needs attention. Resolved threads collapse visually but remain part of the Activity history. Reopen the thread when discussion needs to continue.
Resolve and reopen actions write thread history. They do not create separate top-level Issue activity rows.
Edit, delete, restore, and view history
Authors can edit or delete their own comments. Authorized moderators can delete or restore comments when the Issue policy allows it.
Deleted parent comments show a lightweight tombstone so child replies remain readable. Comment history preserves edit/delete/restore and thread state evidence.
Reactions
Reactions update in realtime but do not create Activity rows, Inbox notifications, or email.