Allow Slack thread sync for Jira issues created via Slack Webhook / Workflow Builder "Create Issue"

[Vittoria Zago]

When a Jira issue is created through the official Atlassian "Create Issue" action inside Slack's Workflow Builder (triggered by an incoming webhook), the resulting issue has no Slack thread association. The "Sync Thread" feature — which bidirectionally links Slack thread replies to Jira comments — is unavailable for these issues.

Current behavior

• Issues created manually via the "Raise a Request" shortcut in Slack correctly establish a native thread link and enable bidirectional comment sync.
• Issues created via the Workflow Builder's native Jira "Create Issue" step, or via the Jira REST API, do not establish this link. The Sync Thread option does not appear on the resulting Slack message.

Root cause (as understood)

The sync engine appears to register the thread association at the moment the form is submitted through the official Jira Slack app UI. There is no public API parameter or post-creation endpoint that allows a thread_ts to be associated with an existing Jira issue after creation — even when using Atlassian's own first-party Workflow Builder action.

Requested change

One or more of the following:

1. Expose an API endpoint (e.g. POST /rest/api/3/issue/{issueKey}/slack-thread) that accepts a Slack channel_id and thread_ts and registers the sync association — equivalent to what the UI does internally.
2. Have the Workflow Builder "Create Issue" step automatically post a linked message to the originating channel and register the thread sync, mirroring the behavior of the manual shortcut.
3. Alternatively, document the internal mechanism used by the Jira Slack app so that Marketplace app developers or automation platforms can replicate it.
   
   

   Business impact

   Teams using Slack Workflow Builder to automate ticket intake (e.g. routing form submissions, webhook-triggered bug reports, or on-call alert escalations into Jira) currently cannot use thread sync at all. This forces a choice between automation or sync — not both. Bridging this gap would make the existing native integration usable for modern async workflows without requiring third-party tools.