# Threadmaker > Two-way comment sync between Jira and Slack. Every ticket gets one Slack thread — edits, attachments, and @mentions stay intact. Free for 10 users. Threadmaker is a two-way Jira ↔ Slack comment-sync app. It bridges each Jira issue to a single Slack thread and keeps the comment conversation in sync both ways: a Slack reply becomes a Jira comment and a Jira comment becomes a Slack reply, carrying comment edits, deletions, file attachments, inline images, and @mention mapping in both directions. On top of the comment sync, Slack emoji reactions can post a note to Jira (off by default, Slack-to-Jira only), and a live status anchor at the top of the Slack thread re-renders the issue type, status, priority and assignee as they change. It works across Jira Software, Jira Work Management (Business), and Jira Service Management, and can create Jira issues from Slack with the /jira-create command. It is a comment-and-conversation bridge, not a bidirectional field-level record-sync tool: it does not map issue fields, custom fields or workflow state between systems the way a general integration platform does. (Jira status is surfaced read-only in the Slack thread via the live status anchor above; it is not written back.) The Slack app is free forever; the Jira side is billed per Jira user through the Atlassian Marketplace, with a free tier for up to 10 Jira users. ## Documentation - [Threadmaker Docs — Set Up Jira & Slack Comment Sync](https://threadmaker.dev/docs): Install and configure Threadmaker: map a Slack channel to a Jira project, sync comments both ways, forward messages, and create issues with /jira-create. - [Jira–Slack attachment and image sync — Threadmaker](https://threadmaker.dev/docs/attachments): Sync file attachments both ways between Jira and Slack (up to 3.5 MB per file, any type) and render screenshots inline in the Jira comment body. - [Jira–Slack @mention mapping — Threadmaker](https://threadmaker.dev/docs/mentions): Map @mentions between Jira and Slack: an @mention becomes a real ping when the two accounts share an email, with a readable name fallback otherwise. - [Edit and delete sync — Jira and Slack — Threadmaker](https://threadmaker.dev/docs/edits): Edit and delete comments sync both ways between Jira and Slack — fix a typo or remove a comment on either side and the other updates within seconds. - [Live Jira status in your Slack thread — Threadmaker](https://threadmaker.dev/docs/live-status): Threadmaker posts a live anchor atop each Slack thread — issue type, status, priority, summary and assignee re-render as they change in Jira. - [Set up Jira–Slack comment sync in 5 steps — Threadmaker](https://threadmaker.dev/setup): Step-by-step Threadmaker setup: grab your Slack token, connect Jira, map a channel to a project, enable per-project sync, and tune it — with screenshots. ## Comparisons - [Jira Cloud for Slack alternative — Threadmaker](https://threadmaker.dev/vs/jira-cloud-for-slack): Threadmaker vs Jira Cloud for Slack: two-way comment sync in every project — Software, Business, JSM — plus edits, attachments and inline images. - [Unito alternative — Threadmaker](https://threadmaker.dev/vs/unito): A Unito alternative built for Jira and Slack: one Slack thread per ticket, two-way comments with edits, attachments and inline images — not record sync. - [ClearFeed alternative — Threadmaker](https://threadmaker.dev/vs/clearfeed): A ClearFeed alternative for Jira and Slack: a focused two-way comment bridge — free for 10 users, Forge-native, not a whole Slack helpdesk to adopt. ## Use cases - [Jira–Slack bug triage for engineering — Threadmaker](https://threadmaker.dev/use-cases/engineering-triage): Triage Jira bugs in Slack: every ticket gets one thread, comments sync both ways, and edits, screenshots and live status stay on the issue automatically. - [Escalate support tickets from Slack to Jira — Threadmaker](https://threadmaker.dev/use-cases/support-escalation): Escalate support from Slack to Jira: forward the message onto the ticket, sync replies both ways, and build the diagnostic trail without retyping context. - [Incident response in Slack & Jira — Threadmaker](https://threadmaker.dev/use-cases/incident-response): Run incidents in Slack with a live Jira anchor: status, assignee and priority re-render in the thread, and the thread becomes your postmortem. ## Support & legal - [Threadmaker Support — Jira & Slack Sync Help & Contact](https://threadmaker.dev/support): Get help with Threadmaker's Jira–Slack sync: email support, business hours, and billing. Best-effort, European business hours, Mon–Fri. - [Threadmaker — Security & Vulnerability Disclosure](https://threadmaker.dev/security): How to report a security vulnerability in Threadmaker: contact, scope, our good-faith safe-harbour commitment, and what to expect. - [Threadmaker — Privacy Policy](https://threadmaker.dev/privacy): How Threadmaker processes and protects your Jira and Slack data: what we store, retention, sub-processors, and your GDPR rights. - [Threadmaker — Terms of Service](https://threadmaker.dev/terms): The terms governing your use of Threadmaker, the two-way Jira–Slack comment-sync app: subscriptions, acceptable use, liability, and termination. - [Threadmaker — Data Processing Addendum](https://threadmaker.dev/dpa): Threadmaker Data Processing Addendum: GDPR Article 28 roles, sub-processors, security measures, and international-transfer safeguards for your data. - [Threadmaker — Sub-processors](https://threadmaker.dev/privacy/subprocessors): The sub-processors Threadmaker relies on to sync comments between Jira and Slack, and the data each one processes on our behalf.