Overview

Comments let your team discuss work in context. A comment thread attaches to a specific item, so the conversation lives next to the thing it's about. Supported item types are test, endpoint, project, test run, requirement, and workflow. This guide walks the Comments panel exactly as it appears in the app. Explore the capability at comments.

Availability: Professional and Enterprise.

Before you begin

You need the comment_view permission to read a thread and comment_create to post or edit. Deleting anyone else's comment needs comment_delete.
Access follows project membership: to comment on an item in a project, you must be able to reach that project (administrator, project owner, collaborator, or member). Otherwise the panel returns a no-access error.
The Comments panel appears on supported items; it's headed Comments with the subtitle "Discuss this [item] with your team."

Step 1 — Post a comment

Open the Comments panel on a supported item. Existing comments load oldest-first; an empty thread shows "No comments yet."
Type your message in the Write a comment… box (a comment can be up to 5,000 characters).
Click Post. The button is disabled until the box has text and reads while sending. Your comment appears at the bottom of the thread.

Each comment shows its author (name, or email as a fallback) and a timestamp.

Step 2 — Edit a comment

Only the comment's author can edit it. After an edit, the comment carries an (edited) marker next to its timestamp so the change is visible to everyone. (Editing requires the comment_create permission and only works on your own comments — others get a "not author" error.)

Step 3 — Delete a comment

Click the trash icon on a comment to remove it. You can delete a comment if you are its author, or if you hold the comment_delete permission (which lets you remove anyone's comment). Deletion is a soft-delete — the comment is removed from the thread. Users who are neither the author nor hold comment_delete get a "not authorized" error.

Step 4 — Mention a teammate

Use @mentions in a comment to notify specific teammates. Mentions are resolved to users (by id or email) and emitted as a comment.mention activity event, so they surface through:

the live activity feed, and
outbound webhooks (if enabled),

letting mentioned people follow up even if they aren't looking at the thread.

Troubleshooting / Notes

Comments panel returns a no-access error — you're not a member of the item's project. Access follows project membership (admin / owner / collaborator / member).
Can't edit a comment — only the author can edit; there's no override permission for editing.
Post fails on a long comment — the body limit is 5,000 characters; shorten it.
Comments unavailable entirely — the feature is Professional/Enterprise and can be disabled at the deployment level; if it's off, the panel isn't served.
Mentions didn't reach someone — confirm the mentioned identifier matches a real user (id or email) and, for webhook delivery, that outbound webhooks are enabled.