Live Jira status at the top of every Slack thread
Every synced ticket gets an anchor — a message at the top of its Slack thread that shows the issue's current state and re-renders in place as the ticket moves, so no one has to ask "is this still in progress?"
Add Threadmaker to Slack — free for up to 10 Jira users.
What the anchor shows
The first time a Jira ticket has activity in a paired channel, Threadmaker posts the anchor — the thread root for everything that follows. The default format:
WEB-1234 — Add export to PDF
Type: Story · Status: In Progress · Priority: High · Assignee: AliceWhen issue type, status, priority, summary, or assignee change in Jira, the anchor updates in place to reflect the new value — the thread title in Slack always shows the current state. Updates edit the existing message silently; they don't fire new notifications.
The per-project toggle
Live updates can be switched off in Project settings → Apps → Threadmaker → Sync anchor on Jira field changes (default ON). When off, the anchor posts once at thread creation and never updates — useful if your team prefers immutable thread roots.
Customising the anchor template
The anchor format is a configurable template with a live preview in the settings page. The most-used variables:
{{issue.key}},{{issue.summary}},{{issue.url}}{{issue.status}},{{issue.type}},{{issue.priority}},{{issue.assignee}},{{issue.reporter}}{{issue.labels}},{{issue.components}},{{issue.fixVersions}}, plus project and channel variables- …and admin-defined custom-field aliases
(
{{issue.<alias>}}, up to 20 per project)
{{tm.anchor}} is optional and renders nothing — the anchor is
tracked invisibly via Slack message metadata, so you no longer need to place it
in the template.
FAQ
Can I stop the anchor from changing? Yes — turn off "Sync anchor on Jira field changes." The anchor then posts once and stays put.
Which fields trigger a re-render? Issue type, status, priority, summary, and assignee.
Related
Full reference in the setup guide. See also edits and deletes, attachments, and @-mention mapping — or read the incident-response playbook, where the live anchor tracks the war room. Back to all features.
Ready to try it?