ThreadFlow: Smart Slack Conversations

Overview

What it does

• Two-way comment sync: Replies in the linked Slack thread and comments on the Jira issue stay synchronized in real time.

• Issue updates reflected in Slack: When a Jira issue is updated, ThreadFlow automatically updates the original Slack message in the channel to keep everyone informed.

• Single source of truth: The Jira issue remains the canonical place to review the full discussion, files, and decisions.

• Less context switching: Engineers, support agents, and managers can follow updates and participate from whichever tool they prefer.

Typical workflow

1. Bind a Jira project to a Slack channel in ThreadFlow settings.

2. When a Jira issue is created, ThreadFlow posts a message to the configured Slack channel.

3. Replies in the Slack thread under that message are synced to the Jira issue comments (and kept aligned going forward).

Who it’s for

• Agile & DevOps teams who track work in Jira but live in Slack for day-to-day communication.

• Stakeholders and Product Owners who need visibility into issue progress without jumping between multiple tools.

Initial setup

Prerequisites

• Jira Administrator access (or Project Administrator rights where ThreadFlow will be enabled).

• Slack Workspace Admin/Owner access (required to create and configure a custom Slack app).

Step 1: Install the app in Jira

1. Log in to your Jira Cloud instance as an administrator.

2. Navigate to Apps → Find new apps (or Manage apps).

3. Search for ThreadFlow and click Get app / Install.

Step 2: Create and configure your private Slack App

ThreadFlow uses a private bot approach. You don't connect to a multi-tenant shared bot—instead, you deploy your own app, retaining 100% control over tokens and permissions.

2.1 Create the Slack app from the Manifest

1. In Jira, navigate to Jira Settings (⚙️) → Apps → ThreadFlow Global Settings.

2. Under the Create a Slack Bot section, copy the automatically generated Slack App Manifest (JSON).

3. Open the Slack API Dashboard (Your Apps) in a new tab and click Create New App.

4. Choose From an app manifest, select your target Slack workspace, paste the JSON payload, and click Next then Create.

5. Note: Ensure the YOUR_WEBHOOK_URL placeholder inside the manifest is replaced with the actual Slack Event Request URL provided in your ThreadFlow Global Settings.

2.2 Link the Slack Bot Token to Jira

1. In your Slack App dashboard, navigate to OAuth & Permissions (under the Features menu).

2. Click Install to Workspace and authorize the app.

3. Copy the generated Bot User OAuth Token (it always starts with xoxb-).

4. Go back to Jira → ThreadFlow Global Settings, paste the token into the Slack Bot Token field, and click Save.

2.3 Invite the Bot to Slack Channels

⚠️ Important: The bot cannot read or sync threads unless it is present in the channel.

Go to your Slack workspace, open the target channel(s) (both public or private), and invite your bot by typing:
/invite @YourBotName

Step 3: Bind a Jira Project to a Slack Channel

1. Navigate to your specific Jira project and open Project settings.

2. Find the ThreadFlow configuration menu item on the left sidebar.

3. Select the Slack channel from the dropdown list that should be associated with this project.

4. Save your changes.

Step 4: Verify Setup (Smoke Test)

1. Create a new test issue in the configured Jira project.

2. Confirm that a new message representing this issue appears in the selected Slack channel.

3. Reply in the Slack thread under that message; confirm the reply appears as a comment inside the Jira issue.

4. Add a comment directly in Jira; confirm it streams back into the Slack thread.

Advanced Technical Features

User Mentions Mapping

ThreadFlow maps users automatically between platforms. When a user is tagged in Slack or Jira, the app checks if they share the same email address. If a match is found, the raw system ID is converted into a native @mention in both systems, ensuring proper notifications are triggered.

Advanced JQL Searching & Dashboards

ThreadFlow utilizes native Jira Issue Properties to handle data linking without database overhead. This architectural approach allows Jira administrators to query Slack-related data directly via JQL.

You can search for issues associated with specific Slack channels using the following syntax:

Code-Snippet

issue.property[threadflow:link:data].channel = "YOUR_CHANNEL_ID"

This allows you to build custom queues, filter developer dashboards, or trigger native Jira Automation based on active Slack communication.

Jira Service Management (JSM) Projects

ThreadFlow handles Service Desk queues smartly to protect internal and external privacy:

• Jira ➡️ Slack: All comments (both Public and Internal notes) made by agents or system automation in Jira are synced to the Slack thread.

• Slack ➡️ Jira: To prevent internal team chatter from accidentally exposing secrets to customers, all replies coming from Slack into a JSM project are automatically created as Internal notes.

Roadmap (Upcoming Features)

We are actively developing ThreadFlow based on infrastructure flexibility and user requests. Here is what is on our radar:

• Slack Emoji Actions: Change Jira issue statuses or assign tickets directly from Slack simply by reacting to messages with specific emojis (e.g., 👀 for In Progress, ✅ for Done).

• Granular Sync Filters: Choose exactly which issue types or priority levels trigger Slack messages using JQL conditions.

• Custom Message Templates: Define your own layout for Slack notifications to control what fields (e.g., Component, Fix Version, Custom Fields) appear in the chat preview.

Support & Feedback

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

• Support Portal: Submit a ticket via our Jira Service Management Portal

• Email Support: Contact us at tim@maierle.xyz

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.

  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".