Comments

Comments keep internal discussion close to the work. Use them when a ticket needs clarification, decisions, or updates that should stay with the ticket.

​

Overview

Ticket comments live on the ticket detail page alongside the ticket description and activity history. Use the description for the durable task summary. Use comments for discussion and updates. The ticket body separates editable ticket content from the comment and activity stream. This lets the current state of the work stay clean while preserving the discussion that led there. Go to Tickets, open a ticket, then use the comment panel.

If a comment changes what needs to happen, update the ticket description or properties too. Otherwise the current task summary can drift from the discussion.

​

Add comments

Comments help teammates collaborate without losing context.

​

Write a comment

Write comments when you need to ask a question, record a decision, or explain a change. Keep comments specific. If a comment changes the actual task, update the ticket description or properties as well.

​

Mention teammates

Mention teammates when they need to review or respond. Mentions are most useful when the teammate is not already the assignee.

​

Add context

Reference linked conversations, related tickets, Linear issues, Jira issues, or company context when it helps the reader. Use quote or reply context when responding to a specific earlier comment or detail.

​

Manage comments

Comment actions depend on permissions and ownership.

​

Edit comments

Edit a comment when you need to correct or clarify what you wrote.

​

React to comments

Use reactions for lightweight acknowledgement.

​

Delete comments

Delete comments when they should no longer appear on the ticket. Deleted comments should not be used as a substitute for correcting the ticket description. If the comment contains outdated instructions, update the durable ticket content too.

​

Activity history

Activity history records changes to the ticket.

​

Status changes

Status activity shows when the ticket moved through the workflow.

​

Assignee changes

Assignee activity shows ownership changes.

​

Label changes

Label activity shows categorization changes.

​

Linked conversation changes

Conversation activity shows when conversations were linked or removed.

​

When to comment vs edit

Use the right surface for the kind of change you are making.

​

Use comments for discussion

Ask questions, record decisions, or explain why a change was made.

​

Use the description for the current task

Update the description when the actual work, requirements, or expected outcome changes.

​

Use properties for routing

Change status, assignee, labels, due date, and links instead of describing those changes only in a comment.