Done

Ticket-view modal shows comments as raw plain text — Markdown (headings, links, images, tables) is not rendered

From Pedro FigueiraDone 1 day ago

What happens

In the ticket-view modal (the ticket detail / "Editar tarefa" panel), the comment thread is rendered as raw plain text. Markdown written in a comment is shown verbatim: ## Heading appears with the literal hashes, [label](url) is not a clickable link, ![alt](url) images never load, fenced code blocks are not monospaced, and tables render as pipe characters instead of a grid. Lists, bold/italic, inline code and blockquotes are all shown as their source characters.

Impact on real use

Agents and humans routinely write structured comments — a reviewer pastes a diff, an RCA links to a PR or a log line, a handoff lists steps as a numbered list or a table. All of it arrives as an unreadable wall of symbols. Long links are not clickable, so the reader copies the raw URL by hand; a screenshot or diagram referenced with image syntax is invisible. The richer the comment, the worse it reads — which punishes exactly the well-structured comments the workflow depends on.

Scope note

This is about the comment thread specifically. The expectation is the Markdown rendering already applied to the ticket description, extended to comments: headings, links, images, tables, code blocks, lists, emphasis and blockquotes.

AgentsRoom diagnostics

App version: 1.222.0
OS: linux 7.0.0-38-generic (x64)
Agent CLI: claude
App language: system

Problem to solve

Comments in the ticket-view modal are rendered as raw plain text. Markdown source is shown verbatim — headings keep their "##", link and image syntax is inert, fenced code is not monospaced, tables show as pipes. Well-structured comments (reviewer diffs, RCA links, handoff step lists/tables) become an unreadable wall of symbols, and long URLs cannot be clicked.

Proposed behavior

Render each comment body as Markdown in the modal, matching the renderer already used for the ticket description: headings, bold/italic, inline and fenced code, ordered/unordered lists, blockquotes, clickable links, images and GFM tables. Sanitize the HTML output (no raw script/iframe) and keep bare URLs auto-linked. Ideally reuse the same component so description and comments stay visually consistent.

Who benefits

Everyone who reads ticket comments in the modal — human users and agents, on any project — especially teams whose agents post structured comments: code reviews with diffs, RCAs with links to PRs/logs, and cross-role handoffs written as step lists or tables.

Acceptance criteria

A comment written in Markdown displays formatted: headings as headings, links clickable, images shown, tables as a grid, code in monospace. Reading a structured comment no longer requires mentally parsing raw symbols, and referenced links and images are usable directly from the modal.

Replies

The team1 day ago

This will be available in the next version. Ticket comments were displayed as plain text, while the ticket description already used Markdown. Comments now use the same rendering as the description: headings, lists, bold and italic, clickable links (including bare URLs), images, tables and monospaced code blocks. This applies to both the conversation with the reporter and the private comments, on desktop and in the mobile app (on mobile, images in a comment's text are not shown yet; attachments still are). If this is not what you had in mind, tell us and we will adjust it.