Hi Team, I’m trying to implement a clean Jira–Slack integration and would like guidance on whether this is supported natively or if there’s a recommended alternative approach. What I want to achieve One Jira issue should map to exactly one Slack thread. Expected behaviour: * When a Jira issue is created, post one Slack message in a channel * All future comments on that Jira issue should be added as replies to the same Slack thread * Avoid posting a new Slack message for every comment * Keep all discussion grouped under one Slack thread per Jira issue What I tried (current setup) Rule 1 – On issue creation * Trigger: Work item created * Condition: project = SANDBOX * Action: Send Slack message to #jira-sandbox * Result: * Slack message is posted successfully * Slack thread timestamp is returned * Follow-up action: * Store the Slack thread_ts in a Jira custom field (Slack Thread Timestamp) This part works correctly. Rule 2 – On issue comment * Trigger: Work item commented * Condition: * project = SANDBOX * Slack Thread Timestamp is not empty * Action: * Send Slack message * Use the stored Slack Thread Timestamp as the thread context Expected: Comment appears as a reply in the original Slack thread. Issues I’m facing * Jira automation does trigger on comments * Audit log frequently shows “NO ACTIONS PERFORMED” * Even when actions run, Slack messages: * Appear as new standalone messages * Or are silently skipped * Tried both: * “Send Slack message” action * “Send web request” using https://slack.com/api/chat.postMessage * Verified: * Slack OAuth scopes (chat:write, chat:write.public) * Custom field value exists and is populated * Smart values resolve correctly Despite this, threading is not reliable or does not work. What I believe is happening It looks like Jira Automation is stateless, and Slack threading requires stateful correlation (thread_ts) across multiple events. Because of this: * Stored thread timestamps are not consistently reused * Jira Automation cannot reliably maintain Slack thread context My questions to the community * Is native Jira Automation + Slack capable of reliable threaded replies? * If not, is this a known limitation of Jira Cloud Automation? * Are there recommended alternatives that Atlassian supports or suggests? * Atlassian Forge? * Jira webhooks + external service? * Slack app + Events API? * Has anyone successfully implemented one Jira issue → one Slack thread in production? Goal We want a low-noise, scalable, and maintainable Jira–Slack integration that works for a full engineering team without flooding Slack channels. Any guidance, confirmation, or best-practice recommendations would be greatly appreciated. Thanks in advance 🙏

Thanks, Emily! Happy to share a bit more detail. Under the hood the architecture is still intentionally simple: * Jira → Slack uses a Forge trigger that fires on issue events and posts/updates the Slack message. * Slack → Jira comes in through a Forge webtrigger that receives Slack Events API callbacks. * Both sides push work into a small queue so the sync stays stable even in busy channels. * The mapping is just the stored thread_ts on the Jira issue, so correlation is deterministic. There’s also a small configuration page in Jira where you bind a project to a Slack channel and drop in the bot token — that’s basically the whole setup. Honestly, the easiest way to understand how it behaves is to install it in a test project. Setup takes about a minute, and the sync pattern becomes obvious right away. If you hit a specific scenario or edge case, I can clarify how that part works.

If anyone is still exploring ways to achieve a reliable one‑issue ↔ one‑Slack‑thread sync, there’s also a lightweight Forge‑based approach that avoids the usual Automation limitations. I built a small app called ThreadFlow, which handles this pattern natively: * creates a Slack thread when the Jira issue is created * syncs all Jira comments into that same thread * syncs all Slack thread replies back into Jira * keeps the mapping stable by storing thread_ts in issue properties (so it doesn’t depend on Automation state) It runs fully inside Atlassian Forge, so there’s no external server or webhook service to maintain. If anyone is curious about how the implementation works under the hood (Slack events, thread correlation, rate‑limit handling, or Forge architecture), feel free to ask — happy to share the technical details.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira → Slack Threading Automation (One Jira Issue = One Slack Thread)

manideep tumati

Hi Team,

I’m trying to implement a clean Jira–Slack integration and would like guidance on whether this is supported natively or if there’s a recommended alternative approach.

What I want to achieve

One Jira issue should map to exactly one Slack thread.

Expected behaviour:

When a Jira issue is created, post one Slack message in a channel
All future comments on that Jira issue should be added as replies to the same Slack thread
Avoid posting a new Slack message for every comment
Keep all discussion grouped under one Slack thread per Jira issue

What I tried (current setup)

Rule 1 – On issue creation

Trigger: Work item created
Condition: project = SANDBOX
Action: Send Slack message to #jira-sandbox
Result:
- Slack message is posted successfully
- Slack thread timestamp is returned
Follow-up action:
- Store the Slack thread_ts in a Jira custom field
  (Slack Thread Timestamp)

This part works correctly.

Rule 2 – On issue comment

Trigger: Work item commented
Condition:
- project = SANDBOX
- Slack Thread Timestamp is not empty
Action:
- Send Slack message
- Use the stored Slack Thread Timestamp as the thread context

Expected:
Comment appears as a reply in the original Slack thread.

Issues I’m facing

Jira automation does trigger on comments
Audit log frequently shows “NO ACTIONS PERFORMED”
Even when actions run, Slack messages:
- Appear as new standalone messages
- Or are silently skipped
Tried both:
- “Send Slack message” action
- “Send web request” using <a href="https://slack.com/api/chat.postMessage" rel="noopener nofollow noreferrer" target="_blank">https://slack.com/api/chat.postMessage</a>
Verified:
- Slack OAuth scopes (chat:write, chat:write.public)
- Custom field value exists and is populated
- Smart values resolve correctly

Despite this, threading is not reliable or does not work.

