Comments and mentions
Every task in Orsane has its own comment thread for discussion, decisions, and the back-and-forth that happens around the work. Comments — together with @mentions and the rich-text task description — are how teammates collaborate inside a task.
Where the thread lives
Section titled “Where the thread lives”Open any task to see its detail panel. The panel has tabs for Description, Activity, and (when there are subtasks) Subtasks. Comments live under the Activity tab, interleaved with the task’s update history (status changes, assignment changes, etc.) so the timeline reads as a single conversation.
The Activity tab of a task detail panel showing two or three comments interleaved with at least one task-update entry (e.g. a status change), to illustrate the unified timeline.
Writing a comment
Section titled “Writing a comment”The comment editor supports rich text. You can:
- Make text bold, italic, or
strikethrough - Create bulleted or numbered lists
- Insert emoji
Headings, code blocks, and blockquotes are intentionally not available in comments — they’re meant for short, conversational messages, not documents. (For longer-form content, use the task Description — see below.)
Attaching files and images
Section titled “Attaching files and images”Drag any file onto the comment editor, or paste an image from your clipboard, and it uploads inline. Each file can be up to 10 MB. Images render in the comment thread; other file types appear as downloadable links.
@mentions
Section titled “@mentions”Type @ in a comment (or in the task description) to start a mention.
Orsane suggests workspace members matching what you’ve typed; pick one
with Enter or by clicking. Mentions are limited to members of the
current workspace — you can’t @ a teammate from a different workspace.
The comment editor mid-mention: an @ typed followed by a few characters, with the typeahead dropdown showing matching workspace members.
Mentions are how Orsane knows to notify someone:
- Mentioning someone in a comment sends them a Comment mention notification.
- Mentioning someone in a description sends them a Description mention notification.
Both arrive in the Inbox and trigger the usual email-after-a-short-delay rule.
Replies
Section titled “Replies”Posting a comment on a task that already has comments automatically notifies the previous commenters with a Comment reply notification — no explicit “reply” action needed. That keeps everyone who has been involved in the conversation in the loop.
There aren’t separate threaded reply chains; the discussion is flat per task.
Description vs comments
Section titled “Description vs comments”Tasks have a separate rich-text Description field that’s distinct from the comment thread. Use it for the persistent context of the task — the brief, the spec, the acceptance criteria — and use comments for the unfolding conversation.
The description editor has the same toolbar as comments, plus headings and the ability to grow into a longer document. It also supports @mentions, which trigger their own notification type so people aren’t confused about whether they’re being pinged in the brief or in a chat message.
Editing comments
Section titled “Editing comments”Once posted, comments are immutable — there’s no edit or delete action. If you need to retract or correct something, post a follow-up comment. This is intentional: it keeps the activity timeline accurate.