All guides

Posts & blocks

Discuss inside a thread, react to posts, give kudos, flag concerns and keep the conversation next to the work.

What it does

Every thread has a conversation made up of posts. You write a post, teammates reply, and everyone can react. Posts keep the discussion in the same place as the task, so there's no separate chat app to check.

A post is a collection of blocks β€” each block is a piece of content with its own shape (text, heading, code, quote, checklist, divider or file). One post can mix shapes: a heading, then some text, then a code block and a checklist. Your first block is whatever you typed in the composer; you can then add more blocks to the same post.

Add a block to a post

  1. Under a post you can edit, click Add block.
  2. Pick the block's shape (Text, Heading, Code, Quote, Checklist, Divider or File).
  3. Type the content (a Divider needs none; a Checklist takes [ ] one item per line), then click Add. The new block appears at the end of the post.
Ticking a checklist item updates that block. Everything you write across a post's blocks is also kept as the post's plain-text summary, so search, mentions and notifications keep working.

Work with a single block

Hover a block (on a post you can edit) to reveal its actions:

  • React β€” click πŸ‘ to react to that specific block; the count shows beneath it. (Anyone with access can react; you don't have to be the author.)
  • Convert β€” for a text-style block (Text, Heading, Code, Quote) a small type button lets you change its shape.
  • Move up / down β€” reorder the block within the post.
  • Move to another thread β€” sends just that block to another thread as a new post, leaving a note in this thread linking to where it went (and a back-reference in the destination). Only available when the post has more than one block β€” to move a single-block post, move the whole post.
  • Delete β€” remove the block (a post always keeps at least one block).
Posts no longer have a single "type" β€” each block carries its own shape, so one post can freely mix text, headings, code, checklists and more.

Attach artefacts (commits & test runs)

Below the conversation, the Artefacts panel records the concrete outputs of the work on a thread:

  1. Click Add and choose Code commit or Test execution.
  2. Give it a title, an optional commit/branch or test reference, and a link (e.g. to the commit or CI run). A test execution also takes an outcome (Pass / Fail / Skipped).
  3. Click Add artefact. It appears in the list with its reference, outcome (colour-coded) and an open link; hover to remove it.
Time logged on the thread is its own kind of artefact β€” see the time-tracking guide.

Where to find it

Open any thread (/dashboard/threads/<id>) and scroll to the Conversation section.

Step by step

Write a post

  1. Open a thread and find the composer at the bottom of the conversation.
  2. Type your message. To mention a teammate, type @ and start their name β€” a list of people pops up.

Use the arrow keys (or your mouse) and press Enter/Tab to insert the mention; they'll get an Update. The same @ menu also lists tasks (threads) β€” type a task's reference (e.g. PLAT-12) or title to drop a link to that task straight into your post. The task's assignee gets an Update that their task was referenced. It also lists workspaces and projects β€” type the name to drop a link to that workspace or project into your post (handy for pointing someone at where the work lives). You can only mention things you can see: private-workspace tasks, workspaces and projects you're not in won't appear in the menu. You can also mention a date β€” type @ then today, tomorrow, yesterday, a weekday name (e.g. @friday for the next Friday), or a date like @2026-06-15, and pick it to drop a tidy date label into your post (e.g. "15 Jun 2026").

  1. Use the composer footer to pick the block type, review/log thread time, set whether the post should clear after

a while, then click Post or press ⌘/Ctrl + Enter.

Tip β€” what gets a notification: mentioning a person notifies them, and mentioning a task notifies that task's assignee. Workspace, project and date mentions are labels/links only β€” they don't notify anyone, so use them freely to add context.

Choose a block type

Pick what kind of post to write β€” two ways:

  • Slash menu: type / at the start of the composer to open a menu of block types; keep typing to

filter (e.g. /code), use the arrow keys and Enter to choose. Fast and keyboard-only.

  • Block picker: or click the block-type button in the composer footer.

The block types are:

  • Text β€” a normal message (the default), with mentions.
  • Checklist β€” one item per line; each becomes a tickable box. Tick items off as you go (anyone who can

edit the post can tick them). Great for turning a discussion into trackable tasks.

  • Heading β€” a bold section title.
  • Code β€” a monospaced block that preserves spacing β€” paste snippets or logs here.
  • Quote β€” an indented quotation with a coloured rule.
  • Divider β€” a horizontal line to break up a long thread (no text needed).

Reply to a post

  1. Under any post, click Reply. An inline composer opens beneath it.
  2. Write your reply (you can @-mention people here too) and click Reply.
  3. Replies appear indented under the post they answer, forming a chain. The author of the post you

replied to gets an Update.

  1. Each reply shows a small "in reply to <name>" link β€” click it to jump straight up to the post it answers,

which briefly highlights so you can find it in a long conversation.

Move a post to another thread

  1. Click Move on a post (your own, or any if you're an owner/admin).
  2. Choose a destination thread β€” the picker lists threads from every project, grouped by project β€” and

click Move.

  1. The post moves over and leaves a trail both ways: a note in the original thread β€” _"moved a post to

MOB-7" β€” and one in the **destination** β€” "moved a post here from PLAT-2"_. The thread reference in each note is a link, so you can click straight through to where the post went (or came from).

Pin an important post

  1. Click Pin on a post to keep it at the top of the thread; a Pinned marker appears next to the author.
  2. Click Unpin to release it. You can pin your own posts; owners and admins can pin any post.

Filter the conversation

  • The Conversation header has filter chips for All posts, Pinned, Checklist and Disappearing.

Use them to narrow a long thread to the posts that matter for the task you're doing.

Edit or delete your post

  1. On a post you wrote, click Edit to change it inline (mentions work here too); click Save.

An (edited) marker appears next to the timestamp.

  1. Click Delete, then confirm, to remove a post. If the post had replies, they aren't lost β€” they move up

to sit under whatever the deleted post was replying to, so the conversation stays intact. (The one exception: you can't delete the opening post of a thread while it still has replies β€” remove or move those first.)

  1. You can edit your own posts for as long as the team's edit window allows (set in Settings; the

default is 15 minutes). Owners and admins can edit or delete any post at any time.

Change a block's type (convert)

  • While editing a text-style block (Text, Heading, Code or Quote), a Type row appears above the Save

button β€” click another type to convert the post (for example, turn a plain message into a Heading). The text you wrote is kept; only how it's displayed changes.

  • Checklists and dividers can't be converted (their content works differently), so the Type row doesn't appear

for them.

Reorder blocks (move up / down)

  • On a post you can edit, the β–² / β–Ό buttons in its action row move that block up or down in the thread,

so you can arrange blocks into the order you want rather than strict chronological order.

  • Pinned posts always stay at the top, so a block moves only among others in the same group (a button is

greyed out when the block is already at the top or bottom of its group).

Make a post disappear after a while

  • In the composer, the ⏳ Clear after dropdown (next to the Post button) lets you mark a post to

auto-clear: choose 1h, 24h or 7d, or leave it on Keep for a normal permanent post.

  • While the post is still live it shows an amber "clears <when>" badge by the author name, so everyone

knows it's temporary. Once the time is up, the post quietly disappears from the conversation.

  • Change your mind later? On a post you can edit, the ⏳ Timer dropdown in its action row lets you

change the expiry at any time β€” pick Keep permanently to stop it disappearing, or set a fresh 1h / 24h / 7d window (counted from now, so you can give a soon-to-vanish note more time). The opening post of a thread never disappears, so it has no Timer control.

  • A disappearing post is kept (it won't vanish) if it earns its place β€” if it's pinned, tagged,

reacted to (πŸ‘ / kudos / flag), has a reply, or is the opening post of the thread. So anything the team engages with sticks around; only ignored, time-boxed notes clear themselves.

  • Use it for "heads-up, I'm restarting the server in 10 minutes" style messages that don't need to clutter the

thread forever.

  • Owners/admins can clear them out for good. When a post's timer runs out it's hidden from the conversation

but the row still sits in the database. On Settings β†’ Team β†’ Maintenance, the Purge expired posts button permanently deletes every expired post that nobody kept (the same keep rules above), in one go. It's a tidy-up, not a requirement β€” the hidden posts never show up anyway. Permanent posts are never affected.

React, give kudos or flag

  • Under any post, click:
  • πŸ‘ to react,
  • Award to give kudos for great work,
  • Flag to raise a concern about a risky practice.
  • Click again to remove your reaction. Kudos and flags notify the post's author.
  • Add-reaction, reply, log-time, pin and more controls appear in the top-right hover toolbar. Reaction and

post-time chips stay visible only when that post has saved metadata.

Log time on a post

  • Hover a post and click the ⏱ Timer (Log time) button β€” or open β‹― More actions β†’ Log time… β€” to open the

Post time popover. Type the minutes and an optional note, then click Add (or press Enter).

  • The popover lists each entry on that post (who, when, how long). Remove your own with the bin icon; owners and

admins can remove anyone's. Once a post has time, a ⏱ time chip under it shows the total and reopens the popover.

  • Post time rolls up into the thread total, so it also appears on the Time page and in Reports. See the

time-tracking guide for the full flow.

What each screen shows

  • Conversation β€” each post shows the author's avatar and name, a relative timestamp, the message, persistent

reaction/time metadata and top-right hover actions. Replies nest underneath their parent with a left rule.

  • Composer β€” a text box with block, time, disappearing-post and post controls in the footer; the inline reply

composer is smaller and attached to a specific post.

Tips

  • Kudos are a quick way to recognise good work and keep momentum visible.
  • Flags are for surfacing concerns early β€” they're tracked separately from ordinary reactions.
  • A disappearing post is great for transient notices β€” and if it turns out to matter, just **pin, tag or

react** to it and it stays. Reacting to a teammate's clearing post is the quickest way to keep it.

Troubleshooting

  • My mention didn't notify anyone β€” pick the person from the @ pop-up so the mention is inserted correctly; plain typed @Name text won't trigger a notification.
  • No Edit button on my post β€” the team's edit window may have passed. Ask an owner/admin to make the change, or to widen the window in Settings.

Related guides