Issues, rich text, attachments & replies

What does an issue have?

• Type: epic, task, subtask (needs a parent) or bug
• Status, assignee, reporter, story points, sprint, labels and parent
• Links: blocks / blocked by, relates, duplicates and clones — the inverse link is written on the other issue for you
• A rank: its order on the board and in the backlog

Change several fields and save once — that is one new version.

How do I write descriptions and comments?

In a WYSIWYG editor: headings, bold, italic, strikethrough, code, lists, checklists, tables, links, quotes, code blocks (including mermaid) and dividers. Markdown shortcuts work as you type, and images you paste, drop or insert show inline at once while they upload.

Everything is saved as Markdown in the .md file — parts you did not touch are written back byte for byte. Prefer raw Markdown? Open the Markdown tab, or view the whole .md file.

How are attachments handled?

Attach with the button or by dropping files; they upload straight to object storage. Each issue's attachments table shows a thumbnail, name, date added, size and uploader (badged when uploaded over MCP), filters All, Images, Documents, Videos and Other, and offers preview and download.

Storage counts per company, with 10 GB free; see your usage in the admin console.

How do comment replies work?

Press Reply under any comment and the composer opens under its thread. Replies are grouped under the top-level comment (one level deep); a reply to a reply shows whom it answers with a short quote. Threads over 3 replies collapse, and every comment has its own link.

Comments are append-only: they cannot be edited once sent.

When do I get emails?

• When an issue is assigned to you
• When someone comments on an issue you are assigned to or reported
• When someone replies to your comment
• Never about your own actions, and never two emails for one event

Emails carry English and Thai in one message, and say when the change came from an AI agent.