Formatting
Comment and reply text supports a small set of rules called Markdown Lite. Four rules, nothing else. Anything that is not one of them is shown exactly as typed, so plain text comments look the same as before.
The Rules
| You type | You get |
|---|---|
| **bold** | bold |
| `code` | code |
| - item (at the start of a line) | A bullet list. Consecutive "- " lines form one list. |
| Enter | A line break. |
Unbalanced markers stay literal: a single * or a lone backtick is just text. Formatting never applies inside a code span.
Writing It
- Select text in the comment box and a small popover offers Bold, Code, and List.
- Keyboard: ⌘B (Ctrl+B) for bold, ⌘E (Ctrl+E) for code, ⌘⇧8 (Ctrl+Shift+8) for a list.
- Type
-at the start of a line to begin a list. Enter continues it with a new-item, and Enter on an empty item ends the list.
Comments are stored as plain text with the markers in place. Nothing is rewritten, so a destination that cannot show formatting still gets the words.
How It Travels
| Destination | What arrives |
|---|---|
| Trello, ClickUp, GitHub, Linear, Discord | The text as written. These tools read the same markers natively. |
| Slack | Converted to Slack formatting (single-asterisk bold, bullet lines). |
| Jira | Converted to Jira's document format (bold, code, bullet list). |
| Asana, Monday | Markers removed, words kept. List items become • lines. |
| Rendered as bold, code, and lists in the notification. | |
| REST API, webhooks, MCP | Raw text with the markers, plus textFormat: "markdown-lite" beside it so your code knows how to read it. |
Titles never carry formatting. Where comment text is used as a title, for example a card name, the markers are stripped.
See the REST API, Webhooks, and AI Agent (MCP) pages for where textFormat appears.