Comments, mentions, and audit trail
Discuss tasks in threads, link to them with #PREFIX-N or a permalink from anywhere, and review every change in the audit log.
Comments
Each task has a comment thread baked into the detail modal. The thread uses Monad's standard messaging machinery, so:
- Mentions —
@user,#space,#PREFIX-N,@here,@channelall work. Mentioning a user notifies them; mentioning a task inside a comment turns into a hover-card chip. - Reactions — react to any reply with an emoji.
- Read cursors — Monad tracks who's caught up on the discussion.
- Resolve — when the discussion is over, an admin or the
thread starter can mark it resolved. Resolved threads don't take
new replies until reopened. Resolving requires the
task:resolve_commentpermission, which is broader than just posting a comment — anyone can comment, but only people with resolution rights can close a thread.
#PREFIX-N task mentions
Type #ENG-12 (or #eng-12 — case is ignored) anywhere in a
message, comment, or canvas document. Monad does two things:
- Inline rewrite. The bare text becomes a link to the task, visible to anyone with read access on it.
- Hover-card. Hover over the chip to see the task's title + status without leaving the page. The popover lazy-loads on open, so messages with hundreds of mentions don't fan out N requests on render.
Because a task can be on several boards, it can be mentioned by any of
its ids — #ENG-12 and #DES-4 for the same task both work, and each
chip keeps whichever id was typed. Old ids that were freed by unsharing a
task from a board still resolve too — links never break.
Task links
Every task has a stable permalink. Open the ⋯ menu in the task
header and choose Copy link to put it on your clipboard. Pasting a
task link anywhere in Monad turns it into a clickable task chip, just
like a #PREFIX-N mention. The link always opens the same task no matter
which board it's currently shown on.
Audit trail
The detail modal's Activity section is a reverse-chronological
log of every change to the task:
- Status flips, priority changes, assignee changes
- Labels added or removed
- Sub-tasks added, removed, or re-parented
- The task shared to or unshared from a board
- Title and description edits — but with a 2-second debounce, so a single typing burst becomes a single audit entry rather than one per keystroke
The audit log is per-task and follows the task wherever it's shared — its full history is in one place regardless of how many boards it's on.
Following a task
Open the ··· menu in the task header and choose Follow to follow a task. Following means you get the task's status and assignment changes in your Activity feed — even if the task isn't assigned to you. Choose Unfollow from the same menu to stop.
You're automatically followed into a task when you:
- get assigned to it,
- create it,
- comment on it, or reply to one of its comments.
So once you've engaged with a task you keep up with it automatically; choose Unfollow if you'd rather not — that sticks, even if you're later assigned again or comment again. You can follow any task you can open, including one shared with you through a board you're on — you don't have to be on the board where it started.
Notifications
You'll get notified when:
- A task is assigned to you.
- The status changes on a task you follow (the assignee follows automatically, unless they've unfollowed it).
- A task you follow is reassigned or unassigned.
- Someone replies to a thread you started or replied to.
- Someone @mentions you in a task comment.
- Someone @mentions you in the task's title or description (mention fan-out runs the same as message mentions).
You're never notified of your own change — you won't get pinged for assigning a task to yourself or moving your own work. These updates show up in your Activity feed alongside mentions and replies, and link straight to the task on a board you can open.
Group @mentions (e.g. @design-team) in a task comment notify the
group. Use them sparingly — they hit every member.
Read access
Anyone who can read the task can read its comment thread. There isn't a separate "comment-only" tier — the gate is the same as reading the task. A task is readable by anyone in a space that hosts one of its boards, so a thread on a sensitive task should live on a board in a sensitive space.
Editing a comment
You can edit your own task comment for 24 hours after posting it. Open the
comment's menu, choose Edit, change the text, and save. The comment shows an
"Edited …" label afterwards, and everyone viewing the task sees the change
live. Adding a new @mention in an edit notifies that person; people already
mentioned aren't pinged again. Viewing earlier versions of a comment isn't
available yet.