ThreadFlow

🧵

ThreadFlow is a user-facing integration that keeps Jira and Slack aligned by syncing Jira issue comments with replies in a linked Slack thread—so the discussion stays consistent in both tools.

Available only for Jira Cloud

Overview

What it does

  • Two-way comment sync: replies in the linked Slack thread and comments on the Jira issue stay in sync.
  • Issue updates reflected in Slack: when the Jira issue is updated, ThreadFlow updates the original Slack message in the channel.
  • Single source of truth: the Jira issue remains the canonical place to review the full discussion and decisions.
  • Less context switching: stakeholders can follow updates from either tool.

Typical workflow

  1. Bind a Jira project to a Slack channel in ThreadFlow settings.
  1. When a Jira issue is created, ThreadFlow posts a message to the configured Slack channel.
  1. Replies in the Slack thread under that message are synced to the Jira issue comments (and kept aligned going forward).

Who it’s for

  • Teams using Jira to track work and Slack to collaborate day-to-day.
  • Stakeholders who want visibility without jumping between tools.

Initial setup

Prerequisites

  • Jira admin access (at least at the project level where ThreadFlow will be enabled).
  • Slack workspace admin/owner access (to create and configure a Slack app).
  • ThreadFlow installed in Jira (Marketplace or internal distribution).

1) Install the app in Jira

  1. Open Jira → Apps / Manage apps.
  1. Install ThreadFlow.
  1. Confirm the app is available in the target project.

2) Create and configure the Slack app

2.1 Create a Slack app

  1. Go to the Slack API dashboard (Your Apps) and create a new app from scratch.
  1. Give it a name (e.g., ThreadFlow) and select your workspace.

2.2 Create a Bot User OAuth Token

  1. Navigate to OAuth & Permissions in the Slack sidebar.
  1. Generate the Bot User OAuth Token and copy it.
  1. Paste this token into the plugin’s global settings page at Jira Settings (⚙️) > Apps > ThreadFlow Global Settings.

2.3 Configure Bot Token Scopes

In OAuth & Permissions → Bot Token Scopes, add:

  • channels:history
  • channels:read
  • chat:write
  • chat:write.customize
  • groups:history
  • groups:read
  • users:read

2.4 Enable Event Subscriptions

Open Event Subscriptions and toggle the switch to enable events.
In the Request URL field, paste the URL copied from Jira Settings (⚙️) > Apps > ThreadFlow Global Settings (located in the left sidebar).

Under Subscribe to bot events, add:

  • message.channels
  • message.groups

2.5 Private channels note

To use ThreadFlow in private channels, you must explicitly invite/add the Slack app to each private channel where it should read and post messages.

3) Bind a Jira project to a Slack channel

  1. Open Jira project → Project settings.
  1. Find ThreadFlow configuration.
  1. Select the Slack channel that should be associated with this project.
  1. Save changes.

4) Verify (smoke test)

  1. Create a new Jira issue in the configured project and confirm a message appears in the configured Slack channel.
  1. Reply in the Slack thread under that message and confirm it appears on the Jira issue as a comment.
  1. Add a comment in Jira and confirm it appears in Slack (in the linked thread).

Roadmap (Upcoming Features)

We are actively working on improving ThreadFlow. Here is what is coming next:

  • Automated OAuth 2.0 Setup: Eliminating the need to manually create a Slack App. You will be able to connect your workspace with a single click via an "Add to Slack" button.
  • Slack Emoji Actions: Change Jira issue statuses directly from Slack by reacting to messages with specific emojis (e.g., đź‘€ for In Progress, âś… for Done).
  • And much more to come! We are constantly working on new features and improvements. Stay tuned for future updates!

Support & Feedback

If you encounter any issues, have feature requests, or need assistance with the setup, please reach out to us:

Atlassian Marketplace (EULA & Privacy)

  • End User License Agreement (EULA)

    ThreadFlow is distributed under the Bonterms Standard End User Agreement (Version 1.0), subject to the following Provider-Specific Terms:

    Provider Entity: Tim Maierle
    Standard Agreement: Bonterms Standard End User Agreement Version 1.0
    Governing Law: The laws of the Federal Republic of Germany.
    Courts: The competent courts located in DĂĽsseldorf, Germany.
    Support Policy: Support is provided via our Jira Service Management Portal.

    By installing or using ThreadFlow, you agree to the Standard Agreement as modified by these Provider-Specific Terms

  • Privacy Policy

    Effective Date: May 28, 2026

    This Privacy Policy explains how Tim Maierle ("we", "our", or "us") collects, processes, stores, and protects data when you install and use the ThreadFlow integration ("the App") for Jira and Slack.

1. Data Controller
The data controller responsible for processing your data under the General Data Protection Regulation (GDPR) is:
Name: Tim Maierle
Location: DĂĽsseldorf, Germany
Contact Email: tim@maierle.xyz

2. Data We Process
To provide two-way synchronization between Jira and Slack, ThreadFlow processes only the minimum necessary data, which includes:
Jira Data: Issue identifiers (keys, IDs), issue summaries, descriptions, and comments.
Slack Data: Channel identifiers, message text, user names/identifiers, timestamps, and thread metadata.
Technical Logs: Temporary system logs containing API request metadata to ensure service stability and debugging.

3. Purpose of Processing
We process this data solely to perform the core functionality of the App:
* Syncing comments from Jira issues to designated Slack threads.
* Syncing replies from Slack threads back to Jira issues as comments.
* Updating Slack messages when the status or details of a Jira issue change.

4. Legal Basis for Processing (GDPR)
We process personal data based on **Article 6(1)(b) of the GDPR** (processing is necessary for the performance of a contract / providing the service you requested by installing the App).

5. Data Retention and Storage
No Permanent Storage of Message Content: ThreadFlow acts as a conduit. We do not permanently store the text of your Jira comments or Slack messages on our servers. Content is processed in real-time to facilitate transmission between Atlassian and Slack systems.
Configuration Data: We securely store infrastructure configuration data (such as encrypted Slack Bot OAuth tokens and Jira project mappings) using the secure **Atlassian Forge Storage API**. This data resides entirely within the Atlassian Cloud infrastructure.
Logs: Technical debugging logs are automatically deleted after 14 days.

6. Data Transfers to Third Parties
Data is shared exclusively with **Atlassian** and **Slack** via their official, secure APIs to fulfill the integration's purpose. We do not sell, rent, or share your data with any other third parties.

7. Your Rights (GDPR)
As a user located in the European Economic Area (EEA), you have the following rights under the GDPR:
* Right of access, rectification, or erasure of your data.
* Right to restrict or object to processing.
* Right to data portability.

To exercise any of these rights, or if you have questions regarding your data, please open a ticket on our Support Portal or contact us via email at tim@maierle.xyz.

8. Changes to This Policy
We may update this Privacy Policy from time to time. Any changes will be posted directly on this documentation page with an updated "Effective Date".