What I believe is happening

It looks like Jira Automation is stateless, and Slack threading requires stateful correlation (thread_ts) across multiple events.

Because of this:

Stored thread timestamps are not consistently reused
Jira Automation cannot reliably maintain Slack thread context

My questions to the community

Is native Jira Automation + Slack capable of reliable threaded replies?
If not, is this a known limitation of Jira Cloud Automation?
Are there recommended alternatives that Atlassian supports or suggests?
- Atlassian Forge?
- Jira webhooks + external service?
- Slack app + Events API?
Has anyone successfully implemented one Jira issue → one Slack thread in production?

Goal

We want a low-noise, scalable, and maintainable Jira–Slack integration that works for a full engineering team without flooding Slack channels.

Any guidance, confirmation, or best-practice recommendations would be greatly appreciated.

Thanks in advance 🙏

Accepted answers

All comments

Evgenii

Hi, @manideep tumati

What you're asking is possible. I implemented exactly the same logic on our instance, and it's working — when an issue is updated, a message is sent directly to the corresponding Slack thread.

The only difference is that I store the complete Slack thread URL in a custom field.

The logic works like this: when something happens with the issue, a rule is triggered, parses the field value to extract the channel, threadtime, and threadms, and uses these to build the request body for the API call.

Here is example, how I made it

Evgenii

regexps used

channel:
{{issue.Slack Thread.match("\/archives\/(.*)\/p")}}

threadtime:
{{issue.Slack Thread.match("archives\/.*\/p(.{10})")}}

threadms:
{{issue.Slack Thread.match("archives\/.*\/p.{10}(.{6})")}}

Sid Pathirana

Hi - if you're using Slack then you should have access to the free Jira Cloud app that is available from the Slack Marketplace. This app was enhanced a few months ago to provide a threaded comments feature that allows the entire conversation thread to be synced across both Jira and Slack.

Once the Jira Cloud app has been installed to your Slack workspace and connected to your Jira, then when you paste a Jira ticket link in to a Slack thread, you'll get an option to Sync thread in Slack. This will connect any following discussion in that Slack thread with the Jira ticket.

any further replies in the Slack thread will be added to the Jira ticket.
any comments in the Jira ticket will be added to the Slack thread.

Els Bassant

Hi @manideep tumati ,

Would you mind sharing how you capture the thread_ts response?

We currently have a few processes that send a Slack message, and being able to post any follow up actions as threaded comments to the original post would add a lot of value.

Matas Gasparavičius

Hey, Sid,

I don't see an option to sync the Slack thread.

Dave Buitenhek

Matas - try this to create a new connection ... note that you'll need to connect Jira Cloud to Slack if you haven't already.

Go to a particular Slack message (the start of a new thread is ideal), then click ... (More actions) > Connect to apps > Create Issue from Jira Cloud.

Complete the form to create a Jira Work Item in the Space you want to test with. You'll see a message from the Jira App that your Work Item was created -and- the following:

This Slack conversation thread is now synced to the Jira work item. Replies in synced threads will automatically update across both Slack and Jira.

Once that connection is in place, comments in Slack will reach the Jira Work Item, and comments in the Jira Work Item will reach Slack ... until the Jira Work Item is closed, then the sync stops (a message displays stating this).

Otherwise, you can choose a Slack thread and then just paste the URL to a Jira Work Item ... a small preview box appears with the buttons (Open in Jira and Sync Thread). Click the Sync Thread button to create a new sync for the Slack thread to the Jira Work Item. You can also create multiple!

Emily Abramson

@manideep tumati

I'm curious if you ever found a solve to this, as I'm running into the same issues as you. I am currently manually connecting Jira notifications in slack with the comment threads in the Jira ticket through the updated Jira Cloud / Slack connection, but I imagine there has to be a way to automate this process somewhat easily (without setting up an API call).

Emily Abramson

@Dave Buitenhek

Thank you for sharing this! Do you know if there's a way to automate the Sync Thread option, so that all future Slack notifications in a certain channel automatically sync?

Tim Maierle

If anyone is still exploring ways to achieve a reliable one‑issue ↔ one‑Slack‑thread sync, there’s also a lightweight Forge‑based approach that avoids the usual Automation limitations.

I built a small app called ThreadFlow, which handles this pattern natively:

creates a Slack thread when the Jira issue is created
syncs all Jira comments into that same thread
syncs all Slack thread replies back into Jira
keeps the mapping stable by storing thread_ts in issue properties (so it doesn’t depend on Automation state)

It runs fully inside Atlassian Forge, so there’s no external server or webhook service to maintain.

If anyone is curious about how the implementation works under the hood (Slack events, thread correlation, rate‑limit handling, or Forge architecture), feel free to ask — happy to share the technical details.

Emily Abramson

I would definitely be interested in the technical details! i've been using Appfire's Slack Integration+ but it's not a perfect solve for our team.

Tim Maierle

Thanks, Emily! Happy to share a bit more detail.

Under the hood the architecture is still intentionally simple:

Jira → Slack uses a Forge trigger that fires on issue events and posts/updates the Slack message.
Slack → Jira comes in through a Forge webtrigger that receives Slack Events API callbacks.
Both sides push work into a small queue so the sync stays stable even in busy channels.
The mapping is just the stored thread_ts on the Jira issue, so correlation is deterministic.

There’s also a small configuration page in Jira where you bind a project to a Slack channel and drop in the bot token — that’s basically the whole setup.

Honestly, the easiest way to understand how it behaves is to install it in a test project. Setup takes about a minute, and the sync pattern becomes obvious right away.

If you hit a specific scenario or edge case, I can clarify how that part works.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management