Skip to content

Comments and Activity

Every work item in SetGet has a built-in discussion area where team members can leave comments and view the complete activity history. Comments support rich text formatting, @mentions, threaded replies, and emoji reactions. The activity feed captures every change made to the work item — state transitions, priority updates, assignee changes, and more — providing a complete audit trail.

Adding a comment

  1. Open a work item (via peek view or full detail page).
  2. Scroll to the Comments section at the bottom of the work item.
  3. Click the comment input area.
  4. Type your comment using the rich text editor.
  5. Click Comment or press Ctrl+Enter / Cmd+Enter to submit.

The comment appears immediately and is visible to all project members who have access to the work item.

Rich text comments

The comment editor supports the same formatting capabilities as the page editor, scaled down for comment-sized content:

FeatureHow to use
BoldCtrl+B / Cmd+B or **text**
ItalicCtrl+I / Cmd+I or *text*
Strikethrough~~text~~
Inline code`code` or Ctrl+E / Cmd+E
Code block``` on a new line
Bullet list- at the beginning of a line
Numbered list1. at the beginning of a line
Checklist[] at the beginning of a line
LinkCtrl+K / Cmd+K or [text](url)
Heading# through ### for H1-H3
Block quote> at the beginning of a line
ImagePaste or drag and drop an image into the comment

Pasting content

You can paste formatted text, images, or code snippets directly into the comment editor. The editor preserves the original formatting when possible.

File attachments in comments

Drag and drop a file into the comment editor or click the attachment icon to upload a file. Supported file types include images, PDFs, documents, and archives. Files are stored in the instance storage and linked in the comment.

@Mentions

Tag team members in comments to notify them and draw their attention to the discussion.

How to mention someone

  1. Type @ in the comment editor.
  2. A dropdown appears with a list of project members.
  3. Start typing the member's name to filter the list.
  4. Click the member's name or press Enter to insert the mention.

The mentioned member's name appears as a highlighted link in the comment.

Mention notifications

When you @mention someone:

  • They receive an in-app notification in the Notification Center.
  • They receive an email notification if their preferences include email for mentions.
  • The notification links directly to the comment.

Mentioning groups

You can also mention:

MentionWho is notified
@member-nameThe specific member
@assigneesAll current assignees of the work item

Threaded replies

Comments support threaded replies for focused discussions that do not clutter the main comment stream.

Replying to a comment

  1. Hover over the comment you want to reply to.
  2. Click the Reply button.
  3. A reply input appears below the comment.
  4. Type your reply and submit.

Replies are nested under the parent comment and displayed in chronological order. Each reply shows the author, timestamp, and supports the same rich text formatting as top-level comments.

Thread behavior

AspectDetail
Nesting depthOne level — replies cannot have sub-replies
Thread collapseThreads with many replies can be collapsed to save space
Thread participantsAll members who have replied to a thread are notified of new replies
NavigationClick "View thread" to expand a collapsed thread

Editing comments

You can edit your own comments after posting:

  1. Hover over your comment.
  2. Click the ... menu.
  3. Select Edit.
  4. The comment content becomes editable.
  5. Make your changes and click Save.

Edited comments display an "(edited)" label with the edit timestamp. The original content is not preserved — only the latest version is shown.

TIP

Edit comments promptly after posting if you notice a mistake. Frequent edits after others have replied can be confusing.

Deleting comments

  1. Hover over your comment.
  2. Click the ... menu.
  3. Select Delete.
  4. Confirm the deletion.

Who can delete

RoleCan delete own commentsCan delete others' comments
Comment authorYesNo
Project adminYesYes
Workspace adminYesYes

WARNING

Deleting a comment is permanent. Replies to a deleted comment remain visible, but the parent comment is replaced with a "[deleted]" placeholder.

Reactions on comments

React to comments with emoji to express agreement, acknowledgment, or feedback without adding a new comment.

  1. Hover over a comment.
  2. Click the emoji icon (smiley face).
  3. Select an emoji from the picker.
  4. Your reaction appears below the comment.

If others have already reacted with the same emoji, the count increments. Click your own reaction again to remove it. See Reactions for the full guide.

Activity feed

The activity feed is a chronological log of every change made to the work item. It appears alongside comments in the work item detail view.

What the activity feed tracks

EventExample
State change"Changed state from Backlog to In Progress"
Priority change"Changed priority from Medium to High"
Assignee change"Added Alice as assignee" / "Removed Bob as assignee"
Label change"Added label 'bug'" / "Removed label 'enhancement'"
Due date change"Set due date to March 30, 2026"
Start date change"Set start date to March 15, 2026"
Estimate change"Changed estimate from 3 to 5"
Cycle change"Added to Sprint 4" / "Removed from Sprint 3"
Module change"Added to Auth Module"
Title change"Changed title from 'Old title' to 'New title'"
Relation added"Linked as blocking WEB-42"
Relation removed"Removed link to WEB-42"
Attachment added"Added attachment: design-v2.png"
Archive/unarchive"Archived this work item"

Activity feed display

Each activity entry shows:

  • Who made the change (author avatar and name)
  • What changed (property name and old/new values)
  • When it happened (timestamp, with relative and absolute time on hover)

Filtering the feed

You can toggle between three views in the discussion area:

ViewShows
AllComments and activity entries interleaved chronologically
CommentsOnly comments and replies
ActivityOnly property change events

This lets you focus on the discussion or the change history depending on your needs.

Comment notifications

Comments generate notifications according to the following rules:

EventWho is notified
New commentAll subscribers of the work item
Reply to a threadAll thread participants
@mentionThe mentioned member
ReactionThe comment author (if enabled in preferences)

The commenter is auto-subscribed to the work item when they post. Assignees are subscribed by default. Other members can manually subscribe. See Notification Preferences for control over what generates notifications.

Comment permissions

ActionWho can
View commentsAll members with access to the work item
Add a commentAll members with access to the work item
Edit a commentThe comment author
Delete a commentThe comment author, project admin, workspace admin
Add a reactionAll members with access to the work item
Remove a reactionThe member who added it

Keyboard shortcuts for comments

ShortcutAction
Ctrl+Enter / Cmd+EnterSubmit comment or reply
Ctrl+B / Cmd+BBold selected text in the comment editor
Ctrl+I / Cmd+IItalic selected text
Ctrl+K / Cmd+KInsert link
Ctrl+E / Cmd+EInline code
EscCancel editing or close reply box

Best practices

  • Use @mentions deliberately — mention people when you need their specific input. Avoid mentioning large groups for routine updates.
  • Use threaded replies — keep conversations organized by replying in threads rather than posting separate top-level comments.
  • Use reactions for simple acknowledgment — a thumbs-up reaction is often more efficient than a "sounds good" comment.
  • Write actionable comments — state what you need, what decision is pending, or what the next step should be. Avoid ambiguous comments.
  • Check the activity feed — before asking "what changed?", check the activity feed for a complete history.
  • Format code and technical content — use code blocks and inline code formatting to make technical comments readable.
  • Pin important decisions — when a comment thread reaches a decision, summarize it in the work item description so future readers do not have to scan the entire comment history.
  • Keep comments professional — comments are part of the project record. Write clearly and constructively.